Nature of Problem:

The references to UML, MOF and XMI in the KDM 2.2 are not appropriate.

The references to 19502:2005 and 10503:2005 are not used anywhere in the
spec and should be removed.

The ref to MOF should be to the actual version used.

The proposed resolution below assumes the Latest Versions used are MOF
2.0 and XMI 2.1.1.

Proposed solution:

In section 3

Change:
“
3 Normative References
The following normative documents contain provisions, which, through
reference in this text, constitute provisions of this specification. For
dated references, subsequent amendments to or revisions of any of these
publications do not apply.
• OMG UML 2.2 Infrastructure Specification formal/2009-02-04
• OMG Meta-Object Facility (MOF) ver. 2.0 formal/2006-01-01
• OMG Semantics of Business Vocabularies and Business Rules (SBVR) Ver
1.0 formal/08-01-02
• ISO/IEC 19502:2005 Information technology – Meta Object Facility (MOF)
• ISO/IEC 19503:2005 Information technology – XML Metadata Interchange
(XMI)
• ISO/IEC 11404:2007 Information technology – General-Purpose Datatypes
(GPD)
“
To:
“
3 Normative References
The following normative documents contain provisions, which, through
reference in this text, constitute provisions of this specification. For
dated references, subsequent amendments to or revisions of any of these
publications do not apply.
• OMG UML 2.4 Infrastructure Specification <omg spec ref URL>
• OMG Meta-Object Facility (MOF) ver. 2.0 <OMG spec ref URL>
• OMG MOF XML Metadata Interchange (XMI) ver. 2.1.1 <OMG spec ref URL>
• OMG Semantics of Business Vocabularies and Business Rules (SBVR) Ver
1.0 formal/08-01-02
• ISO/IEC 11404:2007 Information technology – General-Purpose Datatypes
(GPD)
"

Replace Normative References section 3, page 6, with the following:
The following normative documents contain provisions, which, through reference in this
text, constitute provisions of this specification. For dated references, subsequent
amendments to or revisions of any of these publications do not apply.
• OMG UML Infrastructure Specification, ver. 2.3, formal/2010-05-03
• OMG Meta Object Facility (MOF) Specification, ver. 2.0, formal/06-01-01
• OMG MOF XML Metadata Interchange (XMI) Specification, ver. 2.1, formal/05-09-01
• OMG Semantics of Business Vocabularies and Business Rules (SBVR) Specification,
ver. 1.0, formal/08-01-02
• ISO/IEC 11404:2007 Information technology – General-Purpose Datatypes (GPD)

12.7.2 StorableUnit Class

StorableUnit class is a concrete subclass of the StorableElement class that represents variables of the existing software

system.

No Data Available

'Table A.4 - Control actions' contains two rows related with Incr and Decr ActionElement Micro actions. In the column named 'Outputs' the word 'DataUnit' is incorrectly used twice, one per row. It should read 'DataElement'.

Page 296, A.4 replace “DataUnit” with “DataElement” (2 times)

Cobol code erroneously says "PERFROM" instead of "PERFORM".

Page 222, replace “perfrom” with “perform”

Small typo at 19.3.8

“attrbiutes” instead of attributes

Page 258, 19.3.8 replace “attrbuites” with “attributes”

In 10.5.1, Stereotype class, it says that: “In the meta-model the Stereotype is a subclass of ModelElement.”

This should read as: “In the meta-model the Stereotype is a subclass of Element.”

10.5.1. replace “In the meta-model the Stereotype is a subclass of ModelElement” with
“In the meta-model the Stereotype is a subclass of Element”

In the preface to part III we have the following:

KDM is designed in such a way that the Resource level analysis can use KDM models from the Platform Elements Layer as input and produce Resource Layer models as output. There should be no references from lower KDM layers to higher layers; therefore, new Resource Layer models can be built on top of existing Program Element layer models.

Couple of points:

1. There is no “Platform Elements Layer”. As shown in the next sentence it should probably read “Program Elements Layer” which is part II.

2. The 2 places where it refers to “Resource Layer” might be renamed to “Runtime Resources Layer” to better match the part title.

Page 159, replace “commpon properties of the Resource Layer” with “common properties of the
Runtime Resources Layer”
(After bullets) Replace “Since Resource Layer” with “Since “Runtime Resources Layer”
Replace “a way that the Resource Layer” with “a way that the Runtime Resources Layer”
Replace “produce Resource Layer models” with “produce Runtime Resources Layer
models”
Replace “new Resource Layer models” with “new Runtime Resources Layer models”
Replace “Platform Elements Layer as input” with “Program Elements Layer as input”
Replace “Resource Layer package systematically: with “Packages of the Runtime
Resources Layer”
Bullet 1 replace “Each Resource Layer package defines” with “Each Runtime Resources
Layer package defines”
Bullet 2 replace “Each Resource Layer package defines” with “Each Runtime Resources
Layer package defines”
Bullet 2 replace “Each Resource Layer package defines” with “Each Runtime Resources
Layer package defines”
Replace “modularity between Resource Layer packages” with “modularity between
KDM packages”
Page 160
Bullet 5 replace “elements of Resource Layer package” with “elements of Runtime
Resources Layer package”
Bullet 6 replace “Each Resource Layer package defines” with “Each Runtime Resources
Layer package defines” After bullets: replace “Resource Layer packages are independent” with “Runtime
Resources Layer packages are independent”
Replace “action containers in Resource Layer models” with “action containers in
Runtime Resources Layer models”
In the next bulleted list replace “Resource Layer patterns” with “Runtime Resources
Layer patterns”

In the following paragraph, the DataInterface has been gone since 2006, so maybe we just want to remove the last sentence or reword it to refer to the PlatformActions.

15.5.5 FileResource Class

FileResource represents platform resources that provide any non-database related storage. In the meta-model the

FileResource class is a subclass of ResourceType. It also implements the DataInterface so that this class can be the

endpoint of Data relations.

Page 170, delete sentence “It also implements the DataInterface so that this class can be the
endpoint of Data relations.”