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

*

Guidelines for creating and using WSDL

Source:

*

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

Work item code:

Category:

*

Reason for

change:

*

Annex E in OWS Common defines "Guidelines for creating and using WSDL". This Annex is informative. In clause E.2 ("Relationship to OGC service descriptions"), a way is shown with which the WSDL description of a service can be referenced from within the Capabilities document of a service. This is a nice feature.

However, the XML Schema from OWS Common for the CapabilitiesBaseType and otherwise do not contain such an element at all, though it would be quite helpful. Why is it not included / defined as an optional part of the CapabilitiesBaseType (or sub-component)? It could for example be another - optional - section of the Capabilities document that can be queried by clients.

Summary of

change:

*

Provision of another - optional - section of the Capabilities document that can be queried by clients for WSDL description of a service

within the XML Schema from OWS Common for the CapabilitiesBaseType

(2)

Consequences if

not approved:

Clauses affected:

*

Annex E

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

This table also specifies the UML model data type, source of values and multiplicity of each listed parameter, plus the meaning to servers when each optional parameter is not

A client application uses the GML application schema definition of a feature type to refer to feature instances of that feature type, and to refer to the names and types of all the

the schema s the gco and gmd namespaces via a local copy of an interim version of the ISO 19139 implementation of the ISO 19115 metadata schema. In turn this s GML using a

The OWS Common 1.2 SWG Scope of Work includes the need to Define a URN to Identify Service Type, this should consider profile versions. Summary

Alternatively, the time specification format that goes into a <when> tag could be expanded to allow the optional inclusion of pieces of seconds (perhaps it could be

Then the question is if common OWS operation parameters (like for example the acceptLanguages parameters) would not better be put into common extension elements of operation

The xpath attribute specifies the XML element/value from the given XML Document where the ref value specifies the mapping. Summary of change:  Enhances parameterization of

WSDL does not support the definition of dynamic parameter names, all parameters have to be defined at interface description stage.. 3.1.4 Specific