- From: Ari Nordström <ari.nordstrom@gmail.com>
- Date: Tue, 10 Oct 2017 10:01:28 +0200
- To: Carine Bournez <carine@w3.org>
- Cc: XProc Dev <xproc-dev@w3.org>
Received on Tuesday, 10 October 2017 08:01:58 UTC
Hi, Fair enough--and I just learned something new--but the same question would have to be applied to every non-XML content type you might want to address through @select. Or would the spec say 'XPath for XML content, implementation-specific for any other'? Or just say 'anything goes' for any content type? Or did I get this wrong? Best, /Ari On 10 October 2017 at 09:11, Carine Bournez <carine@w3.org> wrote: > On Tue, Oct 10, 2017 at 08:56:03AM +0200, Ari Nordström wrote: > > Hi, > > > > I'd say no. There is a well-defined expectation of what it is, both in > > XProc and outside it, and there's nothing comparable to XPath for > > addressing a non-XML document, as far as I know. > > > Hi, > > JSON Patch uses JSON Pointer (https://tools.ietf.org/html/rfc6901) > This could be an interesting way to @select something in JSON, > albeit very simple. > > > > > -- > Carine Bournez /// W3C Europe >
Received on Tuesday, 10 October 2017 08:01:58 UTC