fix #62 by specifying href format #92
Conversation
| NOTE: The platform can be another `System` (e.g. a UAV or a station), but can also be any feature (e.g. a building or a tree). | ||
|
|
||
| When referencing a deployed local system resource via `deployedSystems`, the system SHALL be identified using a URN. | ||
| When referencing an external system resource the system SHALL be identified using a URL. |
There was a problem hiding this comment.
Since this is somewhat encoding specific, I think it should be specified in the encoding sections instead:
- For GeoJSON, add a requirement below the association mapping table
- For SensorML-JSON, add a requirement below the association mapping table
In the requirements, we should refer to the System uniqueIdentifier instead of just saying "a URN".
Also, if you look at Deployment examples in GeoJSON and SensorML-JSON, you will see that both href and uid can be provided in the schema. So I think when you read it back, the uid property already contains the URN and the href can remain the URL. However, what I had in mind (sorry I did not express this clearly in the issue), is that on insertion, to simplify things for the server, we could mandate that the href is the UID instead of the URL when linking to a local system (whereas for remote systems, either the href URL only, or both URL and UID would be provided).
Does this make sense?
fixes #62