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

Open Geospatial Consortium

OGC Doc 08-114

CR-Form-v3

CHANGE REQUEST

GML CR 08-114

 rev

-

 Current version: 3.2.1 

For

HELP

on using this form, see bottom of this page or look at the pop-up text over the symbols.

Proposed change affects:  AS Imp Spec X Best Practices Paper Other

Title:  Deprecate GML components that were immature or innappropriate

Source:  CSIRO

Work item code:Date:  2008-07-31

Category:C

Use one of the following categories:

F (Critical correction)

A (corresponds to a correction in an earlier release)

B (Addition of feature),

C (Functional modification of feature)

D (Editorial modification)

Detailed explanations of the above categories can be found in the TC Policies and Procedures.

Reason for change:  A significant number of components in GML were included after insufficient implementation testing, or in retrospect were inappropriate in the core GML schema for other reasons. There are also multiple ways to do the same thing in some places, with not functional benefit. These bloat the GML core schema, and increase the implementation barrier. These should be marked "deprecated" to alert implementors that they will be removed or at least revised in future versions of GML.

Summary of change:Mark the following components deprecated:

1. Coordinate reference systems (move into separate spec and namespace) 2. Dynamic features (harmonize with ISO 19141)

3. Definition and Dictionary (replace with SKOS) 4. Value Objects (superseded by SWE Common) 5. Observations (superseded by O&M)

6. Coverages (move into separate spec and namespace, improve alignment with ISO 19123)

7. dictionaryEntry

Consequences if

not approved: 1. GML core schema perceived as too bloated for broad implementation2. Existing implementations will continue to be either incomplete, or burdened by implementing aspects that are almost never used in practice.

(2)

The OGC Technical Committee Policies & Procedures 05-020r3

Other specs  Other core specifications 

Affected: Abstract specifications Best Practices Document

Supporting Doc.

Other comments:

Status  Disposition 

How to create CRs using this form: Comprehensive

information and tips about how to create CRs can be found at:

https://portal.open geospatial.org/files /?

artifact_id=10678. Below is a brief summary:

Fill out the above form. The symbols above marked 

contain pop-up help information about the field that they are closest to.

Obtain the latest version for the release of the specification to which the change is proposed. Use the MS Word "revision marks" feature (also known as "track changes") when making the changes. All Open GIS specifications can be downloaded from the OGC server under

http://www.opengeospa tial.org/specs/

If a Word version of the document is not available, please contact the TCC or his designee.

With "track changes" disabled, paste the entire CR form (use CTRL-A to select it) into the specification just in front of the clause containing the first piece of changed text. Delete those parts of the specification that are not relevant to the change request.

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

The “opt” schema provides the description of metadata common to all EO Products derived from optical satellite based remote sensing. It describes the same fields as the “eop”

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

Reason for change:  Application Domain Extensions (ADE) defined in CityGML (see clauses 6.12, 10.11, Annex G of OGC 08-007-r1) propose an extension mechanism which enables

Reason for change:  ISO 19111-2 has extended the scope of ISO 19111 coordinate reference systems to include ‘parametric coordinate reference systems’ often used in

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

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

Reason for change:  To enable remote referencing and the possibility of avoiding inline metadata bloat in AIXM instances. Summary of change:  Enable remote referencing on 3