Now all data models have an interactive specification. (As long as they have examples)
This is the first step to deeper interactive services for every data model contributed.
See the example for weatherForecast.
** issue with HL7/FHIR-R4 models validation : tests failed with "*** schema.json file not found"
** generate_sql_schema - enum clashes
** AirQualityObserved - simplified JSON-LD examples fail JSON Schema validation
** AirQualityObserved SQL schema missing refDevice column
** AirQualityObserved SQL schema - as is a keyword
** feat(PointOfInterest): Add openingHours and openingHoursSpecification properties
** Add field to store POI opening hours information (e.g. openingHours)
** feat(PointOfInterest): Add openingHours and openingHoursSpecification properties
** 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
** Proposal: canonical PAR attribute naming and unit encoding policy
** Proposal: add stemDiameterVariation attribute in Agrifood models
** Add soilPh and normalize line endings (LF)
** Add soilPh and normalize line endings (LF)
** add "tractionBatteryCapacity" property (VehicleModel)
** added examples and needed files for all resource types of HL7/FHIR-R4
** add "tractionBatteryCapacity" property (VehicleModel)
** added examples and needed files for all resource types of HL7/FHIR-R4
** 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
** feat: add properties to DataService data model
** Extend schemas for Dataset and DataService from 2.1.1 to 3.0.0
** ParticipantAgent/schema.json: credentialStore $ref points to a non-existent definition
