W3C home > Mailing lists > Public > public-xmlsec@w3.org > April 2009

Proposal: Add parallel processing requirement, close ISSUE-27, ISSUE-29, ISSUE-30 related to transform simplification

From: Frederick Hirsch <frederick.hirsch@nokia.com>
Date: Mon, 6 Apr 2009 14:39:13 -0400
Message-Id: <ABF21DC3-4ABC-4FA3-853E-1B9FF46EC160@nokia.com>
To: XMLSec WG Public List <public-xmlsec@w3.org>
Cc: Frederick Hirsch <frederick.hirsch@nokia.com>
I propose we close the following issues, as being addressed in the   
XML Signature Transform Simplification: Requirements and Design draft  
[1] after confirming that #2 is possible and after adding requirement  
associated with #2 to the XML Security Use Cases and Requirements  
draft [2].

(1) ISSUE-27 : Profile XML Signature spec to disallow removal of used  
namespace nodes from nodesets

This should be addressed by the notion of maintaining namespace  
context with a selection context, without incurring the cost of  
copying namespace nodes.

(2) ISSUE-29 - Able to run transforms in parallel (in general  
parallelism related to pipelining)

If this should be possible as a result of ability to stream then this  
should be closed.  Do you agree that it should be possible?

Propose to add requirement to requirements draft "Able to run  
transforms in parallel where possible."

(3) ISSUE-30 - Limit XPath Filter transform to be first transform or  
to not use parent axis

The transform simplification note has an explicit concept of selection  
as the first processing stage.

regards, Frederick

Frederick Hirsch

[1]  http://www.w3.org/2008/xmlsec/Drafts/transform-note/Overview.html

[2] http://www.w3.org/2008/xmlsec/Drafts/xmlsec-reqs/Overview.html
Received on Monday, 6 April 2009 18:41:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:11 UTC