public-xml-processing-model-comments@w3.org from April 2009 by date

Tuesday, 28 April 2009

• [closed] Re: HTTP redirects: MUST follow? Norman Walsh
• Re: HTTP redirects: MUST follow? Florent Georges
• Re: Rejecting invalid/unsupported p:serialization Norman Walsh
• [closed] Re: Relative URIs in p:log Norman Walsh
• Re: HTTP redirects: MUST follow? Norman Walsh
• [closed] Re: @href: HTTP request body as an external file Norman Walsh
• Re: p:exec - quote characters Norman Walsh
• Re: p:validate-with-xml-schema - multiple schemas provided Norman Walsh

Monday, 27 April 2009

• RE: [closed] Re: p:exec - path separators Toman_Vojtech@emc.com
• Re: [closed] Re: p:exec - path separators Norman Walsh
• Re: Default namespaces in XPath Norman Walsh
• Re: Default namespaces in XPath David A. Lee
• Re: Default namespaces in XPath mozer
• Re: Default namespaces in XPath David A. Lee
• RE: [closed] Re: p:exec - path separators Toman_Vojtech@emc.com
• Default namespaces in XPath Toman_Vojtech@emc.com
• Rejecting invalid/unsupported p:serialization Toman_Vojtech@emc.com

Saturday, 25 April 2009

• Re: @href: HTTP request body as an external file Florent Georges

Friday, 24 April 2009

• [closed] Re: reconsider non primary p:output on p:compare Norman Walsh

Thursday, 23 April 2009

• Re: reconsider non primary p:output on p:compare Norman Walsh
• Re: @href: HTTP request body as an external file Norman Walsh
• [closed] Re: p:exec - path separators Norman Walsh

Wednesday, 22 April 2009

• [closed] Re: c:request/@send-authorization default Norman Walsh
• [closed] Re: isnt p:group just p:declare-step Norman Walsh
• [closed] Re: p:group on p:try a bit verbose Norman Walsh
• [closed] Re: errors and exceptions in xproc Norman Walsh
• Re: c:request/@send-authorization default Florent Georges
• Re: c:request/@send-authorization default Norman Walsh
• Re: reconsider non primary p:output on p:compare Norman Walsh

Tuesday, 21 April 2009

• Re: p:choose is poorly and/or incorrectly specified Norman Walsh
• Re: Relative URIs in p:log Norman Walsh
• Re: p:choose is poorly and/or incorrectly specified Henry S. Thompson
• RE: p:choose is poorly and/or incorrectly specified Toman_Vojtech@emc.com
• RE: p:choose is poorly and/or incorrectly specified Toman_Vojtech@emc.com
• Re: p:choose is poorly and/or incorrectly specified Jeni Tennison
• Re: p:choose is poorly and/or incorrectly specified Henry S. Thompson
• Re: Relative URIs in p:log mozer
• RE: Relative URIs in p:log Toman_Vojtech@emc.com

Monday, 20 April 2009

• Re: XQuery 1.0 Norman Walsh
• Re: Relative URIs in p:log Norman Walsh
• Re: p:choose is poorly and/or incorrectly specified Norman Walsh
• Re: choose is poorly and/or incorrectly specified Norman Walsh

Thursday, 16 April 2009

• Re: Test http-request-012: p:http-request and 302 HTTP redirect Florent Georges
• [closed] Re: p:http-request: required cookie support? Norman Walsh
• Re: Test http-request-012: p:http-request and 302 HTTP redirect Norman Walsh
• Re: Test http-request-012: p:http-request and 302 HTTP redirect Florent Georges
• Re: p:http-request: required cookie support? Florent Georges
• [closed] Re: p:validate-with-xml-schema question Norman Walsh
• Re: Test http-request-012: p:http-request and 302 HTTP redirect Norman Walsh
• Re: p:http-request: required cookie support? Norman Walsh
• [closed] Re: p:http-request - conflicting content-type information for body parts Norman Walsh
• [closed] Re: err:XS0010 and err:XS0031 Norman Walsh

Tuesday, 14 April 2009

• [closed] Re: p:www-form-urldecode - decoding of parameter names and values Norman Walsh
• Re: p:exec - path separators Norman Walsh
• RE: err:XS0010 and err:XS0031 Toman_Vojtech@emc.com
• RE: p:exec - path separators Toman_Vojtech@emc.com
• RE: [closed] Re: 5.4 p:output. Informative para request Toman_Vojtech@emc.com

Friday, 10 April 2009

• Re: p:exec - path separators Norman Walsh
• Re: err:XS0010 and err:XS0031 Norman Walsh
• Re: c:request/@send-authorization default Norman Walsh
• [closed] Re: Error in the XProc Relax NG schema? Norman Walsh
• [closed] Re: 2.9, 2.10, 2.11 variables, options, parameters Norman Walsh
• Re: 2.9, 2.10, 2.11 variables, options, parameters Dave Pawson
• Re: [closed] Re: Editorial. Section 2 note Dave Pawson
• Re: [closed] Re: 5.4 p:output. Informative para request Dave Pawson
• Re: 2.9, 2.10, 2.11 variables, options, parameters Norman Walsh
• [closed] Re: Editorial. Section 2 note Norman Walsh
• [closed] Re: 2.6 Clarification Norman Walsh
• [closed] Re: 5.4 p:output. Informative para request Norman Walsh
• RE: [closed] Re: Test err-c0016-001.xml and xs:boolean Toman_Vojtech@emc.com
• RE: xquery and c:data Toman_Vojtech@emc.com

Thursday, 9 April 2009

• Re: [closed] Re: Test err-c0016-001.xml and xs:boolean Norman Walsh
• [closed] Re: p:exec - multiple source documents Norman Walsh
• [closed] Re: p:xquery and c:data Norman Walsh
• Re: p:exec - path separators Norman Walsh
• Re: xquery and c:data Norman Walsh
• Re: p:xquery and c:data Norman Walsh
• [closed] Re: Section 5.11 unnecessary complex? Norman Walsh
• [closed] Re: Inherited environment and input/output ports Norman Walsh
• [closed] Re: p:xquery - empty context item Norman Walsh
• Re: p:validate-with-xml-schema question Norman Walsh
• RE: [closed] Re: Test err-c0016-001.xml and xs:boolean Toman_Vojtech@emc.com
• Re: [closed] Re: Handling of 'non-XProc' pipeline sources Norman Walsh
• [closed] Re: http-request: if detail is true, XML not parsed? Norman Walsh

Wednesday, 8 April 2009

• [closed] Re: Test err-c0016-001.xml and xs:boolean Norman Walsh
• [closed] Re: p:http-request: c:response/c:body/@content-type value Norman Walsh
• [closed] Re: p:http-request content-type and encoding Norman Walsh
• [closed] Re: p:http-request: status message Norman Walsh
• [closed] Re: p:http-request - duplication of information in c:multipart Norman Walsh
• Re: HTTP redirects: MUST follow? Florent Georges
• RE: [closed] Re: Handling of 'non-XProc' pipeline sources Toman_Vojtech@emc.com
• Re: XQuery 1.0 Florent Georges
• HTTP redirects: MUST follow? Florent Georges
• Re: http-request: if detail is true, XML not parsed? Florent Georges
• Re: [closed] Re: Required serialization methods support Florent Georges

Tuesday, 7 April 2009

• [closed] Re: p:hash and xml:base Norman Walsh
• [closed] Re: Ordering of steps in a subpipeline Norman Walsh
• [closed] Re: Handling of 'non-XProc' pipeline sources Norman Walsh
• Re: Handling of 'non-XProc' pipeline sources Norman Walsh
• Re: http-request: if detail is true, XML not parsed? Norman Walsh
• [closed] Re: Required serialization methods support Norman Walsh
• Re: XQuery 1.0 mozer
• [closed] Re: err:XC0016 and err:XD0019 Norman Walsh
• [closed] Re: New http-request test, http-request-012.xml Norman Walsh
• [closed] Re: p:unescape-markup - "namespace" confusion Norman Walsh
• [closed] Re: Select expression in input declaration Norman Walsh
• [closed] Re: p:unescape-markup - changing the namespace URI Norman Walsh
• [closed] Re: Replacing the document node in p:string-replace Norman Walsh
• [closed] Re: p:xquery and XQueries that cannot be evaluated Norman Walsh
• XQuery 1.0 Norman Walsh
• [closed] Re: Explain "&" in the syntax tableaux Norman Walsh
• [closed] Re: Return code from p:exec? Norman Walsh
• [closed] Re: Our algorithm for anonymous step names doesn't work Norman Walsh
• [closed] Re: http-request authentication missing realm? Norman Walsh

Thursday, 2 April 2009

• Relative URIs in p:log Toman_Vojtech@emc.com
• Re: p:choose is poorly and/or incorrectly specified mozer
• Re: isnt p:group just p:declare-step mozer
• RE: choose is poorly and/or incorrectly specified Toman_Vojtech@emc.com
• Re: reconsider non primary p:output on p:compare mozer
• Re: isnt p:group just p:declare-step James Fuller
• Re: p:group on p:try a bit verbose Norman Walsh
• Re: errors and exceptions in xproc Norman Walsh
• Re: reconsider non primary p:output on p:compare Norman Walsh
• Re: isnt p:group just p:declare-step Norman Walsh
• p:choose is poorly and/or incorrectly specified Norman Walsh

Last message date: Tuesday, 28 April 2009 18:42:17 UTC