Operation Request – GetCapabilities GetCapabilities Operation

Copyright © 2011 Open Geospatial Consortium 53 Requirement http:www.opengis.netspecSPS2.0reqGetCapabilitiesRequestdataType REQ 33. The SPS GetCapabilities data type shall contain the properties of the OWS Common GetCapabilities data type from OWS Common listed in table 3 of [06-121r3]. In addition, it shall contain the properties according to Table 17. Table 17 — Properties in the GetCapabilities data type Name Definition Data type and values Multiplicity and use extension container for elements defined by extension specifications Any type value is defined by the extension specification Zero or more optional service service type identifier Character String type, not empty value shall be “SPS” Zero or one optional default value is “SPS” NOTE The request property – derived from OWS Common GetCapabilities type – is explicit or implied by each specific binding of the GetCapabilities operation, so is not necessarily part of the request representation defined by that binding. OWS operations usually do not allow the addition of elements. However, with respect to the core extension pattern for service specifications where the core service functionality is defined in the base specification and extension specifications may define further functionality that integrates with the existing one it is desirable to have a place in service requests and responses where elements defined by extensions, for example policy assertions, can be added without the XML instances becoming invalid. The extension property of the GetCapabilities data type is the realization of such an extension point. Requirement http:www.opengis.netspecSPS2.0reqGetCapabilitiesRequestsectionNames REQ 34. The allowed set of service metadata or Capabilities section names and meanings shall be as specified in Tables 6 and 10 of [OGC 06-121r3], with the addition listed in Table 18 below. Table 18 — Additional Section name value and meaning Section name Meaning notifications Return Notifications section in service metadata document The “Multiplicity and use” column in Table 3 of [OGC 06-121r3] and Table 19 in this specification specifies the optionality of each listed parameter in the SPS GetCapabilities operation request. 54 Copyright © 2011 Open Geospatial Consortium Requirement http:www.opengis.netspecSPS2.0reqGetCapabilitiesRequestparameters REQ 35. SPS clients and servers shall implement the GetCapabilities parameters as defined in Table 19. Table 19 — Implementation of parameters in GetCapabilities operation request Name Multiplicity Client implementation Server implementation service Zero or one optional May be implemented by all clients, using specified value If parameter not provided, default value is to be assumed by service Shall be implemented by all servers, checking that parameter is received with specified value Default value shall be assumed if parameter is not provided in request request One mandatory Shall be implemented by all clients, using specified value In specific binding the value may be implied through encoded request structure Shall be implemented by all servers, checking if parameter is received with specified value In specific binding the value may be implied through encoded request structure acceptVersions Zero or one optional Should be implemented by all software clients, using specified values Shall be implemented by all servers, checking if parameter is received with specified values sections Zero or one optional Each parameter may be implemented by each client If parameter not provided, shall expect default response If parameter provided, shall allow default or specified response Each parameter may be implemented by each server If parameter not implemented or not received, shall provide default response If parameter implemented and received, shall provide specified response updateSequence Zero or one optional acceptFormats Zero or one optional

7.3.2.4 Operation Response – Capabilities

The Capabilities data type defines the normal response returned by an SPS when a valid GetCapabilities request has been received. It is derived from the OWSServiceMetadata data type defined by OWS Common see clause 7.4 in [OGC 06-121r3]. It contains two more sections contents and notifications – depending upon the GetCapabilities request and the functionality supported by the service. Copyright © 2011 Open Geospatial Consortium 55 Requirement http:www.opengis.netspecSPS2.0reqGetCapabilitiesResponsedataType REQ 36. The Capabilities data type shall include the properties of the OWSServiceMetadata data type as defined in clauses 7.4.2 to 7.4.7 in [OGC 06-121r3] with the additional properties according to Table 20. Table 20 — Properties in the Capabilities data type Name Definition Data type and values Multiplicity and use contents metadata about the provided sensors and supported data encodings SPSContents, see clause 7.3.3 Zero or one optional inclusion depends on the values in the Sections parameter of the GetCapabilities operation request extension container for elements defined by extension specifications Any type value is defined by the extension specification Zero or more optional use as explained for the extension property in the GetCapabilities operation request data type see clause 7.3.2.3 notifications metadata about the supported notification functionality NotificationProducerM etadata, see clause 8 in [OGC 09-001] Zero or one optional inclusion depends on the values in the Sections parameter of the GetCapabilities operation request Requirement http:www.opengis.netspecSPS2.0reqGetCapabilitiesResponsedefaultVersion REQ 37. A service implementing this standard shall at least be capable of providing a Capabilities document with version number “2.0.0” that is structured as defined in section 7.3.2.4. Requirement http:www.opengis.netspecSPS2.0reqGetCapabilitiesResponsesections REQ 38. An SPS shall implement the sections of the Capabilities document listed in Table 21 according to the Use column in that table.