XProc Agenda 13 May 2015

Meeting 271.

The XML Processing Model (XProc) WG will meet on Wednesday, 13 May 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 29 Apr 2015.
   4. Next meeting: 20 May 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-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-268-01: Norm to attempt to clarify p:cast-content-type
      • A-268-03: Norm to rewrite the proposal, “p:filter has only a select attribute, only does positive selection, and can be on p:input as a filter attribute as a syntactic shortcut.”
      • A-269-01: Alex to review the RDF Shapes work and see if this validation step will cover that use case.
      • A-269-02: Norm to review the current state of play wrt to JSON schema and see if we can cover that use case too.
      • A-269-03: Jim to raise an issue with some specific examples of the kinds of assertions he has in mind
      • A-269-04: Norm to define the validation-attempted output format and propose a non-normative report structure
      • A-269-05: Norm to make sure there's a "Validation with Schematron" section.
      • A-269-06: Henry to review the current p:validate-with-xml-schema step and see what we should possibly say differently
      • A-267-01: Norm to move p:sort into the steps specification.
      • A-267-02: Norm to add function import to the language spec by overloading p:import.
2. Technical
   1. Local filesystem encodings, issue #159?
   2. Properties shortcut, issue #146?
3. Any other business