XSD round-tripping - anyone succeeded?

[Paolo F Cantoni]

Given the new release (818 ) of EA, we thought we'd give XSD round-tripping another go...

The results "missed by that much" as Maxwell Smart would say...

Has anybody successfully round-tripped an XSD?

My quick observations were:
Somethings (particularly <annotation> and some defaults were missed on import)

Some things (especially ordering - but that's been a problem with EA exports since forever...) were changed on output.

The emitted XSD was self inconsistent (that is, failed validation by more robust tools such as Altova XML Spy).

The import offers two choices: XSD Element/ XSD Attributes as UML Attributes or UML Associations (but not both - which is what I'd like - since that's more in-line with general UML modelling - where a named AssociationEnd IS an Attribute.

Oh, and there doesn't seem to be a way to refresh (Synchronize) a model and an XSD - is that correct?

Admittedly, the XSD is non-trivial - however, it's not that obtuse.

Comments, thoughts, pointers?

TIA,
Paolo

[salayande]

I have raised several requests on XSD round-tripping.
This is an area of great opportunity for Sparxsystem. I submitted use cases on a workbench for XSD development including custom NDR (Naming and Design rules, example UN/CEFACT CCTS) based generation
Please, kindly raise more feature requests and this will raise the priority of XSD on the feature lists.