5 new data models from SAREF4Buildings

The new subject datamodel.S4BLDG is mapping the data models from SAREF for buildings 1.1.2.

Thanks to the contributors Grzegorz Wiszniewski and Jakob Bjørnskov t the project Twin4Build – A holistic Digital Twin platform for decision-making support over the whole building life cycle.

  • AudioVisualAppliance. An audio-visual appliance is a device that displays, captures, transmits, or receives audio or video. Audio-visual appliances may be fixed in place or may be able to be moved from one space to another. They may require an electrical supply supplied either by an electrical circuit or provided by a local battery source. Audio-visual appliances may be connected to data circuits including specialist circuits for audio-visual purposes only.

  • Boiler. A boiler is a closed, pressure-rated vessel in which water or other fluid is heated using an energy source such as natural gas, heating oil, or electricity. The fluid in the vessel is then circulated out of the boiler for use in various processes or heating applications.

  • Burner. A burner is a device that converts fuel into heat through combustion. It includes gas, oil, and wood burners.

  • Chiller. A chiller is a device used to remove heat from a liquid via a vapor-compression or absorption refrigeration cycle to cool a fluid, typically water or a mixture of water and glycol. The chilled fluid is then used to cool and dehumidify air in a building.

  • Coil. A coil is a device used to provide heat transfer between non-mixing media. A common example is a cooling coil, which utilizes a finned coil that circulates chilled water, antifreeze, or refrigerant that is used to remove heat from air moving across the coil’s surface. A coil may be used either for heating or cooling purposes by placing a series of tubes (the coil) carrying a heating or cooling fluid into an airstream. The coil may be constructed from tubes bundled in a serpentine form or finned tubes that give an extended heat transfer surface. Coils may also be used for non-airflow cases such as embedded in a floor slab.

Davidson Hall

 

New subject mapping saref 4 buildings and 3 new data models

There is a new subject datamodel.S4BLDG mapping the data models from SAREF for buildings 1.1.2.

Thanks to the contributors Grzegorz Wiszniewski and Jakob Bjørnskov t the project Twin4Build – A holistic Digital Twin platform for decision-making support over the whole building life cycle.

The original linked data descripton is also kept and a @context could be generated with the service home->tools -> map @context with external ontologies. In this video there is an explanation on how to do it.

For the moment 3 entities has been published but there are more on the queue

  • Actuator. An actuator is a mechanical device for moving or controlling a mechanism or system. An actuator takes energy, usually created by air, electricity, or liquid, and converts that into some kind of motion.

  • AirToAirHeatRecovery. An air-to-air heat recovery device employs a counter-flow heat exchanger between inbound and outbound air flow. It is typically used to transfer heat from warmer air in one chamber to cooler air in the second chamber (i.e., typically used to recover heat from the conditioned air being exhausted and the outside air being supplied to a building), resulting in energy savings from reduced heating (or cooling) requirements.

  • Alarm. An alarm is a device that signals the existence of a condition or situation that is outside the boundaries of normal expectation or that activates such a device. Alarms include the provision of break glass buttons and manual pull boxes that are used to activate alarms.

Illuminated roof of the skyscraper Millenia Tower at night in Singapore

MasterSheet for submission of simple data models

We have released a master sheet that simplifies the contribution to the smart data models.

It uploads the data model to a new repository called drafted.

The video help is also available

Steps for using the spreadsheet

0.- Make a local copy in your google account and grant permission the first time you use it (it warns you that it is not validated by google, true, but anyhow go to advance and grant the permissions

1.- Include your example in json key values

2.- Include the name of the data model, its title, the subject, and the description together with your email

3.,- Describe the attributes, their NGSI type, their data type, and the written description.

And click on the two buttons

 

Extended context.jsonld in all data models

Every subject — a group of data models — has a file named contex.jsonld at their root.

This file contains the @context with automatically generated IRI for the terms used in the data model.

The Entity types are also available in this file with their long IRI.  In the pointed example are the entries for “SeaConditions”, “WeatherAlert”, “WeatherForecast”, and “WeatherObserved”

Remember that if you want to use other IRI coming, for example, from existing ontologies you can use the service on the Home -> Tools -> Mapper @context with external ontologies

updated common-schema.json

We have noticed an error in the description of the attribute location in the file common-schema.json, a file that is embedded in most of the data models. It does not affect the data types (so the validation of the schemas is not affected) but it affects the qualification of the NGSI type that it is not properly identified,

GeoProperty is written with capital middle P.

The file has been updated and soon it will be launched an update of all the data models affected.

EBSI Verifiable Credentials mapped as data models

There is a new subject – Verifiable Credentials – in the Cross-Sector domain, with 5 data models derived from those at EBSI. Minor changes to be adapted as standard data models. Due to the fact that they are used only in key-values format the examples are only in this format. The @context defined has been removed because they are implicit attributes in NGSI-LD.

Check the derivedFrom metadata in every schema.json file to get to the EBSI source.

ebsi European Blockchain