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] Serialization of XDM


> It has sequences (arrays) which was the problem being complained of. 
> It can be exported into XDM and imported back, with minimal 
> conventions. It has explicit types.
>
Sequences are not the core problem, they are the *missing bits* of a 
problem that is already largely solved with XML Text Serialization.
The core problem with using JSON is XML itself.  not the few extra 
things that XDM requires.

You claim:

" It can be exported into XDM and imported back, with minimal conventions. "

I have not had this experience.   Converting XML documents, or even 
elements,  into JSON then back is lossy at best and there is absolutely 
no standard "convention" on how to do it.

While JSON might be able to support sequences and atomic types fairly 
cleanly, it does not support the more complex (and most common) types 
namely "Document". Translating things like processing instructions,  
namespaces, even mixed content in JSON is very difficult.

Unless you are saying that everything except atomic types are encoded as 
JSON Strings ...

Even given that,  I agree with Micheal.   In the XML community, working 
with XML types, XML tools it a JSON serializing format wont have any 
significant acceptance.


-- 
David A. Lee
dlee@calldei.com  
http://www.calldei.com
http://www.xmlsh.org
812-482-5224




[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