- From: Achim Berndzen <achim.berndzen@xml-project.com>
- Date: Tue, 10 Oct 2017 09:16:31 +0200
- To: XProc Dev <xproc-dev@w3.org>
- Cc: Norman Walsh <ndw@nwalsh.com>
As Gerrit said: This is a can of worms and might lead to the problems we had with XProc 2.0 again. Our decision to stick with XPath and use XPath as far as possible (via XPath 3.1 functions etc.) was the gateway to XProc 3.0. Lets stick with XPath and see how it will work out, having non-XML data following between steps and XPath as an expression language. If it does not work out well, we can discuss this issue again for XProc 4.0 ;-)) Achim > Am 10.10.2017 um 04:53 schrieb Norman Walsh <ndw@nwalsh.com>: > > Today, @select is defined as an XPath expression. Should it be defined > more generally as a string, interprted according to the media type of > the document to which it’s applied? Why should I not be able to select > a portion of a JSON document, or a region of an image? > > Be seeing you, > norm > > -- > Norman Walsh > Lead Engineer > MarkLogic Corporation > Phone: +1 512 761 6676 > www.marklogic.com -------------------------------------- Achim Berndzen achim.berndzen@xml-project.com http://www.xml-project.com
Received on Tuesday, 10 October 2017 07:17:00 UTC