Issue 9148: References to other specification documents are not up to date                                                                                                                                          (mof2idl-ftf)
Source: Fraunhofer FOKUS (Mr. Michael Soden, soden@ikv.de soden@fokus.fraunhofer.de)
Nature: Uncategorized Issue
Severity: 
Summary: Throughout the current specification ptc/05-03-05, references are made to other specifications which are not up to date. References to submission documents should be updated to their respective adopted documents and the affected sections should be corrected too. The specification should avoid making references directly to UML Specifications but rather to the MOF2.0 Core specification which in turn makes the appropriate references to UML.
Resolution: 
Revised Text: Resolution:
The reference (cp. 5.1.2) in section 5.3.1 on page 3 was deleted.

In section 1 (Scope), page 1, the statement:

"The mapping rules basically depend on the state of the MOF2.0 document [6] and the U2P UML Infrastructure [9]"

was changed to:

"The mapping rules basically depend on the state of the MOF2.0 document [6]" 
The name of the document [6] on page 85 should then be changed to "MOF2.0 Core Specification, OMG document ptc/04-10-15".

In section 2 (Conformance), page 1, the statement:

"An implementation that confirms to the MOF 2 IDL specification must conform to one of these compliance points in MOF 2 Core (ptc/03-10-04) …"

was changed to:

"An implementation that confirms to the MOF 2 IDL specification must conform to one of these compliance points in [6] …"

In section 3 (Normative Reference), page 1, the statement:

"Object Management Group, MOF 2.0 Core Final Adopted Specification, ptc/03-10-04
should later be changed to the final adopted specification replacing ptc/04-10-15.
was changed to:
Object Management Group, MOF 2.0 Core Adopted Specification, ptc/04-10-15.

In section 3 (Normative Reference), page 1, the statement:

"…, there might occur inconsistencies with respect to these documents."

was changed to

"…, inconsistencies might occur with respect to these documents."

In section 6.2.3 (Mapping of the PrimitiveType Package), page 13, the statement:

"This is aligned with the constraints of CMOF as described in section 9.4 of [8] (CMOF Constraints) for the primitive types."

was changed to:

"This is aligned with the constraints of CMOF as described in section 14.3 of [6] (CMOF Constraints) for the primitive types."

The name of the document [6] on page 85 had to be changed to "MOF2.0 Core Specification, OMG document ptc/04-10-15".

Actions taken:
November 15, 2005: received issue
March 8, 2006: closed issue
Discussion: 

End of Annotations:=====
MG Issue No: [Temp1]
Title:	References to other specification documents are not up to date.
Source:
Michael Soden, soden@ikv.de
Summary:
Throughout the current specification ptc/05-03-05, references are made to other specifications which are not up to date. References to submission documents should be updated to their respective adopted documents and the affected sections should be corrected too. The specification should avoid making references directly to UML Specifications but rather to the MOF2.0 Core specification which in turn makes the appropriate references to UML.

Discussion:

Resolution:
The reference (cp. 5.1.2) in section 5.3.1 on page 3 was deleted.
In section 1 (Scope), page 1, the statement:
.The mapping rules basically depend on the state of the MOF2.0 document [6] and the U2P UML Infrastructure [9].
should be changed to:
.The mapping rules basically depend on the state of the MOF2.0 document [6]. 
The name of the document [6] on page 85 should then be changed to .MOF2.0 Core Specification, OMG document ptc/04-10-15..
In section 2 (Conformance), page 1, the statement:
.An implementation that confirms to the MOF 2 IDL specification must conform to one of these compliance points in MOF 2 Core (ptc/03-10-04) ..
should be changed to:
.An implementation that confirms to the MOF 2 IDL specification must conform to one of these compliance points in [6] ..
In section 3 (Normative Reference), page 1, the statement:
.Object Management Group, MOF 2.0 Core Final Adopted Specification, ptc/03-10-04
should later be changed to the final adopted specification replacing ptc/04-10-15.
It was changed to 
Object Management Group, MOF 2.0 Core Adopted Specification, ptc/04-10-15.
In section 3 (Normative Reference), page 1, the statement:
.., there might occur inconsistencies with respect to these documents.. was changed to
.., inconsistencies might occur with respect to these documents..
In section 6.2.3 (Mapping of the PrimitiveType Package), page 13, the statement:
.This is aligned with the constraints of CMOF as described in section 9.4 of [8] (CMOF Constraints) for the primitive types..
should be changed to:
.This is aligned with the constraints of CMOF as described in section 14.3 of [6] (CMOF Constraints) for the primitive types..
The name of the document [6] on page 85 should then be changed to .MOF2.0 Core Specification, OMG document ptc/04-10-15..

Disposition:	open