Modeling loops and connections

[ektrah]

A few questions about loops:

• What exactly is a loop?
  • brick:Loop is currently defined as a collection of connected equipment. (Would that be a s223:System in 223?)
  • Project Haystack defines it as pipework.
• How would I use brick:Loop in conjunction with 223:Connection?
  • Can the connections be inferred given a list of connected equipment?
• How can I indicate that a loop is a primary loop, secondary loop, tertiary loop?
  • See plantLoop and primaryLoop, secondaryLoop, tertiaryLoop in Project Haystack.

[gtfierro]

You think think of a Loop as the "closure" of the brick:feeds and/or the family of s223:connect... relationships. It was introduced in Brick in order to get around having to model individual pipes/flows/ducts/etc. The idea is that one could write a SPARQL query or SHACL rule that would infer membership in a Loop object.

I think s223:System could be used as a parent of brick:Loop but I haven't had this discussion with the 223 team yet. I would think that s223:Connection and s223:Connectable would be members of the brick:Loop.

We will need to decide if we want create an entity property which captures the "flavor" of the loop, or make the different kinds of loop their own class