hit2gap-eu-project / bemont

BEMOnt - the ontology at the core of BEMServer

BEMOnt (formerly HIT2GAPOnt)

BEMont (formerly HIT2GAPOnt) is focused on establising a common data model and semantic knolwedge management for buildings, including their interecction with the occupants. Whith this aim, the proposed ontology will take into consideration the following aspects:

• Building infrastructure data models and semantic representation (Building Infrastructure Ontology): As mechanims to represent the different systems and infrastructure involved in BIM and required for the performance of the project tools (building simulation tols, building behaviour tools, visualization tools, etc).

• User Behaviour data models and semantic representation (User Behaviour Ontology): This part of the ontology is aimed at representing building occupants DNA (Drivers, Needs and Actions). This type of modelling will serve to represent the user-building interaction not only in form of activities but also considering comfort parameters and other aspects that motivate users to perform buildign actions.

Therefore and since semantic representation, HIT2GAP project will harmonise all information related to buildings monitoring and control activities (management activities), considering the user as an important aspect to adjust energy according to their preferences.

Getting Started

To run the project, you only need to fork it or download it into your local machine. Then, the ontology could be opened and edited using either semantic modeler IDEs. As IDE, we recomend to use:

• Protege/Protege Web.
• TopBraid Composer Community edition or higher.

Description

• The models contain the ontology files, splitted in two (for OWL or RDF files). The bemont.rules is the inference file associated to the BEMOnt. It has been used and tested on Jena.
• The ontology-docs folder contain the online documentation of the ontology generated with widoco.
• The docs folder contain some additional documentation associated to BEMOnt.

Installing

For running the ontology, we recommend to use the IDEs mentioned in the Getting Started section. Moreover, if you want to publish the ontology or use it for public consumption and inference, we recomend to use a Semantic Repository or Graph data base

Built With

TBD

Contributing

Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

Authors

• Pierre Bourreau - Initial author
• Gulben Calis - Initial author
• Yudith Cardinale - Initial author
• Richard Chbeir - Initial author
• Aitor Corchero - Intial author

See also the list of contributors who participated in this project.

How to cite?

If you wish to cite, or find additional information on the BEMOnt ontology, please use the following:

Chbeir R. et al. (2019) OntoH2G: A Semantic Model to Represent Building Infrastructure and Occupant Interactions. In: Kaparaju P., Howlett R., Littlewood J., Ekanyake C., Vlacic L. (eds) Sustainability in Energy and Buildings 2018. KES-SEB 2018. Smart Innovation, Systems and Technologies, vol 131. Springer, Cham

License

This work is licensed under a MIT License.

bemont's Issues

Create SPARQLs corresponding to the APIs described in D4.1

Prepare Occupant class diagram

Convert current Occupant class diagram Graph into a HTML based diagram using plantuml.

Transform current "Needs" categories to maintain it more general

Maintain only the "Needs" class and the subclasses "OccupantPrefrences", "Privacy", "Thermal", "Acoustic", "IAQ" and "Visual".

Zenodo link my Github Account

Hi Pierre et. al.
I would like to link the Github Repo to Zenodo (there is an integration tool). (see the cat icon here https://zenodo.org/).
Do I have to be a contributor? How can I do that without participation (pull request etc...).
Regards
Luis

Definition of Occupant Behaviour Part

Text description of the Occupant Behaviour sematic module and their corresponding parts.

Transform "HIT2GAP:OccupantAttitude" to "HIT2GAP:OccupantBehaviourModel"

Convert current "HIT2GAP:OccupantAttitude" to "HIT2GAP:OccupantBehaviourModel"

Discussion about Occupant class Diagrams

I have opened this issue to discuss about the comments and improvements over the Occupant Behaviour Model

This task comprise the issues: #12 #1 #3 #22

Generate OWL file based on the elaborated class diagrams

Generate RDF/OWL diagrams based on defined and validated class diagrams.

Ensure D2.7 information coverage with the current version of the semantic model

Ensure that the APIs information and the categorised inforamtion on D2.7 (Annex 13) is covered in the semantic model.

Discussion about the integration of Building elements (ifcOwl and Haystack)

The domains that seems of a particular interest in the IFC are the following:

• the IfcProductExtension which contains physical objects that are relevant in describing the building/site. In particular, we are interested in the spatial structure of a building site through the IfcSpatialStructureElements, and IfcZones classes.
• the IfcBuildingControlsDomain which includes monitoring elements such as sensors, actuators, alarms…, which are instances of the IfcDistributionControlElement class.
• the IfcHvacDomain (for elements that are used to describe heat, ventilation and air-conditioning systems), IfcElectricalDomain (for elements related with electricity production/consumption/storage). All the elements of interest are accessible under the IfcFlowStorageDevice, IfcFlowMovingDevice, IfcFlowController, IfcFlowTerminal, IfcFlowTreatmentDevice and IfcEnergyConversionDevice classes

I guess all the classes listed above should be set as ssn:FeatureOfInterest.
Also, I guess there should be an equivalence relation between IfcSensor and some concept of the SSN ontology (ssn:SensingDevice? ssn:Sensor?).

Additionally, three elements extracted from the Haystack model could be integrated in the HVAC domain:

• airHandlingUnit
• plant
• fanCoilUnit
• chiller
  Nevertheless, we are not sure these elements are not already present in the ifcOwl ontology under different names.

Dead links to Building Infrastructure Ontology and User Behaviour Ontology in README.md

There seems to be dead links to Building Infrastructure Ontology and User Behaviour Ontology in README.md.

We're starting a new project on building contextual data into commercial energy/building analytics and wanted to check out the platform and the ontologies you used.

Generate the minutes of the miting into the WIKI

Generate in the WIKI an entry summarizing main point of the Skype meeting discussion.

Prepare Building Infrastructure class diagram

Prepare class diagram regarding the building infrastructure and the Observation and measurement (converging IFC, SSN and onto-MG).

For that purpose, we need to see previous version

[Typo] Streess

s/Streess/Stress/

###  http://bemserver.org/property#Streess
<http://bemserver.org/property#Streess> rdf:type owl:Class ;
                                        rdfs:subClassOf <http://bemserver.org/property#OccupantStateProperty> ;
                                        rdfs:comment "Stress represents an observation of the  measure of the stress of an occupant of the building in a specific time."@en ;
                                        rdfs:label "Stress"@en .

Meeting with Richard to update the semantic model status

Meeting with Richard to update the status of the model definition

Observation types missing label

I get errors when trying to register measures with the following observation types:

• Power
• Irradiance
• Rainfall

It could be due to a missing label.

There might be other types affected by this.

Refine User and SIMULATION class diagram part

Refine USER and SIMULATION class model considering all defined point of views and the information described in D2.7.

Remember to get all Github user accounts to add into the project.

Remember all involved users to get their Github account to link it with the project.

Develop an IFC Parser - IFC to RDF

Develop a Python parser for the IFCs that are available in the project - as far as we know only NUIG, IFC 2X3_TC1.
The parser will:
-extract only relevant information (for instance, no spatial/geometric information)
-create RDF triples from this information according to the schemas in IFC-OWL: http://ifcowl.openbimstandards.org/IFC2X3_TC1/index.html
-insert the data into a Jena instance.

Definition of Building infrastructure part

Text Description of the Building infrastructure part (in Gitbook)

Discussion about the Building Infrastructure class Diagrams

Open discussion about the Building Infrastructure class Diagrams