wg2sd11b-issue-list-p3r-table-20000103

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

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

Date: 03 January 2000

Supersedes: 06 December 1999

Source: Ray Gates, Canada, for the project editor

The columns in the document have the following meanings:

SEQ # — A sequence number indicating the total number of comments

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: Major technical, minor technical, major editorial, minor editorial, procedural, 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: Open, Draft Resolution, Resolved, Withdrawn.

SEQ #	Cmnt ID	Related Issues	Severity	Reference	Title / Description	Addressed By	Tentative Resolution	Status
1	Issue 001 DD Mann US expert	Issue 022 Issue 027 Issue 035 Issue 054	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.	WD 11179-3 (1999-05-05)	Date: 1999-06-25 Proposal accepted. Some additional text changes identified as required. Resolution modified by Issue 054.	Draft Resolution
2	Issue 002 DD Mann US expert	Issue 031	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.	WD 11179-3 (1999-05-05)	Rejected. Use Definition of Associated Administered Component. If the resolution is confirmed, the changes already made will need to be reversed.	Draft Resolution.
3	Issue 003 DD Mann US expert	Issue 023 Issue 039	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.	Draft Resolution.
4	Issue 004 DD Mann US expert	Issue 009-07	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)	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 not yet included in 1999-12-13 metamodel.	Draft Resolution.
5	Issue 005 DD Mann US expert	Issue 025	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	Draft Resolution.
6	Issue 006 DD Mann US expert	Issue 009-01 Issue 024 Issue 032 Issue 055	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.	Draft Resolution.
7	Issue 007 DD Mann US expert	Issue 056 Issue 059	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.	Draft Resolution.
8	Issue 008 DD Mann US expert	Issue 011 Issue 014	Major technical	WD 11179-3 (1998-12-08)	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			Open.
9	Issue 009 DD Mann US expert	Issue 055, & see specific proposals.	Major technical	WD 11179-3 (1998-12-08)	Proposed Metamodel revision UML-3b Solution See following 10 proposals.		See specific proposals.	See specific proposals.
10	Issue 009-01 DD Mann US expert	Issue 006 Issue 024 Issue 032 Issue 055	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.	Draft Resolution.
11	Issue 009-02 DD Mann US expert	Issue 038 Issue 055	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. Draft resolution of Issue 038 is to reject the proposal, so the original agreement stands.	Draft resolution
12	Issue 009-03 DD Mann US expert	Issue 038 Issue 055	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. Draft resolution of Issue 038 is to reject the proposal, so the original agreement re Issue 009-03 still stands.	Draft resolution
13	Issue 009-04 DD Mann US expert		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.	Draft Resolution.
14	Issue 009-05 DD Mann US expert		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.	Draft Resolution.
15	Issue 009-06 DD Mann US expert	Issue 033 Issue 055	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)	Originally agreed, but reopened by Issue 033.	Open.
16	Issue 009-07 DD Mann US expert	Issue 004 Issue 055	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.	Draft Resolution.
17	Issue 009-08 DD Mann US expert	Issue 041	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)	Originally agreed, but reopened by Issue 041.	Open.
18	Issue 009-09 DD Mann US expert	Issue 005 Issue 025	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.	Draft Resolution.
19	Issue 009-10 DD Mann US expert	Issue 31	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.	Draft Resolution.
20	Issue 010-01 DD Mann US expert	Issue 012 Issue 051 Issue 052	Minor technical	WD 11179-3 (1998-12-08)	Change the title of 11179-3 to "Basic attributes of data element components".			Open.
21	Issue 010-02 DD Mann US expert		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.			Open.
22	Issue 011 Canada	Issue 008 Issue 051 Issue 052	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.	Open.
23	Issue 012 Canada	Issue 010-01	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 Solution			Open.
24	Issue 013-01 Canada		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.	Draft Resolution.
25	Issue 013-02 Canada		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.	Draft Resolution.
26	Issue 013-03 Canada	Issue 011 Issue 012	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.			Open.
27	Issue 014 Canada	Issue 008 Issue 016	Major technical	WD 11179-3 (1999-05-05) SC32 N0264 32 N0265 MAT 013	Alignment of metamodel with definitions and other text. 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. Solution		Editor to undertake a thorough comparison of Clauses 4-7 with Clauses 8 and 9 and with other Standards and to then update Working Draft immediately following June 24/25 L8 discussions. Input/assistance from Doug Mann would be most welcome. In updating Clauses 4 to 7 for consistency, some changes will be made to achieve more consistent format and presentation of text and tables throughout the Working Draft of making. No attempt was made at the meeting to explicitly answer the question. "What is the level of granularity that the standard should have?".	Draft Resolution
28	Issue 015 Canada		Major editorial	WD 11179-3 (1999-05-05)	General editing Page numbers, clauses and Annexes to be numbered correctly. Solution		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.	Draft Resolution.
29	Issue 016-1 Canada	Issue 014	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 non-intelligent 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.	Draft Resolution.
30	Issue 016-2 Canada	Issue 037	Major technical	WD 11179-3 (1999-05-05) 32N0265 MAT013 (item 3)	Linguistically neutral identifier (1) - problems introduced by recent metamodel changes.		The 1999-06-25 meeting resolved that a linguistically-neutral identifier for each data element component is already a mandatory requirement in the metamodel, and instructed the Editor to ensure that the Committee Draft makes this abundantly clear. However, this is not in fact the case. Issue 037 restates problem 2 in the context of the 1999-08-31 metamodel. See further discussion under Issue 037.	Open.
31	Issue 017 Canada	Issue 018 Issue 028	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.			Open.
32	Issue 018 Canada	Issue 017.	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.		This issue has been resolved with respect to linguistically neutral identifiers. Editor to check applicability and incorporate appropriate changes in next revision of Working Draft.	Open.
33	Issue 019 Canada, France	Issue 001 Issue 031	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 addresses this issue, as follows. (1) The "data element concept association" allows inter-relationships between concepts to be identified. (2) The "component classification association" allows relationships between data element components to be classified. (3) The resolution of Issue 01 has provided a way to indicate that certain data elements can be derived from others. The text should be reviewed to ensure the above facilities are adequately described. If specific deficiencies exist, change proposals to correct them are invited.	Draft Resolution.
34	Issue 020 Canada		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.		It was agreed that editor’s notes should be added to the annexes in the next (October) revision of the working draft. A decision should be made on which Annexes are essential inclusions in the standard, and which Annexes could be moved to Content Technical report. The latest WD (WG2 N00201) has marked Annexes for deletion and for moving to the TR.	Open.
35	Issue 021 Canada	Issue 030 Issue 057	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.	Open
36	Issue 022 Canada	Issue 001 Issue 027 Issue 035	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.		US - proposes - Defer for further investigation. The current model addresses rules for data elements 19991208	Open
37	Issue 023 Canada	Issue 003 Issue 039 Issue 050 Issue 057 Issue 058	Major technical	WD 11179-3 (1999-05-05 CAN 32C0048R3	Canadian response to Issue 003. Solution Rename "Classified Component" to "Administered Component". 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.	Draft Resolution.
38	Issue 024 Canada	Issue 006 Issue 009 Issue 016 Issue 023 Issue 032	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.	Draft Resolution.
39	Issue 025 Ray Gates Cdn expert	Issue 005 Issue 028	Minor technical	WD 11179-3 (1999-05-05) CAN 32C0054R1	Canadian Response to Issue 005 - Component Identifier Solution 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 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. Need to check for corresponding text changes.	Draft Resolution.
40	Issue 026 US & Canada	Issue 061	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. Need to check for corresponding text changes.	Draft Resolution.
41	Issue 027 US & Canada	Issue 001 Issue 022	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.	Draft Resolution.
42	Issue 028 Ray Gates Cdn expert	Issue 017 Issue 025 Issue 029	Minor technical	WD 11179-3 (1999-05-05)	Provide default values for optional parts of identifiers. Solution			Open.
43	Issue 029 Ray Gates Cdn expert		Minor technical	WD 11179-3 (1999-05-05)	Move OPI-source out of registration identifier. Solution Proposal withdrawn after review of ISO 6523.		No action required.	Withdrawn.
44	Issue 030 Ray Gates Cdn expert	Issue 021 Issue 057	Minor technical	WD 11179-3 (1999-05-05)	Identification and naming of Context. Make "Context" an Administered Component. Solution			Open.
45	Issue 031 DD Mann US expert	Issue 032 Issue 040	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.	TBD. Modified by Issues 032 and 040.	Open.
46	Issue 032 DD Mann US expert	Issue 009-01 Issue 024 Issue 031	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	Draft resolution
47	Issue 033 DD Mann US expert	Issue 009-06 Issue 034	Minor technical	WD 11179-3 (1999-05-05)	Removal of value domain character set.	1999-08-31 metamodel.	Included in Current Model 19991213	Open
48	Issue 034 DD Mann US expert	Issue 033	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	Open.
49	Issue 035 DD Mann US expert		Minor technical	WD 11179-3 (1999-05-05)	Addition of a dimensionality attribute to the conceptual domain	1999-08-31 metamodel.	Included in Current Model 19991213	Open.
50	Issue 036 DD Mann US expert		Minor technical	WD 11179-3 (1999-05-05)	Add "explanatory comment" as attribute of Administered Component.	1999-08-31 metamodel.	Included in Current Model 19991208	Open.
51	Issue 037 Ray Gates Cdn expert	Issue 016 Issue 039	Major technical	WD 11179-3 (1999-05-05)	Requirement for Administered Component Information. Make "Administered Component Information" <<required>>.			Open.
52	Issue 038 Ray Gates Cdn expert	Issue 009-2 Issue 009-3 Issue 055	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.	Draft Resolution.
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	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	Draft Resolution.
54	Issue 040 Ray Gates Cdn expert	Issue 031 Issue 039 Issue 041 Issue 042 Issue 050	Minor technical	1999-08-31 metamodel	Rename "Link" in Classification Region of Meta Model	1999-10-15 metamodel.	Rename to "Classification Scheme Item Relation".	Draft Resolution.
55	Issue 041 Ray Gates Cdn expert	Issue 039 Issue 040 Issue 042 Issue 050	Major technical	1999-08-31 metamodel	Representation Class as Classification Scheme.			Open.
56	Issue 042 Ray Gates Cdn expert	Issue 039 Issue 050 Issue 051 Issue 058-1 Issue 058-2	Minor technical	1999-08-31 metamodel	Description of Classification Region Meta Model Components.			Open.
57	Issue 043 Canada	Issue 044 Issue 045 Issue 046 Issue 047 Issue 048	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	Draft Resolution.
58	Issue 044 Canada	Issue 043 Issue 045 Issue 046 Issue 047 Issue 048	Minor technical	1999-08-31 metamodel	Support for multiple documentation languages in registration authority.	1999-10-15 metamodel.	Agreed in principle. Detailed text changes required.	Draft Resolution.
59	Issue 045 Canada	Issue 043 Issue 044 Issue 046 Issue 047 Issue 048	Minor technical	1999-08-31 metamodel	Allow multiple languages to be specified for reference documents.	1999-10-15 metamodel.	Agreed in principle. Detailed text changes required.	Draft Resolution.
60	Issue 046 Canada	Issue 043 Issue 044 Issue 045 Issue 047 Issue 048	Minor technical	1999-08-31 metamodel	Make Language a property of Definition and Designation, rather than Context.	1999-10-15 metamodel.	Agreed in principle. Detailed text changes required.	Draft Resolution.
61	Issue 047 Ray Gates Cdn expert	Issue 043 Issue 044 Issue 045 Issue 046 Issue 048	Minor technical	1999-08-31 metamodel	Use codes from ISO 639-2:1998/T to represent languages.		Agreed in principle. Detailed text changes required.	Draft Resolution.
62	Issue 048 Ray Gates Cdn expert	Issue 043 Issue 044 Issue 045 Issue 046 Issue 047	Minor technical	1999-08-31 metamodel	Allow for variations in language use between countries.	1999-10-15 metamodel.	Agreed in principle. Detailed text changes required.	Draft Resolution.
63	Issue 049 Ray Gates Cdn expert	Issue 014	Major technical	WD 11179-3 (1999-05-05) 1999-08-31 metamodel SC32 N0267	Applying the metamodel concepts to its own description.			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	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.	Draft Resolution.
65	Issue 051 Ray Gates Cdn expert	Issue 011 Issue 050 Issue 052	Major technical	11179-2 WD 11179-3 (1999-05-05)	Merge 11179-2 into 11179-3			Open.
66	Issue 052 Ray Gates Cdn expert	Issue 011 Issue 051	Major technical	11179-1 WD 11179-3 (1999-05-05)	Merge 11179-3 into 11179-1			Open.
67	Issue 053 US		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	Draft resolution.
68	Issue 054 Ray Gates Cdn expert	Issue 001	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".	Draft resolution.
69	Issue 055 Ray Gates Cdn expert	Issue 009-2 Issue 009-3 Issue 038	Major technical	1999-08-31 metamodel	Interpretation of encapsulation in UML syntax.		UML reference from OMG were provides to support the interpretation 19991209	Draft resolution.
70	Issue 056 DD Mann US expert	Issue 007 Issue 008	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"	Draft resolution.
71	Issue 057 Ray Gates Cdn expert	Issue 021 Issue 030	Minor technical	1999-10-15 metamodel & WD 11179-3 (1999-10-04)	Is "context" modeled correctly?		This may require additional investigation. 19991209	Open
72	Issue 058-1 DD Mann US expert	Issue 039 Issue 042 Issue 050 Issue 059	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.		Drop Classified Component and replace with a relationship. Use classifying and classified by with the Relationship name of Classification. 19991209	Draft Resolution
73	Issue 058-2 DD Mann US expert	Issue 039 Issue 042 Issue 050	Minor Technical	1999-10-15 metamodel	To change the definition and thus the role of Classified Component Solution We need to review the text to determine whether the term is still useful. If so, we need a revised definition. Ray Gates proposes: "A Classified_Component is an Administered Component of that has been classified in one or more Classification Schemes by association with one or more Classification Scheme Items."		The draft resolution of Proposal 58.1 eliminates Classified Component as a separate object class within the metamodel, but need not necessarily eliminate Classified Component as a term.	Open
74	Issue 059 DD Mann US expert	Issue 007 Issue 058-1	Minor Technical	1999-10-15 metamodel	Improvement of Relationship Role Labels		See resolution of Issue 058-1.	Draft Resolution
75	Issue 060 DD Mann US expert		Minor Technical	1999-10-15 metamodel	Naming of Attributes based on Encapsulated Data types		Included in model 19991209	Open.
76	Issue 061 Dan Gillman, U.S. expert	Issue 026.	Major Technical	1999-10-15 metamodel	Generalizing support for Time Frames			Open.
77	Issue 062 Ray Gates Cdn. expert		Major Technical	1999-12-13 WD 11179-3	Clarifying the level and role of the metamodel.			Open.