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

203

results

How to

sto - i40 Standards Lanscape Vocabulary
https://w3id.org/i40/sto#

A vocabulary to describe the relation between standards in use on the Industry 4.0, and related concepts @en
ishi - Ishikawa diagram ontology
https://w3id.org/ishikawa-diagram-ontology

The Ishikawa ontology aims to provide a data and view model to manage data encoded in Ishikawa diagrams which are also known as fishbone or cause and effect diagram (CED). Ishikawa diagrams result from (iterative) workshops. Thus, the ontology includes the basic modelling of workshops to create Ishikawa diagrams. @en
mdo-calc - Materials Design Ontology - Calculation Module
https://w3id.org/mdo/calculation/

This is the calculation module of Materials Design Ontology. @en
core - Materials Design Ontology - Core Module
https://w3id.org/mdo/core/

This is the core module in Materials Design Ontology. @en
mdo - Materials Design Ontology - Full
https://w3id.org/mdo/full/

This is the Materials Design Ontology. @en
nen2660 - NEN 2660-2:2022 'Rules for information modelling of the built environment - Part 2: Practical configuration, extension and implementation of NEN 2660-1''
https://w3id.org/nen2660/

Ontology which is a normative part of the Dutch NEN 2660-2 standard @en
mdo-struc - Materials Design Ontology - Structure Module
https://w3id.org/mdo/structure/

This is the structure module in Materials Design Ontology. @en
loin - Level of Information Need (LOIN) Ontology
https://w3id.org/loin

The Level of Information Need (LOIN) Ontology is defined for specifying information requirements for delivery of data in a buildings' life cycle. The LOIN ontology is based on the standard BS EN 17412-1 (2020). Furthermore, it is extended with vocabulary for connecing Information Delivery Specifications (IDS) and Information containers for linked document delivery (ICDD) as per ISO 21597-1 (2020). @en
ontouml - OntoUML Metamodel Vocabulary
https://w3id.org/ontouml

A reference implementation of the OntoUML metamodel in OWL. @en
sdom - The Software Description Ontology for Models
https://w3id.org/okn/o/sdm

The Software Description Ontology for Models (SDM) expands the software description ontology (SD) to add information about scientific software models. Examples of scientific software models are hydrology models, agriculture models or economy models. @en
sdont - The Software Description Ontology
https://w3id.org/okn/o/sd

An ontology for describing software and their links to inputs, outputs and variables. The ontology extends schema.org and codemeta vocabularies @en
okh - Open Know How (OKH) ontology
https://w3id.org/oseg/ont/okh

Used for indexing, searching and comparing Open Source Hardware projects @en
nno - The Neural Network Ontology
https://w3id.org/nno/ontology

This is the Neural Network Ontology. Designed by the AIFB (http://www.aifb.kit.edu/web/Web_Science) @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
seas-eval - The SEAS Evaluation ontology
https://w3id.org/seas/EvaluationOntology

The Evaluation ontology describes evaluation of [`seas:Property`ies](https://w3id.org/seas/Property). There may be: - direct evaluations, or - qualified evaluations. @en

1...9 101112 13 14

Selected vocabularies

Patterns?:	type name both
Flatten?:	yes no

Type

vocabulary (203)
property/class >
agent >

Language

English (163)
German (15)
French (14)
Spanish (13)
Portuguese (10)
Italian (8)
Dutch (7)
Russian (7)
Swedish (6)
Afrikaans (5)
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)