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

results

How to

reco - RECommendations Ontology
http://purl.org/reco#

The RECO ontology defines the vocabulary for representing preferences-as-constraints and preferences-as-ratings as RDF graphs. This lightweight vocabulary provides domain-independent means to describe user profiles in a coherent and context-aware way. RECO has been designed as an extension of both Friend-Of-A-Friend (FOAF) and Who Am I! (WAI) ontologies. @en
vsearch - vSearch Vocabulary
http://purl.org/vsearch/

The vSearch vocabulary facilitates the querying and retrieval of vocabulary terms from a vocabularies directory. It can be used to map keywords with mapped result terms accompanied with a ranking value. @en
uneskos - UNESKOS Vocabulary
http://purl.org/umu/uneskos

An RDF vocabulary for extending some SKOS and ISO-THES functions in order to improve the linked data consumption of SKOS datasets @en
cdm - Conceptual Depth and Momentum
http://purl.org/twc/ontology/cdm.owl#

An attempt to represent how universal/accepted/popular a URI is @en
conversion - Conversion Ontology
http://purl.org/twc/vocab/conversion/

Ontology used to describe interpretations of tabular literals to produce RDF @en
xkos - XKOS
http://rdf-vocabulary.ddialliance.org/xkos

An extension of SKOS for representaion of nomenclatures @en
isoadr - ISO19160-1:2015 Address ontology
http://reference.data.gov.au/def/ont/iso19160-1-address

This ontology is a version of the ISO TC211, Group for Ontology Management (GOM)'s OWL ontology interpretation of the ISO19160-1:2015 "Addressing -- Part 1: Conceptual model" standard (see https://www.iso.org/standard/61710.html) taken from that ontology's source code, published at https://github.com/ISO-TC211/GOM/tree/master/isotc211_GOM_harmonizedOntology/19160-1/2015. @en
odapps - The vocabulary for (L)OD ideas and applications
http://semweb.mmlab.be/ns/odapps

odapps is an RDF vocabulary defined to facilitate the description of Open-Data-based ideas and applications published on the Web. @en
apps4X - The vocabulary for Co-creation Events based on Open Data
http://semweb.mmlab.be/ns/apps4X

apps4X is an RDF vocabulary defined to facilitate the description of Open-Data-based Co-creation events @en
spin - SPIN Inferencing Vocabulary
http://spinrdf.org/spin

An RDF Schema that can be used to attach constraints and rules to RDFS classes, and to encapsulate reusable SPARQL queries into functions and templates. @en
sp - SPIN SPARQL Syntax
http://spinrdf.org/sp

An RDF Schema to syntactically represent SPARQL queries (including SPARQL UPDATE) as RDF triples. @en
dady - Dataset Dynamics (dady) vocabulary
http://vocab.deri.ie/dady

A vocabulary that allows for coarse-grained descriptions of the data-source dynamics as well as the discovery of change notification mechanism(s). @en
cogs - COGS Vocabulary
http://vocab.deri.ie/cogs

Vocabulary for describing ETL and data transformation activities. @en
gvp - Getty Vocabulary Program ontology
http://vocab.getty.edu/ontology

The GVP Ontology defines classes, properties and values (skos:Concepts) used in GVP LOD. It is complete regarding AAT and TGN (as of version 2.0), and will be extended in time with more elements needed for the other GVP vocabularies (ULAN, CONA). @en
rml-fnml - RML-FNML
http://w3id.org/rml/fnml/

RML-FNML provides data transformations for generating knowledge graphs from (semi-)structured data @en

123 4...6

Selected vocabularies

Patterns?:	type name both
Flatten?:	yes no

Type

vocabulary (86)
property/class >
agent >

Language

English (58)
French (6)
Spanish (6)
German (5)
Italian (5)
en (5)
Japanese (3)
Russian (3)
Czech (2)
Dutch (2)
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)