Overview

Capabilities of conformance level 1

ISO19139 application schemas A.1 Minimum conformance with this Technical Specification requires that geographic metadata instance (XML) documents can be validated without error against the XML schemas. While many tools are available to test validation of XML instance documents against provided XML Schemas, it is important to understand that not all validation tools implement the full W3C XML Schema recommendation and not all validation tools interpret the W3C XML Schema recommendation in the same manner. It is recommended that a tool with strict interpretation of XML Schema and full support for the W3C XML Schema recommendation be used to ensure conformance.

“Table 1 in the ISO19139 specfication defines the conformance classes related to ISO19139 application schemas. In this test suite mandatory conformance requirements are checked, and every ISO19139 instance document is thoroughly validated against all referenced application schemas. However, the classes dealing with less commonly used types of objects are not covered by the current test suite. Table 1 below provides the name of the conformance classes, references to the relevant clause in the abstract test suite (ATS) in Annex A, and information about its implementation status.”

Capabilities of conformance level 2

1. A.2.1 By-Value or By-Reference or gco:nilReason Validation of XML instance documents against the schemas described in this document is not all that is required for conformance to this specification. However, because of the design of the XCPT the property element may have no content or attributes, or it may have both content and attributes and still be XML Schema-valid. It is not possible to constrain the co-occurrence of content or attributes. Some mechanism in addition to an XML Schema validation (e.g., Schematron, XSL Transformations) must be used to restrict a property to be exclusively by-value, or by-reference, or expressing a NULL reason.

2. A.2.2 Co-Constraints XML 1.0 does not support the enforcement of certain types of constraints. For example, co-constraints such as the requirement that an ‘extent’ in the form of an ‘EX_GeographicBoundingBox’ or ‘EX_GeographicDescription’ be used in the ‘MD_DataIdentification’ object when the ‘hierarchyLevel’ of ‘MD_Metadata’ is equal to “dataset” can not be enforced with an XML schema.

Capabilities of conformance level 3

A.3 Against user define Schematron This conformance level validates an XML instance documents against a schematron uploaded by the users. This conformance level lets users test the XML instance against conformance 1 and 2 along with conformance 3 to validate the XML agsint the technical specifications as well as any other rules that are defined in the user entered schematron.

Validating via a Web User Interface

The web site is available here: http://cite-dev-03.opengeospatial.org/teamengine/

It requires an easy registration and a login process.

Validating via an HTTP Request

• URL: http://cite-dev-03.opengeospatial.org/teamengine/rest/suites/iso19139/1.0/run

• Parameters can be:

  • iut = Instance (or implementation) under test (Mandatory)
  • ics = An implementation conformance statement that indicates which conformance classes or options are supported.
  • sch = A URI that refers to the schematron and when ics=3 then sch is mandatory.

  NOTE: Ampersand (‘&’) characters must be percent-encoded as ‘%26’

For example::

  http://cite-dev-03.opengeospatial.org/teamengine/rest/suites/iso19139/1.0/run?iut=http://hydro10.sdsc.edu/metadata/Raquel_Files/37E28B7A-0406-449B-8A45-3988AE675368.xml

Example with sch:

  http://cite-dev-03.opengeospatial.org/teamengine/rest/suites/iso19139/1.0/run?iut=http://hydro10.sdsc.edu/metadata/Raquel_Files/1E97BD2D-0FDD-4BAC-8DEA-FEB57AB53A6E.xml&sch=http://cite-dev-03.opengeospatial.org/teamengine/checkScopeOfXmlFile.sch

 In GET Request : iut and sch are URI's

 In POST Request : iut and sch are keys of the files attached in the POST Body

To test via GET API :

Using the GET API you can send the URL’s as query parameters. For ics=2 (i.e. Conformance level 2) iut (i.e. Metadata URL) is mandatory.

For ics=3 (i.e. Conformance level 3) iut (i.e. Metadata URL) is mandatory and sch (i.e. Schematron URL) also needs to be passed otherwise the confomrance 3 tests will fail.

curl -sS 'http://teamengineProjectURI/rest/suites/testName/1.0/run?iut=www.exampleURL/Metadata.xml&sch=www.exampleURL/Schematron.sch&ics=3'

To test via POST API :

A POST request by default take ics=3 (i.e. Conformance level 3)

Whenever a user wants to test a Metadata file against a given Schematron (both given as a input by the user) with the help of the Teamengine’s REST POST API where both the Metadata and Schematron is present in the Local file system then he needs to send these files via POST body instead of query parameters(as shown in the example below):

  curl -X POST --header "Content-Type:multipart/form-data" -F "iut=@path/to/XML" -F "sch=@path/to/Schematorn" http://teamengineProjectURI/rest/suites/testName/1.0/run

In the above example path/to/XML is the path to the Local Metadata file and path/to/Schematorn is the path to the Local Schematron file.

Results are given in XML TestNG:

   <?xml version="1.0" encoding="UTF-8"?>
      <testng-results failed="0" passed="3" skipped="0" total="3">
         <reporter-output>
            <line>The result of the test is-</line>
            <line>Passed tests for suite 'iso19139-1.0' is:3</line>
            <line>Failed tests for suite 'iso19139-1.0' is:0</line>
            <line>Skipped tests for suite 'iso19139-1.0' is:0</line>
            <line>REASON:</line>
            <line>http://hydro10.sdsc.edu/metadata/Raquel_Files/37E28B7A-0406-449B-8A45-3988AE675368.xml conforms to the clause A.1 of ISO 19139.</line>
        </reporter-output>
    </testng-results>