Annotation model consistency

[CoryCasanave]

• Properties with primitive types have inconsistent compositions. I know this is irrelevant to our provisioning, and I have left them out of the report to avoid confusion, but it would be tidier if they were either all composite or all not composite. This would avoid misleading readers of the model file who might infer a difference where none is intended. I would prefer composite, and I’m happy to make the changes in the model if you agree.
• Similarly, visibilities (apart from protected) are randomly selected from private, public and unspecified. Any objection if I make them all unspecified apart from the protected ones?

[st3v3c00k]

I did this. Unfortunately it seems that MagicDraw will not allow one to set a visibility to unspecified once it has been set to something else (this would be a bug - UML allows unspecified visibility). So I set them all to public, except the protected ones. And then the diagram does not reliably track the model - another MD bug.