ISSUE-61 (streaming reqmts): characterize what is meant by streaming and associated requirements [Rqmts (XML Signature and Canonicalization V Next Requirements)]

ISSUE-61 (streaming reqmts): characterize what is meant by streaming and associated requirements [Rqmts (XML Signature and Canonicalization V Next Requirements)]

http://www.w3.org/2008/xmlsec/track/issues/61

Raised by: Frederick Hirsch
On product: Rqmts (XML Signature and Canonicalization V Next Requirements)

define streaming use case and requirements

incorporates following issues:

Minimal caching to support streaming
http://www.w3.org/2008/xmlsec/track/issues/15

Backward reference for streaming - don't know what is referenced, algs
http://www.w3.org/2008/xmlsec/track/issues/16

Placement of KeyInfo relative to SIgnedInfo
http://www.w3.org/2008/xmlsec/track/issues/17

Data between algorithm info and digest?
http://www.w3.org/2008/xmlsec/track/issues/18

Placement of signature relative to signing or verification, different placement?
http://www.w3.org/2008/xmlsec/track/issues/19

Transform model should support streaming, filtering model
http://www.w3.org/2008/xmlsec/track/issues/20

Arbitrary selection from nodeset vs XPath expressions without backward references, traversal and navigation
http://www.w3.org/2008/xmlsec/track/issues/21

Received on Wednesday, 8 October 2008 15:05:05 UTC