When an URI is used to specify a procedure in a DescribeSensor request to a SOS server 1.0.0, the requested procedure is not found

[nsavard]

A DescribeSensor? request to a SOS server 1.0.0 with a procedure written as an URI format (urn:ogc:def:procedure:604) returns an exception saying that this procedure is not found. If only the procedure number (604) is typed in, the procedure is found. The server should accept a procedure written as an URI since the DescribeSensor? schema specifies "anyURI" as the type for a procedure element.

The request is:

URL:  http://dev1.lan.mapgears.com/manwe/cgi-bin/mssos100_ogc_cite? Body:

<DescribeSensor? xmlns=" http://www.opengis.net/sos/1.0"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ctl="http://www.occamlab.com/ctl" xmlns:parsers="http://www.occamlab.com/te/parsers" xmlns:ogc="http://www.opengis.net/ogc" xmlns:sos="http://www.opengis.net/sos/1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:te="java:com.occamlab.te.TECore" xmlns:sosFunctions="https://cite.opengeospatial.org/sos-1.0.0/src/ctl/functions.xml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wms="http://www.opengis.net/wms" xmlns:gml="http://www.opengis.net/gml" xmlns:om="http://www.opengis.net/om/1.0" xmlns:ows="http://www.opengis.net/ows/1.1" outputFormat="text/xml; subtype=sensorML/1.0.0" service="SOS" version="1.0.0">

<procedure>urn:ogc:def:procedure:604</procedure>

</DescribeSensor>

The response is:

<?xml version="1.0" encoding="ISO-8859-1"?> <ows:ExceptionReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ows="http://www.opengis.net/ows/1.1" version="1.0.0" xml:lang="en-US" xsi:schemaLocation="http://www.opengis.net/ows/1.1  http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd">

<ows:Exception exceptionCode="InvalidParameterValue?" locator="procedure">

<ows:ExceptionText>msSOSDescribeSensor(): SOS server error. procedure urn:ogc:def:procedure:604 not found.</ows:ExceptionText>

</ows:Exception>

</ows:ExceptionReport>

The CITE test used to verify this case is: describeSensor:core-SOS.DescribeSensor-ResponseMatchingResponseFormat.1

[tomkralidis]

Fixed:

• in trunk in r7438
• in msautotest/wxs in r7439
• updated  http://mapserver.gis.umn.edu/docs/howto/sos_server

Norm: can you check and verify?

[nsavard]

Replying to tomkralidis:

Fixed: * in trunk in r7438 * in msautotest/wxs in r7439 * updated  http://mapserver.gis.umn.edu/docs/howto/sos_server Norm: can you check and verify?

I'll check.

[nsavard]

Tom: The URI format urn:ogc:def:procedure:604 now is accepted. I have a question. Since the data type for the procedure element is "anyURI" should we accept "604" and " http://dev1.lan.mapgears.com/manwe/sml/604.xml" as well?

[tomkralidis]

We should, in the sense that we shouldn't expect URLs themselves to follow the URN scheme of SOS, just the identifiers themselves. In other words, let providers names files as they wish.

Is this okay? Can we close this ticket?

[tomkralidis]

Norm: to clarify on comment:3, we should not accept "604" because the procedure identifiers are supposed to be fetched from the Capabilities XML, so the client will only ever know about the anyURI-ish id of the procedure.

[nsavard]

Re: comment:5

Tom: I have a better understanding of what you mean now. You can close it.