Re: [xsl] question on standards and xml/json

Subject: Re: [xsl] question on standards and xml/json
From: "BR Chrisman brchrisman@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 13 Jul 2019 17:36:29 -0000
Thanks Wendell,

I think this is kind of similar.
Basically, I work with a number of people/groups that are pretty much JSON-only.
I commonly find the need to take some sort of XML that we've been
using and provide them with an extract of that data in the JSON
While it's not that difficult to convert XML into JSON with XSLT, I've
been wanting to have some of my structures more 'ready to convert'
As Liam mentioned, the reverse can be problematic because JSON may
include XML-excluded characters, but my interests right now are mostly
around "other people need data (currently in XML) that I'm working on,
and I need to make it easier on me to get it to them.
I've evaluated some xml->json conversion stylesheets, but I would
guess some standard like: "If you wind up with *only* this subset of
XML functionality, your XML will always be reasonably and directly
accessible after conversion to JSON." would help me a lot.
Things like:
- no multiple-namespaces (ie, I can have namespaces in my XML, but
they cannot be reasonably expressed in JSON, so anything in any other
namespace will only exist for XML processing tools)
- containers - can I mark up items to explicitly be containers such
that they translate well to JSON arrays?  This frustrates me because
XML doesn't require objects of ostensibly the same type (element name)
to be stored in an array, but JSON does (using language loosely here,
hope the meaning is pretty clear)
- attributes vs text nodes... lots of ways to go there.. but perhaps
choosing only one of those is the best option?
- (maybe other stuff)

In essence, I know there's certainly a way to express *any* XML in
JSON, so long as we're willing to go far enough in producing ugly
JSON.... but I've been looking for a standard such that if I express
my XML in 'just such a way', it will provide JSON that ... doesn't
make people angry... :)

- Brian

On Mon, Jun 24, 2019 at 2:25 PM Wendell Piez wapiez@xxxxxxxxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> Good readers,
> Gerrit points out to me the link was broken. Which is odd, but here's
> another one:
> Apologies! -- Wendell
> On Mon, Jun 24, 2019 at 5:16 PM Wendell Piez wapiez@xxxxxxxxxxxxxxx
> <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> >
> > Hi,
> >
> > XML and JSON alignment is one of the problems we've been working on here
> >
> >
> >
> > Warning: under development and subject to change. But lots of XSLT in there!
> >
> > Cheers, Wendell
> >
> >
> > On Sat, Jun 22, 2019 at 11:07 PM BR Chrisman brchrisman@xxxxxxxxx
> > <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> > >
> > > Has there been any work to define an XML subset which is
> > > simply/directly transformable into JSON?
> > > I know there are many XML expressions that  are very difficult to
> > > convert to JSON due to limits in JSON that make such a conversion very
> > > messy, but I would guess that with a number of standardized
> > > restrictions, that might be easier?
> > > Just wondering... I'm seeing more and more situations where I need
> > > that kind of 'more direct compatibility'.
> > >
> > > - Brian
> > >
> >
> >
> >
> > --
> > ...Wendell Piez... ...wendell -at- nist -dot- gov...
> >
> >
> >
> --
> ...Wendell Piez... ...wendell -at- nist -dot- gov...

Current Thread