ࡱ > 7 ; bjbjUU ( 7| 7| l z z z z n B V 8 8 8 8 8 T 9 V f , : v 8; : r; r; h = = = = Of Qf Qf Qf Qf Qf Qf h j Qf z * = j = = D@ A Qf lF z z = = ff lF lF lF B h z = z = Of lF = Of lF lF K X z z +Z = : IV 8" 8 E T SY +Z $ |f 0 f eY
m lF
m +Z lF V V z z z z TITLE \* Upper \* MERGEFORMAT OPENGIS PROJECT DOCUMENT 2005-064
TITLE: TITLE \* MERGEFORMAT OpenGIS Project Document 2005-064 AUTHOR: Name: AUTHOR \* FirstCap \* MERGEFORMAT Panagiotis (Peter) A. VretanosOrganization:CubeWerx Inc. USERADDRESS \* MERGEFORMAT USERADDRESS \* MERGEFORMAT DATE: DATE \* MERGEFORMAT 31/07/2005CATEGORY: DOCPROPERTY "Category" \* MERGEFORMAT Change ProposalCR-Form-v3
CHANGE REQUEST #1(SFGMLCR05-064( rev-( Current version:05-033r9(Proposed change affects: (AS Imp SpecxRecom. Paper OtherTitle: (Change the title of 03-033r9.Source: (Panagiotis (Peter) A. VretanosWork item code: (Date: (31 Aug 2005Category: (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 canbe 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.Consequences if (not approved:Confusion since SF-SQL is a subset of 05-033r9 and 05-033r9 is directly related to GML but only related to SF-SQL by virtue of the fact that SF-SQL is related to GML.Clauses affected: (Title page.Other specs ( None (Affected:Other comments: (
CR-Form-v3
CHANGE REQUEST #2(SFGMLCR05-064( rev-( Current version:05-033r9(Proposed change affects: (AS Imp SpecxRecom. Paper OtherTitle: (Add the length facet to properties with character content.Source: (Panagiotis (Peter) A. VretanosWork item code: (Date: (31 Aug 2005Category: (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 canbe 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
3
4
5
6 ? Optional facets described is sub-clause 8.4.3.2 ?
7
8
9
whch means that only varying length character string properties can be defined.
This definition should optionally allow the xsd:length facet to be used instead of the xsd:maxLength facet so that fixed length strings may be defined.
The new template should be:
1
3
4
5 <[xsd:maxLength | xsd:length] value="nCharacters"/>
6 ? Optional facets described is sub-clause 8.4.3.2 ?
7
8
9
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 mayConsequences if (not approved:Will not be able to defined properties with a fixed number of characters as content.Clauses affected: (8.4.3.5Other specs ( None (Affected:Other comments: (
CR-Form-v3
CHANGE REQUEST #3(SFGMLCR05-064( rev-( Current version:05-033r9(Proposed change affects: (AS Imp SpecxRecom. Paper OtherTitle: (Annexes showing how to encode well-known data sources using SFGML.Source: (Panagiotis (Peter) A. VretanosWork item code: (Date: (31 Aug 2005Category: (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 canbe 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:No major consequences but it is always nice to help kick start developers use of a specification by showing them how to apply it to common situations (like encoding well know data sources).Clauses affected: (Future Work Items clauseOther specs ( None (Affected:Other comments: (
TITLE \* FirstCap \* MERGEFORMAT OpenGIS Project Document 2005-064 SAVEDATE \* MERGEFORMAT 31/07/2005 11:20 PM Page PAGE 1
PAGE \# "'Page: '#''" Enter the AS or Implementation Specification Name and Number in this box. For example, WMS 1.1.1 or GML 3.0. Do not prefix the number with anything, i.e. do not use "OGC", "GSM" or "OGC" etc.
PAGE \# "'Page: '#''" Enter the CR number here. This number is allocated by the OGC support team.
PAGE \# "'Page: '#''" Enter the revision number of the CR here. If it is the first version, use a "-".
PAGE \# "'Page: '#''" Enter the version of the specification here. This number is the version of the specification to which the CR will be applied if it is approved. Make sure that the more recent version of the specification (of the relevant release) is used when creating the CR. If unsure what the latest version is, go to http://www.opengeospatial.org.
PAGE \# "'Page: '#''" Mark one or more of the boxes with an X. AS = Abstract Specification, IS = Implementation Specification, Recom. Paper = Recommendation Paper, Other = DIPR/IPR, etc.
PAGE \# "'Page: '#''" Enter a concise description of the subject matter of the CR. It should be no longer than one line.
PAGE \# "'Page: '#''" Enter the source of the CR. This is either (a) one or more OGC members or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source.
PAGE \# "'Page: '#''" IF there is one, enter the work item code or issue code that is applicable to the change. These codes will relate to Work Items identified in a WBS associated with a particular OGC initiative. If there is no code, leave blank.
PAGE \# "'Page: '#''" Enter the date on which the CR was last revised.
PAGE \# "'Page: '#''" Enter a single letter corresponding to the most appropriate category listed below. For more detailed help on interpreting these categories, see the TC Policies and Procedures".
PAGE \# "'Page: '#''" Enter text which explains why the change is necessary.
PAGE \# "'Page: '#''" Enter text which describes the most important components of the change. i.e. How the change is made.
PAGE \# "'Page: '#''" Enter here the consequences if this CR was to be rejected. It is necessary to complete this section only if the CR is of category "F" (i.e. essential correction).
PAGE \# "'Page: '#''" Enter each the number of each clause which contains changes.
PAGE \# "'Page: '#''" Enter an X in the box if any other specifications are affected by this change.
PAGE \# "'Page: '#''" If known, list here the specifications which are affected or the CRs which are linked.
PAGE \# "'Page: '#''" Enter any other information which may be needed by the group being requested to approve the CR. This could include special conditions for it's approval which are not listed anywhere else above.
PAGE \# "'Page: '#''" Enter the AS or Implementation Specification Name and Number in this box. For example, WMS 1.1.1 or GML 3.0. Do not prefix the number with anything, i.e. do not use "OGC", "GSM" or "OGC" etc.
PAGE \# "'Page: '#''" Enter the CR number here. This number is allocated by the OGC support team.
PAGE \# "'Page: '#''" Enter the revision number of the CR here. If it is the first version, use a "-".
PAGE \# "'Page: '#''" Enter the version of the specification here. This number is the version of the specification to which the CR will be applied if it is approved. Make sure that the more recent version of the specification (of the relevant release) is used when creating the CR. If unsure what the latest version is, go to http://www.opengeospatial.org.
PAGE \# "'Page: '#''" Mark one or more of the boxes with an X. AS = Abstract Specification, IS = Implementation Specification, Recom. Paper = Recommendation Paper, Other = DIPR/IPR, etc.
PAGE \# "'Page: '#''" Enter a concise description of the subject matter of the CR. It should be no longer than one line.
PAGE \# "'Page: '#''" Enter the source of the CR. This is either (a) one or more OGC members or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source.
PAGE \# "'Page: '#''" IF there is one, enter the work item code or issue code that is applicable to the change. These codes will relate to Work Items identified in a WBS associated with a particular OGC initiative. If there is no code, leave blank.
PAGE \# "'Page: '#''" Enter the date on which the CR was last revised.
PAGE \# "'Page: '#''" Enter a single letter corresponding to the most appropriate category listed below. For more detailed help on interpreting these categories, see the TC Policies and Procedures".
PAGE \# "'Page: '#''" Enter text which explains why the change is necessary.
PAGE \# "'Page: '#''" Enter text which describes the most important components of the change. i.e. How the change is made.
PAGE \# "'Page: '#''" Enter here the consequences if this CR was to be rejected. It is necessary to complete this section only if the CR is of category "F" (i.e. essential correction).
PAGE \# "'Page: '#''" Enter each the number of each clause which contains changes.
PAGE \# "'Page: '#''" Enter an X in the box if any other specifications are affected by this change.
PAGE \# "'Page: '#''" If known, list here the specifications which are affected or the CRs which are linked.
PAGE \# "'Page: '#''" Enter any other information which may be needed by the group being requested to approve the CR. This could include special conditions for it's approval which are not listed anywhere else above.
PAGE \# "'Page: '#''" Enter the AS or Implementation Specification Name and Number in this box. For example, WMS 1.1.1 or GML 3.0. Do not prefix the number with anything, i.e. do not use "OGC", "GSM" or "OGC" etc.
PAGE \# "'Page: '#''" Enter the CR number here. This number is allocated by the OGC support team.
PAGE \# "'Page: '#''" Enter the revision number of the CR here. If it is the first version, use a "-".
PAGE \# "'Page: '#''" Enter the version of the specification here. This number is the version of the specification to which the CR will be applied if it is approved. Make sure that the more recent version of the specification (of the relevant release) is used when creating the CR. If unsure what the latest version is, go to http://www.opengeospatial.org.
PAGE \# "'Page: '#''" Mark one or more of the boxes with an X. AS = Abstract Specification, IS = Implementation Specification, Recom. Paper = Recommendation Paper, Other = DIPR/IPR, etc.
PAGE \# "'Page: '#''" Enter a concise description of the subject matter of the CR. It should be no longer than one line.
PAGE \# "'Page: '#''" Enter the source of the CR. This is either (a) one or more OGC members or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source.
PAGE \# "'Page: '#''" IF there is one, enter the work item code or issue code that is applicable to the change. These codes will relate to Work Items identified in a WBS associated with a particular OGC initiative. If there is no code, leave blank.
PAGE \# "'Page: '#''" Enter the date on which the CR was last revised.
PAGE \# "'Page: '#''" Enter a single letter corresponding to the most appropriate category listed below. For more detailed help on interpreting these categories, see the TC Policies and Procedures".
PAGE \# "'Page: '#''" Enter text which explains why the change is necessary.
PAGE \# "'Page: '#''" Enter text which describes the most important components of the change. i.e. How the change is made.
PAGE \# "'Page: '#''" Enter here the consequences if this CR was to be rejected. It is necessary to complete this section only if the CR is of category "F" (i.e. essential correction).
PAGE \# "'Page: '#''" Enter each the number of each clause which contains changes.
PAGE \# "'Page: '#''" Enter an X in the box if any other specifications are affected by this change.
PAGE \# "'Page: '#''" If known, list here the specifications which are affected or the CRs which are linked.
PAGE \# "'Page: '#''" Enter any other information which may be needed by the group being requested to approve the CR. This could include special conditions for it's approval which are not listed anywhere else above.
! B C K L c d 7 8 @ A W X b c o p
& ' ( ) - . 6 7 9 F G ֶּ >*>*mHsH5;mHsH 56 5mHsH5CJ mHsHmHsH 5CJ j 0J3 <OJ QJ U j z 5CJ 66CJ j U E D K |T p $$If l 4 0 T% T
t 0 & 4
l a
$If $If U ; 9 : @ d {p u u u { u u $If $$If l 4 F T
% b
t 0 & 4
l a d e o y G 2 $$If * % % & 4
* a 6 $ $If a$ 6 $If p $$If l 4 0 T% T
t 0 & 4
l a
Ff 6
! $If 6
q $If 6 $ $If a$6 $ $If a$2 $$If * % % & 4
* a 6 $If
) - . 7 9 G H N O P Q R \ z ͤ 6 d $If ^d 6
$If Ff 6 $If 6 $ $If a$6 $ $If a$6
$If 2 $$If * % % & 4
* a G H R Y Z [ \ { | ~ / 0 f g " # $ % & ' ) < = > ?
"
#
$
3
5\ 6CJ
56CJ
6>*CJ 6CJ 5j 0J3 <OJ QJ U j z 56 5;Pz { | } ~ ^ R F 6 d $If ^d 6
$If E $$If * 0 % 3 u & 4
* a 6 $If T $$If * 0 % 3 u & 4
* a ^ R F 6 d $If ^d 6
$If E $$If * 0 % 3 u & 4
* a 6 $If T $$If * 0 % 3 u & 4
* a = 5 5 6 $If $$If * r % 3 O
2 & 4
* a 6 d $If ^d 6 $ $If a$6 d $If ]d yH m a V 6 $ $If a$6 d $If ^d 6
$If ~ $$If * r E
% 3
O & 4
* a 6 $If # $ % } m m g S S 6
$If ^ `6 $If 6 $If ^`6 $If z $$If * \ 3 &O 4
* a % & ' ( ) ? Z N 6
$If E $$If * 0 % 3 u & 4
* a 6 $If X $$If * F % 3 F / & 4
* a
^ R 6
$If E $$If * 0 % & 4
* a 6 $If T $$If * 0 % & 4
* a
3
^( R 6
$If E $$If * 0 % & 4
* a 6 $If T $$If * 0 % & 4
* a
^ R 6
$If E $$If * 0 % & 4
* a 6 $If T $$If * 0 % & 4
* a
( ) , - . 1 2 4 D E F G I K L V W h l m n o w x ~ ƾ ưƪ >*>*mHsH5;mHsH 5mHsH5CJ mHsHmHsH 5CJ 5CJ 66CJ mH sH OJ QJ mH sH 5; 56 j 0J3 <OJ QJ U j zB
^l R G 6 $ $If a$6
$If E $$If * 0 % & 4
* a 6 $If T $$If * 0 % & 4
* a ( ) * + , a8 Y N Y a 6 $ $If a$6 $If $$If * \ % ( & 4
* a 6 c $If ^c 6
M $If , - . / 0 1 2 3 Z $$If * \ % ( & 4
* a 6 c $If ^c 6 $ $If a$6 $If 3 4 G H I J L W T N L L H 6 T $$If * 0 % & 4
* a 6 d $If ^d 6
$If E $$If * 0 % & 4
* a W i j k l o u x Ff 6
! $If 6
q $If 6 $ $If a$6 $If 2 $$If * % % & 4
* a 6 $ $If a$ 6
$If Ff 6 $ $If a$6 $ $If a$6
$If 2 $$If * % % & 4
* a 6 $If
8 9 ; C D E F f g i y z { | ~ #
$
>
?
f
g
4 5 7 J K L M p d e g mH sH 6CJ
56CJ
6>*CJ 6CJ 55\ 56 j 0J3 <OJ QJ U j zP 7 8 9 : ; F e R F 6
$If E $$If * 0 % 3 u & 4
* a 6 $If T $$If * 0 % 3 u & 4
* a 6 d $If ^d e f g h i | } ^ R F 6 d $If ^d 6
$If E $$If * 0 % 3 u & 4
* a 6 $If T $$If * 0 % 3 u & 4
* a } ~ = 5 5 6 $If $$If * r % 3 O
2 & 4
* a 6 d $If ^d 6 $ $If a$6 d $If ]d yH m a V 6 $ $If a$6 d $If ^d 6
$If ~ $$If * r E
% 3
O & 4
* a 6 $If
} m m g S S 6
$If ^ `6 $If 6 $If ^`6 $If z $$If * \ 3 &O 4
* a
3 Z8 N 6
$If E $$If * 0 % 3 u & 4
* a 6 $If X $$If * F % 3 F / & 4
* a 3 4 5 6 7 M ^ R L $If 6
$If E $$If * 0 % & 4
* a 6 $If T $$If * 0 % & 4
* a
L | O P 9 m - H _ p $If 6 $If c ^ R 6
$If E $$If * 0 % & 4
* a 6 $If T $$If * 0 % & 4
* a c d e f g | ^x R 6
$If E $$If * 0 % & 4
* a 6 $If T $$If * 0 % & 4
* a g y z { |
* + , 2 K L M N R S [ \ ^ k l m w ~ ԾԸ >*>*mHsH5;mHsH 5mHsH5CJ mHsHmHsH 5CJ 5CJ 66CJ 5; j 0J3 <OJ QJ U j z 56H ^l R G 6 $ $If a$6
$If E $$If * 0 % & 4
* a 6 $If T $$If * 0 % & 4
* a a8 Y N Y a 6 $ $If a$6 $If $$If * \ % ( & 4
* a 6 c $If ^c 6
M $If Z $$If * \ % ( & 4
* a 6 c $If ^c 6 $ $If a$6 $If T N L L H 6 ! T $$If * 0 % & 4
* a 6 d $If ^d 6
$If E $$If * 0 % & 4
* a
! * - . / 0 Ff 6
! $If 6
q $If 6 $ $If a$6 $If 2 $$If * % % & 4
* a 6 $ $If a$ 0 1 2 N R S \ ^ l m s t u v w 8 6
$If Ff 6 $ $If a$6 $ $If a$6
$If 2 $$If * % % & 4
* a 6 $If R F 6
$If E $$If * 0 % 3 u & 4
* a 6 $If T $$If * 0 % 3 u & 4
* a 6 d $If ^d ! " ' 1 2 3 4 6 7 8 9 : ? B _ a y z l m n o p q s h i k | } ~ M N P b c d e 5; 6CJ
56CJ
6>*CJ 6CJ 556 j 0J3 <OJ QJ U j zR
^ R F 6 d $If ^d 6
$If E $$If * 0 % 3 u & 4
* a 6 $If T $$If * 0 % 3 u & 4
* a
! " # = 5 5 6 $If $$If * r % 3 O
2 & 4
* a 6 d $If ^d 6 $ $If a$6 d $If ]d # $ % & ' 4 6 7 8 yH m a V 6 $ $If a$6 d $If ^d 6
$If ~ $$If * r E
% 3
O & 4
* a 6 $If 8 9 : ; m n o } m m g S S 6
$If ^ `6 $If 6 $If ^`6 $If z $$If * \ 3 &O 4
* a o p q r s Z N 6
$If E $$If * 0 % 3 u & 4
* a 6 $If X $$If * F % 3 F / & 4
* a g ^ R 6
$If E $$If * 0 % & 4
* a 6 $If T $$If * 0 % & 4
* a g h i j k L ^ R 6
$If E $$If * 0 % & 4
* a 6 $If T $$If * 0 % & 4
* a L M N O P e ^ R 6
$If E $$If * 0 % & 4
* a 6 $If T $$If * 0 % & 4
* a ^l R G 6 $ $If a$6
$If E $$If * 0 % & 4
* a 6 $If T $$If * 0 % & 4
* a a8 Y N Y a 6 $ $If a$6 $If $$If * \ % ( & 4
* a 6 c $If ^c 6
M $If - . A B H I O P Q R U V l n o p 1 2 H J K L ! q r 2 3 I K L M
j 0J3 U0J3 0J mH nH u0J
j 0J UmH nH u j Uj 0J3 <OJ QJ U j z 5; 56L Z $$If * \ % ( & 4
* a 6 c $If ^c 6 $ $If a$6 $If S T U T N J H F F 6 T $$If * 0 % & 4
* a 6 d $If ^d 6
$If E $$If * 0 % & 4
* a U 1 q 2 ~ ! ! l" +# # # b$ @% &