Lists Home |
Date Index |
Some people use a single text node to represent an object's "most
obvious" value but include child elements as well. I'm not a big fan of
this, but it gets done. For example:
Saha Rabindra N wrote:
> I have one generic question on XML structure [XML element].
> If an XML element represents an object then element's attributes would be properties of that object.
> Then any subelement [be it leaf or non-leaf] would represent the hierarchy of the objects [containment].
> If the element is a leaf node then that element's value will be meaning full.
> BUT if the element is not a leaf node then what is the BUSINESS/Real-life meaning of having value in that element ?
> My understanding is that an element's attributes and its sub-elements are enough to represent an object.
> Example :
> <?xml version="1.0" encoding="ISO-8859-1"?>
> Some value
> What is the business meaning of allowing element value for non-leaf element in XML W3C standards.