W3C home > Mailing lists > Public > xproc-dev@w3.org > September 2009

RE: [xml-dev] Serialization of XDM - Use cases / Proposal

From: Jim Tivy <jimt@bluestream.com>
Date: Sat, 19 Sep 2009 10:38:20 -0700
To: "'Michael Kay'" <mike@saxonica.com>, "'David A. Lee'" <dlee@calldei.com>
Cc: <xml-dev@lists.xml.org>, "'XProc Dev'" <xproc-dev@w3.org>
Message-ID: <00b301ca394f$fb81fc40$9701a8c0@Taku>
Hi Folks


Yes, there is a question of scope.


Regarding scope of an XDM Serialization recommendation, would not an XDM
Serialization recommendation subsume the XSLT and XQuery serialization
specification - or should they not be the same specification since
XQuery,XPath and XSLT are tied to XDM?




From: Michael Kay [mailto:mike@saxonica.com] 
Sent: Saturday, September 19, 2009 2:10 AM
To: 'David A. Lee'; 'Jim Tivy'
Cc: xml-dev@lists.xml.org; 'XProc Dev'
Subject: RE: [xml-dev] Serialization of XDM - Use cases / Proposal



This spec describes concatenation of node sequences such that they are
parseable as entities.

In the case you describe I think that fits well.
Atleast in my reading

5 XML Output Method

This describes serializing a sequence of nodes.  I think this spec would fit
for your use case.
Atleast that is my read, I admit I have a hard time following the reading of
this spec (not to blame the authors, I just have a hard time understanding
it all)


I agree. The existing W3C serialization is intended for this use case and is
regularly used in this way. (Though perhaps the HTML output method is more
suitable than the XML output method.) This requirement is out of scope for
this project, which needs to retain information present in the XDM that the
existing serialization methods throw away.



Michael Kay

Received on Saturday, 19 September 2009 17:39:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:03:05 UTC