Warning:
This wiki has been archived and is now read-only.
WidgetsMandelieuAgenda
NOTE: This document is no longer maintained because the Web Applications Working Group was closed in October 2015 and its deliverables transferred to the Web Platform Working Group.
The Web Applications WG will have a f2f meeting in Mandelieu France 20-21 October 2008. The group will meet in two separate rooms: one group will focus on the group's Widgets specs and the other group will focus on the group's other specs, mainly API specs.
This is the agenda page for the Widgets part of the Web Applications WG's f2f meeting. The agenda for WG's APIs meeting on these days is not included on this page but is available here.
Pre-registration for this meeting is Mandatory and must be completed by October 12 at the latest. See the Registration Page for more information.
See the meeting registration list for the list of people registered for both meetings.
Contents
Meeting Logistics
- Voice Conference Bridge = +1.617.761.6200, conference 943438 ("WIDGET"); ONLY IF/WHEN NEEDED
- IRC channel = #wam; irc.w3.org:6665
- Dates = 20-21 October 2008
- Time = 09:00 - 17:00
- Location = Mandelieu France
- Meeting Room = Iles A
- Scribe: EVERY WG member will scribe some part of the meeting
Mandelieu Information
Please see the TPAC Home Page for information about Mandelieu.
Documents
- Widgets 1.0: Packaging and Configuration
- Widgets 1.0: Digital Signature
- Widgets 1.0: APIs and Events
- Widgets 1.0: Updates
Agenda
The primary objective of the meeting is to advance the Widgets 1.0 specification suite by discussing and resolving open issues.
The overall scheduling of the topics is loose, in that only a few of the agenda items have pre-defined time slots to accommodate meeting with other groups.
We will attempt to close all open issues by the end of the meeting. Therefore, please be prepared to comment on: a) all of the Open Issues explicitly identified in the specs and b) the open Widgets issues in the Issues Database. Closing issues before the meeting is preferred.
If you have any related WebApps Open Actions, please close them before the meeting.
Topics in Priority Order
- Packaging and Configuration spec
- Open Issues
- Issue 46 - Need to define a for i18n purposes in configuration document
- Issue 16 - Do widgets need their own URI scheme? - see Monday 14:00-15:00, joint discussion with TAG members
- Red Blocks Issues in the spec
- The use of URI and IRI is not consistent
- Section 5.4 Need to check this document from a validator's point of view
- Section 5.5 Need to register MIME type - Action #199
- Section 6.14 - Version string needs to be written
- Section 7. - Need to add text about encoding (cp437 = AB, UTF= TY)
- Section 8.2 - Should add something here about running out of space
- Section 8.2, Step #10 - How to handle SVG Icon Formats
- Section 8.2, Step #11 - Is additional security model needed here?
- Section 8.2, Step #11 - Need to describe what happens if the widget already exists
- Section 9.1 Locating thumbnails needs to be written
- Last Call: determine date and plan for Last Call publication
- Testing (see Tuesday afternoon)
- Implementations and Candidate
- Open Issues
- Digital Signature spec
- Open Issues
- Issue 22 - Is sha1 as a DigestMethod strong enough for Widgets digital signatures? - to be discussed with XML Security WG on Tuesday
- Issue 19 - Widgets digital Signatures spec does not meet required use cases and requirements
- Red Block Issues in the spec
- ...
- Plans for next publication
- Open Issues
- Updates spec
- Red Block Issues in the spec
- Need to change name of <update> element
- Plans for next publication
- API and Events spec
- Red Block Issues in the spec
- Plans for FPWD
- Requirements LC #2
- Discuss any Hot Topics resulting from comments
- Discuss next step for this doc e.g. remain in LC, promote to Candidate
Monday, October 20
- Introductions, logistics
- Member confidentiality
- Agenda tweaking
- Priority topics
- Joint meetings
- Begin working on topics
- 14:00-15:00 - joint meeting with TAG members to discuss widget URI Scheme
- Web Apps ISSUE #16 - Do widgets need their own URI scheme?
- TAG ISSUE #61 - URI Based Access to Packaged Items
- Use Case and Rationale
- Requirement #6 - Addressing Scheme
- Other schemes considered
- http: - see August 26 discussion
- file: - see proposal from Mark Baker and the ensuing discussion
- cid: - see comments from Josh Soref and response from Roy Fielding
Tuesday, October 21
- Continue working on topic list ...
- 11:00-12:00 - joint meeting with the XML Security WG; will meet in Iles C room
- September 30 Questions
- 1. What (if any) issues do you foresee if we require support for SHA-256 (rather than SHA-1)?
- 2. What algorithm should we use?
- 3. What identifier should we use for the algorithm?
- How to find multiple signatures in a manifest?
- Red Block Issues in the latest Widgets 1.0: Digital Signature Editor's Draft
- September 30 Questions
- Continue working on topic list ...
- 15:30-16:30 (approx) - Widget testing with Carmelo (and possibly members of the Mobile Web Test WG)
- What methodology do we use?
- What are some good projects to follow/model?
- What about an automated harness?
- What naming conventions to we use?
- Any other advice, guidance?
- Next steps ...
- Continue working on topic list ...
- AOB
- Publication plan for rest of 2H08
- F2F meetings in 2009?
- Benoit's Widgets presentation
- OpenAjax Alliance's Style Guide