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

164

results

How to

tac - TripleAccessControl Ontology
http://ns.bergnet.org/tac/0.1/triple-access-control

The TripleAccessControl Ontology is an extension to WebAccessControl Ontology to describe access control rules for RDF triples. @en
dcndl - NDL Metadata Terms
http://ndl.go.jp/dcndl/terms/

RDF Schema declaration for Japan NDL Metadata Terms @en
irao - Informatics Research Artifacts Ontology
http://ontology.ethereal.cz/irao

Informatics Research Artifacts Ontology, described using W3C RDF Schema and the Web Ontology Language OWL. @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
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
limoo - License Model Ontology
http://purl.org/LiMo/0.1#

A vocabulary to describe licenses @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
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
api - Linked Data API Vocabulary
http://purl.org/linked-data/api/vocab#

Configuration vocabulary for the Linked Data API @en
dvia - The visualization vocabulary for LOD applications
http://purl.org/ontology/dvia

dvia is an RDF vocabulary designed to facilitate interoperability between visualization applications published on the Web. @en
voidext - Extended Vocabulary of Interlinked Datasets (VoIDext)
http://purl.org/query/voidext

The Extension of the Vocabulary of Interlinked Datasets (VoID) RDF Schema that includes the concept of virtual links. This extension enhances interoperability among heterogeneous and distributed RDF data sets by bridging them through explicitly defined virtual links. @en
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
rss - Vocabulary for Rich Site Summary (RSS) 1.0
http://purl.org/rss/1.0

RDF Schema declaration for Rich Site Summary (RSS) 1.0 @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
summa - SUMMA Vocabulary
http://purl.org/voc/summa/

The SUMMA Vocabulary enables to request and represent summarized RDf resources. It should be used in context to the SUMMA API definition. @en

1 234 5...11

Selected vocabularies

Patterns?:	type name both
Flatten?:	yes no

Type

vocabulary (164)
property/class >
agent >

Language

English (125)
French (6)
German (3)
Italian (2)
Japanese (2)
Czech (1)
Korean (1)
Spanish (1)

: 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)