{"id":43813,"date":"2026-11-13T09:27:30","date_gmt":"2026-11-13T08:27:30","guid":{"rendered":"https:\/\/smartdatamodels.org\/?p=43813"},"modified":"2026-11-12T21:28:30","modified_gmt":"2026-11-12T20:28:30","slug":"realestatecore-joins-smart-data-models-10-candidate-models-for-real-estate-and-smart-buildings","status":"publish","type":"post","link":"https:\/\/smartdatamodels.org\/index.php\/realestatecore-joins-smart-data-models-10-candidate-models-for-real-estate-and-smart-buildings\/","title":{"rendered":"RealEstateCore Joins Smart Data Models: 10 Candidate Models for Real Estate and Smart Buildings"},"content":{"rendered":"

Smart Data Models\u2019 Candidates repository<\/a> now includes a new candidate standard translated from RealEstateCore (REC)<\/strong>: realestatecore<\/code><\/strong>, with 10 candidate models<\/strong> for real estate and smart buildings. REC is published under BSD-3-Clause<\/strong>. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context<\/code> and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.<\/p>\n

About RealEstateCore<\/h2>\n

RealEstateCore<\/a> is an ontology for the real estate industry, maintained by the RealEstateCore Consortium. It describes the spatial hierarchy of property (sites, buildings, levels, rooms, zones), building elements, the assets placed in buildings, administrative groupings such as portfolios and premises, organizations, and events such as leases. Since version 4, REC is co-designed with Brick Schema<\/strong>: Brick provides the equipment and sensor-point taxonomy, and REC provides the real estate and location layer. This translation uses release v4.1.0<\/strong> (June 2026).<\/p>\n

The models<\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Model<\/th>\nTypes in recClass<\/code><\/th>\nExamples<\/th>\n<\/tr>\n<\/thead>\n
Site<\/code><\/td>\n\u2013<\/td>\na parcel of land<\/td>\n<\/tr>\n
Building<\/code><\/td>\n6<\/td>\nBuilding, Hospital, School, ShoppingMall, Stadium<\/td>\n<\/tr>\n
Level<\/code><\/td>\n4<\/td>\nLevel, BasementLevel, MezzanineLevel, RoofLevel<\/td>\n<\/tr>\n
Room<\/code><\/td>\n95<\/td>\nOffice, ConferenceRoom, CookingRoom, Bedroom, Lobby, OperatingRoom<\/td>\n<\/tr>\n
Zone<\/code><\/td>\n6<\/td>\nHVACZone, OccupancyZone, AccessControlZone, ParkingSpace, Workspace<\/td>\n<\/tr>\n
Asset<\/code><\/td>\n61<\/td>\nDesk, Chair, Door, Window, IAQSensorEquipment, NetworkRouter<\/td>\n<\/tr>\n
Collection<\/code><\/td>\n8<\/td>\nApartment, Campus, Portfolio, Premises, RealEstate<\/td>\n<\/tr>\n
BuildingElement<\/code><\/td>\n7<\/td>\nFacade, Wall, Slab, Roof, Balcony<\/td>\n<\/tr>\n
Organization<\/code><\/td>\n3<\/td>\nOrganization, Company, Department<\/td>\n<\/tr>\n
Lease<\/code><\/td>\n\u2013<\/td>\na lease of a building, premises or asset<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The models are connected through REC\u2019s own relationships: spaces hasPart<\/code> and isPartOf<\/code> each other, assets are locatedIn<\/code> spaces and hasPoint<\/code> their Brick sensor points, collections includes<\/code> their members, and leases link leaseOf<\/code>, leasee<\/code> and leasor<\/code>. In NGSI-LD these become Relationships.<\/p>\n

Brick and REC, together in the Candidates repository<\/h2>\n

The examples come from the same real deployment as the existing Brick Schema candidate<\/a>: Brick\u2019s own indoor air quality example, a single-family home at 123 Alder Street. REC describes the site, the building (with its address and 165\u00a0m\u00b2 gross area), the first floor, the kitchen, the whole-home HVAC zone and the kitchen\u2019s sensor device. The device\u2019s hasPoint<\/code> links point straight to the Brick candidate\u2019s CO2, PM2.5, PM10, humidity and occupancy sensors. In the same update, the Brick candidate\u2019s examples now point to these REC rooms and zones instead of placeholder location IDs, so the two candidates form one connected graph.<\/p>\n

Translation notes<\/h2>\n