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

Michael Sokolov wrote:
200909191125.n8JBPgFv006236@hades.falutin.net" type="cite">

I have sometimes needed to be able to serialize a heterogeneous sequence of items which may be either atomic values or nodes. I'm not sure, but this may be what Jim is driving at. It is OK for my purpose if the values do not carry intrinsic type information and are simply text in the serialization, but what is important in this case is to distinguish between the items in the sequence: they have to remain distinct even if they are adjacent text items, say.

maybe this all just goes without saying, but somehow I couldn't resist saying it anyhow


This new specification would attempts to solve your problem (Mike)

because it would preserve sequences and not do "sequence normalization" on text nodes.
("A" , "B" , 1 , 2 , <foo/>}  will be preserved as a sequence of 5 items, not turned into  "AB12 <foo/>" as  the current XDM serialization spec does.

But it likely will not solve the problem Jim was describing (which is already solved).
Why ?  I haven't written it yet ... waiting for some more arguments/discussions on the use cases first.
But the direction I'm going is likely going to require a 'layer' of wrapped XML in order to preserve the XDM information such as items and types.
This implies that to use in the context Jim was suggesting wouldn't work because there would be an outer XML node containing the HTML nodes.
Thus the results would have to be 'unwrapped' before they could be used in place in JSP. In which case were back to the same problem.

This does bring to mind that perhaps there is a desire for multiple text serialization formats, such that Jim's use case would work ...
but I think I will have enough problems coming up with a single format thats acceptable to enough people and use cases.
Especially considering that Jim's particular case is already solved (by simply concatenating the text serialization of each HTML node), I doubt another spec is needed for that use case.


David A. Lee

[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