Brick v1.4.0 Released!
Gabe Fierro
Oskar Nilsson
Hi,
Thank you for your efforts! Is there an estimate timeline for the documentation? Brick locations got replaced by rec:Space but there are many other rec entities and it is not clear to me how to use Brick 1.4 to model a building. What are the class trees and which relation to use in each situation. Also, there are both a rec and brick collection, shouldn’t one be deprecated?
Thanks
Gabriel Fierro
Sorry for my delay in reply! I’ve been travelling the past couple weeks.
We absolutely need some better documentation on this topic. We do have some basic stuff online (https://docs.brickschema.org/modeling/terminal-units.html) but I will make writing up some Brick/REC usage documentation a priority this week.
The short, oversimplifying answer is: use Brick for equipment/points, use REC for locations. The existing Brick relationships will work with all of these, assuming you are using Brick 1.4. In a few of these cases where there are both Brick and REC classes with the same name (e.g., Collection) then one is usually preferred. REC’s collection is more general than Brick, so it is the “superclass” of the brick:Collection. You can generally put anything in a REC collection, but Brick’s collections are a bit more specific (https://ontology.brickschema.org/brick/Collection.html)
Best,
Gabe
--
You received this message because you are subscribed to the Google Groups "Brick User Forum (Unified Building Metadata Schema)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
brickschema...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/brickschema/e2cfeaa6-1ea6-42aa-82b9-fdb07f9f6f52n%40googlegroups.com.