• 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:

*

Clarification of profile property

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 - see 7.4.4 - now contains a profile property of cardinality 0..*. Table 11 states that the definition of this property is: "Identifier of OGC Web Service (OWS) Application Profile".

This property and its definition seem to be outdated with respect to "The Specification Model" (see OGC 08-131r3), especially that

specifications are going to be structured in conformance classes that are supported by implementations (or not).

Summary of

change:

*

The "profile" property should be revised to support this new concept.

Consequences if

not approved:

With respect to SPS, it would be desirable to indicate which

profile(s) / set of conformance classes a specific service instance supports. This is especially true as the SPS EO profile will extend the SPS functionality and thus clients could readily determine that

(2)

the EO profile is supported by a service or not. In addition, service requests and responses now allow additional parameters via extension elements (see SWE Service Model specification, work in progress and foreseen to be ready at Nov 19th 09). With a revised "profile" element, a service could indicate which extensions it supports.

Clauses affected:

*

see 7.4.4

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) Test Purpose: Verify that a server satisfies all requirements on the Execute operation response for raw data output. b) Test Method: Make several Execute requests including

a) Test Purpose: Verify that a basic CSW server interface satisfies all requirements of the GetDomain operation. b) Test Method: Make several GetDomain requests using a variety

Either drop the SWE Time class, or clearly document the circumstances in which it should be used in preference to ISO 19103 Time. If it is kept, correct the definitions: the XML

Adding a circle property type would allow GMLSF to be used with these components more easily. Summary

Comments/justifications for changes: A new conceptual model and encoding for temporal concepts is developed as part of SWE Common instead of importing ISO 19108.. The reasons for

Specification Section number: 12..3.1 GetData normal response parameters. Criticality:

All WCS servers shall specify the encodings that may be sent using HTTP POST transfer of operation requests. Specifically, an ows:Constraint element shall be included, with

Reason for change:  The WPS 1.0.0 specification does not provide any mechanism for querying the status of an asynchronous process, though the specification does require an