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

108

results

How to

a4bdg - aerOS Building ontology
https://w3id.org/aerOS/building

Ontology that defines the conceptual model for the Pilot 5 - Smart Building use case @en
dco - domOS Common Ontology
https://w3id.org/dco

domOS Common Ontology (dCO) represents a common information model to share a unified understanding for humans and machines and to ensure semantic interoperability in a heterogeneous IoT infrastructure. This ontology allows the decoupling of the infrastructure from the software services and applications. @en
dtw - WoTDT: The WoT Digital Twin Ontology.
https://w3id.org/def/dtw#

Digital Twin ontology used to define Digital Twins and Semantic Digital Twins and aggregations by dimensions using Web of Things. @en
och - OWL Change Ontology
https://w3id.org/def/och#

An ontology for describing changes between OWL ontology versions @en
dsv - Data Specification Vocabulary
https://w3id.org/dsv#

Data Specification Vocabulary (DSV) is a vocabulary for describing semantic data specifications, namely vocabularies and application profiles. @en
hpont - The Heat Pump Ontology (HPOnt).
https://w3id.org/hpont

The Heat Pump Ontology (HPOnt) aims to formalize and represent all the relevant information of Heat Pumps. The HPOnt has been developed as part of the REACT project which has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement no. 824395. @en
eppl - The EP-Plan ontology
https://w3id.org/ep-plan

PROV extension for linking Plans and parts of plans to their respective executions. @en
ifc - IFC4_ADD1
https://w3id.org/ifc/IFC4_ADD1

OWL ontology for the IFC conceptual data schema and exchange file format for Building Information Model (BIM) data @en
opm - OPM: Ontology for Property Management
https://w3id.org/opm

The Ontology for Property Management (OPM) extends the concepts introduced in the Smart Energy Aware Systems (SEAS) Evaluations ontology. @en
opti - Offshore Wind Power Platform Ontology for OPTiMAR
https://w3id.org/optimar

This ontology describes the components, failures, sensors, and events related to offshore wind platforms. @en
ontouml - OntoUML Metamodel Vocabulary
https://w3id.org/ontouml

A reference implementation of the OntoUML metamodel in OWL. @en
ofo - Occupant Feedback Ontology
https://w3id.org/ofo#

The aim of the Occupant Feedback Ontology is to semantically describe passive and active occupant feedback and to enable integration of this feedback with linked building data. @en
seast - The SEAS Time Ontology.
https://w3id.org/seas/TimeOntology

This ontology defines: - a set of subclasses of `seas:Evaluation` to better interpret evaluations of quantifiable properties. - a set of sub properties of `seas:hasProperty` to qualify time-related properties. @en
seasd - The SEAS Device ontology
https://w3id.org/seas/DeviceOntology

The SEAS Device ontology defines `seas:Device` as physical system that are designed to execute one or more procedures that involve the physical world. @en
seasfo - The SEAS Forecasting ontology
https://w3id.org/seas/ForecastingOntology

The SEAS Forecasting ontology extends the [Procedure Execution ontology (PEP)](https://w3id.org/pep/) @en

1...4 567 8

Selected vocabularies

Patterns?:	type name both
Flatten?:	yes no

Type

vocabulary (108)
property/class >
agent >

Language

English (73)
en (6)
Spanish (4)
French (3)
Italian (3)
Czech (2)
German (2)
Chinese (1)
Dutch (1)
Hungarian (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)