15:02:59 RRSAgent has joined #wam 15:02:59 logging to http://www.w3.org/2009/01/08-wam-irc 15:03:11 zakim, aabb is Mark 15:03:11 +Mark; got it 15:03:18 +??P17 15:03:30 zakim, P17 is Claudio 15:03:30 sorry, ArtB, I do not recognize a party named 'P17' 15:03:36 +Frederick_Hirsch 15:03:42 zakim, ??P17 is Claudio 15:03:42 +Claudio; got it 15:03:51 Meeting: Widgets Voice Conference 15:04:06 Date: 8 January 2009 15:04:09 Chair: Art 15:04:16 ScribeNick: ArtB 15:04:18 zakim, passcode? 15:04:18 the conference code is 9231 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), marcos 15:04:19 Scribe: Art 15:04:31 Agenda: http://lists.w3.org/Archives/Public/public-webapps/2009JanMar/0033.html 15:04:49 fjh has joined #wam 15:04:54 mpriestl has joined #wam 15:05:05 zakim, Frederick_Hirsch is fjh 15:05:05 +fjh; got it 15:05:08 +??P24 15:05:09 Present: Art, Frederick, Mark, Claudio, Jere 15:05:16 zakim, ??P24 is Marcos 15:05:17 +Marcos; got it 15:05:21 Present+ Marcos 15:05:28 Regrets: Arve 15:05:42 Topic: Agenda review and tweak 15:05:48 AB: agenda http://lists.w3.org/Archives/Public/public-webapps/2009JanMar/0033.html 15:05:54 AB: any change requests? 15:05:56 [None] 15:06:03 Topic: Annoucements 15:06:07 q+ 15:06:17 AB: I don't have any widget-specific annoucments 15:06:34 FH: XML Sec WG is having a f2f meeting next week 15:06:42 ... we will look at sig properties 15:06:50 ... if anyone wants to attend, please let me know 15:07:10 ... Also, if we have any comments to discuss, I can make that happen 15:07:28 ... I may be able to rearrange things if needed 15:07:39 http://lists.w3.org/Archives/Public/public-xmlsec/2009Jan/0011.html 15:07:49 AB: please notify FH if you want to take advantage of it 15:07:53 MC: I may try to join 15:08:03 AB: any other annoucements? 15:08:08 [None] 15:09:16 Topic: R44. Support for Multiple Message Digest Algorithms 15:10:04 + 15:10:07 q+ 15:10:12 AB: FH thinks the requirement is unclear 15:10:27 arve has joined #wam 15:10:42 ArtB: as indicated, I'll be regretting 15:10:50 FH: need to clarify the model 15:11:15 ... this will effect validation 15:11:40 MP: there may be a misunderstanding in what we are trying to achieve 15:11:54 ... expect the sig to always be in the package 15:13:29 concerned how core validation can be meaningful if signature not with references, especially if using relative uris 15:13:33 ... [Mark describes some use cases that motiviated his comments] 15:14:11 this sounds like an implemention optimization, not sure it belongs in spec 15:14:14 ... I don't want to add complexity 15:14:40 FH: sounds like some pre-caching 15:15:10 ... I think we just want to say core validation is done via XML Sig spec 15:15:56 MP: don't want the spec to preclude my use case 15:16:32 ... agree we don't want to specify a separate delivery mechanism 15:16:53 ... want to make sure the two major steps can be done in either order 15:17:32 +Shepazu 15:17:34 AB: let's take the tech discussion to the public list 15:17:56 MP: I will respond to the list with more details of the use case 15:18:06 Topic: R45. Support for Multiple Signature Algorithms 15:18:48 AB: just need some clarification to SHA1 and SHA256 15:18:58 FH: yes, we need some clarification here 15:19:09 FH: a separate issue is XML Sig 1.1 15:19:34 AB: what is the status and roadmap for 1.1? 15:19:47 FH: we are very close to FPWD for 1.1 15:19:56 ... will be a topic for next week's f2f meeting 15:20:18 ... I don't expect any major issues 15:20:33 ... I think we can align the two specs 15:21:17 ... I think best case in about 3-4 months to start the Candidate phase 15:21:30 ... But we need to discuss this next week 15:22:15 AB: so you expect 1.1 REC in 2009? 15:22:20 FH: yes; definitely 15:22:30 AB: any concerns about 1.1? 15:23:06 MP: are there any other major diffs for 1.1 (besides algorithms)? 15:23:10 http://www.w3.org/2008/xmlsec/Drafts/roadmap/roadmap.html 15:23:40 FH: besides algorithms, SHA-256 migration is in scope 15:24:01 ... we have some minor errata 15:24:25 ... all major changes will be deferred to v2.0 15:25:12 AB: propose we resolve XML Sign 1.1 will be the basis for our spec 15:25:22 AB: any objections to that proposal? 15:25:56 MP: is it possible for this to hold up our spec? 15:27:02 AB: based on what FH said, I think this won't be an issue 15:27:23 Present+ Doug 15:27:43 DS: cannot go to REC if a normative reference is not a REC 15:28:05 ... need a month for PR, month for CR, month for LC 15:28:47 ... Given this, probably will take 4-5 months to get XML Sig to REC, perhaps a bit longer 15:29:28 FH: the two specs could progress together 15:30:29 AB: given where we are today, e.g. no tests, not in LC yet, I don't think we will be blocked by XML Sig 1.1 15:32:27 AB: Mark do you still have some concerns? 15:32:42 MP: I don't have any concerns about using 1.1 15:33:20 AB: any objections to using XML Sig 1.1? 15:33:22 [None] 15:33:45 RESOLUTION: propose we resolve XML Sign 1.1 will be the basis for our spec 15:34:08 Topic: R46 and R49 15:35:04 AB: the email on these shows there is agreement by Mark on FH's changes 15:35:10 AB: is that true? 15:35:12 FH: yes 15:35:15 MP: yes 15:35:27 AB: please implement the proposed changes 15:35:59 Topic: New Req proposal (5): add role of signer 15:36:56 AB: MP raised some questions about the use cases 15:37:07 AB: it wasn't clear to me how it would satisfied 15:37:32 FH: the role could be used to clarify the distributor 15:37:45 ... could use a signature property 15:38:03 ... I don't think the author element is relevant here 15:39:00 MP: if the roles are different it implies different processing 15:40:16 s/: propose we resolve/: we resolve/ 15:40:19 MP: different purposes for signing , signer vouching for trust, or update signature 15:41:06 MP: role of signature, not role of signer 15:41:44 MP: think something like this is needed but is related to the 2nd requirement proposed 15:42:26 MP: usage might be better name 15:43:30 MP: role and usage have been dealt with elsewhere 15:43:38 ... usage is different than policy 15:44:28 s/MP: role and/FH: role and/ 15:44:46 define property in sig properties, values in widgets signature 15:45:04 MPupdate signature indicates update of package 15:47:09 [Some discussions about the update mechanisms: http://dev.w3.org/2006/waf/widgets-updates/ ] 15:48:17 MikeSmith has joined #wam 15:48:23 requirment 5 should be usage instead of role 15:48:56 AB: is there consensus to add req 5? 15:49:02 Zakim, call Mike 15:49:02 ok, MikeSmith; the call is being made 15:49:04 +Mike 15:49:05 MC: no, I need to consider this more 15:49:12 FH: I tihink we need it 15:49:19 -Shepazu 15:49:30 MC: I want some time to think about this 15:50:11 AB: how much time do you need Marcos? 15:50:15 MC: one week 15:50:21 MP: I will send an email by Monday 15:50:39 AB: what about req 6? 15:50:54 -Mike 15:50:56 suggest profile with uri for signature spec 15:51:10 s/profile/profile property/ 15:51:12 MC: I'm OK with that proposal 15:52:57 FH: req #8 provides a motivation about the Expires property 15:53:08 MP: agree Expires property makes sense 15:53:35 billyjackass has joined #wam 15:53:37 issue of granularity of time stamps? 15:53:43 ... a concern I had is the text implies a short expiration period 15:53:54 ... but I agree with the overall intent 15:54:05 Zakim, code? 15:54:05 the conference code is 9231 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), billyjackass 15:54:41 +??P41 15:54:54 Present+ Mike 15:55:06 Zakim, P41 is me 15:55:06 sorry, billyjackass, I do not recognize a party named 'P41' 15:55:18 Zakim, P41 is me 15:55:18 sorry, billyjackass, I do not recognize a party named 'P41' 15:55:25 FH: I think we need to continue discussion on req #8 15:55:26 Zakim, ??P41 is me 15:55:26 +billyjackass; got it 15:55:36 ... could use something from Schema 15:56:02 suggest we use xsd:dateTime but need clarification of processing rules around comparisons 15:56:31 hello? 15:56:42 AB: any last comments about FH's original email? 15:56:51 [None] 15:57:13 Topic: Section 5. definitions 15:57:28 AB: who can help? 15:57:28 +Josh_Soref 15:57:45 FH: I can help but it isn't a high priority 15:58:01 Topic: Section 9 and X509 15:58:11 FH: do we really need to define something here? 15:58:44 AB: agree we should reference existing work if possible 15:59:40 MP: concern about interoperability related to optional features 15:59:45 MP: concerened about addressing some interop issues we've had in the mobile industry 15:59:49 MP: both for OCSP and CRLs 15:59:59 ... we could ref some existing specs 16:00:12 ... not sure they meet all of our reqs 16:00:17 -billyjackass 16:00:38 ... Agree there is an open question on how much X509 processing we need to specify. 16:01:22 q+ 16:01:38 q- 16:01:40 q+ 16:02:08 AB: Mark, you will provide input on OCSP and CRLs 16:02:14 http://lists.w3.org/Archives/Public/public-webapps/2009JanMar/0038.html 16:02:20 http://lists.w3.org/Archives/Public/public-webapps/2009JanMar/0039.html 16:02:36 AB: and contributors for 6.1 and 8? 16:02:50 FH: I sent a proposal for 6.1 to the list earlier today 16:03:22 FH: I made a proposal for section 8 too 16:03:36 ack 16:04:06 q- 16:04:09 JS: there is a protocol for helping sort out a chain if something is missing 16:04:16 ... Gecko has some new suport for this 16:05:45 Topic: P&C Last Call WD 16:06:00 AB: which WG do we want to request feedback? 16:06:16 MC: I18N WG 16:06:20 ... WAI P&F 16:06:37 ... MWBP 16:06:44 i think this is probably a related url, http://ieeexplore.ieee.org/Xplore/login.jsp?url=/iel5/4221005/4224052/04224150.pdf?arnumber=4224150 16:07:06 FH: XML Sec 16:08:07 .... the P&C should just point at the Widgets DigSig spec 16:08:39 MP: I think the P&C spec needs to address how to address handling more than one sig 16:08:57 should point to Widgets DigSIg spec since it handles properties etc 16:09:12 Topic: AOB 16:09:17 AB: next call is Jan 15 16:09:25 ... FH regrets already sent 16:09:40 AB: quick poll on Paris f2f attendance 16:09:47 AB: any definites? 16:09:55 MP: yes 16:09:59 anne has left #wam 16:10:02 AB: yes 16:10:10 CV: most likely 16:10:26 MC: I don't know 16:10:37 doubtful as of now 16:11:16 AB: meeting adjourned 16:11:21 -Mark 16:11:24 -Josh_Soref 16:11:25 -Marcos 16:11:25 - +358.503.85aaaa 16:11:26 -fjh 16:11:30 -Claudio 16:11:39 RRSAgent, ent, make logs public 16:11:39 I'm logging. I don't understand 'ent, make logs public', ArtB. Try /msg RRSAgent help 16:11:46 RRSAgent, make minutes 16:11:46 I have made the request to generate http://www.w3.org/2009/01/08-wam-minutes.html ArtB 16:11:48 -Art_Barstow 16:11:49 IA_WebApps(Widgets)10:00AM has ended 16:11:51 Attendees were +358.503.85aaaa, +44.771.751.aabb, Art_Barstow, Mark, Claudio, fjh, Marcos, Shepazu, Mike, billyjackass, Josh_Soref 16:12:33 RRSAgent, make logs public 16:13:03 Present+ Josh 16:13:15 RRSAgent, make logs public 16:13:15 JereK has left #wam 16:15:46 RRSAgent, make minutes 16:15:46 I have made the request to generate http://www.w3.org/2009/01/08-wam-minutes.html ArtB 16:16:19 zakim, bye 16:16:19 Zakim has left #wam 16:16:46 rrsagent, bye 16:16:46 I see no action items