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] Which is more declarative? More XMLish?

On 2 Dec 2017, at 22:18, Hans-Juergen Rennau <hrennau@yahoo.de> wrote:

Michael Kay wrote: "the result of serializing the map as JSON and then converting the JSON to XML will be an infinite XML document"

But this assumes a certain way of representing JSON data in XML (or, more generally, "information objects" in XML),

Yes, I was talking in the context of XPath 3.1 and this phrase was intended to mean "applying the function serialize($map, {'method':'json'}) and then applying the function json-to-xml()".

Of course the XML representation of JSON delivered by this function is not the only one possible. In particular, it is chosen ("arbitrarily" if you like) as a format that gives a lossless XML representation of any JSON text. For specific constrained JSON vocabularies and data models (e.g. the Linked Data model), you will always be able to devise something that's more suited to the particular model. For example, you can always do better if you know that all the keys in the JSON text will be valid XML names.

Michael Kay

[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