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

*

David Stuebe

Organization:

*

RPS-ASA

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:

*

DataChoice Cardinality

Source:

*

IOOStech working group

Work item code:

Category:

*

Reason for

change:

*

There is no need to require a cardinality of two or more (2*) on the elements of a DataChoice field. It places an unnecessary constraint on the data model which requires a different structure for degenerate cases of a single item or the use of a dummy item to meet the requirements.

Summary of

change:

*

Make the minOccurs attribute of the sequence element named item equal to zero.

Consequences if

not approved:

Dummy data choice items will be used to meet a spec requirement that serves no purpose.

Clauses affected:

*

(2)

Additional

Documents

affected:

The IOOS SOS 1.0 templates are affected by this issue. See examples here: https://code.google.com

/p/ioostech/source/browse/#svn%2Ftrunk%2Ftemplates%2FMilestone1.0 The single station, single

property example is included purely due to this issue as it requires the use of a dummy item.

Supporting

Documentation:

Included a snippet of the current and suggested xsd.

Comments:

Please, please change this.

Status:

Assigned

Assigned To:

Referensi

Dokumen terkait

This Specification defines Symbology Encoding, an XML language for styling information that can be applied to digital Feature and Coverage data.. This document is together with

An abstract query element from which service specifications can subclass a concrete query element that implements a query operation that allows a client to specify a list of

Clauses affected: * A.6.5 Additional Documents affected: Supporting Documentation: Comments: Status: Assigned To:. 2

 Category “ Policy Language Encoding ” ( PLE) defines conformance test cases that focus on the capability of the implementation being able to properly process the XACML

The GeoAPI Implementation Standard defines, through the GeoAPI library, a Java language application programming interface (API) including a set of types and methods which can be

Clauses affected: * 6.4 Additional Documents affected: Supporting Documentation: Comments: Status: Assigned 1.. Assigned To: OM

i) User defined (transparent) chaining , where the user defines and controls the order of execution of the individual services. Here the details of the services are not hidden

Additional Documents affected: Supporting Documentation: Comments: Status: Assigned To: Disposition:. 2