For the included files in PRR, there are a number of problems with the EMOF, CMOF, XSD and Profile files as discussed by the AB. These are: 1. Profile document is missing. 2. The model as described in these files have several "private" associations defined, where all such associations should be "public". 3. The model as described in these files have several end associations defined as "" in the specification indicating "0.." cardinality, but are represented as ".." (lower bound * instead of 0) in the model. 4. The model as described in these files refers to CMOF Behavior instead of UML Behavior as per the spec. e.g. <superClass href="http://schema.omg.org/spec/MOF/2.0/cmof.xml#Behavior"/>

Adjust the PRR model in Magicdraw to generate model files that comply with the above
suggestions, and ensure these corrected model files are part of the PRR specification:

• Ensure all association ends that are .. ranges are changed to 0..*
• Ensure all associations are public not private
• Ensure all inherited classes from UML (Class, Behavior, NamedElement, Expression)
  are defined as being explicitly from UML2
• Ensure that an explicit UML Profile file is provided
  Note that none of these require any change to the specification document, just to the
  delivered normative model files delivered with PRR

As a demonstration on an SBVR project, I wrote a version in SBVR Structured English of the example in PRR Annex E, pages 58 - 65.
It was suggsted at a PRR meeting that it could be useful as an alternative view of the example, and might be included as an additional annex (or perhaps included in Annex E). It is contained in a separate document.