RealEstateCore version 3.2 has arrived
We are happy to announce that RealEstateCore version 3.2 is released.
-Extensive support for analytics and machine learning.
-A new SensorInterface class, mirroring the design of the ActuatorInterface class from REC 3.1. This allows you to represent shared aspects of a set of identical sensors (e.g., their data schemas) in a single place, reducing duplication across the knowledge graph. It also simplifies translation of RealEstateCore graphs into, e.g., Microsoft DTDL or Web of Things TD.
-A new Lantmäteriet module, representing the Swedish Real Property Register (Fastighetsregister). This module, intended for the Swedish market, is optional and thus not loaded in REC Full by default.
-A new Collections class, intended to represent generic administrative collections of things (e.g. packaging of service into new products)
-Additional Quantity Kind and Measurement Unit individuals supporting waste management and more presence detection use cases.
-An official alignment to BOT (Building Topology Ontology).
For details and download, please see the release notes:
Hey all. As you may have seen in the issues list and in the "develop" branch, I have, based on the expressed needs of some strategic partners, been working on an "Equipment" class and hierarchy. This largely mirrors Brick, and will primarily deal with things that are mounted in the building, e.g., HVAC systems, plumbing, elevators, etc.
Initially I have myself thought of these Equipment things as being disjoint from Devices. We have Devices that we communicate with (Sensors/Actuators), and these may act on, serve, or sense data from some legacy Equipment system. The divided is something along the line of "Equipment is dumb, Devices are smart", or "Equipment contains machinery, Devices contain microcontrollers". So in modeling a Smart HVAC-system for instance, I guess I'd think of it as an HVAC system being equipment, and it's controller being a Device, and the Device being mounted physically inside of the Equipment.
But of course, in light of the increasing smarts being built into all sorts of systems these days, this could be quite a backwards attitude, to differentiate in this way. I'm interested in hearing how you think of these things and how to express these relations in your use cases.