Issue 9150: Subsection 6.2.1 (Mapping of Identifiers) should be independent of MOF1.4                                                                                                                               (mof2idl-ftf)
Source: Fraunhofer FOKUS (Mr. Michael Soden, soden@ikv.de soden@fokus.fraunhofer.de)
Nature: Uncategorized Issue
Severity: 
Summary: In subsection 6.2.1 the current specification ptc/05-03-05 makes references to the MOF1.4 Specification, ptc/01-10-04 forcing the reader to refer to that document. I think the specification should rather just mention that mapping of identifiers has been carried over from MOF1.4 and outline the mapping rules in detail here again.
Resolution: 
Revised Text: 
Actions taken:
November 15, 2005: received issue
March 8, 2006: closed issue
Discussion: 
Resolution:
Outline what format_1, format_2 and format_3 produce.
Format 1 text changed to
identifier format_1 ( <MOF model element identifier> ) returns an identifier for an IDL definition according to 5.7.1.2 of [1]. In format 1, the first letter of each word is converted into upper case, and all other letters remain the same as input. It is used to produce names of modules and interfaces.
Format 2 text changed to
identifier format_2 ( <MOF model element identifier> ) returns an identifier for an IDL definition according to 5.7.1.3 of [1]. In format 2, all letters in each word are converted to lower case and all words are separated by an underscore ("_"). It is used to produce names of attributes, operations and formal parameters and members of structured data types.
Format 3 text changed to
identifier format_3 ( <MOF model element identifier> ) returns an identifier for an IDL definition according to 5.7.1.4 of [1]. In format 3, all letters in each word are converted to upper case and all words are separated by an underscore ("_"). It is used to produce names of constants.
For the resolution of a name in the target IDL, basically the naming conventions of MOF1.4 are reused (interfaces, that are derived for a class, receive an identifier in format 1, operations in format 2 and so on). For details see the following sections.
was changed to
Table 1 on page 13 on page   Error! Bookmark not defined. shows some examples.
an tabular example was introduced.

End of Annotations:=====
MG Issue No: [Temp3]
Title:	Subsection 6.2.1 (Mapping of Identifiers) should be independent of the MOF1.4 Specification.
Source:
Michael Soden, soden@ikv.de
Summary:
In subsection 6.2.1 the current specification ptc/05-03-05 makes references to the MOF1.4 Specification, ptc/01-10-04 forcing the reader to refer to that document. I think the specification should rather just mention that mapping of identifiers has been carried over from MOF1.4 and outline the mapping rules in detail here again.

Discussion:

Resolution:
Outline what format_1, format_2 and format_3 produce.
Format 1 text changed to
identifier format_1 ( <MOF model element identifier> ) returns an identifier for an IDL definition according to 5.7.1.2 of [1]. In format 1, the first letter of each word is converted into upper case, and all other letters remain the same as input. It is used to produce names of modules and interfaces.
Format 2 text changed to
identifier format_2 ( <MOF model element identifier> ) returns an identifier for an IDL definition according to 5.7.1.3 of [1]. In format 2, all letters in each word are converted to lower case and all words are separated by an underscore (._.). It is used to produce names of attributes, operations and formal parameters and members of structured data types.
Format 3 text changed to
identifier format_3 ( <MOF model element identifier> ) returns an identifier for an IDL definition according to 5.7.1.4 of [1]. In format 3, all letters in each word are converted to upper case and all words are separated by an underscore (._.). It is used to produce names of constants.
For the resolution of a name in the target IDL, basically the naming conventions of MOF1.4 are reused (interfaces, that are derived for a class, receive an identifier in format 1, operations in format 2 and so on). For details see the following sections.
was changed to
Table 1 on page 13 on page   Error! Bookmark not defined. shows some examples.
an tabular example was introduced.

Disposition:	open