Issue 66 in ioostech: SensorML component encoding not compliant with 09-033 OWS-6 SensorML Profile for Discovery

[ioos...@googlecode.com]

Status: New
Owner: sh...@axiomalaska.com
Labels: Type-Defect Priority-Low

New issue 66 by sh...@axiomalaska.com: SensorML component encoding not
compliant with 09-033 OWS-6 SensorML Profile for Discovery
http://code.google.com/p/ioostech/issues/detail?id=66

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/SML-DescribeSensor-Network.xml#160

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

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

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings