GML 3.2.1 CR - encoding rule for association class
OGC Doc 08-109r1
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
GML CR 08-109r1
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:
GML encoding rule for UML association classes
Source:
CSIRO
Work item code:
Category:
Other
Date: 2008-07-31
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:
Standard UML modelling allows for an association to have a multiple properties, in
the form of an association-class. For most cases this may be converted into an
"intermediate" class which may then be serialized using the standard UML-GML
encoding rule.
Summary of change: An association class may be mapped into an equivalent intermediate class. See the
following diagram:
GML CR 08-109r1
Name:
Package:
Version:
Author:
AssociationClass
GML CRs
1.0
Simon Cox
F12
role2_1
«FeatureTyp...
Feature1
«FeatureTyp...
Feature2
a..b
F34
«FeatureTyp...
Feature3
role3_4
c..d
role4_3
«FeatureTyp...
Feature4
e..f
The encoding rule is to process to perform the mapping and then encode the model
in the standard manner.
Consequences if
not approved:
Association classes not allowed in GML Application Schemas.
Clauses affected:
E
Last Revision Date: 2 December 2017
Page2
GML CR 08-109r1
Other specs
Affected:
Supporting Doc.
Other comments:
Status
Disposition
Other core specifications
Abstract specifications
Best Practices Document
How to create CRs using this form:
Comprehensive
information and
tips about how to
create CRs can be
found at:
https://portal.open
geospatial.org/files
/?
artifact_id=10678.
Below is a brief
summary:
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.
Last Revision Date: 2 December 2017
Page3
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
GML CR 08-109r1
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:
GML encoding rule for UML association classes
Source:
CSIRO
Work item code:
Category:
Other
Date: 2008-07-31
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:
Standard UML modelling allows for an association to have a multiple properties, in
the form of an association-class. For most cases this may be converted into an
"intermediate" class which may then be serialized using the standard UML-GML
encoding rule.
Summary of change: An association class may be mapped into an equivalent intermediate class. See the
following diagram:
GML CR 08-109r1
Name:
Package:
Version:
Author:
AssociationClass
GML CRs
1.0
Simon Cox
F12
role2_1
«FeatureTyp...
Feature1
«FeatureTyp...
Feature2
a..b
F34
«FeatureTyp...
Feature3
role3_4
c..d
role4_3
«FeatureTyp...
Feature4
e..f
The encoding rule is to process to perform the mapping and then encode the model
in the standard manner.
Consequences if
not approved:
Association classes not allowed in GML Application Schemas.
Clauses affected:
E
Last Revision Date: 2 December 2017
Page2
GML CR 08-109r1
Other specs
Affected:
Supporting Doc.
Other comments:
Status
Disposition
Other core specifications
Abstract specifications
Best Practices Document
How to create CRs using this form:
Comprehensive
information and
tips about how to
create CRs can be
found at:
https://portal.open
geospatial.org/files
/?
artifact_id=10678.
Below is a brief
summary:
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.
Last Revision Date: 2 December 2017
Page3