>Ok , you're right, I should have said "no way you can get rid of prefixes".
>I understand your point, the code you modified works great,
>( I use the same approach on other component for schema definitions -nson- )
>but it looses on the way the real object structure, and convert back to xml,
>or create xml by using vfp objects would be a much hard task...
>
>I used a simpler XML to make the comparison ( attached images for 3 different views - nfXml, XmlPad, and your nfXml fork )
>
>

>
><?xml version="1.0" encoding="windows-1252"?>
>
><theroot xmlns:a="customers" xmlns:b="employees">
>
>  <queryresult a:sqlquey="select id,name from customers" b:sqlquery="select id,name from employees" >
>
>    <a:id> ALFKY </a:id>
>    <b:id> 0009 </b:id>
>
>    <a:name> Albert Fulks dont remember </a:name>
>    <b:name> Ms Davolio </b:name>
>
>    <aemptyproperty/>
>
>    
>  </queryresult>
>
></theroot>
>
>

We have different views, here, which is fine :-), but I think that having those xml* properties attached to each element and attribute is what allows a higher roundtripability of the serialization. In fact, I noticed that at least there are two other critical properties missing: xmlname (for the original name of the element or attribute) and xmlposition (for the position of the element). Without those (that I'm thinking of, right now) the xml can not be properly serialized back.

For objects that do not include those properties, because they were not serialized from XML or simply because they are pure VFP objects, the serialization into XML just follows VFP naming rules and positioning.

I'm looking into this and will come back with any developments, when they get significant.