owl:Classand are arranged into a hierarchy with
We are eliminating equipment-flavored classes where it makes sense
brick:AHU_Average_Exhaust_Air_Static_Pressure_Sensoris just a
Average_Exhaust_Air_Static_Pressure_Sensorthat is a point of an AHU.
(Relationships are the Brick term for owl ObjectProperties between instances of classes)
At the surface level, relationship work the same as they did in the original Brick.
All the same relationships still exist (where I remembered to define them), and they have their
inverses defined using
Domains and ranges are defined in terms of classes. Stating that the
rdfs:range of a relationship
is of class
brick:Equipment means that the object of the relationship should be an instance of the