Below is the draft agenda for the November 20 Widgets Voice
Conference (VC).
Two notes on this agenda:
1. NOTE the TIME CHANGE!
2. It is highly unlikely we will cover the Widgets DigSig spec or the
API and Events spec. Please review the related ACTIONs and respond
accordingly.
Inputs and discussion on the agenda topics before the meeting is
encouraged.
Logistics:
Time: 24:00 Tokyo; 17:00 Helsinki; 16:00 Paris; 15:00 London;
10:00 Boston; 07:00 Seattle
Duration = 60 minutes
Zakim Bridge +1.617.761.6200, conference 9231 ("WAF1")
IRC channel = #wam; irc.w3.org:6665
Confidentiality of minutes = Public
Agenda:
1. Review and tweak agenda
2. Announcements
a. December VC schedule: December 18 is the next and last VC of the year
3. P&C spec: NOTE - BEFORE the VC, please review Section 1-7 and
submit any comments to public-webapps:
<http://dev.w3.org/2006/waf/widgets/>
a. File extension to Media-type - see discussion thread "Content-type
sniffing and file extension to MIME mapping":
<http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/
0340.html>
b. Action-231: "Work with Marcos to submit a proposal to address the
feature fallback problem "; Marcos + Arve
<http://www.w3.org/2008/webapps/track/actions/231>
c. Agree on plan to publish LCWD. Tentative plan: Dec 10 - Marcos
completes last edits; Dec 11-17 - CfC period; Dec 18 - submit LCWD
publication request with a comment period ending 2 February 2009.
4. Widget testing - MWTS WG proposed a testing directory for Widgets.
If you object to this proposal, please do so before this VC begins,
otherwise, the proposed directory will be used:
<http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/
0309.html>
5. DigSig spec:
<http://dev.w3.org/2006/waf/widgets-digsig/>
a. Questions for XML Security WG:
<http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/
0242.html>
b. Issue 19 "Widgets digital Signatures spec does not meet required
use cases and requirements": what needs to be done to address and
close this issue?
<http://www.w3.org/2008/webapps/track/issues/19>
c. Action-163 "Determine Opera's position regarding signing All
versus Partial signing [with Arve]"; Arve + Charles
<http://www.w3.org/2008/webapps/track/actions/163>
d. Action-208 "Contribute security considerations for decompression
and signature validation"; Thomas
<http://www.w3.org/2008/webapps/track/actions/208>
e. Action-224 "Work with Marcos to flesh out the details of the
processing model for multiple signatures"; Mark
<http://www.w3.org/2008/webapps/track/actions/224>
f. Action-273 "Do you object to the removal of the
WidgetSignatureInfo element?"; Thomas
<http://www.w3.org/2008/webapps/track/actions/273>
g. Action-275 "What is our lifecycle, revocation model?"; Mark
<http://www.w3.org/2008/webapps/track/actions/275>
h. Issues in Section 7 "Procedure for Verifying a Digital Signature
Document":
<http://dev.w3.org/2006/waf/widgets-digsig/#procedure>
i. Plan for next publication
6. APIs and Events spec:
<http://dev.w3.org/2006/waf/widgets-api/>
a. Red Block Issues in Section 2: add some context so reader can
understand the issue;
b. Action-233 "Research the Widget object's preference attribute to
make sure it uses the correct type"; Arve
<http://www.w3.org/2008/webapps/track/actions/233>
c. Action-232 "Check the API spec for compliance with the Web IDL
spec"; Arve
<http://www.w3.org/2008/webapps/track/actions/232>
d. Plan for FPWD
7. AOB
a. Next f2f meeting -> tentative proposal is Feb 24-26 in Paris with
an alternate of Feb 10-12 in Paris
