The URL of the service being testedThe OGC identifier for the type of service being tested (i.e. SPS)The version of the service being testedThe name of the root element of a Capabilities document returned by this service (i.e. Capabilities, WFS_Capabilities, etc.)The location of the Capabilities schema for the service being testedThe type of resource specified in the capabilitiesResponseSchemaLocation above (i.e. url, file, resource). Corresponds with the CTL XMLValidatingParser schema type attribute.The expected HTTP header content type of the GetCapabilities response (i.e. text/xml)The location of the ExceptionReport schema for the version of OWS Common being testedThe type of resource specified in the exceptionReportSchemaLocation above (i.e. url, file, resource). Corresponds with the CTL XMLValidatingParser schema type attribute.Run test group for GetCapabilities requests using the GET method.**********************************************************************The GET method request must be supported (using HTTP GET).GetCapabilities by GET. Pass if all of the following conditions are true: (1) the response is schema valid; (2) the root element matches the provided root element.
OWS.GetCapabilities
OGC 05-008: cl. 7.1, p. 10, cl. 7.2.2; cl. 7.2.3
Executing a valid GetCapabilities request...getGetCapabilitiespostFAILURE: The server did not return a response, or the response was not valid according to the GetCapabilities response schema for .The root element from the response to a GetCapabilities request "" does not match the expected root element of ""A valid GetCapabilities response was returned. This response will be used as appropriate in the remaining OWS Common tests. Executing the remaining OWS Common tests...****************************************************************************************************************************************************************************************************************************************************************************************updateSequence is supported for GetCapabilities requests. Running updateSequence tests...************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************Sections parameter is supported for GetCapabilities requests. Running Sections tests...********************************************************************************************************************************************AcceptFormats parameter is supported for GetCapabilities requests. Running AcceptFormats tests...A response message containing an entity body must contain a Content-Type entity header field that correctly indicates the media type of the message body.Pass if all of the following conditions are true: (1) the response is schema valid; (2) the root document matches the root element name; (3) the response Content-Type header must be $expectedContentType for XML entities.
ows-1.0.0-common-atc2
OGC 05-008c1, 11.7, p.61
Issuing a valid GetCapabilities request...getGetCapabilitiespostFAILURE: The server did not return a response, or the response was not valid according to the GetCapabilities response schema for .FAILURE: The root element from the response to a GetCapabilities request "" does not match the expected root element of ""Checking the content type of the response.The response content type is: . Ensuring that this content type is a valid MIME type and that the returned content type matches the expected content type.FAILURE: Incorrect response encoding. "" was expected, but "" was returned instead.A GetCapabilities request without service parameter should return valid GetCapabilities response .GetCapabilities with no service parameter. Pass if the response is GetCapabilities response schema valid; .Issuing a GetCapabilities request with no service parameter...getGetCapabilitiespostFAILURE: Missing or invalid response entity.FAILURE: The response to a GetCapabilities request is not a correct response.FAILURE: When request didn't give the parameter "service",the service didn't give the default value "SPS".FAILURE: When request didn't give the parameter "acceptVersions",the service didn't give the default value "2.0.0".FAILURE: When request didn't give the parameter "sections",the service didn't give the section block "ows:ServiceIdentification".FAILURE: When request didn't give the parameter "sections",the service didn't give the section block "ows:ServiceProvider".FAILURE: When request didn't give the parameter "sections",the service didn't give the section block "ows:OperationsMetadata".FAILURE: When request didn't give the parameter "sections",the service didn't give the section block "sps:contents".In the event that a GetCapabilities request cannot be processed for any reason, the response entity shall include an exception report. The exception code must be one of those listed in Table 5.GetCapabilities with a bogus service parameter value ('ADSF'). Pass if all of the following conditions are true: (1) the response is schema valid; (2) the root document is an ows:ExceptionReport document; (3) the ExceptionReport shall have the 'InvalidParameterValue' exception code; (4) theExceptionReport @locator value shall be that of the invalid parameter.
ows-1.0.0-metadata-atc5
OGC 05-008c1, 7.4.1, p.19
Issuing a GetCapabilities request with an invalid service parameter value of ASDF...getASDFGetCapabilitiespostFAILURE: Missing or invalid response entity.The response was a valid ExceptionReport. Checking the response elements for validity...The validity check returned: FAILURE: The returned exception report was expected to contain an exceptionCode of "InvalidParameterValue" and a locator value of "service".In the event that a GetCapabilities request cannot be processed for any reason, the response entity shall include an exception report. The exception code must be one of those listed in Table 5.GetCapabilities with an incorrect version parameter ('2000-01-01'), using acceptVersions. Pass if all of the following conditions are true: (1) the response is schema valid; (2) the root document is an ows:ExceptionReport document; (3) the ExceptionReport shall have the 'VersionNegotiationFailed' exception code.
ows-1.0.0-metadata-atc5
OGC 05-008c1, 7.4.1, p.19
Issuing a GetCapabilities request with an acceptVersions parameter of 2000-01-01...getGetCapabilities2000-01-01postFAILURE: The server did not return a response, or the response was not valid according to the ExceptionReport response schema.The response was a valid ExceptionReport. Checking the response elements for validity...The validity check returned: FAILURE: The returned exception report was expected to contain an exceptionCode of "VersionNegotiationFailed".In the event that a GetCapabilities request cannot be processed for any reason, the response entity shall include an exception report. The exception code must be one of those listed in Table 5.GetCapabilities with an incorrect updatesequence ('9999999999'), if higher than the update sequence on the current capabilities document give an exception. Pass if all of the following conditions are true: (1) the response is schema valid; (2) the root document is an ows:ExceptionReport document; (3) the ExceptionReport shall have the 'InvalidUpdateSequence' exception code.
ows-1.0.0-metadata-atc5
OGC 05-008c1, 7.4.1, p.19
Issuing a GetCapabilities request with an UpdateSequence parameter of ...getGetCapabilitiespostFAILURE: The server did not return a response, or the response was not valid according to the ExceptionReport response schema.The response was a valid ExceptionReport. Checking the response elements for validity...The validity check returned: FAILURE: The returned exception report was expected to contain an exceptionCode of "InvalidUpdateSequence".In the event that a GetCapabilities request cannot be processed for any reason, the response entity shall include an exception report. The exception code must be one of those listed in Table 5.GetCapabilities with an incorrect KVP query string, triggering the missing parameter value exception. Pass if all of the following conditions are true: (1) the response is schema valid; (2) the root document is an ows:ExceptionReport document; (3) the ExceptionReport shall have the 'MissingParameterValue' exception code, for the request.
ows-1.0.0-metadata-atc5
OGC 05-008c1, 7.4.1, p.19
GetCapabilities_GET:Issuing a GetCapabilities request with with invalid query string data...getFAILURE: The server did not return a response, or the response was not valid according to the ExceptionReport response schema.The server returned the following response: Checking this response for validity...The validity check returned: FAILURE: The returned exception report was expected to contain an exceptionCode of "MissingParameterValue" and a locator value of "request".Service doesn't support HTTP GET request,so skip this test.Parameter names in KVP strings shall be handled in a case-insensitive manner.GetCapabilities with the KVP parameter names in all uppercase. Pass if all of the following conditions are true: (1) the response is schema valid; (2) the root element matches the provided root element.
ows-1.0.0-common-atc1
OGC 05-008c1, 11.5.2, p.56
Issuing a GetCapabilities request with upper-case parameter names...getGetCapabilitiespostIssuing a GetCapabilities request with mixed-case parameter names...getGetCapabilitiespostIssuing a GetCapabilities request with lower-case parameter names...getGetCapabilitiespostFAILURE: Missing or invalid response entity in one or more of the preceding GetCapabilities requests.FAILURE: The root element(s) from the responses to GetCapabilities requests with mixed-case parameters do not match the expected root element of ""If AcceptVersion is not specified, the service must respond with highest supported version.GetCapabilities with no version and service of $serviceType. Without AcceptVersion, using version negotiation, sends latest copy. Pass if all of the following conditions are true: (1) the response is schema valid; (2) the root document is an wfs:WFS_Capabilities document; (3) the response version must be what was requested.
ows-1.0.0-metadata-atc3
OGC 05-008c1, 7.3.2, p.16
Issuing a GetCapabilities request with no AcceptVersion parameter...getGetCapabilitiespostFAILURE: The server did not return a response, or the response was not valid according to the GetCapabilities response schema for .FAILURE: The root element "" from the response to a GetCapabilities request does not match the expected root element of ""Checking the version attribute () of the root element of the response.FAILURE: The returned value in the version attribute "" does not match the expected version of ""Version negotiation using acceptVersions parameter (preference ordering): Return service metadata corresponding to the most preferred version that is supported. If none of the requested versions are supported, the server must generate an exception with code 'VersionNegotiationFailed'.GetCapabilities with no version and service of $serviceType. With AcceptVersion, expecting one of the versions listed $acceptVersions. Pass if all of the following conditions are true: (1) the response is schema valid; (2) the root document is an Capabilities document; (3) the response version must be what was requested. The AcceptVersion element is used with a number of versions, one is expected to return ('1.1.0').
ows-1.0.0-metadata-atc4
OGC 05-008c1, 7.3.2, p.16
Issuing a GetCapabilities request with an acceptVersions parameter of ...getGetCapabilitiespostFAILURE: The server did not return a response, or the response was not valid according to the GetCapabilities response schema for .FAILURE: The root element "" from the response to a GetCapabilities request does not match the expected root element of ""Checking the version attribute () of the root element of the response.FAILURE: The returned value in the version attribute "" does not match the expected version of ""Version negotiation using acceptVersions parameter (preference ordering): Return service metadata corresponding to the most preferred version that is supported. If none of the requested versions are supported, the server must generate an exception with code 'VersionNegotiationFailed'.GetCapabilities with no version and service of $serviceType. With AcceptVersion, using a bogus version number ('2000-01-01'). Pass if all of the following conditions are true: (1) the response is schema valid; (2) the root document is an ows:ExceptionReport document; (3) the ExceptionReport shall have the 'VersionNegotiationFailed' exception code.
ows-1.0.0-metadata-atc4
OGC 05-008c1, 7.3.2, p.16
Issuing a GetCapabilities request with an acceptVersions parameter of 2000-01-01...2000-01-01getGetCapabilities2000-01-01post2000-01-01FAILURE: The server did not return a response, or the response was not valid according to the ExceptionReport response schema.The response was a valid ExceptionReport. Checking the response elements for validity...The validity check returned: FAILURE: The returned exception report was expected to contain an exceptionCode of "VersionNegotiationFailed".
The response to a GetCapabilities request that includes a sections parameter
with NO VALUE provided shall include an abbreviated capabilities document
that omits all optional sections.
Pass if the response is schema valid and omits all optional
top-level elements.
ows-1.0.0-metadata-atc9
OGC 05-008c1, 7.3.3, p.17
Issuing a GetCapabilities request with an empty Sections parameter...getGetCapabilitiespostFAILURE: The server did not return a response, or the response was not valid according to the GetCapabilities response schema for .Getting the sections of the Capabilities document.FAILURE: There should be no element in the returned Capabilities element of the response.
The response to a GetCapabilities request that includes a sections parameter
listing optional elements shall include only the requested elements in the
response entity.
Pass if the response is schema valid and includes only the requested optional
elements.
ows-1.0.0-metadata-atc9
OGC 05-008c1, 7.3.3, p.17
Issuing a GetCapabilities request with a Sections parameter of ServiceIdentification,OperationsMetadata...OperationsMetadataServiceIdentificationgetGetCapabilitiesServiceIdentification,OperationsMetadatapostOperationsMetadataServiceIdentificationFAILURE: The server did not return a response, or the response was not valid according to the GetCapabilities response schema for .Checking that the OperationsMetadata section is included.FAILURE: The ows:OperationsMetadata element is missingChecking that the ServiceIdentification section is included.FAILURE: The ows:ServiceIdentification element is missingChecking that the ServiceProvider section is not included.FAILURE: The ows:ServiceProvider element is included
The response to a GetCapabilities request containing an acceptVersions
parameter specifying a supported format must include a response entity
that corresponds to the requested media type.
OGC 05-008, 7.3.5
Issuing a GetCapabilities request with an AcceptFormats parameter of ...getGetCapabilitiespostChecking the content type of the response...The response content type is: . Comparing this value with the requested format: FAILURE: Unexpected content type for response entity (Request: , Response: ).The exception report to checkThe exceptionCode to checkThe locator to check (a * can be provided to indicate that any locator value is allowed)The response encoding typeTrue/false depending on whether or not the exception report is validThe respsonseFormat to validateTrue/False depending on whether the input is a valid MIME type based on ows:owsCommon.xsdDetermines if a definition URN is valid