You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
@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
The text was updated successfully, but these errors were encountered: