IUDX joins the steering board of Smart Data Models initiative. This agreement will allow FIWARE and the IUDX to collaborate on data models suitable for use in smart city applications. This work will be done in conjunction with the ongoing joint activity between TM Forum — an alliance of 850+ global companies working together to break down technology and cultural barriers between digital service providers, technology suppliers, consultancies and systems integrators — and FIWARE.
Validate a payload
python package pysmartdatamodels
-
Subscribe to Our Newsletter
MasterSheet
PR and issues
updated every 10 minutes (if empty, it means we are updating, please refresh in couple of seconds)
data-models** fix: wrap column names in generated SQL schema files
** generate_sql_schema - support for anyOf
** fix issue #84 (loading files from base folder)
** issue with HL7/FHIR-R4 models validation : tests failed with "*** schema.json file not found"
** Remove redundant type statement list
** generate_sql_schema - sql_type_statement unused
** generate_sql_schema - enum clashes
** generate_sql_schema column name wrapping
data-models** fix: wrap column names in generated SQL schema files
** fix issue #84 (loading files from base folder)
** Remove redundant type statement list
dataModel.Environment** AirQualityObserved - simplified JSON-LD examples fail JSON Schema validation
** AirQualityObserved SQL schema missing refDevice column
** AirQualityObserved SQL schema - as is a keyword
dataModel.PointOfInterest** feat(PointOfInterest): Add openingHours and openingHoursSpecification properties
** Add field to store POI opening hours information (e.g. openingHours)
dataModel.PointOfInterest** feat(PointOfInterest): Add openingHours and openingHoursSpecification properties
dataModel.Device** Proposal: add batteryTemperature to Device model for hardware diagnostics telemetry
** Device SQL schema missing refDeviceModel column
** SQL schema - clashing enums across repositories
** Modbus model - missing SQL schema
** Camera model - SQL schema issue with on column
dataModel.Agrifood** Proposal: canonical PAR attribute naming and unit encoding policy
** Proposal: add stemDiameterVariation attribute in Agrifood models
** Add soilPh and normalize line endings (LF)
dataModel.Agrifood** Add soilPh and normalize line endings (LF)
incubated** add "tractionBatteryCapacity" property (VehicleModel)
** added examples and needed files for all resource types of HL7/FHIR-R4
incubated** add "tractionBatteryCapacity" property (VehicleModel)
** added examples and needed files for all resource types of HL7/FHIR-R4
dataModel.DCAT-AP** SQL schema files - duplicate column names
** feat: add properties to DataService data model
** Extend schemas for Dataset and DataService from 2.1.1 to 3.0.0
dataModel.DCAT-AP** feat: add properties to DataService data model
** Extend schemas for Dataset and DataService from 2.1.1 to 3.0.0
dataModel.ERA-
Subscribe. mail once a week
Go to a data model
Type part of the name and it will be filteredCategories
- Agrifood (9)
- AI (1)
- Aquaculture (2)
- Battery (3)
- Coding (6)
- contribution (7)
- Cross Sector (245)
- Device (2)
- Energy (5)
- Environment (11)
- Governance (46)
- GreenEnergy (2)
- Internal (24)
- Manufacturing (3)
- PointOfInterest (3)
- Robotics (4)
- Smart Cities domain (262)
- Smart Energy domain (206)
- Smart Environment domain (210)
- Smart Manufacturing domain (195)
- Smart Robotics domain (191)
- Smart Water Domain (219)
- Smart-Sensoring domain (204)
- SmartAeronautics (176)
- SmartAgrifood domain (197)
- SmartDestinations (197)
- SmartHealth (133)
- SmartLogistics (82)
- Transportation (9)
- Uncategorized (5)
- Water (11)
- Weather (6)
Candidates updates- fix: correct schemaVersion to 0.0.1 and add all 4 required example fo… 27/07/2026fix: correct schemaVersion to 0.0.1 and add all 4 required example formats Two process fixes applied retroactively to all 23 existing models across the three published standards (edint-infraestructura, edint-turismo, madrid-accidentes-trafico): 1. $schemaVersion corrected from 0.1.0 to 0.0.1 -- the correct starting version for a first-try candidate. 2. Every model now ships all four required example […]
- feat(madrid-accidentes-trafico): add AccidentInvolvedPerson candidate… 27/07/2026feat(madrid-accidentes-trafico): add AccidentInvolvedPerson candidate, tested against real 2023 data Source: PDF field specification (Direccion General de la Policia Municipal, Madrid, Nov 2023), NOT an ontology -- built directly from the 3-page spec and then cross-checked against the real published 2023 CSV (48,830 rows). Single flat entity (AccidentInvolvedPerson), matching the source dataset's own one-row-per-involved-person structure rather […]
- feat(edint-turismo): add 11 candidate models from SEGITTUR's Core Tou… 22/07/2026feat(edint-turismo): add 11 candidate models from SEGITTUR's Core Tourism Ontology Source repo: https://github.com/EDINT-Ontologia/edint-ontologia-turismo, which contains no ontology of its own -- only usage examples. The actual formal ontology (388 classes, SHACL shapes, SKOS vocabularies) is published externally by SEGITTUR at https://ontologia.segittur.es/turismo/def/core/. This candidate translates only the 11 classes the EDINT repository actually demonstrates with real […]
- fix: correct schemaVersion to 0.0.1 and add all 4 required example fo… 27/07/2026


