Title: Issues List Summary for
ISO/IEC 11179-3 Revision
Status: JTC 1/SC 32/WG 2 Standing
Document
Date: 9 May 2001
Supersedes: 27
February 2000
Source: Ray Gates, Canada, for the 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..
· Description The description provided by the organization with the comment; this includes any solution provided by the organization
· Addressed By Comment if a solution was provided by the organization; a paper number if a known proposal addresses the comment; the version of the WD or metamodel that incorporates the proposal and/or resolution, blank otherwise.
· Tentative Resolution 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: Status, Severity and Cmnt ID. The sequence number is assigned after the sort for ease of reference.
|
SEQ |
Cmnt |
Related |
|
|
Title / |
Addressed By |
Resolution |
Status |
|
13 001 |
Issue 028 Ray Gates Cdn expert |
Issue 017 Issue 025 Issue 029 |
2-Minor Technical |
FCD-11179-3 |
Provide default values for
optional parts of identifiers. Solution |
|
|
1-Open |
|
13-002 |
Issue 081 Ray Gates Cdn expert |
|
2-Minor Technical |
FCD-11179-3 |
Remove inappropriate aggregation symbols |
2000-05-12
metamodel |
|
1-Open |
|
13-003 |
Issue 095 |
|
2-Minor Technical |
FCD-11179-3 |
Attribute
Capsule term and definition |
|
|
1-Open |
|
13-004 |
Issue 097 |
|
2-Minor Technical |
FCD-11179-3 |
Is there a standard for phone numbers? |
|
|
1-Open |
|
13-005 |
Issue 098 |
|
2-Minor Technical |
FCD-11179-3 |
Scope of name spaces |
|
|
1-Open |
|
13-006 |
Issue 099 |
|
2-Minor Technical |
FCD-11179-3 |
Defining Relationship Types used in the model |
|
|
1-Open |
|
13-007 |
Issue 103 |
|
3-Major Editorial |
CD-11179-3 |
Annex B IDL Representation of the metamodel |
|
|
1-Open |
This table is sorted by: Status, Severity and Cmnt ID. The sequence number is assigned after the sort for ease of reference.
|
SEQ |
Cmnt |
Related |
|
|
Title / |
Addressed By |
Resolution |
Status |
|
14-001 |
Issue 017 Canada |
Issue 018 Issue 028 Issue 066 |
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-Open |
|
14-002 |
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-Open |
|
14-003 |
Issue 022 Canada |
Issue 001 Issue 027 Issue 035 Issue 080 |
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-Open |
|
14-004 |
Issue 049 Ray Gates Cdn expert |
Issue 014 |
1-Major Technical |
WD 11179-3
(1999-05-05) 1999-08-31 metamodel SC32 N0267 |
Applying the metamodel
concepts to its own description. |
|
|
1-Open |
|
14-005 |
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 |
|
|
1-Open |
|
14-006 |
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-Open |
|
14-007 |
Issue 091 US |
|
1-Major Technical |
CD
11179-3 |
Naming
& Definition Region Restructure Naming
and Definition Region restructured to support multiple names and multiple
definitions within a Context. |
|
|
1-Open |
|
14-008 |
Issue 094 US |
|
1-Major Technical |
CD
11179-3 |
How to register XML tags for
data. We need to be able to register XML tags for at least
Data Elements, probably for any Administered Item, and possibly for Values
and Value Meanings. |
|
To
be explored as part of a new TR on XML Extensions. Comments
from Ray Gates: We
should keep the issue open until we have a concrete proposal, and can tell
whether or not the model needs extending. |
1-Open |
|
14-009 |
Issue 096 Canada |
Issue 049 Issue 095 Issue 100 |
1-Major Technical |
CD
11179-3 |
Ability to model Attribute
Capsules |
|
|
1-Open |
|
14-010 |
Issue 100 Canada |
Issue 096 Issue 101 |
1-Major Technical |
CD
11179-3 |
Reconciliation with ISO/IEC
11404 |
|
|
1-Open |
|
14-011 |
Issue 101 Canada |
Issue 100 |
1-Major Technical |
CD
11179-3 |
Non-enumerated Conceptual
Domains |
|
|
1-Open |
|
14-012 |
Issue 102 Canada |
|
1-Major Technical |
CD
11179-3 |
Conformance to Basic
Attributes |
|
|
1-Open |
|
14-013 |
Issue 057 Ray Gates Cdn expert |
Issue 021 Issue 030 |
2-Minor Technical |
1999-10-15
metamodel & WD 11179-3 (1999-10-04) |
Is context modeled
correctly? |
|
This may require additional investigation. 19991209. Ray to propose new text to describe what
is actually supported today. |
1-Open |
|
14-014 |
Issue 080 Ray Gates Cdn expert |
Issue 022 Issue 093 |
2-Minor Technical |
2000-04-13
metamodel |
Dimensionality and Unit of Measure |
2000-05-12
metamodel |
|
1-Open |
|
14-015 |
Issue 090 DD Mann [US] |
|
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-Open |
|
14-016 |
Issue 093 US |
Issue 080 |
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-Open |
The issues in this table are sorted on Cmnt ID.
|
SEQ |
Cmnt |
Related |
|
|
Title / |
Addressed By |
Resolution |
Status |
|
|
Issue 001 DD Mann US expert |
Issue 022 Issue 027 Issue 035 Issue 054 Issue 064 |
2-Minor Technical |
WD 11179-3
(1998-12-08) |
Data_Element relationship to Rule Solution Refine the structure between Rule and Data_Element Support an environment where an IDEF0 activity
with its ICOMs (inputs, controls, outputs, mechanisms) or a function of x =
f(y) can be expressed. Remove the data_element_rule relationship. Add the entity Input_Set. This is an ordered set aggregation of
Data_Elements that is used to derive a Data_Element. Add the relationship between Data_Element and
Input_Set that identifies the set of Data_Elements that are used to derive
the Data_Element. Add a relationship between Input_Set and Rule
to derive the Data_Element. Add
associated textual descriptions. |
Issue 064 and 2000-04-13 metamodel. |
Date: 1999-06-25 Proposal accepted. Some additional text
changes identified as required. Resolution modified by Issue 054. Further modified by Issue 064. |
4-Previously Resolved |
|
|
Issue 002 DD Mann US expert |
Issue 031 Issue 071 |
2-Minor Technical |
WD 11179-3
(1998-12-08) |
Concept_Application_Association Solution Specify the Concept_Application_Association role. Add an attribute to
Concept_Application_Association for role. |
Issue 071 |
Issue 071 replaces Role by Type
Description |
4-Previously Resolved |
|
|
Issue 003 DD Mann US expert |
Issue 023 Issue 039 |
1-Major Technical |
WD 11179-3
(1998-12-08) |
Classified_Component. Solution Eliminate the Classified_Component entity. Eliminate the Classified_Component entity by
collapsing it into its supertype of Administered_Component. This entails moving the
Classified_Component relationships to the Administered_Component. |
Issue 039. |
Resolved by Issue 039. |
4-Previously Resolved |
|
|
Issue 004 DD Mann US expert |
Issue 009-07 |
2-Minor Technical |
WD 11179-3
(1998-12-08) |
Contact_Person Solution Add attributes to contact person Contact_Person add the
attributes: |
WD 11179-3 (1999-05-05) WD 11179-3 (1999-12-13) 2000-05-12 metamodel |
Agreed.
Consider whether there are other attributes that should added: e.g.
Cell phone number, pager number. Text changes (including cell phone number and
pager number) included in 1999-12-13 WD. Cell phone number and pager number included in
2000-05-12 metamodel. |
4-Previously Resolved |
|
|
Issue 005 DD Mann US expert |
Issue 025 |
2-Minor Technical |
WD 11179-3
(1998-12-08) |
Component_Registration_Authority Solution The identifier should be decomposed
to include the following attributes: |
Issue 025. |
Resolved by Issue 025 |
4-Previously Resolved |
|
|
Issue 006 DD Mann US expert |
Issue 009-01 Issue 024 Issue 032 Issue 055 |
1-Major Technical |
WD 11179-3
(1998-12-08) |
Administered_Component Solution Remove the totality and exclusive
subtype constraints on the Administered_Component entity. |
Issue 009-01 Issue 032. |
Resolved by Issue 009-01 & Issue 032. This may not be a complete resolution. |
4-Previously Resolved |
|
|
Issue 007 DD Mann US expert |
Issue 056 Issue 059 |
2-Minor Technical |
WD 11179-3
(1998-12-08) |
Data_Element_Concept relationship
with Conceptual_Domain Solution The cardinality of
Conceptual_Domain to Data_Element_Concept should change |
WD 11179-3 (1999-05-05) WD 11179-3 (1999-12-13) |
Proposal accepted. Relationship name added in 1999-12-13 metamodel. Text
description also required. |
4-Previously Resolved |
|
|
Issue 008 DD Mann US expert |
Issue 011 Issue 014 Issue 068 Issue 071 Issue 075 Issue 077 Issue 078 Issue 082 |
1-Major Technical |
WD 11179-3
(1998-12-08) WG2 N215 WG2 N216 |
Harmonization of terms and definitions Solution An analysis of the terms and
definitions in the ISO/IEC 11179-3 and other parts of ISO/IEC 11179 should be
reviewed and harmonized with existing ISO and ISO/IEC standards |
WG2 N203 WG2 N219 |
Adequately addressed for this release. |
4-Previously Resolved |
|
|
Issue 009 DD Mann US expert |
Issue 055, & see
specific proposals. |
1-Major Technical |
WD 11179-3
(1998-12-08) |
Proposed Metamodel revision
UML-3b Solution See following 10 proposals. |
|
See specific proposals. |
4-Previously Resolved |
|
|
Issue 009-01 DD Mann US expert |
Issue 006 Issue 024 Issue 032 Issue 055 |
1-Major Technical |
WD 11179-3
(1998-12-08) |
Encapsulation of the
administered component as administration record. This then becomes the datatype for the
attribute administration data that is utilized in data element, data
element concept, object class, property, etc.. |
Issue 032. |
Resolved by Issue 032. |
4-Previously Resolved |
|
|
Issue 009-02 DD Mann US expert |
Issue 038 Issue 055 |
1-Major Technical |
WD 11179-3
(1998-12-08) |
Encapsulation of object class
for use as a datatype for the attribute object class in data element
concept. |
WD 11179-3 (1999-05-05) |
Originally agreed, but reopened by Issue 038.
Resolution of Issue 038 is to reject the proposal, so the original agreement
re Issue 009-02 still stands. |
4-Previously Resolved |
|
|
Issue 009-03 DD Mann US expert |
Issue 038 Issue 055 |
1-Major Technical |
WD 11179-3
(1998-12-08) |
Encapsulation of property for
use as a datatype for the attribute property in data element concept |
WD 11179-3 (1999-05-05) |
Originally agreed, but reopened by Issue 038. Resolution of Issue 038 is to reject the
proposal, so the original agreement re Issue 009-03 still stands. |
4-Previously Resolved |
|
|
Issue 009-04 DD Mann US expert |
|
2-Minor Technical |
WD 11179-3
(1998-12-08) |
Encapsulation of unit of
quantity for use as a datatype for the attribute unit of quantity in
value domain. |
WD 11179-3 (1999-05-05) |
Proposal accepted. |
4-Previously Resolved |
|
|
Issue 009-05 DD Mann US expert |
|
2-Minor Technical |
WD 11179-3
(1998-12-08) |
Encapsulation of datatype for use as a
datatype for the attribute datatype in value domain. |
WD 11179-3 (1999-05-05) |
Proposal accepted. |
4-Previously Resolved |
|
|
Issue 009-06 DD Mann US expert |
Issue 033 Issue 055 Issue 067 |
2-Minor Technical |
WD 11179-3 (1998-12-08) |
Encapsulation of codeset for use as a
datatype for the attribute codeset in value domain. |
WD 11179-3 (1999-05-05) |
Resolved by Issue 033. |
4-Previously Resolved |
|
|
Issue 009-07 DD Mann US expert |
Issue 004 Issue 055 |
1-Major Technical |
WD 11179-3
(1998-12-08) |
Encapsulation of contact person for use as a
datatype for the attribute contact person in component responsible
organization and . component submitting organization |
WD 11179-3 (1999-05-05) |
Proposal accepted. |
4-Previously Resolved |
|
|
Issue 009-08 DD Mann US expert |
Issue 041 |
2-Minor Technical |
WD 11179-3
(1998-12-08) |
Encapsulation of representation class for
use as a datatype for the attribute representation class in data element. |
WD 11179-3 (1999-05-05) |
Proposal accepted. |
4-Previously Resolved |
|
|
Issue 009-09 DD Mann US expert |
Issue 005 Issue 025 |
2-Minor Technical |
WD 11179-3
(1998-12-08) |
Encapsulation of component identifier for
use as a datatype for the identifier in component registration authority. |
WD 11179-3 (1999-05-05) |
Resolved by Issue 025. |
4-Previously Resolved |
|
|
Issue 009-10 DD Mann US expert |
Issue 31 |
2-Minor Technical |
WD 11179-3
(1998-12-08) |
Change the name of component
name context to designation |
WD 11179-3 (1999-05-05) |
Proposal accepted. |
4-Previously Resolved |
|
|
Issue 010-01 DD Mann US expert |
Issue 012 Issue 051 Issue 052 |
3-Major Editorial |
WD 11179-3
(1998-12-08) |
Change the title of 11179-3 to
Basic attributes of data element components. |
CD 11179-3 |
The WG2 Manhattan meeting changed the title
of ISO/IEC 11179 to "Information technology - Data Management and
Interchange - Metadata Registries (MDR) Status left as Draft Resolution
pending results of CD ballot. |
4-Previously Resolved |
|
|
Issue 010-02 DD Mann US expert |
Issue 086 Issue 087 |
2-Minor Technical |
WD 11179-3
(1998-12-08) |
Proposed change of terms - Data Element Component Throughout the document the term data element should be changed to data element component wherever the notion is of one of the components in the metamodel. Wherever the notion of just data element exists, the term should not change. |
|
Resolved by Issue 087. |
4-Previously Resolved |
|
|
Issue 011 Canada |
Issue 008 Issue 051 Issue 052 |
1-Major Technical |
WD 11179-3
(1999-05-05) SC32N0264 |
Canada believes that
incorporation of ANS X 3.285 into ISO/IEC 11179 requires changes to all parts
of ISO/IEC 11179, not just Part 3. |
|
Editors of each part are requested to identify
the impact on their part of the changes being made to part 3. |
4-Previously Resolved |
|
|
Issue 012 Canada |
Issue 010-01 |
1-Major Technical |
WD 11179-3
(1999-05-05) SC32 N0263 SC32 N0264 SC32 N0267 |
Proposed restructuring and change
of name of ISO/IEC 11179 and its parts |
|
The majority of participants prefer to retain
the existing structure. |
4-Previously Resolved |
|
|
Issue 013-02 Canada |
|
0-Procedural |
WD 11179-3
(1999-05-05) |
Procedures for Progression of Working Draft
(2) While formal progressions of the standard will
be carried out in accordance with JTC1 directives, as much work as possible
should be carried out by email and/or teleconference. |
|
A revised working draft was posted October 4,
to act as a baseline against which detailed change proposals may be made to
resolve outstanding issues. A
subsequent draft is targeted for December 1.
It is hoped that we may be able to produce a CD out of the January
meeting. |
4-Previously Resolved |
|
|
Issue 013-1 Canada |
|
0-Procedural |
WD 11179-3
(1999-05-05) |
Procedures for Progression of Working Draft
(1) That change proposals to Working Drafts (and
subsequent progressions) be documented according to the format used by L8 in
development of the metamodel; and that these be accessible from the WG2
Website. |
SD11 and SD12 |
Issues to be documented in standard form in
standing documents. WG2 FTP and Web site to be revamped. Frank Farance to provide a new web/ftp site. Status left as Draft resolution until new
web site operational. |
4-Previously Resolved |
|
|
Issue 013-3 Canada |
Issue 011 Issue 012 |
0-Procedural |
WD 11179-3
(1999-05-05) |
Procedures for Progression of Working Draft
(3) Canada
has recommended that WG2 establishes procedures to accomplish the merger of
ANS X3.285 with part 3, including: ·
projects
under which each new part can be progressed ·
editorial
support for new working drafts for each part ·
meeting time to discuss the impact on each part. |
Issue
011. |
Editors for the revision of each part have been nominated. |
4-Previously
Resolved |
|
|
Issue 014 Canada |
Issue 008 Issue 016 |
1-Major Technical |
WD 11179-3
(1999-05-05) SC32 N0264 32 N0265 MAT 013 |
Alignment of metamodel with definitions and other text. Solution That the normative text (Clauses 4 to 7 inclusive)
drawn from the existing Part 3 be checked against, and aligned with, the
metamodel and accompanying data dictionary in Clauses 8 and 9. |
|
Metamodel
has been aligned with the definitions in CD 11179-3 (SC32 N0490). Any
problems found in the CD should be raised as ballot comments. |
4-Previously
Resolved |
|
|
Issue 015 Canada |
|
3-Major Editorial |
WD 11179-3
(1999-05-05) |
General editing Page numbers, clauses and Annexes to be numbered
correctly. Solution |
WD
11179-3 (1999-12-13) |
1999-12-13
WD has partially addressed these issues.
There are still some cross-references to clauses that need to be
updated. Ray Gates is assisting the
editor with the use of the template. |
4-Previously
Resolved |
|
|
Issue 016-1 Canada |
Issue 014 |
1-Major Technical |
WD 11179-3
(1999-05-05) 32N0265 MAT013 |
Linguistically neutral identifier (1) - problems
inherited from 11179-3 Solution A linguistically neutral identifier should be made
mandatory for all data element components. |
WD
11179-3 (1999-05-05) |
Resolved,
as a linguistically neutral identifier for each data element component is
already a mandatory requirement in the metamodel. Editor to ensure that the
Committee Draft makes this abundantly clear. Editor to ensure clear
distinction between language-dependent and language-independent concepts in
normative text. |
4-Previously
Resolved |
|
|
Issue 016-2 Canada |
Issue 037 |
1-Major Technical |
WD 11179-3
(1999-05-05) 32N0265 MAT013 |
Linguistically neutral identifier (2) - problems introduced by recent metamodel changes. Solution An Administered Component requires a linguistically neutral identifier. |
|
Issue
037 restates problem 2 in the context of the 1999-08-31 metamodel. See further discussion under Issue 037. In Helsinki, Issue 037 was accepted |
4-Previously
Resolved |
|
|
Issue 019 Canada, France |
Issue 001 Issue 031 |
1-Major Technical |
WD 11179-3
(1999-05-05) MAT 013 |
Supporting various levels of granularity of data |
WD
11179-3 (1999-05-05) |
The
standard already supports this. |
4-Previously
Resolved |
|
|
Issue 020 Canada |
|
3-Major Editorial |
WD 11179-3
(1999-05-05) |
Informative Annexes / Content Technical Report Canada supports the use of the UML model in the normative text, and inclusion of the Chen-based model to an Annex if desired. The Canadian raises the broader issue of how to handle
the multiplicity of annexes that are candidates for inclusion in the
standard. |
CD
11179-3 (SC32 N0490) |
CD
11179-3 (32N0490) contains the Annexes agreed to be kept. |
4-Previously
Resolved |
|
|
Issue 021 Canada |
Issue 030 Issue 057 |
2-Minor Technical |
WD 11179-3
(1999-05-05) |
Name-context relationships Solution Clarify the textual description of the context of a
name to match the representation in the metamodel. |
|
Resolved
by CD ballot comment CAN-P03-069. |
4-Previously
Resolved |
|
|
Issue 023 Canada |
Issue 003 Issue 039 Issue 050 Issue 057 Issue 058 |
1-Major Technical |
WD 11179-3 (1999-05-05 CAN 32C0048R3 |
Canadian response to Issue 003. Solution 1.
Rename
Classified Component to Administered Component. 2.
Make the relationship with Classification Scheme optional
in both directions. |
Issue
039, Issue 050, Issue 058 Metamodel |
Resolved
by Issue 039 as modified by issues 050 and 058. |
4-Previously
Resolved |
|
|
Issue 024 Canada |
Issue 006 Issue 009 Issue 016 Issue 023 Issue 032 |
2-Minor Technical |
WD 11179-3 (1999-05-05 CAN 32C0053R2 SC32 N0265 CAN 32C0048R2 |
Canadian
Response to Issue 009-01 Instead
of the change proposed by DM09 item 1, in Figure 3 of [2] merge
Component_Record with Component_Registration_Authority, since the record is
maintained by a Registration Authority about a Component. |
Issue
032. |
Resolved
by issue 032. |
4-Previously
Resolved |
|
|
Issue 025 Ray Gates Cdn expert |
Issue 005 Issue 028 |
2-Minor Technical |
WD 11179-3
(1999-05-05) CAN 32C0054R1 |
Canadian Response to Issue 005 - Component Identifier Solution 1.
We should identify two
structured identifiers, as shown in Figure 1 of [3]: Registration
Authority Identifier <<Required>>
International Code Designator (ICD) <<Required>> Organization Identifier (OI) <<Optional>>
Organization Part Identifier (OPI) <<Conditional>> OPI Source (OPIS) Component Identifier <<Required>> Registration Authority Identifier <<Required>> Data Identifier <<Required>> Version 2.
These structures should replace the existing
Component Identifier in Figure 3 of [2], and the identifier of Registration
Authority should become registration authority
identifier. |
1999-08-31
metamodel. |
Accepted. |
4-Previously
Resolved |
|
|
Issue 026 US & Canada |
Issue 061 |
2-Minor Technical |
WD 11179-3
(1999-05-05) |
Last change date Add an attribute to the Administration_Record for
Last_change_date This would be a
conditional attribute linked with the occurrence of a change. Solution |
1999-08-31
metamodel. |
Accepted.
|
4-Previously
Resolved |
|
|
Issue 027 US & Canada |
Issue 001 Issue 022 |
5-Future Topic |
WD 11179-3
(1999-05-05) |
A set of guidelines on the use of rules should be
developed. Solution |
|
This
should be passed to the Content group for their Technical Report. It should not be in the Part 3 revision. |
4-Previously
Resolved |
|
|
Issue 029 Ray Gates Cdn expert |
|
2-Minor Technical |
WD 11179-3
(1999-05-05) |
Move OPI-source out of
registration identifier. Solution Proposal withdrawn after
review of ISO 6523. |
|
Withdrawn |
4-Previously
Resolved |
|
|
Issue 030 Ray Gates Cdn expert |
Issue 021 Issue 057 |
2-Minor Technical |
WD 11179-3
(1999-05-05) |
Identification and naming of
Context. Make Context an
Administered Component. Solution |
Included
in 2000-05-12 metamodel |
Accepted. |
4-Previously
Resolved |
|
|
Issue 031 DD Mann US expert |
Issue 032 Issue 040 Issue 076 |
2-Minor Technical |
WD 11179-3
(1999-05-05) |
Objectified relationship
names. Use the same name for the
relationship and the object that represents it. |
1999-08-31
metamodel. |
Accepted. Further
changes proposed by Issue 076. |
4-Previously
Resolved |
|
|
Issue 032 DD Mann US expert |
Issue 009-01 Issue 024 Issue 031 |
2-Minor Technical |
WD 11179-3
(1999-05-05) |
Revise relationship between
Registration Authority and Administered Component. |
1999-08-31
metamodel. |
Agreed.
Included in Current Model 19991213. Corresponding text
changes required. |
4-Previously
Resolved |
|
|
Issue 033 DD Mann US expert |
Issue 009-06 Issue 034 Issue 067 |
2-Minor Technical |
WD 11179-3
(1999-05-05) |
Removal of value domain
character set. Attribute removed
in 1999-08-31 through 19991213 metamodels. |
Issue
067. |
Acceptance
of original proposal confirmed at Helsinki meeting. |
4-Previously
Resolved |
|
|
Issue 034 DD Mann US expert |
Issue 033 |
2-Minor Technical |
WD 11179-3
(1999-05-05) |
Removal of value domain
minimum and maximum character quantity. |
|
Delete
minimum. Keep maximum and make it
optional. |
4-Previously
Resolved |
|
|
Issue 035 DD Mann US expert |
Issue 080 |
2-Minor Technical |
WD 11179-3
(1999-05-05) |
Addition of a dimensionality
attribute to the conceptual domain |
1999-08-31
metamodel. Issue
080 |
Accepted. |
4-Previously
Resolved |
|
|
Issue 036 DD Mann US expert |
|
2-Minor Technical |
WD 11179-3
(1999-05-05) |
Add explanatory comment as
attribute of Administered Component. |
1999-08-31
metamodel. |
Accepted. |
4-Previously
Resolved |
|
|
Issue 037 Ray Gates Cdn expert |
Issue 016 Issue 039 Issue 084 |
1-Major Technical |
WD 11179-3
(1999-05-05) |
Requirement for Administered
Component Information. Make Administered Component
Information <<required>>. |
|
CD
ballot comment CAN-P03-031 accepted. Administration Record made mandatory |
4-Previously
Resolved |
|
|
Issue 038 Ray Gates Cdn expert |
Issue 009-2 Issue 009-3 Issue 055 |
2-Minor Technical |
WD 11179-3
(1999-05-05) |
Relationship of Data Element
Concept to Object Class. Reverse out the changes
applied by Issue 009 items 2 and 3. |
|
Rejected. |
4-Previously
Resolved |
|
|
Issue 039 Ray Gates Cdn expert |
Issue 003 Issue 023 Issue 040 Issue 041 Issue 042 Issue 050 Issue 058-1 Issue 058-2 |
1-Major Technical |
1999-08-31 metamodel |
Merge Classified Component
with Administered Component. This is effectively a
restatement of issue 003 in the context of the latest (99/08/31) model. |
1999-10-15
metamodel. |
Agreed.
See also resolution of issue 58 1999-12-09 |
4-Previously
Resolved |
|
|
Issue 040 Ray Gates Cdn expert |
Issue 031 Issue 039 Issue 041 Issue 042 Issue 050 |
2-Minor Technical |
1999-08-31 metamodel |
Rename Link in Classification
Region of Meta Model |
1999-10-15
metamodel. |
Rename
to Classification Scheme Item Relation. |
4-Previously
Resolved |
|
|
Issue 041 Ray Gates Cdn expert |
Issue 039 Issue 040 Issue 042 Issue 050 |
1-Major Technical |
1999-08-31 metamodel |
Representation Class as
Classification Scheme. |
|
Withdrawn. |
4-Previously
Resolved |
|
|
Issue 042 Ray Gates Cdn expert |
Issue 039 Issue 050 Issue 051 Issue 058-1 Issue 058-2 |
2-Minor Technical |
CD 11179-3 |
Clause 4.71 refers to
Classified Components as if they were part of the model, but classification
is now just a relationship between a Classification Scheme Item and an
Administered Component. |
|
Resolved
by CD ballot comments CAN-P03-113 through CAN-P03-119. The
term "classified component" is no longer used. |
4-Previously
Resolved |
|
|
Issue 043 Canada |
Issue 044 Issue 045 Issue 046 Issue 047 Issue 048 Issue 079 |
1-Major Technical |
1999-08-31 metamodel |
Support for multiple
languages |
Issue
044 Issue
045 Issue
046 Issue
047 Issue
048 |
Agreed
in principle. See issues 044-048 for
details. Included in Model 19991209 |
4-Previously
Resolved |
|
|
Issue 044 Canada |
Issue 043 Issue 045 Issue 046 Issue 047 Issue 048 Issue 079 |
2-Minor Technical |
1999-08-31 metamodel |
Support for multiple
documentation languages in registration authority. |
1999-10-15
metamodel. |
Accepted,
with Language encapsulated as a separate object class, incorporating both a
language identifier and an optional country identifier. |
4-Previously
Resolved |
|
|
Issue 045 Canada |
Issue 043 Issue 044 Issue 046 Issue 047 Issue 048 Issue 079 |
2-Minor Technical |
1999-08-31 metamodel |
Allow multiple languages to
be specified for reference documents. |
1999-10-15
metamodel. |
Accepted,
with Language encapsulated as a separate object class, incorporating both a
language identifier and an optional country identifier. |
4-Previously
Resolved |
|
|
Issue 046 Canada |
Issue 043 Issue 044 Issue 045 Issue 047 Issue 048 Issue 079 |
2-Minor Technical |
1999-08-31 metamodel |
Make Language a property of
Definition and Designation, rather than Context. |
1999-10-15
metamodel. |
Accepted,
with Language encapsulated as a separate object class, incorporating both a
language identifier and an optional country identifier. |
4-Previously
Resolved |
|
|
Issue 047 Ray Gates Cdn expert |
Issue 043 Issue 044 Issue 045 Issue 046 Issue 048 Issue 079 |
2-Minor Technical |
1999-08-31 metamodel |
Use codes from ISO
639-2:1998/T to represent languages. |
|
Accepted,
with Language encapsulated as a separate object class, incorporating both a
language identifier and an optional country identifier. |
4-Previously
Resolved |
|
|
Issue 048 Ray Gates Cdn expert |
Issue 043 Issue 044 Issue 045 Issue 046 Issue 047 Issue 079 |
2-Minor Technical |
1999-08-31 metamodel |
Allow for variations in
language use between countries. |
1999-10-15
metamodel. |
Accepted,
with Language encapsulated as a separate object class, incorporating both a
language identifier and an optional country identifier. |
4-Previously
Resolved |
|
|
Issue 050 Ray Gates Cdn expert |
Issue 003 Issue 011 Issue 039 Issue 041 Issue 042 Issue 051 Issue 058-1 Issue 058-2 |
1-Major Technical |
1999-08-31 metamodel 11179-2 |
Reconcile 11179-2 with
11179-3 Classification Region |
1999-10-15
metamodel. |
Metamodel
has been revised to make it more consistent with 11179-2. |
4-Previously
Resolved |
|
|
Issue 051 Ray Gates Cdn expert |
Issue 011 Issue 050 Issue 052 |
1-Major Technical |
11179-2 WD 11179-3
(1999-05-05) |
Merge 11179-2 into 11179-3 |
|
Retain
part 2 and expand its content. |
4-Previously
Resolved |
|
|
Issue 052 Ray Gates Cdn expert |
Issue 011 Issue 051 |
1-Major Technical |
11179-1 WD 11179-3
(1999-05-05) |
Merge 11179-3 into 11179-1 |
|
Move
overview material from part 3 to part 1 and retain separate parts. |
4-Previously
Resolved |
|
|
Issue 053 US |
|
1-Major Technical |
brought
forward from X3.285 issue list (issue 36). |
Support for Application Level
Attributes |
|
This is an area that should be delt with by individual
registries in their particular business environment. 1999-12-09 |
4-Previously
Resolved |
|
|
Issue 054 Ray Gates Cdn expert |
Issue 001 |
2-Minor Technical |
1999-08-31
metamodel |
Cardinality of relationship
Data Element contained in Input Set. Change the cardinality of the relationship Data
Element Contained In Input Set from 0..1 to 0..*. |
1999-10-15
metamodel. |
Agreed. Included in model 19991015 1999-12-13
metamodel renames Input Set to Source Data Element. |
4-Previously
Resolved |
|
|
Issue 055 Ray Gates Cdn expert |
Issue 009-2 Issue 009-3 Issue 038 |
1-Major Technical |
1999-08-31
metamodel |
Interpretation of
encapsulation in UML syntax. |
|
UML reference from OMG were provides to support the
interpretation 19991209 |
4-Previously
Resolved |
|
|
Issue 056 DD Mann US expert |
Issue 007 Issue 008 |
2-Minor Technical |
1999-10-15
metamodel |
Relationship between Data
Element Concept and Conceptual Domain
- Role and Name. |
|
Work on issue 008 on proposed terms and definitions
revision has defined this as "data element concept conceptual domain
relationship |
4-Previously
Resolved |
|
|
Issue
058-1 DD Mann US expert |
Issue 039 Issue 042 Issue 050 Issue 059 |
2-Minor Technical |
1999-10-15
metamodel |
To correct the cardinality and roles between
Classified_Component and Classification_Scheme_Item in the model from
1999-10-15 on page 4. |
Included
in |
Drop Classified Component and replace with a
relationship. Use classifying and
classified by with the Relationship name of Classification. 19991209 |
4-Previously
Resolved |
|
|
Issue
058-2 DD Mann US expert |
Issue 039 Issue 042 Issue 050 |
2-Minor Technical |
1999-10-15
metamodel |
To change the definition and thus the role of Classified Component Solution Classified Component
is defined in clause 3 of CD 11179-3 as: An administered component
classified in one or more classification schemes. |
|
Drop
the term "classified component" altogether. |
4-Previously
Resolved |
|
|
Issue 059 DD Mann US expert |
Issue 007 Issue 058-1 |
2-Minor Technical |
1999-10-15
metamodel |
Improvement of Relationship Role Labels |
Included
in |
See
resolution of Issue 058-1. |
4-Previously
Resolved |
|
|
Issue 060 DD Mann US expert |
|
2-Minor Technical |
1999-10-15
metamodel |
Naming of Attributes based on Encapsulated Data types [Some changes made as a result of CD ballot comments.] |
Included
in |
Accepted. Left
as draft resolution, until the change is completed. "Identifier" in Administration record" should be
"item identifier". |
4-Previously
Resolved |
|
|
Issue 061 Dan Gillman, U.S.
expert |
Issue 026 Issue 078 |
1-Major Technical |
1999-10-15
metamodel |
Generalizing support for Time Frames |
2000-05-12
metamodel |
Attributes
implemented in 2000-04-13 metamodel. Definitions
of terms proposed by Issue 078, are implemented in 2000-05-12 metamodel. |
4-Previously
Resolved |
|
|
Issue 062 Ray Gates Cdn. expert |
|
1-Major Technical |
1999-12-13
WD 11179-3 |
Clarifying the level and role of the metamodel. |
|
Resolved
by CD ballot comment CAN-P03-036. |
4-Previously
Resolved |
|
|
Issue 063 Ray Gates Cdn. expert |
|
2-Minor Technical |
1999-12-13
metamodel WG2
N219 |
Refining relationship names in the metamodel |
2000-03-15
metamodel |
Agreed
with changes. |
4-Previously
Resolved |
|
|
Issue 064 Ray Gates Cdn. expert |
Issue 001 Issue 054 |
2-Minor Technical |
1999-12-13
metamodel |
Data Element Derivation |
2000-04-13
metamodel |
Agreed
with a minor change. |
4-Previously
Resolved |
|
|
Issue 065 DD Mann US expert |
|
1-Major Technical |
1999-12-13
metamodel |
Refining Enumerated Domains |
2000-04-13
metamodel |
Agreed,
with some changes to names of classes and relationships. |
4-Previously
Resolved |
|
|
Issue 068 DD Mann US expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Qualifying attribute names in the metamodel |
2000-05-12
metamodel |
Accepted
with changes. |
4-Previously
Resolved |
|
|
Issue 069 DD Mann US expert |
Issue 088 |
5-Future Topic |
2000-04-13
metamodel |
Evolving the model through experience |
CD
11179-3 |
An
informative Annex (Annex F) has been added to relate the old part 3 terms to
the new metamodel. |
4-Previously
Resolved |
|
|
Issue 070 DD Mann US expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Recursive Conceptual Domain Relationship |
2000-05-12
metamodel |
Accepted,
with changes. The recursive relationships for Data Element Concept,
Conceptual Domain, and Value Domain should be the same. |
4-Previously
Resolved |
|
|
Issue 071 DD Mann US expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Refining Attribute Names for Consistency |
2000-05-12
metamodel |
Accepted,
with changes. |
4-Previously
Resolved |
|
|
Issue 072 DD Mann US expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Add attribute "Title" to Reference Document |
2000-05-12
metamodel |
Accepted,
with changes. |
4-Previously
Resolved |
|
|
Issue 073 DD Mann US expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Changing Organization Identifier to Name |
2000-05-12
metamodel |
Accepted,
with changes. |
4-Previously
Resolved |
|
|
Issue 074 DD Mann US expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Remove "Name" Attribute from Valud Domain |
2000-05-12
metamodel |
Resolved
by CD ballot comments CAN-P03-031 and CAN-P03-131. |
4-Previously
Resolved |
|
|
Issue 075 DD Mann US expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Further revision of attribute names for uniqueness |
2000-05-12
metamodel |
Accepted,
with changes. |
4-Previously
Resolved |
|
|
Issue 076 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Reviewing the use of Objectified Relationships |
|
|
3-Newly
Resolved |
|
|
Issue 077 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Refining attribute names for consistency |
2000-05-12
metamodel |
Accepted. |
4-Previously
Resolved |
|
|
Issue 078-01 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Redefining definitions of terms - Provide definition for Administered Component - effective date |
2000-05-12
metamodel |
Accepted. |
4-Previously
Resolved |
|
|
Issue 078-02 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Redefining definitions of terms - Revise definition for Administered Component - registration status |
2000-05-12
metamodel |
Accepted. |
4-Previously
Resolved |
|
|
Issue 078-03 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Redefining definitions of terms - Provide definition for Administered Component - until date |
2000-05-12
metamodel |
Accepted,
with changes. |
4-Previously
Resolved |
|
|
Issue 078-04 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Redefining definitions of terms - Provide definition for class "Value" |
2000-05-12
metamodel |
Accepted. |
4-Previously
Resolved |
|
|
Issue 078-05 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Redefining definitions of terms - Provide definition for relationship "permissible value set" |
2000-05-12
metamodel |
Accepted. |
4-Previously
Resolved |
|
|
Issue 078-06 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Redefining definitions of terms - Provide definition for relationship "permitted value" |
2000-05-12
metamodel |
Accepted. |
4-Previously
Resolved |
|
|
Issue 079-01 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Refining the representation of Language in the model - Rename class "Language" to "Language Identifier". |
2000-05-12
metamodel |
Rejected. Agreed to keep as is i.e. "Language". Need to define as Natural or Special
language and not as programming language. Recommend use of "ISO
639-2T". Text changes need to be
specified. |
4-Previously
Resolved |
|
|
Issue 079-02 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Refining the representation of Language in the model - Revise definition for class "Language Identifier" to reflect new name and scope. |
2000-05-12
metamodel |
Rejected. See 079-01. |
4-Previously
Resolved |
|
|
Issue 079-03 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Refining the representation of Language in the model - Include "Language" as a Term with the old definition. |
2000-05-12
metamodel |
Rejected. See 079-01. |
4-Previously
Resolved |
|
|
Issue 079-04 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Refining the representation of Language in the model - Refine the attributes for class "Language Identifier" |
2000-05-12
metamodel |
Rejected. See 079-01. |
4-Previously
Resolved |
|
|
Issue 079-05 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-04-13
metamodel |
Refining the representation of Language in the model - Refine the names and definitions of attributes that use Language as an attribute capsule. |
2000-05-12
metamodel |
Rejected. See 079-01. |
4-Previously
Resolved |
|
|
Issue 082 Ray Gates Cdn expert |
|
2-Minor Technical |
2000-05-14
metamodel |
Administered Component attribute capsule names |
CD
11179-3 |
Superseded
by CD ballot comments. In the revised draft CD2 11179-3 output from Helsinki, the model
uses the term "administered item" in the property names. The text uses the term
"administration record". |
4-Previously
Resolved |
|
|
Issue 083 J. Newton US expert |
|
2-Minor Technical |
CD
11179-3 |
Items in Content TR that are not in the Metamodel |
|
Withdrawn. Resolved in MDRCC TR. |
4-Previously
Resolved |
|
|
Issue 084 D. Mann US expert |
Issue 016 Issue 037 |
1-Major Technical |
CD
11179-3 |
Consistency in use of Identifiers, Names, Versions |
|
Proposal
accepted. |
4-Previously
Resolved |
|
|
Issue 085 D. Mann US expert |
|
2-Minor Technical |
CD
11179-3 |
Contact name |
|
|
3-Newly
Resolved |
|
|
Issue 086 Ray Gates Cdn expert |
Issue 010-2 Issue 087 |
3-Major Editorial |
CD
11179-3 |
Consistency between diagrams and text |
|
|
3-Newly
Resolved |
|
|
Issue 087 Ray Gates Cdn expert |
Issue 010-2 Issue 086 |
1-Major Technical |
CD
11179-3 |
Terminology: Data element, Administered Component et al |
|
The following terms were agreed in Helsinki:: Use "item" instead of
"component". Use "administered item" for any item
that has associated administration information (an "administration
record"). Use "registry item" for any item stored
in a registry. Use "metadata item" as a generic term
for any item described by the metamodel (whether or not it is stored in a
registry). Use "metadata set" for a collection of
metadata items. Use
"bound metadata set" for a metadata set for which a binding exists. |
4-Previously
Resolved |
|
|
Issue 088 Ray Gates Cdn expert |
|
1-Major Technical |
CD
11179-3 |
Restoring Basic Attributes to CD 11179-3. |
|
At
the Helsinki Editing meeting for CD 11179-3, it was resolved that: 1.
The
description of Basic Attributes should be restored, with appropriate changes
to reflect the changes in the model. 2.
Compatibility
with the published 11179-3 must be preserved as much as possible. 3.
Errors
in Annex F should be addressed. 4.
Canada
would submit a change proposal to effect the above resolutions. |
3-Newly
Resolved |
|
|
Issue 089 US |
|
2-Minor Technical |
CD-11179-3 |
Representation
Class relationship and qualifier Remove the relationship between
"Representation_Class" and "Data_Element" as it is
expressed by the "Representation Class" to "Value_Domain"
relationship. Move the "representation_class_qualifier" from the object class "Data_Element" to "Value_Domain". |
|
|
3-Newly
Resolved |
|
|
Issue 092 Sue Ellen Wright & DD
Mann [US] |
|
2-Minor Technical |
CD-11179-3 |
Definition
Source Attribute An
attribute should be added to the "Definition" object class to
denote the "definition_source_reference". The definition of this attribute is "The text that
identifies the document that this definition was extracted from or adapted
from." |
|
|
3-Newly
Resolved |