Issue 6558: Issue: General section to define OCL concepts                                                                                                                                                           (ocl2-ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: Description: The specification should contain an introductory section containing definitions of the terms used in the specification and other notations that are used (e.g. well-formed expression, ill-formed expression, behaviour, undefined-behaviour etc.).
Rationale: This will avoid ambiguities and provide a better specification of the OCL (see specifications for C++, Java, and C#).  

Resolution: 
Revised Text: Revised Text:
1) In the Terms and Definitions (section 3), remove the editorial comment for the FTF
and replace the sentence "For the purposes of this specification, the terms and definitions
given in the normative references and the following apply."
by the sentence: "There are no formal definitions in this specification that are taken from
other documents."
2) In the Symbols chapter, remove the editorial comment for the FTF and replace the
sentence "List of symbols/abbreviations." by "There are no symbols defined in this
specification".
3) In section 6.2, after paragraph "Section 12 …" adds the following paragraph:
"""Section 13 ("Basic OCL and Essential OCL" defines the adaptation of the OCL
metamodel when used in the particular context of Core::Basic infrastructure library
package and in the context of EMOF."""
4) Update the acknowledgement list (6.3) adding France Telecom (alphabetical
ordering)
Actions taken:
November 11, 2003: received issue
November 1, 2005: closed issue
Discussion: 
Resolution:
Ideally we agree that a complete introduction of the concepts used could be provided
within the document to improve understandability of the specification. However, since
OCL makes usage of concepts defined in normative references (UML and MOF), we
prefer let the reader look at the reference documents.
We treat also here two other points concerning the general section: update of the
acknowledgement list and missing reference to chapter 13.
End of Annotations:=====
ssue: General section to define OCL concepts
Description: The specification should contain an introductory section containing definitions of the terms used in the specification and other notations that are used (e.g. well-formed expression, ill-formed expression, behaviour, undefined-behaviour etc.).
Rationale: This will avoid ambiguities and provide a better specification of the OCL (see specifications for C++, Java, and C#).