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

924

results

How to

traffic - Road Traffic Management
http://www.sensormeasurement.appspot.com/ont/transport/traffic

An ontology that describes the management of the traffic in a straight road with two lanes, both in the same direction. @en
nao - NEPOMUK Annotation Ontology
http://www.semanticdesktop.org/ontologies/2007/08/15/nao

The NEPOMUK Annotation Ontology is an ontology for annotation, providing vocabulary which is commonly required to annotate resources on the semantic desktop. @en
ncal - NEPOMUK Calendar Ontology
http://www.semanticdesktop.org/ontologies/2007/04/02/ncal

The NEPOMUK Calendaring Ontology intends to provide vocabulary for describing calendaring data (events, tasks, journal entries) which is an important part of the body of information usually stored on a desktop. It is an adaptation of the ICALTZD ontology created by the W3C RDF Calendar Task Force of the Semantic Web Interest Group in the Semantic Web Activity. @en
nco - NEPOMUK Contact Ontology
http://www.semanticdesktop.org/ontologies/2007/03/22/nco

NEPOMUK Contact Ontology describes contact information, common in many places on the desktop. It evolved from the VCARD specification (RFC 2426) and has been inspired by the Vcard Ontology by Renato Ianella. The scope of NCO is much broader though. This document gives an overview of the classes, properties and intended use cases of the NCO ontology. @en
xhv - XHTML Vocabulary
http://www.w3.org/1999/xhtml/vocab

This is a vocabulary collection utilized by XHTML Family modules and document types using XHTML Modularization, including XHTML Role and XHTML + RDFa as defined in rdfa-syntax. @en
nie - NEPOMUK Information Element Core Ontology
http://www.semanticdesktop.org/ontologies/2007/01/19/nie

The Core Ontology of the NEPOMUK suite defines basic elements such as Data Object, Information Element ... @en
nfo - NEPOMUK File Ontology
http://www.semanticdesktop.org/ontologies/2007/03/22/nfo

Part of Nepomuk Information Element Ontology Framework @en
geo - WGS84 Geo Positioning
http://www.w3.org/2003/01/geo/wgs84_pos

A vocabulary for representing latitude, longitude and altitude information in the WGS84 geodetic reference datum. @en
vs - SemWeb Vocab Status ontology
http://www.w3.org/2003/06/sw-vocab-status/ns

An RDF vocabulary for relating SW vocabulary terms to their status. @en
swrl - Semantic Web Rule Language
http://www.w3.org/2003/11/swrl

OWL definition of the RDF Concrete Syntax for the Semantic Web Rule Language @en
exif - Exif data description vocabulary
http://www.w3.org/2003/12/exif/ns

Vocabulary to describe an Exif format picture data. All Exif 2.2 tags are defined as RDF properties, as well as several terms to help this schema. @en
grddl - Gleaning Resource Descriptions from Dialects of Languages Vocabulary
http://www.w3.org/2003/g/data-view

Gleaning Resource Descriptions from Dialects of Languages Vocabulary @en
skos - Simple Knowledge Organization System
http://www.w3.org/2004/02/skos/core

The Simple Knowledge Organization System (SKOS) is a common data model for sharing and linking knowledge organization systems via the Semantic Web. @en
rdfg - Graph
http://www.w3.org/2004/03/trix/rdfg-1/

Properties allowing statement of intensional equivalence between RDF graphs @en
swp - Graph Authority
http://www.w3.org/2004/03/trix/swp-1

This vocabulary allows to attach an authority to a named graph @en

1...40 414243 44...62

Selected vocabularies

Patterns?:	type name both
Flatten?:	yes no

Type

vocabulary (924)
property/class >
agent >

Language

English (699)
French (76)
Spanish (58)
Italian (49)
German (48)
Dutch (23)
Portuguese (22)
Russian (19)
en (17)
Japanese (16)
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)