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 - Use cases / Proposal

Hi David

I would favour an exploration of an XML parsable solution first.

An XDM outputMethod (XDM serializer) would serialize similar to XML
outputMethod with the  introduction of some xdm wrappers where necessary
such as:

     <xdm:item type=xs:integer>10<xdm:item>
     <xdm:item type=xs:integer>10<xdm:item>

With the above example, you could introduce a processing node after the
InfoSet parser to convert to XDM.


-----Original Message-----
From: David A. Lee [mailto:dlee@calldei.com] 
Sent: Monday, September 21, 2009 4:09 AM
To: Philippe Poulard
Cc: Kurt Cagle; Michael Kay; rjelliffe@allette.com.au;
xml-dev@lists.xml.org; XProc Dev
Subject: Re: [xml-dev] Serialization of XDM - Use cases / Proposal

Philippe Poulard wrote:
> Hi,
> Kurt Cagle a écrit :
>> (<?xml version="1.0" 
>> encoding="UTF-8"?>,"foo",5^positiveInteger,<bar><bat/></bar>,<!-- foo 
>> -->)
> Why not writing it directly as a native XQuery sequence ?
> ("foo",xs:positiveInteger(5),<bar><bat/></bar>,<!-- foo -->)
1) it requires an xquery parser to read it ( against use case 4)
2) It is not canonical (use case 6)  although the serialized form would 
be canonical

But yes if one were to use a non-XML format for this, the xquery format 
would be usable one,  and I'd rather see    "xs:positiveInteger(5)" then 
because it is directly parsable by xquery - if only xquery had an eval 
function :)

Overall, I would summarize the comments as

1) A new serialization format for XDM would be useful (no dissenting 
2) A 'pure XML' wrapper style XML format would work  well and is 
suggested by many
3) Several 'non XML' formats have been suggested with various stylistic 
improvements (namely conciseness) over XML but  no technical advantages 
4) Suggestions  of *multiple* optional formats have been suggested, of 
which I think (IMHO) the XQuery format is the best contender.

But I shall start with just an XML format (first, hold your breath!) and 
see if I can get some holes poked in that before continueing.
Thank you all for your comments !  I hope to get more when I pass the 
next milestone.


David A. Lee


XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

[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