Difference between XSD import as UML Associations or UML attributes

[Modesto Vega]

According to https://sparxsystems.com/enterprise_architect_user_guide/15.2/model_domains/import_xsd.html an XSD can be imported as UML Associations or UML attributes. I have imported the same XSD using both options and cannot see a difference.

What is supposed to be the difference?

Also, is the import supposed to create relationships between complex types? If so, why isn't it doing it? What have I missed?

[qwerty]

There is no standardized mapping between UML and XSD. Try a google search and you find a couple of thesis/papers about this topic. Sparx has implemented their flavor which might or might not fit. For a customer I implemented one that fit his needs. It was quite complex.

q.

[Modesto Vega]

I don't have any major issues with Sparx Systems implementation/interpretation of how to map XML to UML, I am perfectly fine with using a class to represent each complex type. Of course, I could suggest some improvements.

I still would like to know (from Sparx) if importing XML
1) as UML Associations or UML attributes is supposed to result on different models or it is there just to confuse/pretend it does something, and
2) as UML Associations is supposed to create associations between elements representing complex types.