Title: Issues List Summary for
ISO/IEC 11179-3 3rd Edition
Status: JTC 1/SC 32/WG 2 Standing
Document
Date: 2005-04-05
Supersedes: N/A
Source: Ray Gates, Canada - Project Editor
The columns in the
document have the following meanings:
·
SEQ # — A sequence number providing ease of
reference within this version of the document.
The association between SEQ # and Cmnt ID changes from one version of
this document to the next as the status of issues, and therefore their position
in the table, changes.
·
Cmnt ID — The comment identifier assigned by the
organization submitting the comment and the submitting organization
·
Related Issues — Pointers to (comment identifiers of) other
comments that appear to be closely related
·
Severity — The severity of the problem as stated by
the organization submitting the comment.
One of:
0-Procedural
1-Major technical
2-Minor technical
3-Major editorial
4-Minor editorial
5-Future topic
·
Reference — The version of the document against which
the comment was made and/or any paper from which the issue was drawn..
·
Title/Description — The description provided by the
organization with the comment; this includes any solution provided by the
organization
·
Priority — “1” = High, “2” = Medium; “3” = Low.
·
Comments — The description provided from initial
consensus
·
Status — The current status of the issue. Possible values are: 1-Open, 2-Draft Resolution, 3-Newly
Resolved, 4-Previously Resolved
This table is sorted
by: Priority, Severity and Cmnt
ID. The sequence number is assigned
after the sort for ease of reference.
|
SEQ |
Cmnt |
Related |
|
|
Title / |
Priority |
Comments |
Status |
|
|
Issue 017 Canada |
Issue 018 Issue 028 Issue 066 Issue 094 |
1-Major Technical |
WD 11179-3
(1999-05-05) SC32 N0267 |
Inter-operability To examine the applicability of
"inter-operability" to each component of the metamodel. |
1 |
e.g.
Implicit value domains, Datatypes, language. |
1-Open |
|
|
Issue 018 Canada |
Issue 017. |
1-Major Technical |
WD 11179-3
(1999-05-05) 32 N 0267 MAT 013 |
Cultural Adaptability Examine the applicability of "cultural
adaptability" to each component of the model, for example in the specification
of names and definitions which are language-dependent. |
1 |
Multilingual
aspects are High priority. Support
culture, language and function via multilingual character strings, with
locale identifier. |
1-Open |
|
|
Issue 022 Canada |
Issue 001 Issue 027 Issue 035 Issue 080 Issue 134 |
1-Major Technical |
WD 11179-3
(1999-05-05) CAN 32C0044R2 |
Applying rules to data
element concepts Solution Provide support for derivation at the data element concept,
similar to that provided by Issue 01 for data elements. |
1 |
Also
applies to other entities in the model, e.g. Conceptual Domain, Value Domain,
Datatype. Relate
to issue 134. Consider provisions and constraints. |
1-Open |
|
|
Issue 049 Ray Gates Cdn expert |
Issue 014 Issue 135 |
1-Major Technical |
WD 11179-3
(1999-05-05) 1999-08-31 metamodel SC32 N0267 |
Applying the metamodel
concepts to its own description. |
1 |
|
1-Open |
|
|
Issue 057 Ray Gates Cdn expert |
Issue 021 Issue 030 Issue 098 |
2-Minor Technical |
1999-10-15
metamodel & WD 11179-3 (1999-10-04) |
Is “context” modeled
correctly? |
1 |
Related
to the namespace issue. |
1-Open |
|
|
Issue 066 Ray Gates Cdn. expert |
Issue 017 |
1-Major Technical |
1999-12-13
WD 11179-3 |
Impact of metamodel extensions on data sharing and access |
2 |
Need
to identify aspects to be specified in 11179-3 vs. 20944. Consider some general purpose attributes
that an implementation can use for its own purposes. |
1-Open |
|
|
Issue 067 Ray Gates Cdn. expert |
Issue 009-6 Issue 033 |
1-Major Technical |
1999-12-13
metamodel |
Use of character collections and encoding schemes for Value Domains |
1 |
May
be addressed by multistrings. Need to
consider whether to specify at the individual data element level or globally
for the register. |
1-Open |
|
|
Issue 080 Ray Gates Cdn expert |
Issue 022 Issue 093 |
2-Minor Technical |
2000-04-13
metamodel |
Dimensionality and Unit of Measure |
2 |
|
1-Open |
|
|
Issue 090 DD Mann [US] |
Issue 127 |
2-Minor Technical |
CD-11179-3 |
Global
Registry Attributes A
Metadata Registry should have a set of attributes that are used to describe
the registry as a whole. |
1 |
Include
implementation specified limits Expanded
on by Issue 127. |
1-Open |
|
|
Issue 093 US |
Issue 080 Issue 125 |
2-Minor Technical |
CD-11179-3 |
Move
Precision Attribute The
"unit_of_measure_precision" attribute should be moved from the
object class "Unit_of_Measure" to "Value_Domain" as
"value_domain_precision". |
1 |
|
1-Open |
|
|
Issue 094 US |
Issue 137 Issue 017 |
1-Major Technical |
CD
11179-3 |
How to register XML
artifacts? |
1 |
To
be explored as part of a new TR on XML Extensions. |
1-Open |
|
|
Issue 096 Canada |
Issue 049 Issue 095 Issue 100 |
1-Major Technical |
CD
11179-3 |
Ability to model Attribute
Capsules |
1 |
Relates
to applying rules to Datatypes and enabling the model to model itself. |
2-Draft
Resolution |
|
|
Issue 097 USA |
|
2-Minor Technical |
FCD-11179-3 |
Is there a standard for phone numbers? |
3 |
Jake
to provide references and for other electronic addresses. Relates to NWI on contact and location.
Std available as ITU E.164 for phone numbers and RFC 2421 for extensions |
1-Open |
|
|
Issue 098 Canada |
Issue 057 Issue 119 |
2-Minor Technical |
FCD-11179-3 |
Scope of name spaces |
1 |
Part
5 proposes a new class. Need
to consider identifiers and designations. |
1-Open |
|
|
Issue 099 Canada |
|
2-Minor Technical |
FCD-11179-3 |
Defining Relationship Types used in the model |
1 |
This
really applies to all attributes in the model. |
1-Open |
|
|
Issue 100 Canada |
Issue 096 Issue 101 |
1-Major Technical |
CD
11179-3 |
Reconciliation with ISO/IEC
11404 |
3 |
Should
Datatype be on Data Element instead of Value Domain. Dan to write proposal. |
1-Open |
|
|
Issue 104 Canada |
|
1-Major Technical |
FCD
11179-3 |
From
FCD comment CAN-P03-169. We should improve the
modeling of roles and persons. |
3 |
Related
to new Contact and Location module and possibly the Relations module. Ref: 15944-1 and 14662 Open-EDI Ref Model |
1-Open |
|
|
Issue 105 Canada |
|
1-Major Technical |
FCD
11179-3 |
Add
Administered Item Relationship |
1 |
We
need to consider relationships in general. C.f. Classification Scheme area of
model. Consider
relationships when looking at boundaries between items. |
1-Open |
|
|
Issue 106 Canada |
|
1-Major Technical |
FCD
11179-3 |
The
modeling of Contact and Location needs to be improved. |
1 |
|
1-Open |
|
|
Issue 107 USA |
Issue 111 Issue 123 |
1-Major Technical |
FCD
11179-3 |
Improve
support for complex data types. |
1 |
|
1-Open |
|
|
Issue 108 USA |
Issue 080 Issue 121 Issue 124 |
2-Minor Technical |
FCD
11179-3 |
Dimensionality
should be attribute of Datatype |
2 |
|
1-Open |
|
|
Issue 109 Canada |
|
1-Major Technical |
FCD
11179-3 |
Add examples of multi-lingual free text elements from
Annex K (of 19115?), or at least references to them. |
2 |
|
1-Open |
|
|
Issue 110 Canada |
|
4-Minor Editorial |
FCD
11179-3 |
Add a reference to ISO 19115 in the Bibliography
because it provides an example of the use of 11179-3 in a standard. |
2 |
|
1-Open |
|
|
Issue 111 Canada |
Issue 107 Issue 123 |
1-Major Technical |
FCD
11179-3 |
Add Support for Group Objects |
1 |
|
1-Open |
|
|
Issue 112 DD Mann |
|
2-Minor Technical |
WG2-XIY-012 |
Value
object class deletion |
1 |
From
Melbourne mtg: Reject because there are
demonstrated requirements, and the proposed change does not provide
equivalent functionality. |
2-Draft Resolution |
|
|
Issue 113 DD Mann |
|
2-Minor Technical |
WG2-XIY-013 |
Qualifiers
in Data Element Concept |
2 |
From
Melbourne mtg: Accepted. Add text about handling backwards
compatibility. |
2-Draft Resolution |
|
|
Issue 114 DD Mann |
|
1-Major Technical |
WG2-XIY-023 |
Remove
Representation Class |
1 |
From
Xi'an mtg: Remove Representation
Class from the model. Describe a
mechanism(s) for equivalent functionality using the model. |
3-Newly Resolved |
|
|
Issue 115 DD Mann |
|
2-Minor Technical |
WG2-XIY-024 |
Qualifier
in Data Element |
2 |
From
Xi'an mtg: Accepted. |
2-Draft Resolution |
|
|
Issue 116 DD Mann |
|
1-Major Technical |
WG2-XIY-025 |
Remove
Object Class and Property |
1 |
From
Xi'an mtg: Not Accepted. |
2-Draft Resolution |
|
|
Issue 117 DD Mann |
|
2-Minor Technical |
WG2-XIY-026 |
Reference
to ISO/IEC 10027. |
3 |
From
Xi'an mtg:Add the reference to TR 10032
but keep the reference to ISO/IEC 10027 |
2-Draft Resolution |
|
|
Issue 118 DD Mann |
|
1-Major Technical |
WG2-XIY-014 |
Naming
Convention |
1 |
From
Xi'an mtg: Accepted. |
2-Draft Resolution |
|
|
Issue 119 DD Mann |
Issue 098 |
1-Major Technical |
WG2-XIY-015 |
Namespace |
1 |
From
Xi'an mtg: Accepted,
pending more work on part 5, edition 3. |
2-Draft Resolution |
|
|
Issue 120 DD Mann |
|
1-Major Technical |
WG2-XIY-016 |
Namespace
– Naming Convention Relationship |
1 |
From
Xi'an mtg: Accepted,
pending more work on part 5, edition 3. |
2-Draft Resolution |
|
|
Issue 121 DD Mann |
Issue 080 Issue 108 Issue 124 |
2-Minor Technical |
WG2-XIY-027 |
Expanding
on the description of "dimensionality" |
2 |
From
Xi'an mtg: Accepted
with amendments |
2-Draft Resolution |
|
|
Issue 122 Gillman |
|
1-Major Technical |
WG2-XIY-003R1 |
Concept
Super-Class |
1 |
From
Xi'an mtg: Accepted in
principle, with modification. Needs
further consideration. |
1-Open |
|
|
Issue 123 Gillman |
Issue 107 Issue 111 |
1-Major Technical |
WG2-XIY-004R1 |
Aggregated
Data |
1 |
From
Xi'an mtg: Not Accepted. |
2-Draft Resolution |
|
|
Issue 124 Gillman |
Issue 080 Issue 108 Issue 121 |
2-Minor Technical |
WG2-XIY-005R1 |
Dimensionality |
2 |
From
Xi'an mtg:Defer pending input from NIST
project on dimensionality. |
1-Open |
|
|
Issue 125 DD Mann |
Issue 093 |
2-Minor Technical |
WG2-XIY-006R1 |
Precision
attribute |
2 |
From
Xi'an mtg: See discussion notes. |
1-Open |
|
|
Issue 126 DD Mann |
|
2-Minor Technical |
WG2-XIY-007R1 |
accuracy
attribute |
2 |
From
Xi'an mtg: Accepted. |
2-Draft Resolution |
|
|
Issue 127 DD Mann |
Issue 090 |
2-Minor Technical |
WG2-XIY-008R1 |
Global
attributes for Register |
1 |
From
Xi'an mtg: Accepted
with amendments |
2-Draft Resolution |
|
|
Issue 128 DD Mann |
|
3-Major Editorial |
WG2-XIY-009R1 |
Remove
Annex B |
3 |
From
Xi'an mtg: Accepted. |
2-Draft Resolution |
|
|
Issue 129 DD Mann |
Issue 096 |
1-Major Technical |
WG2-XIY-010R1 |
Attribute
Capsule – resolution to Issue 96. |
2 |
From
Xi'an mtg: Accepted. |
2-Draft Resolution |
|
|
Issue 130 Farance |
|
1-Major Technical |
|
Referring Designation |
1 |
From
Xi'an mtg: Accepted in
principle |
1-Open |
|
|
Issue 131 Farance |
|
1-Major Technical |
|
Use
of Ref/Lit datatype instead of String |
1 |
From
Xi'an mtg: Accepted in
principle Need
dereference scheme for references. |
1-Open |
|
|
Issue 132 Farance |
|
1-Major Technical |
|
Identifier-Type-Value
(ITV) bucket |
1 |
From
Xi'an mtg: Accepted in
principle |
1-Open |
|
|
Issue 133 Farance |
|
1-Major Technical |
|
Data
quality |
1 |
From
Xi'an mtg: Accepted in
principle |
1-Open |
|
|
Issue 134 Masa O. |
Issue 022 |
1-Major Technical |
|
Specification
of Constraints |
1 |
From
Xi'an mtg:Awaiting receipt of constraint
descriptions. |
1-Open |
|
|
Issue 135 Masa O. |
Issue 049 |
1-Major Technical |
|
Respecify
the model using MOF |
1 |
From
Xi'an mtg: Await receipt of the model. |
1-Open |
|
|
Issue 136 USA |
|
2-Minor Technical |
|
Directed relationships |
1 |
|
1-Open |
|
|
Issue 137 Canada |
Issue 094 |
1-Major Technical |
|
Reconciliation with ebXML registry |
1 |
To
be submitted |
1-Open |
|
|
Issue 138 USA |
|
2-Minor Technical |
|
Relationship type description |
1 |
To
be submitted |
1-Open |
|
|
Issue 139 USA |
|
2-Minor Technical |
|
Rename Relationships in Figure 3 |
1 |
To
be submitted |
1-Open |
|
|
Issue 140 USA |
|
1-Major Technical |
|
Make “relationship types” into “administered items” |
1 |
To
be submitted |
1-Open |
|
|
Issue 141 USA |
|
1-Major Technical |
|
Identify types of correspondences among “concepts” |
1 |
To
be submitted |
1-Open |
|
|
Issue 142 USA |
|
1-Major Technical |
|
Encode clustered groups in “classification scheme” |
1 |
To
be submitted |
1-Open |
|
|
Issue 143 USA |
|
1-Major Technical |
|
Register formal definitions |
1 |
To
be submitted |
1-Open |
|
|
Issue 144 USA |
|
1-Major Technical |
|
Add “meaning link” from “concept scheme item” to “conceptual domain” |
1 |
To
be submitted |
1-Open |
|
|
Issue 145 USA |
|
1-Major Technical |
|
Use “value domains” to manage “relationship types” |
1 |
To
be submitted |
1-Open |
|
|
Issue 146 USA |
|
1-Major Technical |
|
Add cardinality constraints for both ends of relationships |
1 |
To
be submitted |
1-Open |
|
|
Issue 147 USA |
|
1-Major Technical |
|
Encode data element derivation rules in the data model |
1 |
To
be submitted |
1-Open |
|
|
Issue 148 USA |
|
1-Major Technical |
|
Register formal axioms |
1 |
To
be submitted |
1-Open |
|
|
Issue 149 USA |
|
1-Major Technical |
|
Make axiom module “administered items” |
1 |
To
be submitted |
1-Open |
|
|
Issue 150 USA |
|
1-Major Technical |
|
Represent “rule templates” in data model |
1 |
To
be submitted |
1-Open |
|
|
Issue 151 USA |
|
1-Major Technical |
|
Registration of ontologies |
1 |
To
be submitted |
1-Open |
|
|
Issue 152 USA |
|
1-Major Technical |
|
Represent alternative axiomatic representation of an ontology |
1 |
To
be submitted |
1-Open |
|
|
Issue 153 USA |
|
1-Major Technical |
|
Specify order of sibling concepts in hierarchical concept scheme |
1 |
To
be submitted |
1-Open |
|
|
Issue 154 USA |
|
1-Major Technical |
|
Add Dublin Core attributes to “reference_document” |
1 |
To
be submitted |
1-Open |
|
|
Issue 155 USA |
|
1-Major Technical |
|
Reify “reference” relationship to permit types of reference relationships |
1 |
To
be submitted |
1-Open |
|
|
Issue 156 USA |
|
1-Major Technical |
|
Distinguish coordinates from interval measures |
1 |
To
be submitted |
1-Open |
|
|
Issue 157 USA |
|
1-Major Technical |
|
Add contexts for definitions |
1 |
To
be submitted |
1-Open |
|
|
Issue 158 USA |
|
1-Major Technical |
|
Rename “classification scheme” |
1 |
To
be submitted |
1-Open |
|
|
Issue 159 USA |
|
1-Major Technical |
|
Make “classification scheme” an “administered item” |
1 |
To
be submitted |
1-Open |
|
|
Issue 160 USA |
|
1-Major Technical |
|
Add ability to register “structured entities” |
1 |
To
be submitted |
1-Open |
|
|
Issue 161 USA |
|
1-Major Technical |
|
Register “behaviors” |
1 |
To
be submitted |
1-Open |
|
|
Issue 162 USA |
|
1-Major Technical |
|
Default Set of Relationship Types |
1 |
To
be submitted |
1-Open |
|
|
Issue 163 USA |
|
1-Major Technical |
|
Add type constraints (e.g., domain and range constraints) to relationship types |
1 |
To
be submitted |
1-Open |
|
|
Issue 164 USA |
|
1-Major Technical |
|
Allow specification of “value domains” by reference
to “classification schemes” |
1 |
To
be submitted |
1-Open |