Unapply profile in XMI export

[mobius]

Hi,

Does anyone know how to unapply a profile while exporting to XMI ?

The profile should still be applied to the package in the repository.

BR,

M.

[Geert Bellekens]

What would that be, "unapply a profile"?

Geert

[mobius]

Geert,

Remove all stereotype ( and properties / tagged values  )

BR,

M.

[qwerty]

You can't (AFAIK). To me that's like printing a book originally in French and telling the reader it's Spanish.

q.

[mobius]

Geert,

In a normal XMI it would mean:
- remove the profile IRI and prefix from the root
- remove the 'appliedProfile' from the 'profileApplication' section
- remove all stereotype statements --> all <profilePrefix:profileStereotype ......../> since tagged values are part of these statements these will also disappear.

This will work, but not for EA roudtrip, since EA puts all sorts of redundant information in their <xmi:Extension>.

BR,

M

[mobius]

quote from the spec: ( 12.3.3.3 ProfileApplication )

Once a Profile has been applied to a Package, it is allowed to remove the applied Profile at will. Removing a Profile implies that all elements that are instances of Stereotypes defined in the Profile are deleted including the instances of Profile-defined Classes they compositionally aggregate and the instances of Profile-defined composite Associations linking them. Other instances that are not compositionally aggregated must also be deleted if their defining type is no longer accessible from any other Profile applied to the same model.The removal of an applied Profile leaves the instances of elements from the referenced metamodel intact. It is only the instances of the elements from the Profile that are deleted. This means that for example a profiled UML model can always be interchanged with another tool that does not support the profile and be interpreted as a pure UML model. A Profile which is a packagedElement of another Profile can be applied individually. However, the nested Profile must specify any required metaclass and/or metamodel references if it contains any Stereotypes and may use PackageImport to indicate other Profiles to be co-applied. Metaclass and/or metamodel references are not inherited from a containing Profile.

[Geert Bellekens]

I don't think there's a feature to do that.
You might want to play with the different options in the xmi export, or else write an xslt and apply that after exporting xmi.

Geert

[qwerty]

Still my translation example holds true. Just that Sparx allows to do such things does not make them more meaningful.

q.

[Eve]

I'd look at running an XSLT transform on the exported XMI. There's built-in support to do that, to the extent that you can use it as a new export format.

https://sparxsystems.com/enterprise_architect_user_guide/14.0/modeling_tools/add_import_export_scripts.html

[mobius]

Simon,

I was aware of the xalt option, but not the MDG part of it, thanks.

I will probably try this, can anyone give a hint which information needs to be deleted from the xmi:extension part?

BR,
M.

PS. Are you ever gonna support xslt 2.0 ??