On 11/15/13 12:11 PM, David Sheets wrote:
Can I be caught by the absence of an element not mapping correctly to a null value of a optional element? Is there some reason which I'm missing to encode the null value in a text node as a special value?
XML doesn't know from null. That's not its problem.
If the absence of null strikes you as "fundamentally wrong", you're in the wrong place.Is there something fundamentally wrong with the design of XML that prevents this kind of data modeling? Is there a trade-off?