Linked Open Vocabularies

Vocabs
Terms
Agents
SPARQL/Dump
Patterns

How to

Select the ontologies from which you want to extract patterns.

Select patterns options:

Name, Type or both:

Name: Ontology elements in the patterns represent specific classes and properties names.

For example:

# INPUT
s4bldg:BuildingSpace rdfs:subClassOf [
  rdf:type owl:Restriction ;
  owl:onProperty s4bldg:isSpaceOf ;
  owl:allValuesFrom [
    rdf:type owl:Class ;
    owl:unionOf (
      s4bldg:Building
      s4bldg:BuildingSpace
    )
  ]
]

# OUTPUT
Pattern 16
owl:Class
|rdfs:subClassOf
| |owl:Restriction
| | |owl:allValuesFrom
| | | |owl:Class
| | | | |owl:unionOf
| | | | | |rdf:List
| | | | | | |rdf:first
| | | | | | | |owl:Class
| | | | | | |rdf:rest
| | | | | | | |rdf:List
| | | | | | | | |rdf:first
| | | | | | | | | |owl:Class
| | | | | | | | |rdf:rest
| | | | | | | | | |rdf:nil
| | |owl:onProperty

# INPUT
s4bldg:BuildingSpace rdfs:subClassOf [
  rdf:type owl:Restriction ;
  owl:onProperty s4bldg:isSpaceOf ;
  owl:allValuesFrom [
    rdf:type owl:Class ;
    owl:unionOf (
      s4bldg:Building
      s4bldg:BuildingSpace
    )
  ]
]

# OUTPUT
Pattern 16
owl:Class
|rdfs:subClassOf
| |owl:Restriction
| | |owl:allValuesFrom
| | | |owl:Class
| | | | |owl:unionOf
| | |owl:onProperty

Type: Ontology elements in the patterns are generalized according to the OWL elements used.

No specific classes or properties are used, but OWL skeletons like:

owl:Class
  |rdfs:subClassOf
  |  |owl:Restriction
  |  |  |owl:onProperty
  |  |  |  |owl:DatatypeProperty, owl:FunctionalProperty
  |  |  |owl:someValuesFrom
  |  |  |  |rdfs:Datatype

Flatten or not:
1. Flatten: If there are collections of classes or individuals in the pattern, the full collection is not included.
  ¿SERGIO esto aplica a los named? O solo a los que se generalizan como Type?
  
  Otra cosa es que estaría bien indicar algunos ejemplos, pensaba que se incluían 3.
```
owl:Class
  |owl:equivalentClass
  |  |owl:Class
  |  |  |owl:oneOf
```

Output: Tengo que ver el output final y definir esto en detalle

The retrieved .zip file contains the following folders and documents:

“Data” folder. This folder contains the files:
- A
- B
- C
“flatten” folder (if selected): This folder contains the files:
- A
- B
- C
“not_flatten” folder (if selected): This folder contains the files:
- A
- B
- C
HTML folder. This folder contains the files:
- A
- B
- C

198

results

How to

dcndl - NDL Metadata Terms
http://ndl.go.jp/dcndl/terms/

RDF Schema declaration for Japan NDL Metadata Terms @en
psh - Probabilistic SHACL Validation
http://ns.inria.fr/probabilistic-shacl/

An OWL vocabulary to include and exploit probabilistic information in SHACL validation reports @en
lsweb - ELSEWeb Data Ontology
http://ontology.cybershare.utep.edu/ELSEWeb/elseweb-data.owl

The ELSEWeb Data ontology provides simple classes for describing datasets. This project provides foundational support for the ELSEWeb project(http://elseweb.cybershare.utep.edu/). website: http://elseweb.cybershare.utep.edu/ontologies email: nvillanuevarosales@utep.edu @en
munc - Meta-Uncertainty
http://ns.inria.fr/munc/

An OWL vocabulary for describing uncertainty metadata. @en
dm2e - DM2E model
http://onto.dm2e.eu/schemas/dm2e

The DM2E model is a specialisation of the Europeana Data Model (EDM) and can be used for the description of manuscripts in the cultural heritage domain. @en
omnfed - Open-Multinet Upper Federation Ontology
http://open-multinet.info/ontology/omn-federation

This ontology defines concepts related to federation of internet infrastructures. @en
of - Open Fridge vocabulary
http://owlrep.eu01.aws.af.cm/fridge

Ontology for Open Fridge project @en
limoo - License Model Ontology
http://purl.org/LiMo/0.1#

A vocabulary to describe licenses @en
dce - Dublin Core Metadata Element Set
http://purl.org/dc/elements/1.1/

The Dublin Core Metadata Element Set is a vocabulary of fifteen properties for use in resource description. The name "Dublin" is due to its origin at a 1995 invitational workshop in Dublin, Ohio; "core" because its elements are broad and generic, usable for describing a wide range of resources. @en
coo - Car Options Ontology
http://purl.org/coo/ns#

The COO provides a vocabulary for exposing available configuration options for car models. It allows indicating choices that can be made as well as compatibility, dependency, and inclusion information. The ontology imports and extends the GoodRelations ontology for e-commerce @en
dita - DITA RDF ontology
http://purl.org/dita/ns#

The DITA RDF ontology translates the semantics of a subset of the vocabulary described in the DITA 1.2 specification in a format that can be understood in the semantic Web of data. By Colin Maudry, licensed under the terms of the Unlicense (public domain). @en
dcterms - DCMI Metadata Terms
http://purl.org/dc/terms/

an up-to-date specification of all metadata terms maintained by the Dublin Core Metadata Initiative, including properties, vocabulary encoding schemes, syntax encoding schemes, and classes. @en
ru - Representational Units Metadata Ontology
http://purl.org/imbi/ru-meta.owl

Draft for a recommendation for metadata on Representational Units (RU) which appear in ontologies. It is so far harmonized for implementation through owl annotation properties. @en
inno - Ontology for Innovation
http://purl.org/innovation/ns

One key use case for this ontology is to facilitate the matching of needs and innovations. @en
pat - Patch Request Ontology
http://purl.org/hpi/patchr#

The Patch Request Ontology provides a schema to describe desired changes in Linked Data. By wrapping the Graph Update Ontology (guo) patch requests can be formulated to add, modify or delete particular triples (or subgraphs) within a dataset. @en

123 4...14

Selected vocabularies

Patterns?:	type name both
Flatten?:	yes no

Type

vocabulary (198)
property/class >
agent >

Language

English (148)
German (10)
French (7)
Spanish (7)
en (7)
Italian (4)
Czech (2)
Dutch (2)
Japanese (2)
Catalan (1)
show more...

: Linked Open Vocabularies

Documentation

About
API documentation
Contact

Este trabajo ha recibido financiación del proyecto PIONERA (Potenciando la interoperabilidad en espacios de datos mediante inteligencia artificial), un proyecto financiado en el contexto de la convocatoria Productos y Servicios tecnológicos para Espacio de Datos del Ministerio para la Transformación Digital y de la Función Pública en el marco del PRTR financiado por Unión Europea (NextGenerationEU)