• Tidak ada hasil yang ditemukan

Change Requests | OGC CR_OM2_GML32

N/A
N/A
Protected

Academic year: 2018

Membagikan "Change Requests | OGC CR_OM2_GML32"

Copied!
2
0
0

Teks penuh

(1)

Open Geospatial Consortium

OGC Doc 08-129

CR-Form-v3

CHANGE REQUEST

O&M Part 2 CR 08-129

 rev

-

 Current version: 1.0.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:  GML 3.2 implementation of XML schemas in 07-002r3

Source:  CSIRO

Work item code:Date:  2008-08-25

Category:B

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 GML 3.2 binding of the O&M schemas is required for applications that wish to use the current version of GML 3.2. It is also necessary to underpin an orderly revision process for O&M, in which implementation specifics are handled separately from functional changes.

Summary of change:  1. Add ANNEX D "GML 3.2 XML Schemas for O&M Sampling Features" containing the schema documents in the accompanying zip document

Proposed namespace

http://www.opengis.net/sa/1.0/gml32

Dependencies

- GML 3.2

http://www.opengis.net/gml/3.2

- Metadata

http://www.isotc211.org/2005/gmd

- SWE Common

http://www.opengis.net/swe/1.0/gml32

- SensorML

http://www.opengis.net/sensorML/1.0/gml32

- O&M Core

http://www.opengis.net/om/1.0/gml32

Consequences if

not approved: 1. GML 3.2 applications incompatible with O&M2. Confused process for functional upgrades

Clauses affected:  New Annex E and F

Other specsX Other core specifications  Observations and Measurements

(2)

The OGC Technical Committee Policies & Procedures 05-020r3 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:

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

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

GMLJP2 V1.1 SWG suggests including defaultStyle.xsd in gml.xsd and validating smil schemas so that defaultStyle.xsd is valid. Error reports have already been sent to W3C

Summary of change:  Correct errors encountered caused by: gmlSubset.xsl, depends.xsl, smil schemas, deprecatedTypes.xsd. Consequences if

Summary of change:  Correct errors encountered (depends.xsl, smil schemas, issue with deprecatedTypes.xsd) while running depends.xslt and GMLSubset.xslt. Consequences if

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

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

Reason for change:  First, SPS is not fully harmonized with SWE Common, but uses a proprietary approach to define parameters and tasking arguments..

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