Additional semantics from OMS

[KathiSchleidt]

Under TSML, we're working on a CovJSON encoding. To avoid the old approach of pairing an O&M Observation with the Timeseries Coverage for additional semantics on the value being conveyed, we're proposing integrating these OMS concepts within the coverage (conceptually we use rangeType from 19123, on implementation we use an extension to the CovJSON parameters.

This approach entails adding the following attributes from the oms namespace:

• "oms:observingProcedure"
• "oms:observer"
• "oms:host"
• "oms:featureOfInterest"

Note on the duplication of the locational information between coverage domain and oms:featureOfInterest: in the coverage domain, we can only provide a point location. The target of the oms:featureOfInterest can then be a more fully fleshed out feature, including more detailed geo info (e.g. polygons).

[jonblower]

This looks sensible and valuable to me - and I think it's possible with the existing spec, assuming that the oms prefix can be registered. So is this issue essentially asking for that prefix to be registered?

Regarding the location information, you can use a PolygonSeries coverage type if you want to express that the coverage domain is a polygon. But I do appreciate that you might want to describe the feature of interest in more detail.