public-xml-processing-model-comments@w3.org from January 2008 by date

Wednesday, 30 January 2008

• Re: Using options in XSLT match patterns Florent Georges
• Re: A few items cherry-picked from comment #54 Nikolay Fiykov
• Re: [closed] Re: comments on XProc last-call draft Nikolay Fiykov
• RE: Using options in XSLT match patterns Toman_Vojtech@emc.com
• Using options in XSLT match patterns Toman_Vojtech@emc.com

Tuesday, 29 January 2008

• [closed] Re: Questions + comments on XProc WD 14 December 2007 Norman Walsh
• RE: Questions + comments on XProc WD 14 December 2007 Toman_Vojtech@emc.com

Monday, 28 January 2008

• Re: Questions + comments on XProc WD 14 December 2007 Norman Walsh
• RE: Implicit parameter input on p:pipeline Toman_Vojtech@emc.com
• RE: Comments on Editor's Draft 9 January 2008 Toman_Vojtech@emc.com
• RE: Questions + comments on XProc WD 14 December 2007 Toman_Vojtech@emc.com
• RE: Default bindings for non-primary inputs Toman_Vojtech@emc.com

Friday, 25 January 2008

• Re: Default bindings for non-primary inputs Henry S. Thompson
• Re: Output from for-each that gets evaluated zero times Henry S. Thompson
• Re: [closed] Re: p:declare-step - atomic steps vs. empty pipelines Norman Walsh
• Re: Implicit parameter input on p:pipeline Norman Walsh
• Re: Implicit parameter input on p:pipeline Norman Walsh
• Re: Implicit parameter input on p:pipeline Norman Walsh
• Re: Execution order of steps in a pipeline Norman Walsh
• [closed] Re: XSLT pattern matching in p:viewport - matching descendant nodes Norman Walsh
• Re: Comments on Editor's Draft 9 January 2008 Norman Walsh
• Re: Comments on Editor's Draft 9 January 2008 Norman Walsh
• Re: Questions + comments on XProc WD 14 December 2007 Norman Walsh
• Default bindings for non-primary inputs Norman Walsh
• Output from for-each that gets evaluated zero times Norman Walsh
• [closed] Re: Properties of an implicit output port Norman Walsh
• [closed] Re: sequence-consistency of choose/try branches Norman Walsh
• Re: [closed] Re: An unfulfilled requirement maybe? Norman Walsh
• [closed] Re: Should defaulted ports be named? Norman Walsh
• [closed] Re: Comments from the XSLT WG on the XProc Last Call Document Norman Walsh
• [closed] Re: Does a primary output have to be connected in all branches? Norman Walsh
• [closed] Re: Last Call Comment on XProc - http://www.w3.org/TR/2007/WD-xproc-20070920/ Norman Walsh
• A few items cherry-picked from comment #54 Norman Walsh
• [closed] Re: comments on XProc last-call draft Norman Walsh
• RE: [closed] Re: p:declare-step - atomic steps vs. empty pipelines Toman_Vojtech@emc.com
• RE: [closed] Re: p:declare-step - atomic steps vs. empty pipelines Toman_Vojtech@emc.com
• [closed] Re: p:declare-step - atomic steps vs. empty pipelines Norman Walsh
• RE: Implicit parameter input on p:pipeline Toman_Vojtech@emc.com
• [closed] Re: XSLT 1.0 and XSLT 2.0 Norman Walsh
• RE: Implicit parameter input on p:pipeline Toman_Vojtech@emc.com
• Re: Last Call Comment on XProc - http://www.w3.org/TR/2007/WD-xproc-20070920/ Henry S. Thompson

Thursday, 24 January 2008

• [closed] Re: Compound steps with empty subpipelines Norman Walsh
• [closed] Re: Typo in p:label-elements Norman Walsh
• [closed] Re: clarification of p:pipeline-library and p:import Norman Walsh
• [closed] Re: put optional step in different namespace Norman Walsh
• [closed] Re: Standard (ECMAScript) interface for invoking XProc Norman Walsh
• [closed] Re: Embedding one pipeline into another (or "defaulting pipeline libraries") Norman Walsh
• Re: XSLT 1.0 and XSLT 2.0 Norman Walsh
• [closed] Re: a note on spec link usability Norman Walsh
• [closed] Re: clarify 5.11 p:pipe definition and refering to p:pipeline inputs Norman Walsh
• [closed] Re: Dynamic errors, choose Norman Walsh
• [closed] Re: xinclude processing and XProc Norman Walsh
• [closed] Re: Multiple imports Norman Walsh
• [closed] Re: Improve XProc suitability for localization Norman Walsh
• [closed] Re: Comment: version and forward compatibility Norman Walsh
• Re: Execution order of steps in a pipeline Henry S. Thompson
• [closed] Re: Name Attributes and Fragment Identifiers Alex Milowski
• RE: Execution order of steps in a pipeline Toman_Vojtech@emc.com
• Implicit parameter input on p:pipeline Toman_Vojtech@emc.com

Wednesday, 23 January 2008

• Re: Compound steps with empty subpipelines Norman Walsh
• Re: Execution order of steps in a pipeline Henry S. Thompson
• RE: Comments on Editor's Draft 9 January 2008 Toman_Vojtech@emc.com
• Execution order of steps in a pipeline Toman_Vojtech@emc.com

Friday, 18 January 2008

• Typo in p:label-elements Toman_Vojtech@emc.com
• p:set-attributes - attributes with the "xmlns" prefix Toman_Vojtech@emc.com
• RE: p:declare-step - atomic steps vs. empty pipelines Toman_Vojtech@emc.com

Thursday, 17 January 2008

• Re: declare-step - atomic steps vs. empty pipelines Norman Walsh
• Re: p:declare-step - atomic steps vs. empty pipelines Norman Walsh
• [closed] Re: propose changing p:directory-list filter option Norman Walsh
• [closed] Re: proposed changes and clarifications to p:load Norman Walsh
• [closed] Re: Please add Implementation and Test Suite info to the W3C XProc page Norman Walsh

Wednesday, 16 January 2008

• Re: normalization-form serialization option Alex Milowski
• [closed] Re: http-request/etc. and URI encoded references Alex Milowski
• Re: Compound steps with empty subpipelines Henry S. Thompson
• Compound steps with empty subpipelines Toman_Vojtech@emc.com

Tuesday, 15 January 2008

• RE: declare-step - atomic steps vs. empty pipelines Vasil Rangelov
• XSLT pattern matching in p:viewport - matching descendant nodes Toman_Vojtech@emc.com

Monday, 14 January 2008

• RE: declare-step - atomic steps vs. empty pipelines Toman_Vojtech@emc.com
• RE: declare-step - atomic steps vs. empty pipelines Vasil Rangelov
• p:declare-step - atomic steps vs. empty pipelines Toman_Vojtech@emc.com

Saturday, 12 January 2008

• Re: [closed] Re: An unfulfilled requirement maybe? Vasil Rangelov

Friday, 11 January 2008

• Re: Comments on Editor's Draft 9 January 2008 Henry S. Thompson

Thursday, 10 January 2008

• [closed] Re: xsl-formatter Alex Milowski
• [closed] Re: normalization-form serialization option Alex Milowski
• [closed] Re: headers in p:http-request Alex Milowski
• Comments on Editor's Draft 9 January 2008 Toman_Vojtech@emc.com

Wednesday, 9 January 2008

• [closed] Re: what does p:episode actually mean ? Norman Walsh
• [closed] Re: 3.2 Scoping of Names Norman Walsh
• [closed] Re: Comment 30, Parameter inputs as strings Norman Walsh
• [closed] Re: Output of p:xslt and p:xslt2 / xpointer Norman Walsh
• [closed] Re: p:add-xml-base with relative=true Norman Walsh
• Re: Improve XProc suitability for localization Norman Walsh
• [closed] Re: Comment: untrusted environments and security Norman Walsh
• [closed] Re: Saxonica comments on XProc Last-Call WD, sections 5-7 Norman Walsh
• [closed] Re: Saxonica Comments on XProc last-call draft, sections 3 and 4 Norman Walsh
• [closed] Re: Saxonica Comments on XProc last-call draft, sections 1 and 2 Norman Walsh
• [closed] Re: An unfulfilled requirement maybe? Norman Walsh
• Re: I'm _still_ confused about 3.8 Extension elements Henry S. Thompson

Tuesday, 8 January 2008

• Re: I'm _still_ confused about 3.8 Extension elements Norman Walsh
• Re: I'm _still_ confused about 3.8 Extension elements Norman Walsh

Thursday, 3 January 2008

• Re: Improve XProc suitability for localization Jirka Kosek

Wednesday, 2 January 2008

• [closed] Re: p:function (a.k.a. a standard mechanism for XPath extensions within XProc) Norman Walsh
• [closed] Re: minor p:http-request issues Norman Walsh

Last message date: Wednesday, 30 January 2008 21:08:07 UTC