Agenda and Minutes

Agenda

• Status update

Please add your suggestions here, introduced by your name or initials as a 2nd-level heading. We will sort and prioritize them later.

Erik

• Enhance the functionality or the manifest that feeds the zip creation: Add the possibility to create files-in-the-zip from ports in the pipeline (given that this port has sequence=false). So then you have three possibilities for this: A file from disk, a literal file in the manifest and a port output.
• Use the same mechanism (the same manifest?) for creating a file/directory structure on disk
• Add a p:tee step. Much easier and more low-threshold solution than the current proposal about diagnostics (we could have both). Add a disable option to the step so you can easily switch it off when not debugging
• Make it possible to read recursive directory structures directly
• Specifics for importing and using function libraries in XQuery and XSLT
• Remove p:value-available()

I would also like to show you all what I've done with regard to explaining XProc in book format (O'Reilly already turned it down :-( ). I made some choices that I would like to have feedback on.

On the clarification front I hope we can find some time to discuss (in or out the "official" part) this and others:

• Shouldn't the p:declare-step/@xpath-version be an xs:decimal?
• You need maps in a step's prolog for specifying output serialization. But you can't use variables there, so these will be “fixed” maps, specified in full at the location where they're needed. Would it be an idea to allow variable declarations in between p:input/p:output/p:option elements?
• Why is the @parameters on the p:load an AVT?
• What I thought it was decided that all steps have a primary output port (so also p:store). This is not (yet?) in the specs or am I mistaken?
• What is meant with this for p:group: A group is specified by the p:group element. In a p:try, it is a non-step wrapper, ... ???
• What is meant with: The p:finally has no inputs and no outputs. It exists only to handle recovery and resource cleanup tasks. If cleanup tasks require access to readable ports, put them in the p:catch block of an enclosing p:try.
• Why do p:catch and p:finally have name attributes (and p:when/p:otherwise dont)
• An output port of a viewport is stated as primary in the spec. So do you have to say primary="true" when declaring it?
• What is the default value of @expand-text?
• The explanation of the serialization parameters is not very detailed. Where can I find more information? (e.g. method is unexplained and has no value list, what do the normalization-form-s do, etc.)
• What is the default value of p:option/@required
• Why does the use of @pipe exclude the use of p:pipe, p:document and p:inline on a p:with-input? Seems unnecessary…
• What does this mean with the p:inline: It is a static error (err:XS0071XPS) if the content type value specifies a character set and the encoding attribute is absent.
• I don't understand the example given for p:namespace. I must honestly say I no longer understand p:namespace at all, even I remember understanding it more-or-less in Aachen.
• What happens when on a p:load you set dtd-validate to true and the doc has no DTD ref
• Where does p:system-property(p:language) gets its value from?