Title: Issues List Summary for ISO/IEC 11179-3 Revision

Status: JTC 1/SC 32/WG 2 Standing Document

Date: 09 August 2000

Supersedes: 14 May 2000

Source: Ray Gates, Canada, for the project editor

 

The columns in the document have the following meanings:

0-Procedural

1-Major technical

2-Minor technical

3-Major editorial

4-Minor editorial

5-Future topic

The Word version of the table can be sorted by: Status, Severity and Cmnt ID

SEQ
#

Cmnt
ID

Related
Issues


Severity


Reference

Title /
Description

Addressed By

Resolution

Status

1

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.

3-Resolved

2

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"

3-Resolved

3

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.

3-Resolved

4

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:
phone_number required
electronic_mail_address optional
fax_number optional
telex_number optional

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.

3-Resolved

5

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:
International_Code_Designator
Organization_Identifier
Organization_Part_Identifier
OPI_Source
Data_Identifier

Issue 025.

Resolved by Issue 025

3-Resolved

6

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.

3-Resolved

7

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
from (1,N) to (0,N). This will allow a Conceptual_Domain to exist without a Data_Element_Concept.

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.

3-Resolved

8

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

Work in progress.

 

Comment from US L8 mtg July 20, 2000:

"Adequately addressed for this release."

1-Open

9

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.

3-Resolved

10

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.

3-Resolved

11

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.

3-Resolved

12

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.

3-Resolved

13

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.

3-Resolved

14

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.

3-Resolved

15

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.

3-Resolved

16

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.

3-Resolved

17

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.

3-Resolved

18

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.

3-Resolved

19

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.

3-Resolved

20

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
(SC32 N490)

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.

2-Draft Resolution

21

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.

  

CD 11179-3 made a global change to the term "Data Element" to "Administered Data Component". This leaves the issue unresolved.

1-Open

22

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.

2-Draft Resolution

23

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.

2-Draft Resolution

24

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.

2-Draft Resolution

25

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.

3-Resolved

26

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.

Previous editors of each part to assume responsibility for revisions.

The status will be left as Draft Resolution until progress is shown to be made on the other parts.

2-Draft Resolution

27

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.

3-Resolved

28

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.

3-Resolved

29

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.

3-Resolved

30

Issue 016-2

Canada

Issue 037

1-Major Technical

WD 11179-3 (1999-05-05)

32N0265

MAT013
(item 3)

Linguistically neutral identifier (2) - problems introduced by recent metamodel changes.

Solution

An Administered Component requires a linguistically neutral identifier.

[Note: Administered Component is itself optional in many cases, so this is only a partial solution.]

  

Issue 037 restates problem 2 in the context of the 1999-08-31 metamodel. See further discussion under Issue 037.

1-Open

31

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.

  

Detailed proposal required.

1-Open

32

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.

  

Detailed proposal required.

1-Open

33

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.

3-Resolved

34

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.

3-Resolved

35

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.

  

The 1999-12-13 WD has deleted the parts of clause 5 that contained the text that needed clarification.

2-Draft Resolution

36

Issue 022

Canada

Issue 001

Issue 027

Issue 035

Issue 080

5-Future Topic

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.

  

US - proposes - Defer for further investigation. The current model addresses rules for data elements 19991208

1-Open

37

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
1999-12-13

Resolved by Issue 039 as modified by issues 050 and 058.

3-Resolved

38

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.

3-Resolved

39

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]:

    2. 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.

Resolved

40

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.

3-Resolved

41

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.

Resolved

42

Issue 028

Ray Gates

Cdn expert

Issue 017

Issue 025

Issue 029

2-Minor Technical

WD 11179-3 (1999-05-05)

Provide default values for optional parts of identifiers.

Solution

  

Detailed proposal required.

1-Open

43

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

3-Resolved

44

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.

3-Resolved

45

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.

3-Resolved

46

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.

3-Resolved

47

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.

Restore attribute as "Character set encoding"

Needs to be re-evaluated in light in issue 067.

2-Draft Resolution

48

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.

  

US believes the maximum should be optional 19991209. Included in Current Model 19991213

2-Draft Resolution

49

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

Resolved by Issue 080.

2-Draft Resolution

50

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.

3-Resolved

51

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>>.

    

1-Open

52

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.

3-Resolved

53

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

3-Resolved

54

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".

3-Resolved

55

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.

3-Resolved

56

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.

  

Detailed proposal required.

1-Open

57

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

3-Resolved

58

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.

3-Resolved

59

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.

3-Resolved

60

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.

3-Resolved

61

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.

3-Resolved

62

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.

3-Resolved

63

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.

  

Detailed proposal required.

1-Open

64

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.

3-Resolved

65

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.

3-Resolved

66

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.

3-Resolved

67

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

3-Resolved

68

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".

3-Resolved

69

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

3-Resolved

70

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"

3-Resolved

71

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

72

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
1999-12-13 metamodel

Drop Classified Component and replace with a relationship. Use classifying and classified by with the Relationship name of Classification. 19991209

3-Resolved

73

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."

  

Accepted.

2-Draft Resolution

74

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
1999-12-13 metamodel

See resolution of Issue 058-1.

3-Resolved

75

Issue 060

DD Mann

US expert

  

2-Minor Technical

1999-10-15 metamodel

Naming of Attributes based on Encapsulated Data types

Included in
CD 11179-3 with one exception.

Accepted.

2-Draft Resolution

76

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.

2-Draft Resolution

77

Issue 062

Ray Gates

Cdn. expert

  

1-Major Technical

1999-12-13 WD 11179-3

Clarifying the level and role of the metamodel.

  

Agreed in principle.

2-Draft Resolution

78

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.

2-Draft Resolution

79

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.

2-Draft Resolution

80

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.

2-Draft Resolution

81

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

82

Issue 067

Ray Gates

Cdn. expert

Issue 009-6

Issue 033

5-Future Topic

1999-12-13 metamodel

Use of character collections and encoding schemes for Value Domains

  

US suggests defer to future version of the standard.

1-Open

83

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.

3-Resolved

84

Issue 069

DD Mann

US expert

  

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.

2-Draft Resolution

85

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.

3-Resolved

86

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.

3-Resolved

87

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.

3-Resolved

88

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.

3-Resolved

89

Issue 074

DD Mann

US expert

  

2-Minor Technical

2000-04-13 metamodel

Remove "Name" Attribute from Valud Domain

2000-05-12 metamodel

Keep "Value Domain Name" and add "optional "Value Domain Identifier".

CD 11179-3 (SC32 N0490) implements the original proposal, not the agreed resolution. Ballot comments required to ensure implementation of agreed resolution.

2-Draft Resolution

90

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.

3-Resolved

91

Issue 076

Ray Gates

Cdn expert

  

2-Minor Technical

2000-04-13 metamodel

Reviewing the use of Objectified Relationships

    

1-Open

92

Issue 077

Ray Gates

Cdn expert

  

2-Minor Technical

2000-04-13 metamodel

Refining attribute names for consistency

2000-05-12 metamodel

Accepted.

3-Resolved

93

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.

3-Resolved

94

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.

3-Resolved

95

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.

3-Resolved

96

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.

3-Resolved

97

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.

3-Resolved

98

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.

3-Resolved

99

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.

2-Draft Resolution

100

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.

2-Draft Resolution

101

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.

2-Draft Resolution

102

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.

2-Draft Resolution

103

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.

2-Draft Resolution

104

Issue 080

Ray Gates

Cdn expert

  

2-Minor Technical

2000-04-13 metamodel

Dimensionality and Unit of Measure

2000-05-12 metamodel

  

1-Open

105

Issue 081

Ray Gates

Cdn expert

  

2-Minor Technical

2000-04-13 metamodel

Remove inappropriate aggregation symbols

2000-05-12 metamodel

  

1-Open

106

Issue 082

Ray Gates

Cdn expert

  

2-Minor Technical

2000-05-14 metamodel

Administered Component attribute capsule names

CD 11179-3
(SC32 N490)

SC32 N0487 simply indicates Issue 82 was accepted, without distinguishing between proposals 1 and 2. Only proposal 1 has been implemented.

2-Draft Resolution

107

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.

3-Resolved

108

Issue 084

D. Mann

US expert

Issue 016

Issue 037

1-Major Technical

CD 11179-3

Consistency in use of Identifiers, Names, Versions

    

1-Open

109

Issue 085

D. Mann

US expert

  

2-Minor Technical

CD 11179-3

Contact name

    

1-Open

110

Issue 086

Ray Gates

Cdn expert

Issue 010-2

Issue 087

3-Major Editorial

CD 11179-3

Consistency between diagrams and text

    

1-Open

111

Issue 087

Ray Gates

Cdn expert

Issue 010-2

Issue 086

1-Major Technical

CD 11179-3

Terminology: Data element, Administered Component et al

Ballot comments requested.

    

1-Open