XProc Agenda 01 Apr 2015

Meeting 268.

The XML Processing Model (XProc) WG will meet on Wednesday, 01 Apr 2015 at 10:00a EDT (07:00a PDT, 14:00UTC) for one hour on the W3C Zakim Bridge, +1-617-761-6200 (or via SIP), passcode 97762# ("XPROC").

XProc uses the #xproc IRC channel on irc.w3.org:6665 (or via the web interface). The IRC channel is used for managing agendas, minutes, and other aspects of the teleconference, so please join us there if at all possible.

See the XProc WG page for pointers to current documents and other information. If you have additions to the agenda, please email them to the WG list before the start of the telcon.

1. Administrivia
   1. Roll call.
   2. Accept this agenda.
   3. Accept the minutes of 25 Mar 2015.
   4. Next meeting: 08 Apr 2015.
      Face-to-face meeting confirmed for 10-12 June, 2015 in Edinburgh.
   5. Review of open action items:
      • A-235-01: Alex to provide a use case for user-defined extension functions in XProc
      • A-241-05: Alex to describe use cases for RDF support that require the ability to go back and forth from the triples to the documents.
      • A-263-01: Norm to ask Frederick Hirsh for help with the encryption implementation parts
      • A-263-01: Alex to consider the requirements for making it easy for pipelines to talk to web APIs that use common encryption patterns (e.g., OAuth2)
      • A-265-02: Jim to attempt to describe a minimally interoperable error format for a standard error port.
      • A-266-01: Alex to update issue 138 with an outline of what needs to be covered by a proposal to make the functions more broadly available
      • A-267-01: Norm to make p:load more explicitly like http-request, perhaps by adding a dtd-validate step and describing a pipeline that can use it. He'll also add globbing for file: URIs and perhaps the filtering stuff we discussed.
      • A-267-02: Norm to make sure that the case of casting multipart to single part is covered; Alex believes that binaries are base64 encoded in multipart documents (so that the boundary isn't borked)
2. Technical
   1. Semantics of p:cast-content-type, issue 116? (Continued from last week, review minutes.)
   2. Clarify p:load, issue #145; see proposed changes to p:document, p:load, and p:http-request.
   3. Norm's proposal for filtering inputs, see p:filter.
   4. “Merge” the concepts of ports and options issue 109?
   5. Proposal for p:validate step
   6. Proposal for p:sort step
   7. Proposal for p:import-functions in issue #49
3. Any other business