search

valentinedwv / ioostech

Automatically exported from code.google.com/p/ioostech
0 stars 0 forks source link

SensorML component encoding not compliant with 09-033 OWS-6 SensorML Profile for Discovery #66

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Our current method of encoding child components as sml:Systems in SensorML [1] 
[2] is incompatible with 09-033 OWS-6 SensorML Profile for Discovery [3], which 
limits components to use xlink:href or use sml:Component (rather than 
sml:System). sml:Component is almost exactly the same as sml:System, so we 
could probably switch them out without any loss or change of information. 
However, we may only want to do this if we aim to eventually be fully 
compatible with the discoverability profile. Several other changes in the 
templates would have to be made to do so (e.g. including an sml:capabilities 
bounding box swe:Envelope, see the profile doc for details).

[1] 
https://code.google.com/p/ioostech/source/browse/trunk/templates/Milestone1.0/SM
L-DescribeSensor-Network.xml#160

[2] 
https://code.google.com/p/ioostech/source/browse/trunk/templates/Milestone1.0/SM
L-DescribeSensor-Station.xml

[3] 
http://portal.opengeospatial.org/files/?artifact_id=33284&passcode=wnj8h1z40n071
fy1qy9f

Original issue reported on code.google.com by sh...@axiomalaska.com on 13 Mar 2014 at 3:37