XMI12 — Unclear software compliance - see also issues 3887 and 3889

Appendix C refers only to the conformance of XMI DTDs and Documents and
provides no statements regarding what it means for a software
implementation/tool to be conformant (except tangentially the first bullets
in C.2.2 and C.2.3 under Usage Compliance). Note that references under Usage
Compliance to early releases of many tools not supporting XML 1.0 are now
outdated and statements about 'conforming to the XML recommendation' are too
vague.

Draft strawman resolution (needs to fully absorb myriad points in issue
3887)
----------------------------
Delete existing sections Usage Compliance under C.2.2 and C.2.3.

Add new section C.3 Software Compliance Points
-----------------------------------------
To be "minimally XMI compliant for metamodel M" software must:

• Produce XMI documents compliant with M (as defined in section C.2.2)
  representing its 'internal' elements through the rules of at least one of
  Containment or Package Extent.
• Consume a XMI document compliant with M to create a new set of
  'internal' elements.
• Be at least 'non-validating processor' (as defined in the XML
  Recommendation) with respect to a DTD compliant with M (as defined in
  section C.2.2).
• Support at least simple hrefs using xmi.id of the form outlined in
  section 3.8.2.1.

To be "fully XMI compliant for metamodel M" software must:

• Produce XMI documents compliant with M (as defined in sections C.2.2 and
  C.2.3) representing its 'internal' elements through the rules of at least
  both of Containment or Package Extent.
• Consume a XMI document compliant with M to create/update/delete an
  existing set of internal elements.
• Completely process a set of xmi.differences
• Be a 'validating processor' (as defined in the XML Recommendation) with
  respect to a DTD compliant with M (as defined in sections C.2.2 and C.2.3).
• Support all the href options outlined in section 3.8.2.1.
• Support tool interchange using the recommendation in section 3.10.
• Support the exchange of model fragments as described in section 3.7.

To be "minimally multi-metamodel XMI compliant" software must be minimally
compliant with any metamodel M (as defined above) for any MOF-compliant
metamodel. Additionally it must be able to generate a compliant DTD (as
defined in section C.2.2) for such a metamodel and support at least the XMI
MOF Subset outlined in section C.2.3.

To be "fully multi-metamodel XMI compliant" software must be fully
compliant with any metamodel M (as defined above) for any MOF-compliant
metamodel. Additionally it must be able to generate a compliant DTD (as
defined in sections C.2.2 and C.2.3) for such a metamodel