All services defined underneath “RmsServices” need to have their service operations detailed. They are in the PIM Model, the PSM WSDL model, and in the PSM WSDL artifacts, but not in the PIM service section of the textual specification

Operation definitions have been added

It should be clear that an attribute in the PSM represents a reference to another object and just which object-type it is. For example the attribute might be named a concatenation of the “rolename”, “_”, “ID” to indicate the referenced class via the role of the association. The type of the attribute would be IDREF

Resolved as part of Issue 15212. The convention eventually adopted involved W3C type NCName rather than IDREF.
Revised Text: None

Removing the ports will resolve problems of untyped ports in the XMI.

These two ports were remnants left from services that were eliminated and were therefore untyped. Furthermore, the remaining ports created tool exchange problems. The port diagram is only used for exposition to demonstrate the scope of service provision and consumption, and will be retained in the specification pictorially to provide overview, but they are removed from the XMI. The diagram is updated with one that correctly presents our current suite of services.
Additionally
1. There was a large quantity of Sparx Systems EA extensions in the XMI. These were removed.
2. The original XMI had PSM constructs included that resulted in portability problems. The XMI is now strictly the PIM and now loads cleanly into both MagicDraw and Sparx EA tools.

For example “type” should be “attributableClassType”; all the “definition” (4 of them) should be “attributeDefinition

Managed Record should just have an association to Party to show which party created the record.

This will determine the manner in which Sparx EA will traverse the UML graph to produce the XSD

The link is needed in order to require attribution based on DocumentType; which is the intent

We list a party ID as an attribute in the style of a foreign key in the PIM. Generally we explicitly model associations in the PIM. It would however remain a foreign key in the PSM XSD.

We presume global uniqueness in our ID scheme. Is that assured by the W3C type or do we require further clarification of intent of identifiers.

For example, an AttributeClassType can have many DataProfileAttrDefn’s (maxoccurs=”unbounded”, which is the default).

document.id type is “string”, it should be “ID”.

Title: RecordKeepers and Suspensions Services no longer exist but their ports are in the specification and the XMI file.

Descr: Removing the ports will resolve problems of untyped ports in the XMI.

RMS-FTF: We have the solution for the issue (discovered in Monday’s AB Meeting) and will apply it. A ballot will be issued as soon as we verify that we have clean XMI, and again, I will be asking for a quick turnaround. We need to have this fixed to go through the AB on Thursday