Value of the srsname attribute of the lonLatEnvelope element is invalid in the response document to a WCS 1.0.0 GetCapabilities request

[nsavard]

The value of the srsname attribute of the lonLatEnvelope is optional and fixed to: "urn:ogc:def:crs:OGC:1.3:CRS84".

The CITE test is: wcs1-0-0:basic_service_elements-general_http_request_rules-4

and the request is:

​http://dev1.lan.mapgears.com/manwe/cgi-bin/mswcs100_ogc_cite?&VeRsIoN=1.0.0&BoGuS=ignored&SeRvIcE=WCS&ReQuEsT=GetCapabilities

The relevant part of theschemas are:

wcscapabilities.xsd:

<!-- =========================================================== --> <xs:element name="CoverageOfferingBrief" type="CoverageOfferingBriefType" substitutionGroup="gml:_GML"/> <!-- =========================================================== --> <xs:complexType name="CoverageOfferingBriefType">

<xs:annotation>

<xs:documentation>Brief description of one coverage avaialble from a WCS. </xs:documentation>

</xs:annotation> <xs:complexContent>

<xs:extension base="AbstractDescriptionType">

<xs:sequence>

<xs:element ref="lonLatEnvelope"/> <xs:element ref="keywords" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

owsBase.xsd:

<!-- =========================================================== --> <xs:element name="lonLatEnvelope" type="LonLatEnvelopeType"/> <!-- =========================================================== --> <xs:complexType name="LonLatEnvelopeBaseType">

<xs:annotation>

<xs:documentation>For WCS use, LonLatEnvelopeBaseType restricts gml:Envelope to the WGS84 geographic CRS with Longitude preceding Latitude and both using decimal degrees only. If included, height values are third and use metre units. </xs:documentation> <xs:documentation>Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. </xs:documentation>

</xs:annotation> <xs:complexContent>

<xs:restriction base="gml:EnvelopeType">

<xs:sequence>

<xs:element ref="gml:pos" minOccurs="2" maxOccurs="2"/>

</xs:sequence> <xs:attribute name="srsName" type="xs:anyURI" use="optional" fixed="urn:ogc:def:crs:OGC:1.3:CRS84"/>

</xs:restriction>

</xs:complexContent>

</xs:complexType> <!-- =========================================================== --> <xs:complexType name="LonLatEnvelopeType">

<xs:annotation>

<xs:documentation>Defines spatial extent by extending LonLatEnvelope with an optional time position pair. </xs:documentation>

</xs:annotation> <xs:complexContent>

<xs:extension base="LonLatEnvelopeBaseType">

<xs:sequence minOccurs="0">

<xs:element ref="gml:timePosition" minOccurs="2" maxOccurs="2"/>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

[tomkralidis]

Done:

• fixed in trunk (r7377)
• fixed in msautotest/wxs (r7378)

Norm: can you verify?

[nsavard]

Replying to tomkralidis:

Done:

• fixed in trunk (r7377)
• fixed in msautotest/wxs (r7378)

Norm: can you verify?

Tom: I'll verify and let you know.

[nsavard]

Replying to nsavard:

Replying to tomkralidis:

Done:

• fixed in trunk (r7377)
• fixed in msautotest/wxs (r7378)

Norm: can you verify?

Tom: I'll verify and let you know.

Tom: I still get an error. Did I misinterpret the schema? Here is the error message for the TEAM engine:

Messages from parser wcs1-0-0:GMLValidatingParser:

error at line 71, column 61:

cvc-complex-type.3.1: Value 'urn:ogc:def:crs:OGC:1.3:CRS84' of attribute 'srsName' of element 'lonLatEnvelope' is not valid with repect to the corresponding attribute use.

error at line 79, column 61:

cvc-complex-type.3.1: Value 'urn:ogc:def:crs:OGC:1.3:CRS84' of attribute 'srsName' of element 'lonLatEnvelope' is not valid with repect to the corresponding attribute use.

error at line 87, column 61:

cvc-complex-type.3.1: Value 'urn:ogc:def:crs:OGC:1.3:CRS84' of attribute 'srsName' of element 'lonLatEnvelope' is not valid with repect to the corresponding attribute use.

3 errors detected.

[tomkralidis]

Norm: I get a perfectly valid response (note this is with the fixed wcsCapabilities.xsd which Alexandre Robin fixed and emailed a few days back (edited schema attached -- I have made absolute refs to the other schemas called for portability).

So you'll want to clarify this w/ CITE.

[nsavard]

Replying to tomkralidis:

Norm: I get a perfectly valid response (note this is with the fixed wcsCapabilities.xsd which Alexandre Robin fixed and emailed a few days back (edited schema attached -- I have made absolute refs to the other schemas called for portability).

So you'll want to clarify this w/ CITE.

I sent the following email to the list. Notice that I did not include the error message and the schemas because they are already part of this bug (see above).

email start I have another issue with WCS 1.0.0 tests on the TEAM engine (​http://cite.geoenterpriselab.com/teamengine/). The wcs1-0-0:basic_service_elements-general_http_request_rules-4 test and some others failed with the message below. The srsName of the lonLatEnvelope element is supposed to be optional and fixed to: "urn:ogc:def:crs:OGC:1.3:CRS84". Our server outputs the exact same string for this attribute in the capabilities response. Tom validated the response with XMLSpy and it validates (see concerned schema below). We are wondering what may be the problem.

Is there any issue with the tests? email end

[tomkralidis]

Norm: can you check again? As per the CITE email, they have fixed this (schema) issue.

[nsavard]

Replying to nsavard:

email start I have another issue with WCS 1.0.0 tests on the TEAM engine (​http://cite.geoenterpriselab.com/teamengine/). The wcs1-0-0:basic_service_elements-general_http_request_rules-4 test and some others failed with the message below. The srsName of the lonLatEnvelope element is supposed to be optional and fixed to: "urn:ogc:def:crs:OGC:1.3:CRS84". Our server outputs the exact same string for this attribute in the capabilities response. Tom validated the response with XMLSpy and it validates (see concerned schema below). We are wondering what may be the problem.

Is there any issue with the tests? email end

Response to this email:

Morris, Charles, E. wrote:

FYI, I've updated the scripts and added an option to select which version of the schemas the server imlpements.

• Chuck

---

From: cite.feedback-bounces+chuck.morris=ngc.com@… cite.feedback-bounces+chuck.morris=ngc.com@… On Behalf Of Morris, Charles, E. Sent: Wednesday, February 13, 2008 5:06 PM To: Kralidis,Tom [Burlington]; Normand Savard; cite.feedback@… Subject: Re: [CITE.feedback] WCS 1.0.0 tests on TEAM engine: srsNameattribute's value of lonLatEnvelope element

It's a very messy situation. In my opinion, schemas on schemas.opengis.net should never be changed, even if they contain errors. Updates should always be posted to a new directory, say wcs/1.0.0_c1 for corrigendum 1.

But since that does not seem to be OGC practice, I would say the best thing to do is post a copy of the schemas you are implementing on your own server and point to them. That way you will be insullated from any problems if someone comes along in the future and "fixes" the schema in such a way that it breaks your implementation.

Since there are now two versions of the WCS 1.0.0 schemas (the original ones and the corrigendum ones), perhaps we need to add an option to the test form to specify which version the server implements.

• Chuck

---

From: Kralidis,Tom [Burlington] Tom.Kralidis@… Sent: Wednesday, February 13, 2008 3:02 PM To: Morris, Charles, E.; Normand Savard; cite.feedback@… Subject: RE: [CITE.feedback] WCS 1.0.0 tests on TEAM engine: srsName attribute's value of lonLatEnvelope element

Hi,

But we are pointing to ​http://schemas.opengis.net/wcs/1.0.0 as our schema base. Should we be pointing to another base here? I don't see anything other than 1.0.0 and 1.1.0 on ​http://schemas.opengis.net/wcs/

---

From: Morris, Charles, E. chuck.morris@… Sent: 13 February, 2008 3:58 PM To: Normand Savard; cite.feedback@… Cc: Kralidis,Tom [Burlington] Subject: RE: [CITE.feedback] WCS 1.0.0 tests on TEAM engine: srsName attribute's value of lonLatEnvelope element

The tests are validating against the original WCS 1.0.0 schemas from document 03-065r6, not the ones from the corrigendum (05-076).

• Chuck

[tomkralidis]

Norm: so this should pass the assertion now, I think?

[nsavard]

Replying to tomkralidis:

Norm: so this should pass the assertion now, I think?

Yes it passed by selecting the schemas from the corrigendum.