IBM Defined XSDs Message Model contention

The IBM Defined (auto-generated) XSDs associates
with SOAP 1.2 are causing Message Model contention in both IIB v9 and
IIB v10 (static libraries). Yet another example of how message model
unification that occurs within IIB causes contention because of the
lack of isolation between message models, which was never a problem
with Message Sets.

This issue prevents the deployment of contending message models to the
same integration server (when deployed as independent resources), or
linking of the contending message models to the same application (when
using application containers).

The IBM defined / auto-generated SOAP 1.2 XSD contains an SVN keyword
"$id". When a Message Model utilising a SOAP 1.2 binding is uploaded to
an SVN repository, this SVN keyword is transposed for local revision
information.

Subsequently, when deploying multiple such message models e.g.
"MyLibrary" and "MyLibrary2", IIB attempts to generate a unified
Message Model by comparing the contents of the soap 1.2 XSD from within
"MyLibrary" and "MyLibrary2".

The deployment of the second message model fails with the attached
error (see "deployment_error.log").

"Files in the 'IBMdefined' and 'RemoteFiles' folders can exist multiple
times within an application or execution group (when multiple libraries
are deployed directly to the execution group), but all files that are
contained in these folders, and have the same path, must be identical."

...so, the IIB Message Models are causing contention with themselves
because of the IBM defined folder which Customers are not responsible
for generating.