Issue 17939: Location:  Constraints p 193 - All feturs must be public? (uml25-ftf)
Source: Lockheed Martin (Mr. Michael Jesse Chonoles, michael_chonoles2(at)omg.org)
Nature: Enhancement
Severity: Minor
Summary: Why
An interface should be allowed to have not public proprieties/attributes. These are necessary to have them referred to in the protocol state machine, but they need not be public attributes, i.e., no direct or query-based access to their values from he outside. They need to be there to allow for a consistent description of the state-based behavior.

Resolution: 
Revised Text: 
Actions taken:
September 27, 2012: received issue
Discussion: 

End of Annotations:=====
s is issue # 17939

Problem: 10.016

Severity: Minor
Nature: enhancement
Location:  Constraints p 193 
Title: All feturs must be public?
Why
An interface should be allowed to have not public proprieties/attributes. These are necessary to have them referred to in the protocol state machine, but they need not be public attributes, i.e., no direct or query-based access to their values from he outside. They need to be there to allow for a consistent description of the state-based behavior.
Source: Michael Jesse Chonoles