XProc Agenda 11 Mar 2015

Meeting 266.

The XML Processing Model (XProc) WG will meet on Wednesday, 11 Mar 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").

Note: W3C teleconferences are scheduled on "Boston local time" and the United States moves to daylight savings time on Sunday, 8 Mar 2015. I believe that British Summer Time and European Summer Time both begin on Sunday, 29 Mar 2015. That means this call will be one hour earlier on 11, 18, and 25 Mar in those locales and will shift back to its “normal” time on 1 Apr 2014. (No fooling!)

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 Feb 2015.
   4. Next meeting: 18 Mar 2015.
   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-01: Norm to attempt to spec out a generalized p:xml-validation step.
      • A-265-02: Jim to attempt to describe a minimally interoperable error format for a standard error port.
2. Technical
   1. Collector steps, issue 148?
   2. Content type on p:load, issue 145?
   3. Content type of p:inline issue 144?
   4. Clarify the concept of "URI appearing in an option value, issue 143.
   5. Reading document properties in a step-evaluated XPath issue 138?
3. Any other business