- From: James Fuller <jim@webcomposite.com>
- Date: Fri, 20 Mar 2015 12:37:01 +0100
- To: Norman Walsh <ndw@nwalsh.com>
- Cc: XProc WG <public-xml-processing-model-wg@w3.org>
the changes look good ... I wonder if now that we support multipart (and default sequence=true on output port) and all that it entails if this allows us to go a small step further and allow loading of multiple documents ala with globbing file://somedir/*.xml we may then consider other options (includes, excludes, recursive, etc) ... yes this maybe stomping on p:directory-list toes, but I always wanted p:directory-list usage as different then simple document loading. Avoiding having to do p:directory-list then for-each dance would represent a significant ease of use change, that addresses the common case much better. J On 20 March 2015 at 10:15, Norman Walsh <ndw@nwalsh.com> wrote: > Regarding issue 145, https://github.com/xproc/specification/issues/145 > I've created a draft that attempts to clarify p:document and p:load. > > 1. I've renamed content-type on p:load to override-content-type and > changed its semantics accordingly. > > 2. I've defined the semantics of p:document in terms of p:load. > > 3. I've implied a connection between the semantics of p:load and > p:http-request. > > In the course of these changes, I've changed p:load (and consequently > p:document) so that they can return multiple documents in the case > where the requested resource is multipart. > > See: https://ndw.github.io/specification/langspec/clarify-load/head/xproc20/diff.html#p.document > and: https://ndw.github.io/specification/langspec/clarify-load/head/xproc20-steps/diff.html#c.load > > Be seeing you, > norm > > -- > Norman Walsh > Lead Engineer > MarkLogic Corporation > Phone: +1 512 761 6676 > www.marklogic.com
Received on Friday, 20 March 2015 11:37:29 UTC