Skip to content
/ bpo Public

The Building Product Ontology defines concepts to describe (building) products in a schematic way and aims to be a reference ontologies for products (not just) from the Architecture, Engineering and Construction domain (AEC).

Notifications You must be signed in to change notification settings

tudaIIB/bpo

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 

Repository files navigation

The Building Product Ontology (BPO)

The Building Product Ontology defines concepts to describe (building) products in a schematic way. It provides methods to describe assembly structures and component interconnections, and attach properties to any component without restricting their types, as is often the case in template-driven product descriptions. To allow the description of complex properties, it also contains terms for unordered, two-dimensional lists.

HTML documentation

Introduction to BPO

The BPO's scope is on the schematic description of product only, not including geometry or material compositions. Therefore, it can be used to describe theoretical product components without geometric representations as well as those with geometric representations, without restrictions. To exploit all benefits from the Semantic Web, especially during online searches, the BPO is closely aligned to well-known upper-level ontologies, as schema.org and SEAS.

For classification purposes, it uses the buildingSMART Data Dictionary (bSDD) by referencing to the terms' bSDD GUID. If geometric descriptions are desired for components, the authors suggest to use the Ontology for Managing Geometry (OMG) resp. the File Ontology for Geometry formats (FOG) to connect the descriptions to any desired geometry description.

Combining BPO with other ontologies

As an example, the combination of BPO with an (RDF-based) geometry description and a (non-RDF) taxonomy is demonstrated in this section. Before going into detail, it should be understood that the BPO is not complete but aims to serve as a small ontology that can be re-used in various use cases and scenarios. Thus, in accordance with the best practices for publishing Linked Data, instead of large ontologies that are trimmed towards one specific use cases, smaller ontologies should be combined, which is the idea behind the BPO as well. Recommendations for combining the BPO with other ontologies are to create meaningful links between ontologies for other domains, or creating more specific subclasses and subproperties from the generic terms and concepts of BPO.

SPARQL-visualizer demo

An online sparql-visualizer demo is available, containing sample Abox triples and example queries.

Authors and contributors

Authors:

Contributors:

References

Please cite the following paper when using BPO:

  • Wagner, A., & Rüppel, U. (2019). BPO: The Building Product Ontology for Assembled Products. In Proceedings of the 7th Linked Data in Architecture and Construction workshop (LDAC 2019) (Vol. 7, p. 12), CEUR: http://ceur-ws.org/Vol-2389/08paper.pdf.
  • Wagner, A., Möller, L. K., Leifgen, C., & Rüppel, U. (2018). SolConPro: Describing multi-functional building products using semantic web technologies. In J. Karlshøj & R. J. Scherer (Eds.), EWork and eBusiness in architecture, engineering and construction: proceedings of the 12th European Conference on Product and Process Modelling (ECPPM 2018) (pp. 447–455). CRC Press.

About

The Building Product Ontology defines concepts to describe (building) products in a schematic way and aims to be a reference ontologies for products (not just) from the Architecture, Engineering and Construction domain (AEC).

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published