This is just a summary for the participants of the FIWARE global summit 2026. See you there in Menton.
Smart Data Models’ Candidates repository has grown a lot over the past few weeks. This post is a single roundup of everything in it today: 29 source standards, translated into 385 NGSI-LD / NGSI-v2 candidate data models, each shipping the full Candidates artifact set — a JSON Schema, an NGSI-LD @context, and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), validated against its own schema.
Every one of these is a Candidate: a first, carefully-sourced translation from a real external ontology or specification, not yet promoted to an official Smart Data Models subject. Several carry known open items — license reconciliation, overlap checks against existing official subjects, or cross-standard naming collisions — noted in each standard’s own standard-metadata.yaml and summarized below where relevant.
When real use of the candidates is found then it will be come official smart data models in the usual repositories. WE are trying to help adoption of open standards but only when the standards are actually used.
By the numbers
| Source standards translated | 29 |
| Candidate data models | 385 |
| Largest single standard | Gaia-X Ontology (165 models) |
| Standards from the EDINT data space | 20 |
| Domains touched | Smart Cities, Transportation, Energy, Environment, Cloud/Data Spaces, Cross-Sector Manufacturing, Building |
The full list
Smart cities & urban infrastructure (EDINT data space)
The bulk of recent growth comes from systematically translating the EDINT (Espacio de Datos para las Infraestructuras Urbanas Inteligentes) family of ontologies — 20 standards covering nearly every domain a Spanish local government manages.
| Standard | Models | What it covers |
|---|---|---|
edint-infraestructura |
19 | Municipal facilities, sensors, observations, violations, traffic incidents, control/measuring equipment, regulated zones |
edint-alumbrado-publico |
12 | Public street lighting: posts, luminaires, lamps, control centers, energy consumption |
edint-trafico |
7 | Standalone traffic ontology: street sections, incidents, control/measuring equipment, observations |
edint-vehiculos-compartidos |
7 | Shared-mobility vehicles, stations, docks, routes and waypoints |
edint-catastro |
6 | The Spanish Cadastre: parcels, properties, constructions, references, renovations |
edint-aparcamiento |
5 | On-street and off-street parking, fees, spots, spot groupings |
edint-censo-locales |
5 | Commercial premises census: spaces, entities, permits, terraces, aggregations |
edint-fotovoltaica |
5 | Photovoltaic systems, meters, generation observations, contracts, rates |
edint-suministro |
5 | Utility supply points, meters, consumption, contracts, rates |
edint-gestion-residuos |
4 | Waste collection points (mobile & permanent), containers, management facilities |
edint-medio-ambiente |
3 | Generic environmental sensor platforms, sensors and observations |
edint-censo-vehiculos |
2 | Vehicle registry and access/parking permits |
edint-promocion-comercial |
2 | Commercial promotion campaigns and events |
edint-servicios-publicos |
2 | Public services and their administrative procedures (CPSV-AP) |
edint-agenda |
1 | City events published in municipal public agendas |
edint-contaminacion-acustica |
1 | Noise pollution observations |
edint-oferta-inmobiliaria |
1 | Real estate listings (sale, rent, transfer) |
edint-organizaciones |
1 | Spanish public administration organizations and org charts |
edint-zona-regulatoria |
1 | Regulated zones (low-emission, parking, pedestrian, historical center, …) |
edint-turismo |
11 | SEGITTUR’s Core Tourism Ontology: accommodation, historical/cultural resources |
Cross-sector & building
| Standard | Models | What it covers |
|---|---|---|
cityjson-v2 |
33 | All 33 CityJSON v2.0.2 City Object types: buildings, bridges, tunnels, transportation, vegetation, water, land use |
brick-schema |
10 | Building automation/IoT metadata: points, equipment, and their relationships |
gaiax-ontology-v2111 |
165 | Gaia-X Trust Framework: cloud/infrastructure offerings, connectivity metrics, legal/compliance/credential vocabulary |
untp-v0.8.0 |
2 | UN Transparency Protocol Digital Product Passport and Product |
Transportation
| Standard | Models | What it covers |
|---|---|---|
era-rinf |
38 | ERA Register of Infrastructure: EU rail network topology, tracks, signalling, electrification |
era-evr |
14 | ERA European Vehicle Register: individual authorised rail vehicles |
era-eradis |
14 | ERA document/certification register |
era-eratv |
8 | ERA European Register of Authorised Vehicle Types |
madrid-accidentes-trafico |
1 | Madrid City traffic accident records |
A few things worth knowing before you build on these
- License status varies. Most EDINT candidates are CC-BY-4.0 (matching Smart Data Models’ own convention); a handful of others (
edint-infraestructura,edint-turismo,edint-zona-regulatoria) are CC-BY-SA-4.0 from their source and haven’t been reconciled yet.madrid-accidentes-trafico‘s license isn’t stated in its source at all. Check each standard’slicenseNotebefore using it beyond evaluation. - A few entity names collide across standards. Because several EDINT ontologies independently reference the same real-world concepts (a regulated zone, a vehicle, a parking facility, an organization, a cadastral property, a “permit”), more than one candidate defines an NGSI-LD type with the same name but a different property set. Each collision is documented in the relevant
standard-metadata.yaml— most likely resolution is consolidating on the fuller, more authoritative definition once these move past Candidate status. - Every translation favors real, sourced data over invented examples wherever the original specification provided any — actual open datasets, published sample instances, or real government records, not synthetic placeholders, whenever available.
Browse, and tell us what’s missing
👉 smart-data-models/Candidates
Each standard’s directory under standards/ has its own standard-metadata.yaml with full translation notes, scope decisions, and known caveats. Open an issue or send a PR if you spot something worth fixing before promotion.
