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

Change Request

#:

286

Assigned OGC

Document #:

13-030

Name:

*

Clemens Portele

Organization:

*

interactive instruments

Email:

*

[email protected]

Document

Name/Version:

*

SWE Common Data Model Encoding Standard / 2.0

OGC Project

Document:

*

08-094r1

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:

*

[SOS SWG] Correct encoding rule

Source:

*

OWS-9 SSI thread

Work item code:

Category:

*

Reason for

change:

*

Incorrect statements

Summary of

change:

*

Remove the incorrect statement that �all elements are substitutable for gml:AbstractValue (and thus transitively for gml:AbstractObject) so that they can be used directly by GML application schemas�.

The current Annex C "UML to XML Schema Encoding Rules" is

incomplete. The SWE Common encoding rule in 12-093 section 7.2 might be used to provide a complete encoding rule.

Consequences if

not approved:

Clauses affected:

*

Foreword, Annex C

Additional

Documents

affected:

Supporting

Documentation:

(2)

Comments:

Status:

Assigned

Assigned To:

SOS SWG

Referensi

Dokumen terkait

* The code list encoding in CityGML provides no mechanism to point to the dictionary with the used code list values (and it does not use the GML mechanism) → noone can interpret

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

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

Reason for change:  A number of elements and types representing temporal aggregates are specified in SWE Common (within SensorML, OGC 07-000). These

not approved: Lack of interoperability, lack of harmonised approaches to encoding range semantics information within coverages, inadequate implementation in GML of ISO 19123

Currently, GML and 19107 have Triangle as a subtype of Polygon, constrained to four points but inheriting the possibility of one or more interior boundaries. With striping, this is

The “ref” syntax used for connecting SensorML and SweCommon elements should be replaced. Navigating only on “property” elements or name attributes is error prone

Add ANNEX E "GML 3.2 XML Schemas for SWE Common (Normative)" containing the schema documents in the accompanying zip document.. Proposed