AUTHOR:
Name:
Panagiotis (Peter) A. Vretanos
Organization:
CubeWerx Inc.
DATE:
12/2/2017
CHANGE REQUEST #1
SFGML CR 05-064
rev-
Current version: 05-033r9 Proposed change affects: AS Imp Spec X Recom. Paper Other
Title: Change the title of 03-033r9.
Source: Panagiotis (Peter) A. Vretanos
Work item code: Date: 31 Aug 2005
Category: D
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: The current title does not adequately describe the content of the specification.
Summary of change: Change the title to “Simplified GML Profile for Features with Linearly
Interpolated Geometries”. This title tells people who may be familiar with GML, that this is a simplified profile of that specification (and thus entice them to use GML in their project) and it also lets people know that feature geometries are a subset of the full GML geometry set.
CHANGE REQUEST #2
SFGML CR 05-064
rev-
Current version: 05-033r9 Proposed change affects: AS Imp Spec X Recom. Paper Other
Title: Add the length facet to properties with character content.
Source: Panagiotis (Peter) A. Vretanos
Work item code: Date: 31 Aug 2005
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: To allow fixed length character strings to be defined.
Summary of change: In clause 8.4.3.5, the template for properties with character content is defined as:
1 <xsd:element name="propertyName" minOccurs="0|N" 2 maxOccurs="0|N|unbounded">
xsd:maxLength facet so that fixed length strings may be defined.
The new template should be:
1 <xsd:element name="propertyName" minOccurs="0|N" 2 maxOccurs="0|N|unbounded">
3 <xsd:simpleType>
4 <xsd:restriction base="xsd:string">
5 <[xsd:maxLength | xsd:length] value="nCharacters"/> 6 ? Optional facets described is sub-clause 8.4.3.2 ? 7 </xsd:restriction>
8 </xsd:simpleType> 9 </xsd:element>
Also add the following text after the description of the maxLength element:
“Optionally, the nCharacters value of the value attribute of the length element may be used to indicate the fixed number of characters that the string may contain. Note that this value may not be the same as the fixed length in bytes of the character string. The length of the string in bytes may”
Consequences if
not approved:
Will not be able to defined properties with a fixed number of characters as content.
Clauses affected: 8.4.3.5
Other specs None
Title: Annexes showing how to encode well-known data sources using SFGML.
Source: Panagiotis (Peter) A. Vretanos
Work item code: Date: 31 Aug 2005
Category: D
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: To enhance interoperability by including SFGML encoding for well know data sources.
Summary of change: Add a future work item to include one or more annexes showing how to encode well know data sources using SFGML.
Consequences if
not approved:
Other specs None
Affected:
