Re: [xsl] is XPath 3.1 xml-to-json() function useful

Subject: Re: [xsl] is XPath 3.1 xml-to-json() function useful
From: "David Maus lists@xxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 8 Mar 2019 12:00:07 -0000
On Fri, 08 Mar 2019 12:49:28 +0100,
Mukul Gandhi gandhi.mukul@xxxxxxxxx wrote:
> [1  <text/plain; UTF-8 (7bit)>]
> [2  <text/html; UTF-8 (quoted-printable)>]
> Hi all,
>    I find the XPath 3.1 function json-to-xml() quite useful. It can
>    convert any JSON input to an XML representation. But I'm not
>    convinced that XPath 3.1's xml-to-json() function (as defined in
>    the spec) is much useful.

It is very useful to me because it gives full control over the JSON

At work we recently started to publish descriptions of digital objects
as IIIF Manifests [1]. IIIF Manifest is a JSON-based metadata format,
the source of the object descriptions is in XML.

Example: Manuscript Cod. Guelf. 35 Helmst.


Not sure if a 'generic' XML to JSON conversion would be of much
help. Being explicit about the JSON structure makes the transformation

  -- David

> Taking an example from XPath 3.1 F&O spec, the following XML document
> <array xmlns="";><number>1</number><string>is</string><boolean>1</boolean></array>
> converts into following JSON by the function xml-to-json(),
> [1,"is",true]
> (which is fine)
> But as per the XPath 3.1 F&O spec, simple XML documents like,
> <root>
>    <val>1</val> 
>    <val>2</val>
>    <val>3</val>
>    <val>4</val>
> </root>
> cannot be converted into JSON, by the function xml-to-json(), since the XML input doesn't conform to structure like <array>, <number>, <string> etc (which looks to me, a very limited capability given to the xml-to-json() function).
> Any comments would be useful.
> -- 
> Regards,
> Mukul Gandhi
> XSL-List info and archive 
> EasyUnsubscribe (by email) 

David Maus M.A.

Twitter: @_dmaus

Current Thread