brick:System hasPart, use includes relationship?

[PeteHart]

@gtfierro

The brick:System allows for the brick:hasPart relationship directly to basically any potential part of a system.

Being a subclass to a collection (specifically the brick:Collection, se also #671) would it be possible to use/recommend relationship rec:includes rather than has part to be in line with REC design philosophy for collections? And then deprecate use of brick:hasPart on the brick:System.

Best Peter

[jahrling]

@PeteHart @gtfierro
Old issue, but as an alternative, what about s223:hasMember? brick:hasPart feels like the object is part of a subassembly, not a system. Agreed on deprecating brick:hasPart on brick:System ... and also on brick:Loop.

[gtfierro]

Incorporating S223 directly into Brick is on our roadmap for Brick 2.0 (we are waiting on final publication of the ASHRAE standard before making the full move), and as part of that effort we might re-define some of the relationships in terms of ASHRAE 223P for backwards compatibility. For now, I think using rec:includes is the best move as it keeps collections consistent with RealEstateCore. We will revisit this after Brick 1.5 is released (hoping by end of May)

@PeteHart I've made this change in #775