GML CR - clarify asDictionary encoding rule
OGC Doc 08-185r1
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
GML CR 08-185r1
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
Title:
Clarify GML encoding rule for codeList classes tagged asDictionary="true"
Source:
CSIRO, JRC
Work item code:
Category:
Other
Date: 2009-08-06
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:
1.
The encoding rule for classes stereotyped «codeList» and tagged
asDictionary="true" requires information that is not provided in the model
2. The encoding rule for feature properties whose type is a class stereotyped
«codeList» is ambiguous/incomplete.
Summary of change: 1. Table E.2: add tagged values
- dictionaryCodeSpace (only «codeList»)
- dictionaryIdentifier (only «codeList»)
- itemCodeSpace (only «codeList»)
2. Sub-clause E.2.4.9 replace the sentence
Alternatively, if the class carries a tagged value "asDictionary" with the value
"true", a gml:Dictionary shall be used to represent a code list.
with
Alternatively, if the class carries a tagged value "asDictionary" with the value
"true", the tagged value "dictionaryCodeSpace" may provide a URI that
identifies the authority responsible for the codeList, "itemCodeSpace" may
provide a URI that identifies the authority responsible for the items, the tagged
value "dictionaryIdentifier" may provide a URI that identifies the codeList,
and a gml:Dictionary shall be used to represent a code list.
Then the example dictionary should be accompanied by a note indicating the value
for the tagged value that would lead to this dictionary representation, i.e.
dictionaryCodeSpace=”http://www.someorg.de/cl.xml”
The OGC Technical Committee Policies & Procedures 05-020r3
dictionaryIdentifier=”ParcelUsage”
itemCodeSpace=”http://www.someorg.de/cl.xml#ParcelUsage”
NOTE: in general there is no fixed relationship between the codeSpace for the
dictionary and item identifiers.
3. Sub-clause E.2.4.11 EXAMPLE 6 should be replaced as follows:
EXAMPLE 6 The code list "BuildingType" shall be represented as:
if asDictionary="false" or
http://www.someorg.de/example/cl.xml
If asDictionary="true", where the value of the defaultCodeSpace is provided by the
itemCodeSpace tagged value on the target class.
Consequences if
not approved:
Inconsistent encoding of dictionaries.
Clauses affected:
E
Other specs
Affected:
Supporting Doc.
Other comments:
Status
Disposition
Other core specifications
Abstract specifications
Best Practices Document
This revision of the CR removes the ‘memberIdentifierStem’ tagged value and
rules. The original proposal used assumptions about the structure of identifiers
for dictionary entries that are not resolved, so this aspect has been deferred.
Last Revision Date: 2 December 2017
Page2
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
GML CR 08-185r1
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
Title:
Clarify GML encoding rule for codeList classes tagged asDictionary="true"
Source:
CSIRO, JRC
Work item code:
Category:
Other
Date: 2009-08-06
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:
1.
The encoding rule for classes stereotyped «codeList» and tagged
asDictionary="true" requires information that is not provided in the model
2. The encoding rule for feature properties whose type is a class stereotyped
«codeList» is ambiguous/incomplete.
Summary of change: 1. Table E.2: add tagged values
- dictionaryCodeSpace (only «codeList»)
- dictionaryIdentifier (only «codeList»)
- itemCodeSpace (only «codeList»)
2. Sub-clause E.2.4.9 replace the sentence
Alternatively, if the class carries a tagged value "asDictionary" with the value
"true", a gml:Dictionary shall be used to represent a code list.
with
Alternatively, if the class carries a tagged value "asDictionary" with the value
"true", the tagged value "dictionaryCodeSpace" may provide a URI that
identifies the authority responsible for the codeList, "itemCodeSpace" may
provide a URI that identifies the authority responsible for the items, the tagged
value "dictionaryIdentifier" may provide a URI that identifies the codeList,
and a gml:Dictionary shall be used to represent a code list.
Then the example dictionary should be accompanied by a note indicating the value
for the tagged value that would lead to this dictionary representation, i.e.
dictionaryCodeSpace=”http://www.someorg.de/cl.xml”
The OGC Technical Committee Policies & Procedures 05-020r3
dictionaryIdentifier=”ParcelUsage”
itemCodeSpace=”http://www.someorg.de/cl.xml#ParcelUsage”
NOTE: in general there is no fixed relationship between the codeSpace for the
dictionary and item identifiers.
3. Sub-clause E.2.4.11 EXAMPLE 6 should be replaced as follows:
EXAMPLE 6 The code list "BuildingType" shall be represented as:
if asDictionary="false" or
http://www.someorg.de/example/cl.xml
If asDictionary="true", where the value of the defaultCodeSpace is provided by the
itemCodeSpace tagged value on the target class.
Consequences if
not approved:
Inconsistent encoding of dictionaries.
Clauses affected:
E
Other specs
Affected:
Supporting Doc.
Other comments:
Status
Disposition
Other core specifications
Abstract specifications
Best Practices Document
This revision of the CR removes the ‘memberIdentifierStem’ tagged value and
rules. The original proposal used assumptions about the structure of identifiers
for dictionary entries that are not resolved, so this aspect has been deferred.
Last Revision Date: 2 December 2017
Page2