Human Services Data Specification (HSDS) Joins Smart Data Models: 5 Candidate Models for Human Service Directories

Smart Data Models’ Candidates repository now includes a new candidate standard from Open Referral: hsds, with 5 candidate models for directories of health, human and social services: the organizations, services, programs and locations of a community resource directory. The Human Services Data Specification is published under CC-BY-SA 4.0, so these derived models are shared under the same licence. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.

About the Human Services Data Specification

Open Referral develops the Human Services Data Specification (HSDS), also known as “the Open Referral format”: an exchange format for publishing directory information about human services (food assistance, job training, child care, counselling…) as open data. Governments, information-and-referral providers and community organizations use it to share who offers which service, where, when, for whom and at what cost. The candidate is based on HSDS 3.3.1, the latest release, which defines its objects as JSON Schemas.

The models

Model HSDS object What it describes Attributes
Organization organization An organization that delivers services, with funding, identifiers and phones 24
Service service A service: status, eligibility, fees, application process, operating hours, service areas, languages, costs, required documents 38
Location location A physical, postal or virtual place where services are delivered, with addresses and accessibility 25
ServiceAtLocation service_at_location A service as delivered at one location, with location-specific contacts and schedules 15
Program program A group of related services run by one organization 11

One consistent example directory

The examples are synthetic, and say so. They are adapted from HSDS’s own example data: the fictitious Example Organization Inc. runs the Community Mental Health Support program, whose Community Counselling service is delivered at the MyCity Civic Center. Personal names were removed, phone numbers come from the UK range reserved for drama, and the coordinates are illustrative.

Translation notes

  • HSDS names, verbatim. Every field keeps its HSDS snake_case name (eligibility_description, organization_id, service_at_locations…). Entity types use the HSDS documentation headings in PascalCase. The only rename is id → hsdsId.
  • Linked entities. The links between organizations, programs, services, locations and services-at-location are NGSI-LD Relationships.
  • Nested where HSDS nests. Phones, contacts, schedules, addresses, accessibility, languages, funding, costs, service areas, attributes and taxonomy terms keep their full HSDS structure.
  • Ready for geo-queries. Locations and services-at-location get an NGSI-LD location (GeoJSON point) built from HSDS’s own latitude and longitude. It is the only addition to the HSDS content.
  • Current fields only. Fields that HSDS has deprecated (including service.schedules, replaced in 3.3 by operating_hours and events) are left out.
  • Licence. HSDS is CC-BY-SA 4.0: “Human Services Data Specification: an Open Referral resource”. The candidate models are shared alike.

Try it, and tell us what’s missing

These are Candidates: first, carefully sourced translations that are not yet official Smart Data Models subjects. Before that step, the main open question is overlap: Organization with dataModel.Organization and other organization models, Service with the public services of dataModel.CPSV-AP, and Location with dataModel.PointOfInterest. Natural next steps are taxonomy terms as shared entities and a mapping to CPSV-AP.

Browse the models, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/hsds

Mobility Data Specification (MDS) Joins Smart Data Models: 8 Candidate Models for Shared Mobility Regulation

Smart Data Models’ Candidates repository now includes a new candidate standard translated from the Open Mobility Foundation: mds, with 8 candidate models from the Mobility Data Specification (MDS) 2.1.0: vehicles, events, telemetry, trips, stops, incidents, geographies and policies. MDS is published under CC BY 4.0. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.

About the Mobility Data Specification

MDS is the data standard that cities and public agencies use to manage mobility services operating in the public right of way: shared scooters and bikes, car share and fleets, delivery robots and passenger services such as taxis and robotaxis. Operators share their vehicles, trips, vehicle events and telemetry; agencies publish geographies and policies (fleet caps, speed limits, fees). Release 2.1.0 (July 2026) adds incidents and enforcement, links to GTFS and other external data, statistical areas and accelerometer data.

The models

Model What it describes Attributes Example
Vehicle A vehicle registered by an operator: type, propulsion, capacities 14 Standing e-scooter
Event A change of vehicle state (available, on trip, non-operational…) 21 Trip end at a corral
Telemetry One GPS/GNSS point with sensor data 17 Point mid-trip, on a bike lane
Trip A customer or operator trip with start, end, duration, distance and cost 25 8-minute rider trip
Stop A docking station, corral or parking area, with capacity and availability 24 Corral for scooters and bikes
Incident Crash, tip over, near miss, vandalism, violation… (new in 2.1) 16 Harsh stopping, no injury
Geography A versioned GeoJSON area published by an agency 10 Louisville Metro municipal boundary (real)
Policy Agency rules: caps, speed limits, time and distance limits, fees 12 Fleet cap and 15 mph speed limit

Examples: one story, and privacy first

MDS trip and telemetry data is sensitive location data, so no real operator feed is used. The examples tell one synthetic story in downtown Louisville, Kentucky: a fictitious operator’s scooter makes a short trip, records a harsh-stopping incident and ends the trip at a corral. The Geography example is real: the Louisville Metro municipal boundary that the Open Mobility Foundation publishes in the MDS repository (CC BY 4.0). The example policy refers to that boundary but is invented.

Translation notes

  • Taken from the 2.1.0 tables. The OMF OpenAPI description still covers MDS 2.0 only, so the models were generated from the field tables of the 2.1.0 specification, with the OpenAPI used as a cross-check.
  • MDS names, verbatim. Fields keep their MDS names (device_id, vehicle_state, event_types…). The only rename is the MDS GPS object location, which becomes mdsLocation because location is reserved for GeoJSON in NGSI-LD.
  • Linked entities. References between models (an event’s vehicle, trips, stop and geographies; telemetry’s incidents; a stop’s geography) are NGSI-LD Relationships.
  • Ready for geo-queries. Events, telemetry, stops and geographies get an NGSI-LD location built from MDS’s own coordinates. It is the only addition to the MDS content. Timestamps stay in MDS format (milliseconds since the Unix epoch).
  • Upstream notes. A few small inconsistencies in the specification (for example system_start vs service_start in the event types) are documented in the metadata, ready to report to the OMF.

Try it, and tell us what’s missing

These are Candidates: first, carefully sourced translations that are not yet official Smart Data Models subjects. Before that step, the main open question is overlap with dataModel.Transportation (Vehicle, FleetVehicle, BikeHireDockingStation, RoadAccident…), dataModel.UrbanMobility and the shared-vehicles candidate edint-vehiculos-compartidos. Natural next steps are MDS Reports, Vehicle Status and the agency data Requirements.

Browse the models, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/mds

Project Haystack Joins Smart Data Models: 8 Candidate Models for Smart Buildings and Building Automation

Smart Data Models’ Candidates repository now includes a new candidate standard for buildings: project-haystack, with 8 candidate models translated from Project Haystack 4.0.0, the open tagging ontology for building and IoT data. Project Haystack is published under the Academic Free License 3.0. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.

About Project Haystack

Project Haystack is an open-source community effort that standardizes how building automation data is described: sites, spaces, equipment such as air handlers, chillers and meters, and the sensor, command and setpoint points they expose. Entities carry marker tags (discharge air temp sensor point), value tags and references (siteRef, equipRef). Haystack 4 defines these tags as “defs” (haystack-defs, release 4.0.0, 719 defs) and publishes them as JSON, Turtle and JSON-LD.

The models

Model Haystack def Attributes Example
Site site 23 Bravo hospital, Fort Wayne IN (real)
Space space 12 Bravo space @b-0135 (real)
Equip equip 47 Rooftop unit RTU-1: ahu rtu, chilled water cooling, hot water heating (real)
Point point 36 RTU-1 supply (discharge) air temperature sensor (real)
WeatherStation weatherStation 19 Fort Wayne, IN station (real)
System system 10 Chilled water system (synthetic)
Device device 10 RTU-1 controller (synthetic)
Network network 8 BACnet network (synthetic)

Grounded in a real building

Project Haystack publishes anonymized example buildings under the same licence. Five of the examples come straight from “Bravo”, a hospital with steam, hot water and chilled water plants: the site, a space, rooftop unit RTU-1 (an air handler with chilled water cooling, hot water heating and VAV zones), its supply air temperature sensor, and the Fort Wayne weather station. Bravo has no system, device or network records, so those three examples are synthetic, linked to Bravo, and say so.

Translation notes

  • Haystack names, verbatim. Every attribute is a Haystack tag name, and every @context maps it to the def IRI of the official Haystack RDF export. Model names follow the Haystack 5 (Xeto) specs: Site, Space, Equip, Point…
  • Markers as Haystack itself exports them. Marker tags go in one hasTag list (["ahu", "rtu", "hvac", "equip", …]), the same way Haystack’s own RDF export carries them (ph:hasTag). In JSON-LD each marker expands to its Haystack IRI.
  • Choices as enums. Haystack choices such as pointFunction (sensor, cmd, sp), pointSubject, pointQuantity, coolingProcess or heatingProcess are also enum properties, so they are easy to query.
  • References become NGSI-LD Relationships: site, space, equipment, system and weather station references, sub-metering, and the flow references between equipment (hot water, chilled water, electricity…).
  • Ready for geo-queries. Sites and weather stations get an NGSI-LD location built from Haystack’s geoCoord. It is the only addition to the Haystack content. Areas are in m².

Try it, and tell us what’s missing

These are Candidates: first, carefully sourced translations that are not yet official Smart Data Models subjects. The main open question is overlap with the Brick Schema and RealEstateCore candidates and with the official dataModel.Building and dataModel.Device subjects, since all of them describe buildings and their equipment. Natural next steps are the remaining Haystack entities (EV charging sessions, point groups, machine-learning variables) and the Haystack 5 Xeto specs.

Browse the models, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/project-haystack

CAMARA APIs Join Smart Data Models: 7 Candidate Models for Telco Network Data in Smart Cities

Smart Data Models’ Candidates repository now includes a new candidate standard from the telecom world: camara-apis, with 7 candidate models translated from the CAMARA network APIs: quality on demand, device location and geofencing, crowd data and device reachability. The CAMARA specifications are published under Apache-2.0. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.

About CAMARA

CAMARA is the open-source project of the Linux Foundation, run with the GSMA Open Gateway initiative, that defines network APIs exposed in the same way by mobile operators around the world. Each API is an OpenAPI specification in its own GitHub repository, released in coordinated meta-releases. This candidate uses the latest public release of each API on 13 November 2026: the Fall25 releases of QualityOnDemand, DeviceLocation, RegionDeviceCount and DeviceReachabilityStatus, and the Sync26 release (1.0.0) of PopulationDensityData.

The models

Model CAMARA API What it describes Attributes
QosProfile qos-profiles 1.1.0 A network quality profile: target and maximum rates, latency, jitter, loss, priority 24
SessionInfo quality-on-demand 1.1.0 A quality-on-demand session between a device and an application server 18
DeviceLocation location-retrieval 0.5.0 The network-based location area of a device 10
GeofencingSubscription geofencing-subscriptions 0.5.0 A subscription to area-entered / area-left events for a device 15
CellPopulationDensityData population-density-data 1.0.0 Estimated number of people in a geohash cell for an hourly slot 14
RegionDeviceCount region-device-count 0.2.0 Number of devices in an area and time window, with filters 13
DeviceReachabilityStatus device-reachability-status 1.1.0 Whether a device is reachable, for data and/or SMS 10

One consistent example scenario

CAMARA has no open data (operators expose the APIs only to registered consumers), so the examples are synthetic, and say so. They follow an evening event at Puerta del Sol in Madrid: a QoD session with a QOS_L profile carries a live-video uplink, a field team’s device is located, watched by a geofence and checked for reachability, and the crowd is described by the population density of geohash cell ezjmgtw and a device count for the square. No real phone numbers are used: device identifiers are CAMARA’s own example number +123456789 and documentation IP addresses.

Translation notes

  • CAMARA names, verbatim. Every field keeps its CAMARA name. Entities are named after the CAMARA component, or after the API when the component is generic or a response wrapper (DeviceLocation, GeofencingSubscription, RegionDeviceCount, DeviceReachabilityStatus). Each @context maps terms to their place in the released OpenAPI file.
  • Linked. A QoD session points to its QosProfile as an NGSI-LD Relationship.
  • Ready for geo-queries. Location, geofence, region and geohash cell entities get an NGSI-LD location built from CAMARA’s own areas. It is the only addition to the CAMARA content.
  • No secrets. Delivery credentials (access tokens) of sessions are left out. Device identifiers are personal data, so deployments should use pseudonymous ids where possible.

Try it, and tell us what’s missing

These are Candidates: first, carefully sourced translations that are not yet official Smart Data Models subjects. Before that step, the main open questions are overlap with CrowdFlowObserved (Transportation), Device and NetworkConnection. Natural next steps are the Connected Network Type and Device Roaming Status APIs, QoS provisioning, Edge Cloud and Network Slice Booking.

Browse the models, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/camara-apis

TM Forum Open APIs Join Smart Data Models: 174 Candidate Models for the Whole Telecom Digital-Service Stack

Smart Data Models’ Candidates repository already had a first slice of the TM Forum Open APIs (five inventory, order and trouble-ticket models). The candidate tmforum-open-apis now covers every TM Forum Open API published under Apache-2.0: 86 APIs and 174 candidate models, one per managed resource, linked by 213 NGSI-LD Relationships. As with every candidate, each model has a JSON Schema, an NGSI-LD @context and four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.

About the TM Forum Open APIs

TM Forum is the global industry association of communication service providers and their suppliers. Its Open APIs are the REST interfaces of the Open Digital Architecture (ODA), used across the industry for catalogues, ordering, inventory, assurance, billing, party management, testing, IoT, AI and partner APIs (Open Gateway). Through its API Apache 2.0 project, TM Forum publishes the OpenAPI files on github.com/tmforum-apis. We checked the licence of every repository at the exact release we used. We left out the one API without a licence file (TMF667 Document), the repository template and one repository that has no OpenAPI file yet. We used the latest release of each API: 38 are at v5, the others at v4 or older.

The models

Area TM Forum APIs Models Model names
Catalogues TMF620, TMF633, TMF634, TMF662, TMF767, TMF936 22 ProductCatalog, Category, ProductOffering, ProductOfferingPrice, ProductSpecification, ServiceCatalog, ServiceCategory, ServiceCandidate, ServiceSpecification, ResourceCatalog, ResourceCategory, ResourceCandidate, ResourceSpecification, EntityCatalog, EntityCategory, EntityCatalogItem, EntitySpecification, AssociationSpecification, Association, ProductUsageSpecification, OpenGatewayProductOffering, OpenGatewayProductSpecification
Ordering, qualification and sales TMF622, TMF641, TMF652, TMF648, TMF663, TMF645, TMF679, TMF760, TMF680, TMF699, TMF651, TMF687, TMF700, TMF697, TMF716 21 ProductOrder, ServiceOrder, ServiceOrderSpecification, ResourceOrder, Quote, ShoppingCart, CheckServiceQualification, QueryServiceQualification, CheckProductOfferingQualification, QueryProductOfferingQualification, CheckProductConfiguration, QueryProductConfiguration, QueryProductRecommendation, SalesLead, SalesOpportunity, Agreement, AgreementSpecification, ProductStock, ShippingOrder, WorkOrder, ResourceReservation
Inventory TMF637, TMF638, TMF639, TMF664, TMF685, TMF703, TMF640, TMF702, TMF730 7 Product, Service, Resource, ResourceFunction, ResourcePool, Reservation, TmfEntity
Assurance and performance TMF621, TMF642, TMF656, TMF653, TMF657, TMF649, TMF628, TMF724, TMF655 18 TroubleTicket, TroubleTicketSpecification, Alarm, ServiceProblem, ServiceProblemEventRecord, ServiceTest, ServiceTestSpecification, ServiceLevelObjective, ServiceLevelSpecification, Threshold, ThresholdRule, ThresholdJob, MeasurementCollectionJob, PerformanceIndicatorGroupSpecification, PerformanceIndicatorSpecification, TrackingRecord, Incident, ChangeRequest
Party, customer and identity TMF629, TMF632, TMF669, TMF668, TMF644, TMF683, TMF717, TMF720, TMF691, TMF672, TMF681, TMF646, TMF658, TMF671 27 Customer, Individual, Organization, PartyRole, PartyRoleSpecification, Partnership, PartnershipSpecification, PartyPrivacyAgreement, PartyPrivacyProfile, PartyPrivacyProfileSpecification, PartyInteraction, Customer360, DigitalIdentity, Userinfo, PermissionSet, PermissionSpecification, PermissionSpecificationSet, CommunicationMessage, Appointment, ProgramProductSpec, LoyaltyRule, LoyaltyAction, LoyaltyCondition, LoyaltyEventType, LoyaltyMember, LoyaltyBalance, Promotion
Accounts, billing, payment and usage TMF666, TMF670, TMF676, TMF678, TMF654, TMF635, TMF677, TMF771, TMF735, TMF736, TMF737, TMF738 24 PartyAccount, BillingAccount, SettlementAccount, FinancialAccount, BillFormat, BillPresentationMedia, BillingCycleSpecification, PaymentMethod, Payment, Refund, CustomerBill, AppliedCustomerBillingRate, BillCycle, Bucket, AccumulatedBalance, BalanceActionHistory, ProductUsage, UsageConsumptionReport, ResourceUsage, ResourceUsageSpecification, CdrTransaction, PartyRevSharingAlgorithm, PartyRevSharingReport, PartyRevSharingModel
Places and shipping TMF673, TMF674, TMF675, TMF684 4 GeographicAddress, GeographicSite, GeographicLocation, ShipmentTracking
Test management TMF704, TMF705, TMF706, TMF707, TMF708, TMF709, TMF710 19 TestCase, TestSuite, NonFunctionalTestModel, AbstractEnvironment, ConcreteEnvironmentMetaModel, TestResourceAPI, ProvisioningArtifact, TestDataInstance, TestDataSchema, TestCaseResult, TestSuiteResult, NonFunctionalTestResult, TestEnvironmentAllocationExecution, TestEnvironmentProvisioningExecution, TestCaseExecution, TestSuiteExecution, NonFunctionalTestExecution, TestScenario, GeneralTestArtifact
Process, intent, events and risk TMF701, TMF921, TMF688, TMF696 14 Process, ProcessSpecification, Task, TaskSpecification, Intent, IntentSpecification, IntentReport, Topic, Event, ProductOfferingRiskAssessment, PartyRoleRiskAssessment, PartyRoleProductOfferingRiskAssessment, ShoppingCartRiskAssessment, ProductOrderRiskAssessment
Component suites (IoT, AI, Open Gateway, NaaS, self-care) TMF908, TMF914, TMF915, TMF931, TMF909, TMF910 18 IotDevice, IotDeviceSpecification, DataAccessEndpoint, IotDataEvent, IotManagementEvent, IotService, IotServiceSpecification, User, AiModel, AiModelSpecification, AiContract, AiContractSpecification, AiContractViolation, Rule, ApiProduct, ApiProductOrder, Application, ApplicationOwner

Some APIs, mostly the component suites, only re-publish resources that another API already defines, such as Service, Resource or Alarm. Those resources are modelled once, from the API that owns them. Operations like cancelling an order or acknowledging an alarm are not separate models, and neither are the notification payloads.

Examples

For the 78 models from v5 APIs, the examples are the example payloads in TM Forum’s own OpenAPI files (Apache-2.0, illustrative, not real operator data). The older v4 files have no example payloads, so the other 96 examples are generated from the schema and its example values. Each example says which kind it is in its source. Many of these resources hold personal data in real deployments (individuals, customers, contacts, digital identities), so all examples are fictitious. Names of people are removed or replaced by “Jane Doe”, e-mail addresses use example.com, phone numbers come from the ranges reserved for fiction, and postal addresses and identity-document numbers are placeholders.

Translation notes

  • TMF names, verbatim. Every attribute keeps its TMF name. Each @context maps it to its definition in the versioned OpenAPI file on GitHub, and all 3,181 of these links were checked.
  • TMF polymorphism kept. @type, @baseType and @schemaLocation become tmfType, tmfBaseType and tmfSchemaLocation, and the TMF id becomes tmfId. A few other names that clash with NGSI-LD or with common Smart Data Models attributes also get a tmf prefix, and TMF703’s Entity becomes TmfEntity.
  • A connected graph. When a TMF attribute references a resource that is also a model here, it becomes an NGSI-LD Relationship. For example, a product offering points to its specification and prices, a product to its offering and billing account, and a service problem to the affected service, resource and trouble ticket. Characteristics, prices, related parties and order items keep their full TMF structure as nested JSON.
  • One generator. A single generic script, driven by a table of API, repository, release, file and resources, produces all 174 models. It was also used to regenerate the five original models, which move to schema version 0.0.2 because their references to catalogue, billing and intent resources are now Relationships.
  • Source issues documented. The metadata lists the small problems found in the specifications, such as invalid timestamps, example attributes missing from the schemas, dangling references and copyright lines left over in some files, for reporting upstream.

Try it, and tell us what’s missing

These are Candidates: carefully sourced translations, not yet official Smart Data Models subjects. The main open question before promotion is naming. Many TMF names are generic (Organization, Event, Alarm, Rule, Task, User, Product, Service…) and already exist in Smart Data Models or other candidates with other meanings. There is also scope overlap with dataModel.Organization, dataModel.Device and dataModel.IssueTracking.

Browse the models, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/tmforum-open-apis

RealEstateCore Joins Smart Data Models: 10 Candidate Models for Real Estate and Smart Buildings

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

About RealEstateCore

RealEstateCore 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: Brick provides the equipment and sensor-point taxonomy, and REC provides the real estate and location layer. This translation uses release v4.1.0 (June 2026).

The models

Model Types in recClass Examples
Site – a parcel of land
Building 6 Building, Hospital, School, ShoppingMall, Stadium
Level 4 Level, BasementLevel, MezzanineLevel, RoofLevel
Room 95 Office, ConferenceRoom, CookingRoom, Bedroom, Lobby, OperatingRoom
Zone 6 HVACZone, OccupancyZone, AccessControlZone, ParkingSpace, Workspace
Asset 61 Desk, Chair, Door, Window, IAQSensorEquipment, NetworkRouter
Collection 8 Apartment, Campus, Portfolio, Premises, RealEstate
BuildingElement 7 Facade, Wall, Slab, Roof, Balcony
Organization 3 Organization, Company, Department
Lease – a lease of a building, premises or asset

The models are connected through REC’s own relationships: spaces hasPart and isPartOf each other, assets are locatedIn spaces and hasPoint their Brick sensor points, collections includes their members, and leases link leaseOf, leasee and leasor. In NGSI-LD these become Relationships.

Brick and REC, together in the Candidates repository

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

Translation notes

  • REC 4.1 from its DTDL source. REC is published as both SHACL and DTDL, but in v4.1.0 only the DTDL contains the 4.1 additions (Warranty, asset colour, memberOf, and the Lobby, Lounge and Team room types). The DTDL is used as the source, and SHACL supplies cardinalities and datatypes.
  • Names preserved verbatim. REC’s class and property names are kept exactly as REC writes them, including IPAddress and MACAddress.
  • One model per branch. Rather than 95 separate room types, Room (like Building, Zone, Asset and others) carries the specific REC class in recClass, restricted to the non-deprecated classes of that branch. Brick’s own equipment classes stay with the Brick candidate.
  • Simplified structures. REC’s GeoJSON geometry maps to the NGSI-LD location attribute. Postal address, area and capacity are inlined as structured properties that keep REC’s field names.
  • Licence verified. REC is BSD-3-Clause, the same licence as Brick Schema.

Try it, and tell us what’s missing

These are Candidates: first, carefully sourced translations that are not yet official Smart Data Models subjects. Before that step, the main open question is overlap with existing models, especially dataModel.Building, dataModel.Organization, the S4BLDG subject and the SAREF4CITY candidate. Natural next steps are Region, Person, Warranty and REC’s observation events.

Browse the models, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/realestatecore

New data model VehicleModel at subject dataModel.Transportation

We are pleased to announce the publication of VehicleModel within the subject dataModel.Transportation.

VehicleModel: This entity models a particular vehicle model, including all properties which are common to multiple vehicle instances belonging to such model.

We are grateful to OS2.eu (Project funded by OS2 for danish municipalities.), Piet Bikker from Arvoo, Jose M. Cantera from CanteraFonseca.EU, Dmitrii Demin, Federico M. Facca from Martel Innovate, Marc Fajula from Everis, Paolo Fosci, Jason Fox from FIWARE Foundation, Gorka Garcia from Purple Blob, Víctor González from Universidad de Cantabria (UC), Jone Begoña Ibarzabal from Purple Blob, Bertrand Le Droumaguet from Atos – Sophia Antipolis (SmartCity Project), Martino Maggio from Engineering, Massimo Mangoni, Stephane Roux from Metropole Nice Cote D’Azur (SmartCity Project), Iñigo Ruiz from Purple Blob, Joud Sayed Issa, Gert Van de Wouwer from Digipolis Antwerpen, Gert Van de Wouwer from Digipolis Antwerpen, Srikrishnan None from IUDX, Tom Van den Abbeele from Inuits, Joao Viegas from ubiwhere for their contributions to these data models.

Find all published Smart Data Models at smartdatamodels.org.

SAREF4CITY & SAREF4INMA Join Smart Data Models: 35 Candidate Models for Smart Cities and Manufacturing

Smart Data Models’ Candidates repository now includes two more ETSI SAREF extensions: saref4city and saref4inma, together contributing 35 candidate models. Both ship the full Candidates artifact set — a JSON Schema, an NGSI-LD @context, and all four example serializations — validated against its own schema.

SAREF4CITY — 14 models

SAREF4CITY (ETSI TS 103 410-4, Oct 2024) is aimed at city administrations and smart-city platform builders who need a common, IoT-friendly vocabulary instead of yet another bespoke city data schema. It handles the “one KPI, many measurements” problem distinctly well: a general KPI definition (e.g. “road congestion”) is kept separate from its individual timestamped  ssessments, so historical values accumulate cleanly under one stable definition. It also gives city topology (countries → cities → districts → neighbourhoods, spatially linked via GeoSPARQL) a reusable shape, and models public services with who provides them, who uses them, where, and in what languages — directly reusing the EU’s own ISA² Core Public Service Vocabulary rather than reinventing it.

Category Models
Topology / geo AdministrativeArea, CityObject, Facility, plus City, Country, District, Neighbourhood
Agents & organizations Agent, PublicAdministration
Events & accessibility Event, AccessibilityConcept
KPIs KeyPerformanceIndicator, KeyPerformanceIndicatorAssessment
Services PublicService

https://github.com/smart-data-models/Candidates/tree/master/standards/saref4city

SAREF4INMA — 21 models

SAREF4INMA (ETSI TS 103 410-5) targets factory operators, equipment vendors, and supply-chain software vendors who need to trace a manufactured item back to the exact production equipment, batch, raw material, and timestamp that produced it — both inside the factory and after the item has shipped. It gives semantic interoperability between heterogeneous  roduction-equipment vendors and a standard vocabulary for item/batch/material traceability, aligned with Industry 4.0 reference architectures and IEC 62264’s factory/site/area/work-center location model.

Category Models
Identifier hierarchy ID, GTIN8ID, GTIN12ID, GTIN13ID, GTIN14ID, IRDI, UUID
Products / materials Item, ItemBatch, ItemCategory, MaterialBatch, MaterialCategory, Batch, Size
Production equipment ProductionEquipment, ProductionEquipmentCategory, ProductionEquipmentFunction
Factory/location hierarchy Factory, Site, Area, WorkCenter

All 21 examples are drawn from, and cross-consistent with, the single worked “shaver manufacturing” scenario in the ETSI spec’s own clause 4.3 — so a reader can trace one shaver’s full genealogy across every model.

https://github.com/smart-data-models/Candidates/tree/master/standards/saref4inma

Translation notes

  • Inheritance flattened, not duplicated. SAREF4CITY’s four AdministrativeArea subclasses (City, Country, District, Neighbourhood) and SAREF4INMA’s identifier subclasses (GTIN8ID…UUID → ID, WorkCenter → ProductionEquipment) inherit everything and add nothing of their own — each still gets its own candidate model, documenting what it inherits in its description rather than repeating properties, following the precedent set by this repo’s Gaia-X candidate.
  • A documentation/ontology discrepancy, resolved transparently. ETSI TS 103 410-4’s own property table omits refersToFeature from KeyPerformanceIndicatorAssessment, but the published .ttl and the spec’s own figures both include it — the .ttl was treated as authoritative and the property included, with the discrepancy noted in standard-metadata.yaml.
  • Six near-duplicate identifier relationships simplified. SAREF4INMA’s hasGTIN8ID/hasGTIN12ID/…/hasUUID convenience sub-properties were consolidated into one generic hasIdentifier relationship, documented as a simplification.
  • License recorded exactly as found, not guessed — SAREF4INMA’sdct:license points to ETSI’s own forge software license.

Try it, and tell us what’s missing

These are Candidates — first, carefully-sourced translations, not yet promoted to official Smart Data Models subjects. Overlap with existing official subjects hasn’t been checked in detail, and license terms for the specific v2.1.1 releases should be confirmed before promotion.

Browse the models, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/saref4city
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/saref4inma

New pysmartdatamodels Version 0.8.2.0: Semantic Identification for Data Spaces

We are happy to announce a new release of our Python package, pysmartdatamodels, version 0.8.2.0. The headline feature is aimed squarely at data spaces: a new function that can give semantic meaning to a payload even when the party who sent it never provided one.

What’s New in This Version?

Semantic identification for data spaces: identify_or_draft_datamodel()

In a data space, you routinely receive payloads from other participants with no guarantee they follow any particular standard. identify_or_draft_datamodel() takes any such payload and does one of two things:

  • If it recognizes the payload as an existing Smart Data Model, it returns that model’s real schema, together with a full validation of the payload against it.
  • If it doesn’t, it drafts a brand new schema.json on the spot — following the same structural conventions as a real Smart Data Model — so you have a ready-to-review starting point instead of nothing at all.

It accepts the payload in any of the three formats actually used in practice — plain key-values, NGSI-v2 normalized, or NGSI-LD normalized — detecting and handling the right one automatically:

from pysmartdatamodels import pysmartdatamodels as sdm

payload = {
    "id": "urn:ngsi-ld:WeatherObserved:station-042",
    "type": "WeatherObserved",
    "temperature": 21.5,
    "relativeHumidity": 0.6
}

result = sdm.identify_or_draft_datamodel(payload)
print(result["schema"]["source"])   # "existing" -- it recognized WeatherObserved
print(result["schema"]["validation"]["result"])  # True

When the payload’s own “type” doesn’t match anything, you can optionally ask it to try a softer, attribute-based match against the whole catalog before giving up and drafting a new schema:

result = sdm.identify_or_draft_datamodel(payload, fuzzy=True, fuzzy_threshold=0.3)

And when nothing matches at all, the drafted schema isn’t just a bare shape guess — any attribute whose name is already established elsewhere in the catalog (over 160,000 attribute definitions) gets its real description, model reference, and units reused automatically, so only genuinely new attributes are left with a plain TODO placeholder.

A real validate_payload()

validate_payload(datamodel, subject, payload) existed before but didn’t actually validate anything. It now runs full JSON Schema validation against the live schema of the data model you name, confirms the payload’s “type” matches, and separately flags – without failing – any attribute that isn’t part of the official definition.

Reliability and performance fixes

  • generate_sql_schema() no longer crashes on attributes that can hold more than one type (e.g. a Property that can also be a Relationship), and no longer generates colliding enum type names when two unrelated models happen to share an attribute name.
  • validate_data_model_schema() no longer terminates your entire Python process on a bad input — it returns an error result like every other function in the package.
  • The ~160,000-entry attribute database is now cached in memory instead of being re-read from disk on every single function call — noticeably faster for any code calling the per-attribute lookup functions in a loop.

Get the Latest Version

Update your installation with:

pip install --upgrade pysmartdatamodels

➔️ Get the package on PyPI

New pysmartdatamodels Version 0.8.1.0: Refreshed Data (reduced size 20 times with same functionality)

We are happy to announce a new release of our Python package, pysmartdatamodels, version 0.8.1.0, with a refreshed attribute database, a smaller download, and a cleanup of some leftover dead code.

What’s New in This Version?

Refreshed Data, End to End

The package’s bundled data — the official list of data models, the attribute metadata, and the full attribute database — had gone stale. Fixing this surfaced two real issues in our own publication pipeline, now resolved:

  • One data model repository had accidentally been left private, which was silently breaking the daily metadata regeneration every time it ran.
  • The database backing the attribute export (see below) was far less complete than it should have been. It’s now fully backfilled: 164,926 attribute records across all 82 subjects.

As always, you don’t need to upgrade the package just to get fresh data — calling update_data() pulls the latest information directly:

from pysmartdatamodels import pysmartdatamodels as sdm
sdm.update_data()

Smaller Install, Compressed Attribute Database

The full attribute database is now shipped gzip-compressed inside the package (~5MB instead of ~110MB) — the installed package footprint drops from over 100MB to under 10MB. This is fully transparent if you use the documented functions (load_all_attributes(), description_attribute(), etc.) — nothing changes in how you call them.

The same compressed file is now also available for direct download, alongside the existing uncompressed one, from the attribute database export page.

Cleanup

Removed a small piece of dead code in generate_sql_schema() left over from an earlier implementation — no change in behavior, just a cleaner function. Thanks to the community member who originally reported it.

Get the Latest Version

Update your installation with:

pip install --upgrade pysmartdatamodels

➡️ Get the package on PyPI