- From: Joel J. Bender <jjb5@cornell.edu>
- Date: Mon, 20 Jan 2020 17:15:53 +0000
- To: "public-lbd@w3.org" <public-lbd@w3.org>
I have been working on an OWL/SHACL model for ASHRAE 223 [1] which is similar to BACS [2]. It draws on concepts from Brick Schema [3] and BEDES [4] and is similar to SEAS [5], my current effort is to organize the concepts in Brick with SSN/SOSA features of interest and properties. My puzzler is that the same core property has different labels depending on the context. For example, there is a fan that has a temperature sensor in an air stream, usually on the discharge side, so [discharge air] is the feature of interest and [discharge air temperature] is the [observable property], the sensor is usually labeled [discharge air temperature sensor]. However, when the fan is a [supply fan] component of an [air handling unit] system the air magically becomes [supply air] if it is discharging into the [space/room/zone] or [return air] if the fan is on the return side. To keep the concepts separate I have been using a quad store so that "_:x a brick:Discharge_Air_Temperature" and ""_:x a brick:Supply_Air_Temperature" belong to different graphs even though _:x is the same in both cases, and both graphs would contain "_:x a brick:Air_Temperature, sosa:ObservableProperty". Note that the [discharge air] of an [air handling unit] is often also called [exhaust air]. I'm not convinced this would be appropriate for a "standard" because I would expect that quad stores are already be using named graphs for other things like attaching PROV information to collections of triples. If you have ideas on some options going forward I would appreciate them. Joel [1] https://www.ashrae.org/news/esociety/ashrae-bacnet-committee-works-with-other-organizations-on-new-standard [2] http://publica.fraunhofer.de/documents/N-497126.html [3] https://brickschema.org/ [4] https://bedes.lbl.gov/bedes-online [5] https://ci.mines-stetienne.fr/seas/index.html
Received on Monday, 20 January 2020 17:16:02 UTC