Issue 16126: Issue nnnn: Japan PAS Ballot Comment 3 (ocl2-rtf) (ocl2-rtf)
Source:  (Mr. Tom Rutt, nobody)
Nature: Uncategorized Issue
Severity: 
Summary: Usage of upper/lower case letter is inconsistent with UML.
For example, “Invariant”, “Precondition”, “Postcondition”, etc, in the text should be lower case letter. However, there are UML metamodel elements, such as “Classifier”.
Especially, “collection type” in function flatten, p158, is lower case letter. If this is designated in lower case letter, it is difficult to understand the meaning of sentence. What about “collection type” L1 on 11.2.1? It is confusing whether those are metamodel elements or not.)
It is required to be consistent with convention of UML upper case letter, since this standard is a family of UML, that is, it is required to use upper case letter only for UML/OCL Metamodel element.
Resolution: 
Revised Text: 
Actions taken:
April 20, 2011: received issue
Discussion: 
Initial Comment : It is required to be consistent with convention of UML upper case letter, since this
standard is a family of UML, that is, it is required to use upper case letter only for UML/OCL Metamodel
element.
Comment: In general metaclass names start with upper letter whereas attributes and operations with lower
letters. However within an explanatory text, to ease reading, we believe it make sense not always to use the
capitalized form to refer to a metaclass concept, specially when the term has a meaning in natural language
like “invariant”.
Anyway, a more detailed check to the spec is needed to see if this issue requires any change.
Disposition: Deferred
End of Annotations:=====
s is issue # 16126


Issue 16126: Japan PAS Ballot Comment 3 (ocl2-rtf)

Click here for this issue's archive. 
Nature: Issue from PAS Ballot comment for ISO/IEC DIS 19507
Severity: 
Summary: 

See comment JP 3 in .._JISC.doc.  file in http://www.omg.org/members/cgi-bin/doc?pas/11-03-03.zip
Resolution: