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

hr - hRESTS Ontology
http://iserve.kmi.open.ac.uk/ns/hrests

hRESTS is a vocabulary for describing RESTful Web services @en
msm - Minimal Service Model
http://iserve.kmi.open.ac.uk/ns/msm

A simple RDF(S) ontology able to capture (part of) the semantics of both Web services and Web APIs @en
ends - Vocabulary of endpoint status (availability, responseTime)
http://labs.mondeca.com/vocab/endpointStatus

Endpoint Status vocabulary intends to describe endpoint availability @en
isbd - ISBD elements
http://iflastandards.info/ns/isbd/elements/

This is a registration of classes and properties from International Standard Bibliographic Description (ISBD), consolidated edition, published by De Gruyter Saur in July 2011 (ISBN 978-3-11-026379-4). @en
ldvm - Vocabulary for Linked Data Visualization Model
http://linked.opendata.cz/ontology/ldvm/

Vocabulary for Linked Data Visualization Model (LDVM) serves for description and configuration of components and pipelines according to LDVM @en
lsq - The Linked SPARQL Queries Vocabulary (LSQ(V))
http://lsq.aksw.org/vocab

The Linked SPARQL Queries Vocabulary (LSQ(V)), defined using RDF(S) and OWL, provides a machine readable vocabulary to help describe queries in SPARQL logs and their statistics. The vocabulary builds upon the SPIN vocabulary and the Service Description vocabulary. @en
lsc - Linked Science Core Vocabulary
http://linkedscience.org/lsc/ns#

LSC, the Linked Science Core Vocabulary, is a lightweight vocabulary providing terms to enable publishers and researchers to relate things in science to time, space, and themes. @en
mexcore - MEX Core Vocabulary
http://mex.aksw.org/mex-core

MEX is an RDF vocabulary designed to facilitate interoperability between published machine learning experiments results on the Web. The mex-core layer represents the core information gathered from a basic machine learning experiment design. @en
mexalgo - MEX Algorithm Ontology
http://mex.aksw.org/mex-algo

MEX is an RDF vocabulary designed to facilitate interoperability between published machine learning experiments results on the Web. The mex-algo layer represents the algorithm information existing into a basic machine learning experiment. @en
mexperf - MEX Performance Ontology
http://mex.aksw.org/mex-perf

MEX is an RDF vocabulary designed to facilitate interoperability between published machine learning experiments results on the Web. The mex-perf layer is the 3rd level of the MEX for representing the machine learning algorithm's performances. @en
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
sql - SQL Abstract Syntax Trees Vocabulary
http://ns.inria.fr/ast/sql#

The SQL AST Vocabulary allows SQL code abstract syntax trees to be published in RDF. @en
dcndl - NDL Metadata Terms
http://ndl.go.jp/dcndl/terms/

RDF Schema declaration for Japan NDL Metadata Terms @en
s4ac - Social Semantic SPARQL Security For Access Control Ontology
http://ns.inria.fr/s4ac/v2

A lightweight vocabulary to create fine-grained access control policies for Linked Data. @en
ludo-xapi - Experience API (xAPI)
http://ns.inria.fr/ludo/v1/xapi

This is an OWL formalization of the statements defined in the Experience API (xAPI) specification. It is a module of the LUDO ontology. @en

123 4...14

Selected vocabularies

Patterns?:	type name both
Flatten?:	yes no

Type

vocabulary (198)
property/class >
agent >

Language

English (163)
French (9)
German (6)
Portuguese (3)
Italian (2)
Japanese (2)
Spanish (2)
Korean (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)