• Tidak ada hasil yang ditemukan

Change Requests | OGC

N/A
N/A
Protected

Academic year: 2017

Membagikan "Change Requests | OGC"

Copied!
2
0
0

Teks penuh

(1)

All Fields marked with

*

are mandatory.

Name:

*

Jolyon Martin

Organization:

*

ESA

Email:

*

[email protected]

Document

Name/Version:

*

Web Services Common Standard / 1.2

OGC Project

Document:

*

06-121r8

If this is a revision of a previous submission and you have a Change Request Number, then check here:

Enter the CR number here:

Enter the Revsion Number that you are revising here:

Title:

*

Service Identity

Source:

*

http://wiki.services.eoportal.org/tiki-index.php?page=HMA-FO+OWS+Common+1.2+review

Work item code:

Category:

*

Reason for

change:

*

The ServiceIdentification section in the Capabilities document does not contain a field for providing an identifier for the service

instance that is represented through the Capabilities. The URL of the service can not be used as the identifier in all cases (e.g. in case of URLs using an IP address instead of a domain name). It would be beneficial to be able to reference a certain service instance by a given identifier from within a notification sent by that service. For example, in a notification that contains a CapabilitiesChanged event as message, the service identifier could be used to indicate which service's Capabilities document changed exactly.

Summary of

change:

*

An optional identifier property should be added to the

ServiceIdentification section. The property should be of type

GenericName / Code - i.e. with optional codeSpace and required string value.

(2)

Consequences if

not approved:

Clauses affected:

*

?

Additional

Documents

affected:

Supporting

Documentation:

http://wiki.services.eoportal.org/tiki-index.php?page=HMA-FO+OWS+Common+1.2+review

Comments:

Status:

Disposition:

Referensi

Dokumen terkait

a) GetCapabilities – This request allows a client to retrieve a resource that describes the essential capabilities and non-computational characteristics of the service.

For example, the format should include a fixed content structure (e.g., a single root CityGML document and a fixed subfolder structure for different types of related files), and

a) Test purpose: Verify that when a request contains a TileMatrixSet incorrect value, then the server throws an exception. b) Test method: When a request contains a TileMatrixSet

For example, an SPS may wish to allow a particular user to perform one operation but not a different operation, while other users could request both. Summary

a) GetCapabilities (mandatory) – This operation allows a client to request and receive service metadata (or Capabilities) documents that describe the abilities of the specific

The Harmonization Working Group is currently seeking to define common service metadata elements, and filter capabilities fall within the purview of this group.. 3.2.4 Implications

This will indicate that a WFS must generate a GML document of the result set that conforms to the OpenGIS  Geography Markup Language Implementation Specification, version 3.1.1

A WFS request could then potentially contain both BBOX and FILTER parameters to allow for filtering of spatially constrained data during a BBOX request. In the event that a FILTER