The 2014 Wednesday schedule is different than most years. See below.
See also the page for managing ad-hoc meetings midday on Monday, Tuesday, Thursday, and Friday.
Questions? See the FAQ and IRC at W3C meetings guide. For past, see TPAC 2013.
29 October Schedule
- 08:30-08:35: Welcome — Jeff Jaffe
- 08:35-09:15: Breakout preparation (Ian Jacobs). See Session Ideas.
- 09:15-10:15: Breakouts (10)
- 10:15-10:45: Break
- 10:45-11:45: Breakouts (10)
- 11:45-13:15: Lunch (in ballroom)
- 13:15-14:15: Breakouts (8)
- 14:30-15:00: Seating begins for Symposium
- 15:00-18:00: W3C20 Symposium
- 18:00-19:00: Break / demos
- 19:00-19:30: Seating for dinner
- 19:30-22:00: Dinner
Please review What is good practice for organizing a session?
|| CA Salon 7+8 (75)
|| CA Salon 9 (44)
|| Seattle (68)
|| Portland (68)
|| Santa Barbara (68)
|| Newport Beach (68)
|| Sequoia (41)
|| Sierra (41)
|| Ponderosa (41)
|| Monterey (41)
|| Near Starbucks
|| Telcos @ W3C, Dominique Hazael-Massieux Minutes
|| Application Foundations, Jeff Jaffe
|| Developer engagement in standards, Doug Schepers
|| Trust and Permissions in the Open Web Platform, Dave Raggett Minutes
|| Schema.org and Social WG, Harry Halpin Minutes
|| Web Payments - What you need to know, Manu Sporny, Slides
|| Legal Restrictions, DRM, and the W3C, Danny O'Brien
|| W3C Process 2015 - What is new; What should be new, Steve Zilles
IRC: #w3process Minutes
| Robot Interaction and the Web, Debbie Dahl Minutes
|| TR Publications, Denis Ah-Kang, Robin Berjon Minutes
|| Technical planning for rich text editing; Ben Peters Notes
|| What do you want from your Mobile Carrier?, Natasha Rooney Notes
|| After (HTML) 5 - Web Standards Ecosystem in 2024, Art Barstow.
| Responses to Pervasive Monitoring and Secure Origins, Nick Doty.
IRC: #permon. notes
| startSession("WoT devices"), Tatsuya Igarashi, Saki Homma Minutes
|| Web API for Health Care Sensors, Frederick Hirsch Minutes
|| Credentials on the Web - A 10,000ft Overview, Manu Sporny Slides
|| Music Notation Markup, Joe Berkovitz
|| What is Wide Review and How do we achieve it, Steve Zilles
| Latest news from the Web Platform Testing front, Philippe Le Hégaret
|| Improving Communications to Membership Through Data, Ted Guild IRC notes
|| Beyond Vendor Prefixes, Jacob Rossi
|| Room unavailable
|| Room unavailable
|| A PING for Web Privacy, Christine Runnegar, Tara Whalen and The Web: Privacy AND openness Hadley Beeman, Dan Appelquist Minutes
|| Next Steps for the Web of Things, Dave Raggett
| Crowd sourcing use cases: spec development at light-speed!, Natasha Rooney
|| Bitcoin (cryptocurrency) Payment Protocol, Glen Wiley
|| 5 star Civic Tech / How to promote the 5 star Open Data as the Semantic Web, Taisuke Fukuno
|| An application-oriented API for DANE and DNS, Allison Mankin, Melinda Shore Minutes
|| CSS Extensions to support a round display, Hyojin Song, Dong-Young Lee
| Exploring ideas for improving parallelism in web applications, Travis Leithead Notes
Teleconference Dialout Names
For those groups who have requested teleconference facilities and have speakerphones in your meeting rooms, please use Zakim dialout to call the room as this is far less expensive than calling out from the hotel.
The irc syntax is (e.g. to call to the speakerphone in Salon 1):
zakim, call Salon1
The names to use when requesting dialout from Zakim are:
- SuiteA / ProspectorA
- SuiteB / ProspectorA
- Suite1234 One of the remote callers must ask the hotel operator to connect to Suite 1242
- Suite1242 One of the remote callers must ask the hotel operator to connect to Suite 1242
- Suite1243 One of the remote callers must ask the hotel operator to connect to Suite 1243
There are no spaces in any of the names.