Closed coim32 closed 4 months ago
linking Jinsongdi Yu into the conversation, he has done the test suite.
@Jin: any ideas? Would you want to subscribe to this git as well to stay in the loop?
-Peter
On 04.04.20 01:27, coim32 wrote:
request has wcs:Extension element after wcs:DimensionTrim, is it valid when validating the request against the XSD? shouldn't wcs:Extension be the first child element under wcs:GetCoverage?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/opengeospatial/ets-wcs20/issues/91, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABOR5DQU6ZF5JFRDNKYIJZDRKZWEPANCNFSM4L4QNO3Q.
-- Dr. Peter Baumann
- Executive Director, rasdaman GmbH Bremen (HRB 26793) www.rasdaman.com, mail: baumann@rasdaman.com tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
- Professor of Computer Science, Jacobs University Bremen www.faculty.jacobs-university.de/pbaumann mail: p.baumann@jacobs-university.de tel: +49-421-200-3178, fax: +49-421-200-493178 "A brilliant idea is a job halfdone."
is there an xsd to validate a GetCoverage request that shows if extension element has a constrain in the order it can appear? xs:all can be used to indicate there is no order on the elements as test cases is defined but the elements DimensionSlice and DimensionTrim require maxOccurs="unbounded" which is not allowed in xs:all
@coim32 Please provide a link to the GetCapabilities URL of the server, to help us understand the question more clearly.
request has element after , is it valid when validating the request against the XSD?
shouldn't be the first child element under ?