buildsysuniformmetadata / groundtruth Goto Github PK

I'm currently using the Space object as a stand-in for a "Desk" which hosts sensors and information relating to that workspace (where the desk could potentially move floors in a building) - would a desk object be a useful addition to the schema or is that too specific?

I'm looking at examples for converting existing building metadata to Brick, such as ebu3b_brickgenerator.ipynb. Wondering if there are newer examples than this one?

We would like to capture the relationship between some sensor and what it is associated with.

We have hasLocation, but this is not the same as knowing what entity a sensor is actually measuring.

We have hasPoint/isPointOf, but this seems to be more about encapsulating points in a single piece of equipment.

I think there's a need for a more generic notion of what a point is measuring, or what its controlling. We already have a controls/isControlledBy, which would be associated with some Command Point.

Just to clarify, it is entirely w/n the realm of possibility that we have sensors not associated with any particular piece of equipment.

Any thoughts?

https://github.com/BuildSysUniformMetadata/GroundTruth/blob/master/application_examples/RUN_APPS.py#L106

It looks like we want to query for all temperature sensors from the description, but we also include CO2 and Occupancy sensors?

Hello,

I would like to report an issue with Brick.ttl, indeed we can see that some data are duplicated as shown below.

Dear Brick development team!

it might be helpful for people reusing BRICK to have the license mentioned within the ontology meta-data, via the dcterms:license annotation property. For example in Turtle syntax:

@prefix dcterms: <http://purl.org/dc/terms/> .
<https://brickschema.org/schema/1.0.2/BrickFrame> dcterms:license <https://raw.githubusercontent.com/BuildSysUniformMetadata/GroundTruth/master/LICENSE> .

or similarly.

Best

Georg

BrickFrame.ttl defines a relationship feeds with inverse relationship isFeedBy. This should be isFedBy

BugReport: @joshuagluck found that if you import Brick.ttl in rdflib and serialize it, Protege won’t accept the output.

g = rdflib.Graph()
g.parse('../BuildingSchema/Brick.ttl', format='turtle')
g.serialize(destination='GHCYuvraj_brick.ttl', format='turtle')