Comments (4)
dstenger
commented on July 28, 2024
TEAM Engine gives following error message:
Test getcapabilities:normative-schema type Mandatory default result Passed (s0102/d711e379_1/d3471e26_1/d3471e98_1)
Assertion: The normative content of the schema document referred to by the schemaLocation attribute in the capabilities document is identical to the normative content of the on-line schema referred to in Annex E.1.
Context:
Label:
Value: WMS_Capabilities element
Message d3471e677_1:
Error: The schema does not define xs:attribute lang correctly.
Message d3471e677_2:
Error: The schema does not define xs:attribute space correctly.
Message d3471e677_3:
Error: The schema does not define xs:attribute base correctly.
Message d3471e677_4:
Error: The schema does not define xs:attribute id correctly.
Message d3471e677_5:
Error: The schema does not define xs:attributeGroup specialAttrs correctly.
Message d3471e677_6:
Error: The schema does not define xs:attribute type correctly.
Message d3471e677_7:
Error: The schema does not define xs:simpleType typeType correctly.
Message d3471e677_8:
Error: The schema does not define xs:attribute href correctly.
Message d3471e677_9:
Error: The schema does not define xs:simpleType hrefType correctly.
Message d3471e677_10:
Error: The schema does not define xs:attribute role correctly.
Message d3471e677_11:
Error: The schema does not define xs:simpleType roleType correctly.
Message d3471e677_12:
Error: The schema does not define xs:attribute arcrole correctly.
Message d3471e677_13:
Error: The schema does not define xs:simpleType arcroleType correctly.
Message d3471e677_14:
Error: The schema does not define xs:attribute title correctly.
Message d3471e677_15:
Error: The schema does not define xs:simpleType titleAttrType correctly.
Message d3471e677_16:
Error: The schema does not define xs:attribute show correctly.
Message d3471e677_17:
Error: The schema does not define xs:simpleType showType correctly.
Message d3471e677_18:
Error: The schema does not define xs:attribute actuate correctly.
Message d3471e677_19:
Error: The schema does not define xs:simpleType actuateType correctly.
Message d3471e677_20:
Error: The schema does not define xs:attribute label correctly.
Message d3471e677_21:
Error: The schema does not define xs:simpleType labelType correctly.
Message d3471e677_22:
Error: The schema does not define xs:attribute from correctly.
Message d3471e677_23:
Error: The schema does not define xs:simpleType fromType correctly.
Message d3471e677_24:
Error: The schema does not define xs:attribute to correctly.
Message d3471e677_25:
Error: The schema does not define xs:simpleType toType correctly.
Message d3471e677_26:
Error: The schema does not define xs:attributeGroup simpleAttrs correctly.
Message d3471e677_27:
Error: The schema does not define xs:group simpleModel correctly.
Message d3471e677_28:
Error: The schema does not define xs:complexType simple correctly.
Message d3471e677_29:
Error: The schema does not define xs:attributeGroup extendedAttrs correctly.
Message d3471e677_30:
Error: The schema does not define xs:group extendedModel correctly.
Message d3471e677_31:
Error: The schema does not define xs:complexType extended correctly.
Message d3471e677_32:
Error: The schema does not define xs:element title correctly.
Message d3471e677_33:
Error: The schema does not define xs:attributeGroup titleAttrs correctly.
Message d3471e677_34:
Error: The schema does not define xs:group titleModel correctly.
Message d3471e677_35:
Error: The schema does not define xs:complexType titleEltType correctly.
Message d3471e677_36:
Error: The schema does not define xs:element resource correctly.
Message d3471e677_37:
Error: The schema does not define xs:attributeGroup resourceAttrs correctly.
Message d3471e677_38:
Error: The schema does not define xs:group resourceModel correctly.
Message d3471e677_39:
Error: The schema does not define xs:complexType resourceType correctly.
Message d3471e677_40:
Error: The schema does not define xs:element locator correctly.
Message d3471e677_41:
Error: The schema does not define xs:attributeGroup locatorAttrs correctly.
Message d3471e677_42:
Error: The schema does not define xs:group locatorModel correctly.
Message d3471e677_43:
Error: The schema does not define xs:complexType locatorType correctly.
Message d3471e677_44:
Error: The schema does not define xs:element arc correctly.
Message d3471e677_45:
Error: The schema does not define xs:attributeGroup arcAttrs correctly.
Message d3471e677_46:
Error: The schema does not define xs:group arcModel correctly.
Message d3471e677_47:
Error: The schema does not define xs:complexType arcType correctly.
Message d3471e677_54:
Error: The schema does not define element OnlineResource correctly.
Result: Failed
from ets-wms13.
dstenger
commented on July 28, 2024
The test compares the WMS schema referenced in the capabilities with the one on http://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd.
The schema location in the capabilities looks like this:
...xsi:schemaLocation="http://www.opengis.net/wms http://ws.cadcorp.com/ogctest/ogctest.exe?GetSchema&name=OGC/wms/1.3.0/capabilities.xsd...
The schema is reachable via the referenced URL if the ampersand is escaped.
Further analysis should be done if the ampersand in the query part leads to the described error.
from ets-wms13.
lgoltz
commented on July 28, 2024
As dstenger said not the capabilities are validated but the schemas from the schemaLocation in the capabilities are compared with the one from http://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd
As far as I see a lot of the errors "The schema does not define...") are defined in the xlink schema http://www.w3.org/1999/xlink.xsd (which is referenced in http://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd). But they are missing in the xlink schema http://ws.cadcorp.com/ogctest/ogctest.exe?GetSchema&name=OGC/xlink/1.0.0/xlinks.xsd (The schemaLocation in http://ws.cadcorp.com/ogctest/ogctest.exe?request=GetCapabilities&service=WMS contains http://ws.cadcorp.com/ogctest/ogctest.exe?GetSchema&name=OGC/wms/1.3.0/capabilities.xsd importing this xlink schema) .
So, I don't think the ampersand as entity (which is required for xml) is the problem but the referenced schema files (as the test says).
Why do include your own schemas?
from ets-wms13.
dstenger
commented on July 28, 2024
The issue has been solved by updating the xlink.xsd referenced in the service.
from ets-wms13.
Related Issues (20)
- Issues about the Compliance Testing HOT 4
- GetMap request is not tested for mandatory version parameter HOT 4
- Add template to get an XML/JSON response via rest endpoint HOT 1
- What status codes are expected in the getmap:exceptions module? HOT 1
- WMS 1.3.0 Compliance Test Failed Although the Response Contains the Required Code HOT 9
- How to test view service which doesn't contain "Blue Lake" test data set? HOT 3
- Tests are always run exhaustively HOT 4
- Expected layer names should be listed in the Test Dataset Description
- Update the scripts to remove cite: prefix from the Layer Names HOT 7
- Tests basic:transparent-true and queryable:std-data-queryable are failing when non mandatory cite prefix is missing in layer name HOT 1
- Run Command shell (terminal) failed.
- Test GetMap crs-inherited does not handle AUTO correctly
- GetMap requests do not pass correct values for layers parameter HOT 2
- WMS 1.3.0 interactive tests are failing on the online TEAM Engine platform HOT 8
- Worlfiles for testing WMS 1.3.0 raster conformance link does not exist HOT 4
- Wrong test description for test WMS basic:layer-order HOT 4
- OGC WMS 1.3.0 test gives "validate-using-schemaLocation" failure in the test result for an INSPIRE View Service WMS HOT 4
- OGC test gives "exceptions-default FAILED" in the test result for an INSPIRE View Service WMS HOT 2
- OGC WMS 1.3.0 test fails for multiple CRS values in the test result for an INSPIRE View Service HOT 1
- Test time:time-current-interval finishes with status "Continue" when using TEAM Engine 5.7 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ets-wms13.