Export Open Exchange File doesn't export label expression

[VinceAxe]

When exporting to the open exchange file format, the Label Expression field isn't exported. Meaning when another user is importing the file (in Archi) all the label expressions have disappeared

Version of Archi

Archi 4.7.1

Archi Plug-ins

coArchi 0.6.2 / scripting 0.8

Expected Behaviour

I know label expressions are only visuals and not part of the standard, but it would be nice to keep them.

[Phillipus]

@jbsarrodie and I discussed this might be possible in the future by importing/exporting the expression in a special Property and the evaluated label value in the diagram object's label (over-riding the concept's name value). Would only be useful for Archi -> Archi import/export, though.

[jbsarrodie]

Additional comments:

• When planning to later edit a model in Archi, the native format should be used and not the Exchange format which is "lossy"
• Not all tools support customizing concepts label, and even if they do, there is no guarantee that they'll import them from the Exchange Format. This is because this feature, though present in the format definition, is not part of the interoperability tests.
• Exporting the label will export the value, not the expression (which won't be of any help anyway for another tool). We might export the expression in a way that would make it possible for Archi to get it back, but I'm not sure it makes sens though (because the native format should be prefered in this case).

[VinceAxe]

That's more or less what I told the team I work with thanks both for your replies and precisions

[ZanteBFF]

Hello everybody, I am working on Archi exports and I absolutely need to export label expressions. I've noticed that when exporting a xml format still there are no label expressions tagged. I am wondering if this issue is still open. As a workaround, I've accepted the suggestion to work with native format, where label expressions are visible under the tag "contents". Still there is an inconvenient about native format and Specialization images. When adding specialization images to the model, trying to open the native format results in a not readable binary file (Archi version 4.9.3). Are you aware of this incovenient?

[Phillipus]

I've no plans at the moment to implement export of label expressions in the exchange format.

the native format results in a not readable binary file

Images are stored together with the model in a zip format.

[ZanteBFF]

Thank you for the answer Phil