Serialization of XDM

[David A. Lee]

Somewhat Ironically, this solves the same problem the same way JSON did 
i.e.
make the serialization format the same as the Code (in Jason's case 
Javascript).
It also has the same problem though.
It requires an XQuery paser to parse.  Suppose you want to send the 
results to something that isnt XQuery, say as an external variable to an 
XSLT or XPATH processor.   Those would require XQuery to pase it.

Its an interesting idea with some merit though ...



David A. Lee
http://x-query.com/mailman/listinfo/talk  
http://www.calldei.com
http://www.xmlsh.org
812-482-5224



Pavel Minaev wrote:
> In Mon, Sep 14, 2009 at 8:02 AM, Evgeny Gazdovsky <http://x-query.com/mailman/listinfo/talk> wrote:
>   
>> Still think that JSON may be a variant
>>     
>
> I don't see how JSON could be any sort of serious contender to
> serialize XDM data, given that the latter is much richer than JSON
> primitives.
>
> On the other hand, it seems to me that we already have such a
> serialization format, and it's XQuery itself - or rather the subset
> that involves literals, sequence "constructor" (i.e. comma operator),
> and direct element/attribute/namespace/text constructors. It's as
> portable as it gets - any XQuery processor can immediately parse it.
> And it doesn't seem to be missing anything from XDM, either.
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://x-query.com/pipermail/talk/attachments/20090914/8f599b4f/attachment.htm