-
Notifications
You must be signed in to change notification settings - Fork 90
Open
Description
Today rec:Collection (its subclass brick:Collection) can only be isPartOf Collections and no other entities (e.g. rec:Space, brick:Equipment).
We have certain scenarios where we would like to logically group entities in Collections, where:
- they do not represent a meaningful domain entity such as an equipment, zone etc.; but just a grouping of underlying entities
- they are not at top-level, but within a given context (rec:Space, brick:Equipment).
Some examples:
- CdnMsgCol: Is a collection of condensation message points within a Supply Air VAV.
- Separating different disciplines within a room: HVAC, Lighting, Shading. See RHvacCoo, RLgtCoo, RShdCoo at https://nas.desigo.tw/NGA/Help/en/en-US/10454554635.html
- Organizational "folders" in building automation projects for example for separating room automation from primary automation plants within a building.
So, I propose to extend the properties
- hasPart: allow Collection in the range
- isPartOf: allow Collection in the domain.
This might be better addressed at https://github.com/RealEstateCore/rec. Please advise.
See also: #671
/cc @ektrah
Metadata
Metadata
Assignees
Labels
No labels