Repository navigation
REC 4.1 is a minor, backwards-compatible release that consolidates feature additions, clarifications, and governance improvements accumulated since v4.0.
New Features
- Warranty class. New
Warrantyevent type, plus awarrantyrelationship onAsset, to capture warranty metadata on equipment and other assets. - Asset properties.
Assetnow carries acolourproperty for visual/identification purposes. - New room types. Added
Lobby,Lounge, andTeamroom subclasses underSpace/Architecture/Room/to fill out common facility-management use cases. - Gateway connection parameters. Added
GatewayConnectionParameterand the more specificIoTHubConnectionParameterunder thePoint/Parameterhierarchy, to allow modelling of gateway/edge connection metadata. - Agent membership. New
Agent.memberOfrelationship, with semantics clarified relative toOrganization.isPartOf. - Broadened relationship targets.
System.includesno longer restricts its target type, allowing systems to include a wider range of constituents.Asset.locatedInhas had itssh:minCount 1constraint removed, so assets no longer require a location at shape-validation time.
Deprecated features
Agent.isMemberOfis deprecated in favour of the newAgent.memberOfrelationship.isMemberOfremains in the ontology for backwards compatibility and will be removed in a later release.BACnetControllerandModbusControllerare retained but marked as deprecated. Industry convention has moved to multi-protocol controllers, so these specific subclasses should no longer be used for new modelling.
Governance
- Ontology Decision Records (ODRs). Introduced a lightweight governance framework under
/OntologyDecisionRecords/to capture design decisions going forward. The following ODRs are ratified in 4.1:- ODR 000 — Use of Ontology Decision Records
- ODR 001 — Naming Conventions
- ODR 002 — GatewayConnectionParameter
- ODR 003 — Ontology Versioning (MAJOR.MINOR.PATCH.REVISION scheme, deprecation-before-removal policy)
Fixes
PV_Panelenum values corrected from objects to arrays (#241).- SHACL/DTDL consistency alignment in the ICT Equipment path hierarchy.
- Build system: MSBuild EOL warnings no longer poison the merged JSON-LD output.
Known issues
- The edge message schema has not yet been updated for REC4. A REC4-compliant edge message schema remains planned for a later release in the 4.x series.
Build number
The formal build number of REC 4.1 and of accompanying NuGet packages is 4.1.0.0.