Question to NMF and EMF XML output compability about nmf HOT 3 CLOSED

Hi,

the problem is a little bit that it is nowhere documented how EMF expects the type information. To be fair, the usage in NMF neither is, but NMF is not (yet?) an industry standard.

I have the gut feeling that changing the output manually to the following will do:

...
<stepParameter parameter="program:PrimitiveValue Commands.program#number">
  <value xsi:type="program:Value" value="19" type="DataTypes.program#Integer" />
</stepParameter>
...

I experienced this also in a previous case study. If that works for you, I can change the serialization behavior. By the way, the next version will also be available as .NET 4.5 library, at least for most of the runtime libraries (just shout, if there is a library missing that you require).

Georg

from nmf.

Hello Georg.
Thank you for the fast answer. I've tested your proposal and it works great. I can load it in EMF without any error and there is no data loss. I proved this by loading an EMF generated XML file to NMF, saving the content with NMF, updating the NMF XML file with your proposed solution, loading it back to EMF and saving the content again. Both EMF XML files had identical content and structure, except for a change of the order of two entries that does not change the meaning. Please add this to your next release. If you need someone who tests it I could do it with my current project.

Best regards,
Herbie

from nmf.

Hello Georg.
I saw that the new version 2.0.116 now writes the type information as you suggested. I have tested it against EMF and it loads the output without any data loss. EMF behaves a little bit strange with its type information. Sometimes it adds it explicit sometimes it is implicit, but your solution works now.

from nmf.