XML model examples showing feature gaps with the current swagger 2.0 draft proposal

I've created two xml documents and their corresponding json schemas based on the current swagger 2.0 draft spec.  as you can see, the resulting models end up with "broken" models (due to duplicate properties).

I'm proposing adding a "name" property to the "xml" annotation so that these types of invalid models can be avoided.  the "ammended" versions show the resulting json schema utilizing this new property to make the json schema valid.