According to the the main site, the best way to validate a payload is to simply use https://www.jsonschemavalidator.net/ in combination with the JSON schema files on Github. However, the AirQualityObserved schema only supports the keyValues representation -- which as far as I know, is the least important serialization format of NGSI-LD data.

For instance, the schema file specifies:

"dateObserved": {
  "type": "string",
  "description": "Property. The date and time of this observation in ISO8601 UTCformat. Model:'https://schema.org/Text' "
}

Which conflicts with the current data example:

"dateObserved": {
  "type": "Property",
  "value": "2016-03-15T11:00:00/2016-03-15T12:00:00"
}

With the following error message:

Invalid Type. Expected String but got Object.

Would it be possible to provide schema files for both the keyvalues and the normalized formats?
Additionally, it may be worth considering to use SHACL (or ShEx) instead of JSON Schema, as these languages contain useful LD-specific features that JSON Schema wasn't designed for.

The specification does not cover measurements or attributes regarding Noise Level observations, while in the examples we have these:

  "LAS": 91.6,  
  "LAeq": 67.8,  
  "LAeq_d": 65.4,  
  "LAmax": 94.5,  

The AirQualityObserved model comprises different date... fields:

• dateCreated
• dateModified
• dateObserved

However, only the dateObserved field lacks a format specification, in contrast to the common-schema, which includes a "format": "date-time". Could the "format": "date-time" be added to the specification of the AirQualityObserved model?

Reference Links:

• AirQualityObserved spec.md
• AirQualityObserved schema.json
• common-schema.json

Description

There are some problems in the generation of the spec documents specially related to "Nitrogen monoxide detected" it should be "no" but the result is "False"

Files affected

• spec.md
• spec_DE.md
• spec_ES.md
• spec_FR.md