- From: Michael Kay <mike@saxonica.com>
- Date: Tue, 5 May 2015 09:39:48 +0100
- To: Christian Grün <christian.gruen@gmail.com>
- Cc: EXPath CG <public-expath@w3.org>
I don’t think we can add things to FO 3.1 at this stage simply because we’ve identified a new requirement. To me the natural solution is to allow file:readBinary() (and analogous functions, presumably) to accept HTTP URIs as well as FILE URIs. Michael Kay Saxonica mike@saxonica.com +44 (0) 118 946 5893 > On 5 May 2015, at 09:18, Christian Grün <christian.gruen@gmail.com> wrote: > > As a fact, none of the functions of the File Module provides support > for HTTP URIs. But if it's not too late, fn:unparsed-binary could be > added to the XQFO 3.1 spec? Maybe this would also be your intention? > > > On Tue, May 5, 2015 at 10:06 AM, Michael Kay <mike@saxonica.com> wrote: >> There seems to be an omission in the FILE module: file:readBinary() will >> only read a file from filestore. We don’t seem to have any way to read a >> binary file from an HTTP URI. >> >> Michael Kay >> Saxonica >> mike@saxonica.com >> +44 (0) 118 946 5893
Received on Tuesday, 5 May 2015 08:40:09 UTC