Issue 16122: US PAS Ballot Comment 2 (ocl2-rtf) References (ocl2-rtf) Source: (Mr. Tom Rutt, nobody) Nature: Uncategorized Issue Severity: Summary: The references need to include links to the formal OMG published specifications. The Scope clause refers to UML 2.2, however the reference is UML 2.0 Informal references to UML 1.4.1 and UML 1.5 are included as part of explanatory text in the OCL 2.2 spec which refers to UML 1.x to explain differences of this new version of OCL.. The ISO/IEC 10151 (UML 1.4.1) needs to be added as an informative reference, for use in these explanations. Change: “ 3 Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. • UML 2.0 Superstructure Specification • UML 2.0 Infrastructure Specification • MOF 2.0 Core Specification • UNICODE 5.1 Standard: http://www.unicode.org/versions/Unicode5.1.0/ « To : « 3 References 3.1 Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. • UML 2.2 Superstructure Specification <omg spec Ref URL> • UML 2.2 Infrastructure Specification <omg spec Ref URL> • MOF 2.0 Core Specification <omg spec Ref URL> • UNICODE 5.1 Standard: http://www.unicode.org/versions/Unicode5.1.0/ 3.2 Informative References The following specifications are referenced in informative text: • ISO/IEC 19501:2005 Information technology – Open Distributed Processing -- Unified Modeling Language (UML) Version 1.4.2 , also <omg Spec Ref URL> “ Change all uses of the informal UML 1.x references in the text From: “ UML 1.x” or “UML 1.4.x” “ To: “ ISO/IEC 19501:2005 “ Resolution: Revised Text: The following updates will be applied: (0) In Section 1 change: This specification defines the Object Constraint Language (OCL), version 2.3. OCL version 2.3 is the version of OCL that is aligned with UML 2.3 and MOF 2.0. By This specification defines the Object Constraint Language (OCL), version 2.3.1. OCL version 2.3.1 is the latest version of OCL that is aligned with UML 2.3 and MOF 2.0. (1) In Section 3, change: “ 3 Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. • UML 2.0 Superstructure Specification • UML 2.0 Infrastructure Specification • MOF 2.0 Core Specification • UNICODE 5.1 Standard: http://www.unicode.org/versions/Unicode5.1.0/ « To : « 3.1 Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. • UML 2.3 Superstructure Specification: http://www.omg.org/spec/UML/2.3/Superstructure/PDF/ • UML 2.3 Infrastructure Specification: http://www.omg.org/spec/UML/2.3/Infrastructure/PDF/ • MOF 2.0 Core Specification: http://www.omg.org/spec/MOF/2.0/PDF/ • ISO/IEC 10646:2003 Information technology -- Universal Multiple-Octet Coded Character Set (UCS) • UNICODE 5.1 Standard: http://www.unicode.org/versions/Unicode5.1.0/ • Unicode Technical Standard#10: http://www.unicode.org/reports/tr10/ • ISO 639 Codes for the representation of names of languages • ISO 3166 Codes for the representation of names of countries and their subdivisions 3.2 Informative References The following specifications are referenced in informative text: • ISO/IEC 19501:2005 Information technology - Open Distributed Processing -- Unified Modeling Language (UML) Version 1.4.2 “ (2) In Section 7.3.3 Invariants, replace text: “In the following example the name of the constraint is enoughEmployees. ”In the UML 1.4 metamodel, this name is a (meta-)attribute of the metaclass Constraint that is inherited from ModelElement.” By: “In the following example the name of the constraint is enoughEmployees.” (3) In Section 7.5.12 Collections of Collections, replace the paragraph: “In UML 1.4 a collection in OCL was always flattened (i.e., a collection could never contain other collections as elements). This restriction is relieved in UML 2.0. OCL allows elements of collections to be collections themselves. The OCL Standard Library includes specific flattened operations for collections. These can be used to flatten collections of collections explicitly.” By “ OCL allows elements of collections to be collections themselves. The OCL Standard Library includes specific flattened operations for collections. These can be used to flatten collections of collections explicitly” (4) At the end of Section 9.1 replace sentence: “The disambiguating rules are written in OCL, and use some metaclasses and additional operations from the UML 1.4 semantics” by “The disambiguating rules are written in OCL, and use some metaclasses and additional operations from UML”. (5) In Section 10.2.1, in foot note of “StaticValue” clause, replace sentence: “As StaticValue is the counterpart of the DataType concept in the abstract syntax, the name DataValue would be preferable. Because this name is used in the UML 1.4 specification to denote a model of a data value, the name StaticValue is used here” By “StaticValue is the counterpart of the DataType concept in the abstract syntax, the name DataValue would be preferable. StaticValue is used for historical reasons concerning past versions of UML. “ (6) In Section 10.4.2, in clause OclMessageExpEval , rule [5] replace sentence “Note that the Parameter type is defined in the UML 1.4 foundation package” by “Note that the Parameter type is defined in the UML metamodel” (7) In Section 12.1 Introduction, replace sentence: “In principle, everywhere in the UML specification where the term expression is used, an OCL expression can be used. In UML 1.4 OCL expressions could be used (e.g., for invariants, preconditions, and postconditions)” by “ n principle, everywhere in the UML specification where the term expression is used, an OCL expression can be used.(e.g., for invariants, preconditions, and postconditions). (8) In Section A.2.6 Special Types replace the sentence “The exception has been introduced in UML1.3 because it considerably simplifies the type system [CKM+99]” by “The exception has been introduced in UML because it considerably simplifies the type system [CKM+99]” (9) In Section 6.2 replace sentence: “The OCL Language Description clause gives an informal description of OCL in the style that has been used in the UML versions 1.1 through 1.4.” By “The OCL Language Description clause gives an informal description of OCL” (10) In Section 6.2 replace sentence: “Clause 8 (“Abstract Syntax”) describes the abstract syntax of OCL using a MOF 2.0 compliant metamodel. This is the same approach as used in the UML, v1.4 and other UML 2.0 specifications. The metamodel is MOF 2.0 compliant in the sense that it only uses constructs that are defined in the MOF 2.0.” by “Clause 8 (“Abstract Syntax”) describes the abstract syntax of OCL using a MOF compliant metamodel . This is the same approach as used in UML specifications. The metamodel is MOF compliant in the sense that it only uses constructs that are defined in the MOF.” (11) In Section 12.2 replace “ In UML (1.4) the Expression … “ By “In UML the Expression ...” Actions taken: April 20, 2011: received issue January 11, 2012: closed issue Discussion: Comment: References to UML and MOF need to be updated to most recent versions. Unnecessary references to UML 1.4 need to be removed or replaced by more neutral references (“UML” instead of “UML 1.4”). This concerns at least 6 locations in the spec, like in Section 7.3.3 Invariants and in Section 7.5.12 Collection of Collections. End of Annotations:===== s is issue # 16122 Issue 16122: US PAS Ballot Comment 2 (ocl2-rtf) Click here for this issue's archive. Nature: Issue from PAS Ballot comment for ISO/IEC DIS 19507 Severity: Summary: See comment US 2 in .._ANSI.doc. file in http://www.omg.org/members/cgi-bin/doc?pas/11-03-03.zip Resolution: Revised Text: Actions taken: