Issue 10431: Section 9.2.2 (ocl2-rtf)
Source: NIST (Mr. Peter Denno, peter.denno(at)nist.gov)
Nature: Uncategorized Issue
Severity: 
Summary: "The OCL specification puts no restriction on visibility."


I don't think this statement is true. For example, self is bound to the 
instance in context. There is a whole prior section on scoping. 

Resolution: 
Revised Text: In Section 9.2.2, replace the sentence " The OCL specification puts no restriction on visibility." By 
"The OCL specification puts no restriction on the visibility declared for a property defined in the model (such as 'private', 'protected' or 'public').
Actions taken:
November 2, 2006: received issue
October 16, 2009: closed issue
Discussion: 
In fact the text refers to the visibility concept related to UML properties (public, private, protected …). Visibility is not used here in its general meaning.
This can be clarified to avoid any confusion.
End of Annotations:=====
s is issue # 10431

Section 9.2.2

"The OCL specification puts no restriction on visibility."


I don't think this statement is true. For example, self is bound to the 
instance in context. There is a whole prior section on scoping.