"R.A.F." wrote ...
>> When i see a XML file i'm still wondering what are the differences between
>> writing node data as node attributes or as children nodes.
...
>> my question is the following one :
>> - which XML structure make a node or attribute research faster ?
>>
>> Moreover, what should be written as attribute and what should be written
>> as children node ?
This is an XML question, not a .Net or C# one. Performance is irrelevant;
accuracy of modeling is at issue.
> It depends,
That's the correct answer.
The choice of sub-node versus attribute boils down to whether the aspect in
question is a modification of a thing, or a new thing in its own right.
>> <setting>
>> <client>
[quoted text clipped - 7 lines]
>> <client name="Vaporex" address="Saint Hope st."></client>
>> </setting>
In this example, many people would consider the name and address of a client
as first-class information, deserving of their own elements. In my own mind,
I perceive an address as something that can exist independently of an owner.
Saint Hope St. is going to be there whether Vaporex occupies the property or not.
Another distinguisher is that an attribute represents metadata about an
entity, an element represents data.
These are rules of thumb, not the law of the land. Material that I've read
(in XML tutorials and the like) suggest that the decision is often a grey area.

Signature
Lew