Usecases Need Updating

[EricLo-417]

Hello OGC Connected System People,

I am currently making an implementation of api and wanted to look some example JSONs. I noticed that the usecases may be out of date with the standards documents.

For example,
usecases/hydro/groundwater/systems/waterlevel-sensor-geojson.json

{
  "type": "Feature",
  "id": "8ewqgtmftd61",
  "geometry": null,
  "properties": {
    "uid": "urn:x-usgs:sensors:4001",
    "name": "Water Level Sensor #4001",
    "description": "Water level sensor mounted in ground water well",
    "featureType": "http://www.w3.org/ns/sosa/Sensor",
    "assetType": "http://www.opengis.net/def/x-OGC/Equipment",
    "procedure@link": {
      "href": "https://data.example.org/api/procedures/otxtb9yvouo1?f=json",
      "uid": "urn:x-usgs:datasheets:WL400",
      "type" : "application/geo+json"
    },
    "attachedTo@link": {
      "href": "https://data.example.org/api/systems/tqjswq53bha6?f=json",
      "uid": "urn:x-usgs:platforms:well:384824104332601",
      "type" : "application/geo+json"
    }
  }
}

But if you look at the encoding guidelines "procedure@link" and "attachedTo@Link" do not exist for geojson. I believe these should be in links. This may be the sensorML version

[SpeckiJ]

nice spot, the example from the usecase seems to be somewhat of a blend between SensorML (which has the keyword attachedTo) and the GeoJson Encoding (which uses "type": "Feature").

I suspect the usecase was developed before the JSON Encoding was actually specified, and not updated when the specification actually changed

TODO:

• check all usecases whether they actually conform to the current spec, or still reference/user/conform-to outdated work-in-progress versions