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] XML Redux


That could work too. However, I'm just thinking of the use case {"button-label":"<<< Previous <<<"}. 

"xml(<test>This is a test.</test>)" is both less ambiguous and far less likely to occur as part of a random JSON expression.


On Mon, Feb 21, 2011 at 12:36 PM, John Cowan <cowan@mercury.ccil.org> wrote:
Kurt Cagle scripsit:

> The role of xml() is simply to disambiguate the content within the
> block as being XML rather than being text. In a JSON filter without
> any XML namespace awareness, it would become the responsibility of
> the client to parse the XML into some kind of DOM representation,
> in JAXON this would be a flag used to identify this as intentionally
> xml content. Otherwise, you would need to know a-priori that this was
> an XML property, which rather defeats the whole process.

I still don't understand what you're getting at.  If a value in JSON
begins with a digit or sign, it's a number; if it begins with a quote,
it's a string; if it begins with [ or {, it is an array or object;
if it is true, false, or null, it's those special objects.  It can't
begin with a <, so we just say that in JAXON, if it begins with <, it is
an XML element.  Done.

As we all know, civil libertarians are not      John Cowan
the friskiest group around --comes from        cowan@ccil.org
forever being on the qui vive for the sound     http://www.ccil.org/~cowan
of jack-booted fascism coming down the pike.           --Molly Ivins

[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