XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] [OT] Re: [xml-dev] Lessons learned from the XML experiment

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.

Is there something fundamentally wrong with the design of XML that
prevents this kind of data modeling? Is there a trade-off?
If the absence of null strikes you as "fundamentally wrong", you're in the wrong place.

Also note - null isn't an especially XML conversation:

<https://www.google.com/#q=%22null+considered+harmful%22>

Thanks,
--
Simon St.Laurent
http://simonstl.com/


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS