UML24 — xmi files in the 2.4 RTF deliverables have cmof tags contained in a non-XMI root element

xmi files in the 2.4 RTF deliverables have cmof tags contained in a non-XMI root element. Was it intentional that the current UML format XMI files use MOF/2.4 and
XMI/2.4 in their namespaces, even though these namespaces won't actually be correct? There is also an error in the structure of the .xmi files. A non xmi:XMI root element has been used that includes a cmof:Tag element, which is incorrect. The following files are affected:
10-08-17.xmi
10-08-18.xmi
10-08-22.xmi
10-08-23.xmi
10-08-27.xmi
10-08-28.xmi
10-08-29.xmi
L0.merged.xmi
L1.merged.xmi
L2.merged.xmi
LM.merged.xmi

Example:
==> LM.merged.xmi <==
</ownedComment>
</ownedLiteral>
</packagedElement>
<cmof:Tag xmi:id="_2" name="org.omg.xmi.nsPrefix" value="uml" element="_0"/> </uml:Package> Should be:
==> LM.merged.xmi <==
</ownedComment>
</ownedLiteral>
</packagedElement>
</uml:Package>
<cmof:Tag xmi:id="_2" name="org.omg.xmi.nsPrefix" value="uml" element="_0"/> </xmi:XMI>

I've also just noticed that the most recent package resolution added a property named "URI" rather than "uri", which is inconsistent with the old MOF property and is slightly unusual capitalisation for a property.
However that's a minor point.

It was intentional to use the 2.4 namespaces, see 15530.
Publish all of the xmi files that include cmof:Tag elements with a top-level XMI tag.
Leave the property named URI as it is.
Fix the profile XMI examples to conform to the normative specs.