The scope of the TUBES ontology is to explicitly define the topology of interconnected building service system and their relationship to the spatial structure. It has a strong alignment to other ontologies within the W3C community and aims to provide the means to link information at data level within the AEC industry.
Identifier Standards
- Pattern for Local Unique Identifiers
- Missing LUI pattern
- Example Local Unique Identifier
- AutomationSystem Resolve
- Example CURIE
- tib.tso:AutomationSystem
Contacts
- Contact
- Missing Contact
Ontology
A summary of the relations in the Semantic Farm schema can be found here.
- In Collection (1)
- NFDI4Ing Collection
Mappings to External Registries
Mappings from records in Semantic Farm to external registries comprises the metaregistry. This resource has 1 mapping to an external registry.
| Registry Name | Registry Metaprefix | External Prefix | Curate |
|---|---|---|---|
TIB-TS
|
tib |
tso
|
Providers
A provider turns a local unique identifiers from a resource into a URI. Many providers are also resolvable as URLs (i.e., they can be used in a web browser).
The local unique identifier AutomationSystem is used to demonstrate the providers
available for TUBES system ontology. Some providers may use a different example, which is displayed in the table below.
A guide for curating additional providers can be found
here.
| Provider Name | Provider Code | URI |
|---|---|---|
| TUBES system ontology | tib.tso |
https://w3id.org/tso#AutomationSystem |
| Bioregistry | bioregistry |
https://bioregistry.io/tib.tso:AutomationSystem |