Geography Markup Language (GML) Revision
The Geography Markup Language (GML) 3.2 standard is currently in revision. The history and timeline for the GML Standards Working Group is:
–First meeting in 03/2008
–Public call for change requests 04/2008-09/2008
–Change to persistent SWG in 09/2008
–Organisation of work 12/2008-03/2009
–Processing of change requests targetted since 04/2009
•Both for GML 3.3 and GML 4.0
•Current target dates – subject to change:
–Complete draft of GML 3.3: June 2010
–GML 4.0: No target date yet
There are numerous change requests being process. A current list with status can be found here: https://portal.opengeospatial.org/twiki/bin/view/GML3x3swg/GML3x3Schedule
| 2009 | 2010 | ||||||||||||||
| Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | Jan | Feb | Mar | Apr | May | Jun | |
| 07-112: AddReferenceableGrid | approved | E | E | ||||||||||||
| 08-107: AddStandardXMLattributes (1/2) | approved | E | E | ||||||||||||
| 08-138: CompactEncodingOfCircleArcRectangleTriangle | I/D | D | D | D | D | D | D | D | V | E | E | ||||
| 08-152: TinSupport | |||||||||||||||
| 08-194: CurveInterpolationType | I/D | D | D | D | D | V | E | E | |||||||
| 08-160: MultiPoint | approved | E | E | ||||||||||||
| 08-109: EncodingRuleForAssociationClass | approved | E | E | ||||||||||||
| 08-112: EncodingRuleForUMLredefine | tabled | ||||||||||||||
| 08-155: ExtensionsToUML2XMLEncodingRule | approved | E | E | ||||||||||||
| 08-185: ClarifyAsDictionaryEncodingRule | approved | E | E | ||||||||||||
| 08-154: CityGMLExtensionMechanism | I/D | D | D | D | D | D | D/V | E | E | ||||||
| 08-156: UseOfSchemaComponentsOutsideOfGMLAS | I/D | D | D | D | D | D | D/V | E | E | ||||||
| 08-110: ClarifyIdentifierUsage | D | D | D | D | V | E | E | ||||||||
| 08-111r1: ReplaceDictionarySchemaWithSKOS | D | D | D | D | D | V | E | E | |||||||
| 08-157: RangeType | I/D | D | D | V | E | E | |||||||||
| 08-080/08-082: CorrectGridCellTerms | I/D | D | D | V | E | E | |||||||||
| 08-158: ParametricCRS | I/D | D | D | V | E | E | |||||||||
| 09-022: LinearReferencingSupport | I/D | D | D | D/V | E | E | |||||||||
| 09-023r1: ExtendTimeIndeterminateValueType | I/D | D | V | E | E | ||||||||||
| 08-108: AddTemporalAggregates | I/D | D | D | D/V | E | E | |||||||||
| 08-151: CoverageEncodingApproach | I/D | D | D | D/V | E | ||||||||||
| 08-159: SpatiotemporalSupport | I/D | D | D | D/V | E | ||||||||||
- I = Raising issues
- D = Discussion / consensus building
- V = Voting
- E = Final editing and review
Rules for processing Change Requests
- Each of the relevant change requests should be discussed separately - related change requests may be discussed together.
- We will add new CRs to the discussion as appropriate. In general we will start by raising issues, discuss them, agree on revision of the CR as appropriate and eventually vote by email.
- To support the discussions we will use bi-weekly telecons.
- CRs for which no concrete proposal is available after the discussion phase will be put on hold until a concrete proposal is available. If no concrete proposal can be prepared, it will likely be deferred to a later version.
- If a CR passes an email vote with less than a 2/3 majority, it will be discussed in the next meeting.
Last Updated 2009-11-30.

