See also: IRC log
Meeting NOT on March 16, 23
<tlr> http://www.w3.org/2010/02/09-xmlsec-minutes.html
<tlr> RESOLUTION: minutes from 9 Feb 2010 approved
<pdatta> http://www.w3.org/2008/xmlsec/Drafts/c14n-20/
<tlr> ACTION: scantor to review C14N 2.0 draft - due 2010-03-16 [recorded in http://www.w3.org/2010/02/16-xmlsec-minutes.html#action01]
<trackbot> Created ACTION-519 - review C14N 2.0 draft [on Scott Cantor - due 2010-03-16].
<tlr> ACTION-519 due 2010-03-30
<trackbot> ACTION-519 review C14N 2.0 draft due date now 2010-03-30
<tlr> ACTION: esimon2 to review C14N 2.0 draft - due 2010-03-30 [recorded in http://www.w3.org/2010/02/16-xmlsec-minutes.html#action06]
<trackbot> Created ACTION-523 - review C14N 2.0 draft [on Ed Simon - due 2010-03-30].
<tlr> ACTION: pdatta to circulate list of differences on xmlsec mailing list [recorded in http://www.w3.org/2010/02/16-xmlsec-minutes.html#action03]
<trackbot> Created ACTION-520 - Circulate list of differences on xmlsec mailing list [on Pratik Datta - due 2010-02-23].
<tlr> ACTION-520: (C14N 2.0 vs C14N 1.1)
<trackbot> ACTION-520 Circulate list of differences on xmlsec mailing list notes added
Review of updates to Canonical XML 2.0
All pseudocode in section 4
Reused text from 1.0, modified as necessary
Section 2.3 differences, input model is inclusion/exclusion list
Simpler, don't have to worry about missing namespace nodes, etc
Moving away from xpath so have to more crisply define things without appealing to xpath specs
Section 2.4 is largely a copy from exc-c14n1.0
Except...Exclusive only means for namespaces, not for xml ancestors
Some "visibly utilized" changes
Document traversal means predictable order of elements
<tlr> tlr: none
<tlr> http://lists.w3.org/Archives/Public/public-xmlsec/2010Feb/0022.html
Relationship between this and XADES, clarify?
<jcruella> my reply http://lists.w3.org/Archives/Public/public-xmlsec/2010Feb/0029.html
<jcruella> For XML formats for advanced electronic signatures that incorporate relevant signed properties in business domains and remain valid over long periods, please refer to the [XADES] specification.
Possible concerns over a normative reference outside W3C...but informational reference was the intent
<tlr> "The XAdES specification defines XML formats for advanced electronic signatures that remain valid over long periods, are compliant with the European Directive and incorporate additional useful information in common uses cases."
jcruella: There is still overlap between XADES and Signature Properties, not just in usage but in particulars.
<tlr> "The XAdES specification defines signature property formats for advanced electronic signatures that remain valid over long periods, are compliant with the European Directive and incorporate additional useful information in common uses cases."
<tlr> "The XAdES specification defines signature property formats for advanced electronic signatures that remain valid over long periods, are compliant with the European Directive."
<tlr> "The XAdES specification defines signature property formats for advanced electronic signatures that remain valid over long periods, and are compliant with the European Directive."
<tlr> jcruellas: first one is ok
<tlr> tlr: so, this? "The XAdES specification defines signature property formats for advanced electronic signatures that remain valid over long periods, are compliant with the European Directive and incorporate additional useful information in common uses cases."
bal: The most recent chat entry may be OK
<tlr> RESOLUTION: wording accepted
<tlr> action-518?
<trackbot> ACTION-518 -- Juan Carlos Cruellas to draft email and check with tlr regarding it before sending -- due 2010-02-16 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/518
<tlr> action-518 closed
<trackbot> ACTION-518 Draft email and check with tlr regarding it before sending closed
<tlr> ACTION: thomas to check with EXI group on Type parameter [recorded in http://www.w3.org/2010/02/16-xmlsec-minutes.html#action04]
<trackbot> Created ACTION-521 - Check with EXI group on Type parameter [on Thomas Roessler - due 2010-02-23].
<tlr> action-511?
<trackbot> ACTION-511 -- Thomas Roessler to propose next steps on media type registration (ISSUE-180) -- due 2010-02-16 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/511
<tlr> action-510 closed
<trackbot> ACTION-510 Propose explanation of use of content vs. element in implementations closed
<tlr> ACTION-515?
<trackbot> ACTION-515 -- Aldrin J D'Souza to propose the schema addition for issue-186 -- due 2010-02-23 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/515
<tlr> aldrin: some review internally; hope to have update next week
aldrin: schema permits additional markup per alg?
<tlr> tlr: take to e-mail
<tlr> http://lists.w3.org/Archives/Public/public-xmlsec/2010Feb/0019.html
<tlr> RESOLUTION: Accept proposed Last Call change in http://lists.w3.org/Archives/Public/public-xmlsec/2010Feb/0019.html
<tlr> action-485 closed
<trackbot> ACTION-485 Review actions assigned to Konrad and summarize which can be closed and which need further action closed
<tlr> ACTION-332 closed
<trackbot> ACTION-332 Review wording http://lists.w3.org/Archives/Public/public-xmlsec/2009Jun/0075.html closed
<tlr> action-128 closed
<trackbot> ACTION-128 document e-gov use cases closed
<tlr> action-171 closed
<trackbot> ACTION-171 Draft a proposal for canonicalization improvements closed
<tlr> action-267 closed
<trackbot> ACTION-267 Simplify canonicalization note closed
<tlr> ACTION-13?
<trackbot> ACTION-13 -- Konrad Lanz to review streaming using 2nd edition Signature -- due 2008-11-10 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/13
<tlr> ACTION: pratik to review action-13 results [recorded in http://www.w3.org/2010/02/16-xmlsec-minutes.html#action05]
<trackbot> Created ACTION-522 - Review action-13 results [on Pratik Datta - due 2010-02-23].
<tlr> action-13 closed
<trackbot> ACTION-13 Review streaming using 2nd edition Signature closed
<tlr> action-238?
<trackbot> ACTION-238 -- Konrad Lanz to update the proposal associated with ACTION-222 and send to list. -- due 2009-03-24 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/238
<tlr> action-238?
<trackbot> ACTION-238 -- Thomas Roessler to update the proposal associated with ACTION-222 and send to list. -- due 2009-03-24 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/238
<tlr> ACTION-257?
<trackbot> ACTION-257 -- Konrad Lanz to randomized Hashing (RMX) and Signing (RSA-PSS) provide a Proposal -- due 2009-04-14 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/257
<tlr> action-257 closed
<trackbot> ACTION-257 Randomized Hashing (RMX) and Signing (RSA-PSS) provide a Proposal closed
<tlr> http://lists.w3.org/Archives/Member/member-xmlsec/2010Feb/0018.html
<tlr> action-431 closed
<trackbot> ACTION-431 Fix "they" in RFC2119 section throughout all documents closed
<tlr> action-485 closed
<trackbot> ACTION-485 Review actions assigned to Konrad and summarize which can be closed and which need further action closed
<tlr> action-502 close
<tlr> action-502 closed
<trackbot> ACTION-502 Propose new model for RetrievalMethod in 2.0 closed
<tlr> action-505 closed
<trackbot> ACTION-505 Update acknowledgements in Requirements 1.1 and 2.0, also for Signature Properties closed
<tlr> action-513 closed
<trackbot> ACTION-513 Announce last call outside w3 closed
<tlr> action-516 closed
<trackbot> ACTION-516 Make last call comment and proposed change closed
<tlr> action-517 closed
<trackbot> ACTION-517 Provide proposed update to Signature Properties document closed