Controller and Point Group model

[gtfierro]

Replaces #721 . @fennibay @ektrah let me know what you think!

[github-actions]

The latest build of the Brick ontology on this PR is available here.

[github-actions]

The latest build of the Brick ontology on this PR is available here.

[fennibay]

Thank you @gtfierro.

concerns and controls look good.

Now I see we missed one point about hosts. These hosted Collections need to contain not only Points and PointGroups, but also equipments. See #721: "A collection of entities can be hosted on a Controller (e.g. sensors, zones, light groups etc.), the hosts relationship from brick:Controller to brick:Collection would allow this. " #722 is also related to this.

Below some first ideas on how to address this, we shall discuss tomorrow:

1. Extend PointGroup to also contain Equipment?
2. Go back to Controller hosts Collection, no PointGroup?
3. Merge this PR without hosts and look at it with Collections as part of other entities #722?
4. Merge this PR AS IS, and look at the equipment in Collection with Collections as part of other entities #722?

Below another example assuming option 2 and #722 are in, just to give some concrete context.

@prefix bldg: <http://example.com/controller2#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix rec: <https://w3id.org/rec#> .
@prefix brick: <https://brickschema.org/schema/Brick#> .
@prefix bacnet: <http://data.ashrae.org/bacnet/2020#> .
@prefix unit: <http://qudt.org/vocab/unit/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix ref: <https://brickschema.org/schema/Brick/ref#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .

<http://example.com/controller2> a owl:Ontology ;
    owl:imports <https://brickschema.org/schema/1.4/Brick> .


bldg:Controller_1 a brick:Controller ;
    rdfs:label "AS20" ;
    brick:hosts bldg:HVAC1 ;
    brick:controls bldg:VavSu1 ;
    brick:concerns bldg:R009 ;
.

bldg:HVAC1 a brick:Collection ;
    brick:hasPart bldg:VavSu1 ;
    brick:hasPart bldg:HCl1 ;
.

bldg:VavSu1 a brick:Variable_Air_Volume_Box ;
    rdfs:label "VAV Supply Unit 1" ;
    brick:hasPart bldg:CdnMsgCol1 ;
.

bldg:CdnMsgCol1 a brick:Collection ;
    rdfs:label "Condensation Message Collection 1" ;
    brick:hasPart bldg:CdnMsgRs1 ;
.

bldg:HCl1 a brick:Heating_Coil ;
    rdfs:label "Heating Coil 1" ;
    brick:hasPoint bldg:Pos1 ;
.

bldg:CdnMsgRs1 a brick:Status ;
    rdfs:label "Condensation Message Result 1" ;
.

bldg:Pos1 a brick:Valve_PositionCommand ;
    rdfs:label "Heating Coil Position 1" ;
.

bldg:R009 a rec:Zone ;
    rdfs:label "Room 009 Zone" ;
    brick:hasPoint bldg:TR1 ;
    brick:hasPart bldg:SpTRDTr1 ;
.

bldg:TR1 a brick:Air_Temperature_Sensor ;
    rdfs:label "Room Temperature 1" ;
.

bldg:SpTRDTr1 a brick:Collection ;
    rdfs:label "Room Temperature Setpoint Determination 1" ;
    brick:hasPart bldg:SpTR1 ;
.

bldg:SpTR1 a brick:Air_Temperature_Setpoint ;
    rdfs:label "Room Temperature Setpoint 1" ;
.

[gtfierro]

@fennibay @jbkoh @ektrah I wrote up some docs for the point group here: BrickSchema/docs#26 Please take a look and let me know what you think. Maybe we can merge this next week? I don't think there's any implementation left to do on the model

[gtfierro]

I'm trying to merge this in, but I'm still not 100% happy with the "concerns" relationship name. How do you all feel about manages for the Controller/Zone relationship?

[fennibay]

I'm trying to merge this in, but I'm still not 100% happy with the "concerns" relationship name. How do you all feel about manages for the Controller/Zone relationship?

manages sounds good to me.