UPDM2 — some properties are wrongly marked as mandatory

This is raised on behalf of the OMG Model Interchange Working Group as it affects validation of XMI files which use UPDM.

—

I noticed that the MIWG's current reference xmi for UPDM testing fails some checks on the NIST validator because mandatory string properties are not specified.

For example, in the UPDM 2.0 spec ArchitecturalDescription's 'recommendations' is defined as:
• recommendations : String[1] - States the recommendations that have been developed based on the architecture effort. Examples include recommended system implementations, and opportunities for technology insertion.

Whereas in UPDM 1.1 it was:
• recommendations : String[*] - States the recommendations that have been developed based on the architecture effort. Examples include recommended system implementations, and opportunities for technology insertion.

It is not marked with change bars in the UPDM 2.0 spec, which might indicate that this change was not intended, and the example above certainly doesn't have an obvious need to be mandatory. As far as I know, UML and SysML have avoided making properties like this mandatory.

So, was this and others like it an intended change? Were the ones already in UPDM 1.1 intended to be mandatory?

see pages 37 and 38 of dtc/2012-12-16 for details