Rethink usage of gml:id in sensorML
We had quite a discussion about the gml:id
entries in the sensorML with @rainer.haener.
That affects different aspects of the gml id:
-
When we are in trouble with duplicated gml ids, we should either split the document in different parts & link to that with xlink:href, or we should avoid them (when they are not useful). Background here is that the gml:id is only unique within the document ifself. So it makes only sense if we want to identify the physical system within that document. For identification outside of that, we have the identifiers section & entries that help much, much more.
-
The initial reason why there are gml:ids is to filter for specific objects within the document. This affects mostly WFS (where the gml:id is much more used than in our sensorML).
-
The values of the gml ids - if we really would like to search with them - should be based on a system that can be understood by the user. So using just our internal id inside doesn't make any sense, as the user will not know those normally. What makes more sense here is to use the urns for them (devices: manufacturer-model-serialnumber, platforms: platformtype,shortname, configuration: None yet) as those could be constructed by a user by himself/herself.
So the task is to adjust the usage of the gml ids accordingly, so that "it makes sense"*.