See also: IRC log
<trackbot> Date: 08 February 2011
<fjh> ScribeNick: scantor
No call Feb 22
RESOLUTION: Cancel Feb 22 teleconference
<fjh> RFC 6090 released (ECC-ALGS)
<fjh> http://lists.w3.org/Archives/Public/public-xmlsec/2011Feb/0000.html
fjh: updated references
<fjh> Feedback from implementers of widget signatures requested
<fjh> http://lists.w3.org/Archives/Public/public-xmlsec/2011Jan/0068.html
fjh: PAG status: no update
<fjh> Approve minutes, 25 January 2011
<fjh> http://lists.w3.org/Archives/Public/public-xmlsec/2011Jan/att-0064/minutes-2011-01-25.html
RESOLUTION: minutes from 25 Jan accepted
<Cynthia> I haven't finished the review yet, promise to do it asap
<fjh> Editorial update - ECC Algs reference
<fjh> http://lists.w3.org/Archives/Public/public-xmlsec/2011Feb/0003.html
fjh: suggest we update references later, leave it for now
<fjh> Editorial update - incorrect section references into ECC-ALGS
<fjh> http://lists.w3.org/Archives/Public/public-xmlsec/2011Feb/0010.html (Frederick)
<fjh> http://lists.w3.org/Archives/Public/public-xmlsec/2011Feb/0007.html
<fjh> omitted "When verifiably random curves and base points are used, they shall be generated as described in [ANSI-X9.62]."
magnus: ok, editorial
Cynthia: will review soon
fjh: review for sanity, and any section references that are wrong
... should be close to CR, thomas will fix up the cross refs
... also publish the requirements doc and the RELAX NG schemas
fjh: made same ECC changes
<fjh> Editorial update to add ECC algorithms reference and correction of section references to ECC-ALGS
fjh: pdatta made changes and sent redline text to list
<fjh> http://lists.w3.org/Archives/Public/public-xmlsec/2011Feb/0014.html
fjh: changes were to restrict combining IncludedXPath with ID-based refs
pdatta: only allowed one Include/Exclude, but you can use the OR operator
scantor: need to apply same update to one of the other Selection types
<scribe> ACTION: pdatta to apply ID/IncludedXPath change to additional selection type [recorded in http://www.w3.org/2011/02/08-xmlsec-minutes.html#action01]
<trackbot> Created ACTION-774 - Apply ID/IncludedXPath change to additional selection type [on Pratik Datta - due 2011-02-15].
pdatta: also added a call out to a section describing streaming processing
<fjh> http://www.w3.org/2008/xmlsec/Drafts/xmldsig-xpath/#sec-Streaming-Signatures
scantor: suggesting rewording the sentence to more generically refer the implementer to the XPath profile spec
fjh: does it really change processing?
... aren't the statements in the section on selection algorithm true regardless?
scantor: e.g. "see the XPath profile for implementation guidance on streaming"
pdatta: also removed restriction on inclusions not overlapping, that's handled by c14n
<fjh> ACTION-619?
<trackbot> ACTION-619 -- Ed Simon to review Meiko proposal for ACTION-538 -- due 2011-01-12 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/619
Ed_Simon: I have an action open to review a proposal from Meiko, will do so.
<fjh> ACTION-753?
<trackbot> ACTION-753 -- Scott Cantor to work on creating 2.0 example for Signature 2.0 -- due 2010-12-21 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/753
<fjh> ACTION-717?
<trackbot> ACTION-717 -- Pratik Datta to document the Performance improvements with 2.0 -- due 2010-11-09 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/717
fjh: still need example (scantor)
pdatta: had discussion with XPath group inside Oracle, they asked about XPath 2.0
... may be able to define our subset as applicable to both
... need help from their group looking into possible implications given the differences
... they indicated that the 1.0 implementation they have is legacy, and people have moved on
<scribe> ACTION: pdatta to research XPath 1 vs 2 differences [recorded in http://www.w3.org/2011/02/08-xmlsec-minutes.html#action02]
<trackbot> Created ACTION-775 - Research XPath 1 vs 2 differences [on Pratik Datta - due 2011-02-15].
fjh: probably should nail this down before last call
... don't want to hold up too long though
scantor: suggest we pick one rather than try and support both
<fjh> ACTION-763?
<trackbot> ACTION-763 -- Pratik Datta to review ISSUE-198 and where algorithm should be placed -- due 2011-01-11 -- PENDINGREVIEW
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/763
<fjh> ISSUE-198?
<trackbot> ISSUE-198 -- How to determine if arbitrary text content contains prefixes? Might need to do a lot of searching because text content can be large -- open
<trackbot> http://www.w3.org/2008/xmlsec/track/issues/198
pdatta: we put back the regexps for the XPath scanning, but also a note identifying the cases we don't handle
fjh: please review actions and 1.1 CR docs
<fjh> http://lists.w3.org/Archives/Public/public-xmlsec/2011Jan/0050.html