Comment #2 on issue 70 by
abir...@gmail.com:
OK, it looks like we can fix it in 2 ways:
Option 1 is to rephrase clause (a) to match the OGC CITE test assertion:
"GetObservation requests made for each 'procedure' element advertised in
the Capabilities document produce the responses with <om:procedure> values
that (a) match the 'procedure' values OR ARE A SUBSET OF THE PROCEDURE
VALUES specified in the requests, and (b) are in a form of URN that
conforms to the IOOS Conventions for Observing Asset Identifiers."
Outcome: fixes the "network" issue, since station procedures are members
(i.e. subset) of the network process; however, the "sensor" issue stays
broken.
Option 2 is to rephrase the assertion to focus the assertion upon a single
station/platform:
"GetObservation requests made for each SINGLE PLATFORM/STATION 'procedure'
element advertised in the Capabilities document produce the responses with
<om:procedure> values that (a) match the 'procedure' values specified in
the requests, and (c) are in a form of URN that conforms to the IOOS
Conventions for Observing Asset Identifiers."
Outcome: fixes both "network" and "sensor" issues by moving them out of the
scope of the assertion.
Option 2 seems more correct just because I believe that the test in
question was really supposed to complement
the "getObservation:IOOS-SOS.GetObservation-ResponseMatchingProcedureData.2"
test, which targets a networks of stations, and the assertion was just
poorly worded.