This ontology is an extension of the Building Performance Ontology (BOP). It describes detailed database information. The ontology helps to create database alignment modules and enables the description of database schemas, retention policies and data formats.
Namespace: https://alexdonkers.github.io/bopdb#
Suggested prefix: bopdb:
BOPDB extends the Building Performance Ontology, which is documented at https://www.w3id.org/bop#
This is a place holder text for the introduction. The introduction should briefly describe the ontology, its motivation, state of the art and goals.
bopdb | <http://alexdonkers.github.io/bopdb> |
w3id | <https://w3id.org> |
owl | <http://www.w3.org/2002/07/owl> |
rdf | <http://www.w3.org/1999/02/22-rdf-syntax-ns> |
terms | <http://purl.org/dc/terms> |
xml | <http://www.w3.org/XML/1998/namespace> |
xsd | <http://www.w3.org/2001/XMLSchema> |
rdfs | <http://www.w3.org/2000/01/rdf-schema> |
vann | <http://purl.org/vocab/vann> |
This ontology has the following classes and properties.
The BOP Database Ontology is designed based on the latest version of InfluxDB (v2.0) and covers the key concepts of InfluxDB data elements. Due to the stability of InfluxDB developments, the ontology could also be used to describe previous versions of InfluxDB. Concepts in BOPDB match with the InfluxDB concepts of v1.3 and later. Figure 1 shows the structure of the ontology. It also shows how the ontology could extend BOP by including bop:Property and bop:Database in the schema. Field keys are in practice used to describe properties of the measurement and therefore relate to a bop:Property. Tag keys are used to describe additional metadata, such as the location of the measurement or the researcher making the measurement, and could therefore be linked to a wide range of instances. Some date formats have been added as subclasses of bopdb:DateFormat. However, this list is incomplete by definition. It is likely to be extended in the near future. For additions, please contact Alex Donkers.
IRI: http://alexdonkers.github.io/bopdb/Clause
IRI: http://alexdonkers.github.io/bopdb/DateFormat
IRI: http://alexdonkers.github.io/bopdb/DefaultRetentionPolicy
IRI: http://alexdonkers.github.io/bopdb/DurationClause
IRI: http://alexdonkers.github.io/bopdb/FieldKey
IRI: http://alexdonkers.github.io/bopdb/ReplicationClause
IRI: http://alexdonkers.github.io/bopdb/RetentionPolicy
IRI: https://w3id.org/RFC3339
IRI: http://alexdonkers.github.io/bopdb/ShardDurationClause
IRI: http://alexdonkers.github.io/bopdb/TagKey
IRI: https://w3id.org/Unix-us
IRI: https://w3id.org/Unix-ms
IRI: https://w3id.org/Unix-ns
IRI: https://w3id.org/Unix-s
IRI: https://w3id.org/hasClause
IRI: https://w3id.org/hasDateFormat
has characteristics: functional
IRI: https://w3id.org/hasDefaultRetentionPolicy
IRI: https://w3id.org/hasDurationClause
IRI: https://w3id.org/hasFieldKey
IRI: https://w3id.org/hasReplicationClause
IRI: https://w3id.org/hasRetentionPolicy
IRI: https://w3id.org/hasShardDurationClause
IRI: https://w3id.org/hasTagKey
IRI: https://w3id.org/isClauseOf
IRI: https://w3id.org/isDateFormatOf
has characteristics: inverse functional
IRI: https://w3id.org/isDefaultRetentionPolicyOf
IRI: https://w3id.org/isDurationClauseOf
IRI: https://w3id.org/isFieldKeyOf
IRI: https://w3id.org/isReplicationClauseOf
IRI: https://w3id.org/isRetentionPolicyOf
IRI: https://w3id.org/isShardDurationClauseOf
IRI: https://w3id.org/isTagKeyOf
IRI: https://w3id.org/refersToFieldKey
has characteristics: inverse functional
IRI: https://w3id.org/refersToProperty
has characteristics: functional
IRI: https://orcid.org/0000-0002-8809-3277
Add your references here. It is recommended to have them as a list.
The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.