View source for TPAC/2020/SessionIdeas

You are invited to propose [https://www.w3.org/2020/10/TPAC/ TPAC 2020] '''TPAC Breakout week (October 26-30)''' sessions in advance of the meeting. 
See the [[TPAC/2020/FAQ | TPAC 2020 FAQ]] for more information. Please contact dom@w3.org for any question regarding the organization of TPAC breakouts.

<div style="float:right;clear:right">__TOC__</div>

== How to use this page ==

Please use this page to:

* Propose sessions you wish to lead
* '''Please place new proposals at the bottom of this document'''

== How to propose a session ==

Please provide:
<ul class="show_items">
* session name (as a === subhead === )
* session proposer (yourself, if so sign using 4 tildes; optional: name a desired session leader) and an email address
* one sentence session summary
* type of session: (e.g.: open discussion, talk, panel, tutorial, demo, etc.)
* goals of session
* additional speakers/panelists (to help reduce conflicts when one person is needed in more than one place)
* opt-in to be a [[#Public_Breakout]] open to participation from the public at large
* a shortname that can be used to associate an IRC or Slack channel to your breakout
* by default, we expect breakout to happen at 2pm UTC for '''one hour''' during the week of October 26 to allow participation from as many timezones as possible; if your breakout cannot happen at 2pm UTC, or if your breakout can be scheduled to happen across multiple repeated instances at different time (e.g. for a tutorial, demos), please indicate it
** single instance TPAC breakout sessions proposed outside of the 2pm slot are subject to validation by the organizing committee
* if your breakout needs to happen on a subset of the 5 days of the week, please also indicate it
</ul>

== Public Breakout ==

In addition to the usual breakout discussions organized for the traditional TPAC community (IG/WG participants, W3C member representatives), we are trying something new this year.  We plan to open a set of breakouts to the broader public, in an effort to bring more diverse voices into the W3C community. We feel this is necessary to ensure the fullest range of users and perspectives is represented and encoded in our web standards.  

Breakout proposers are invited to opt-in to make their breakout open to the public in order to invite a wider and more diverse set. While there aren't clearly defined limits to what topics would benefit from this, we encourage Public Breakouts to focus on use cases or ergonomics of a technology, and to provide upfront onboarding and context for any breakouts that include deep technical dive.

The W3C devrel team and their partners will work with Public Breakout proposers to ensure their breakouts are as welcoming and kind as possible when joining their first W3C or Web standardization discussion. For anyone who opts in to propose a Public Breakout , we will be offering dedicated training sessions the week before TPAC breakouts on the topic of facilitating accessible  discussions.

(Many thanks to Boaz Sender, Sheila Moussavi, Jory Burson, Laura Lee McCarthy who have been working with Marie-Claire Forgue and Dominique Hazael-Massieux in setting this up)

== Proposed sessions ==

=== EXAMPLE session with session name ===
* Proposer: <nowiki>~~~~</nowiki> (Instruction: remove <nowiki><nowiki> and </nowiki></nowiki> around the tildas. Explanation: The 4 tildas will sign YOUR name and include a timestamp of your proposal.)
* Email address of proposer: 
* Summary (one-sentence or so): 
* Type of session (e.g.: open discussion, talk, panel, etc.): 
* Goals:
* shortname (used for minting an IRC channel for the breakout)
* [optional] Additional speakers/panelists:
* [optional] Apply to be a [[#Public_Breakout]] (breakouts open to the world at large, not just the W3C community)
* [optional] Timeslot: 2pm UTC ("the golden hour" - 7am US West Coast, 11pm Japan) - if you can't run your breakout proposal at 2pm UTC, we ask that you consider carefully alternatives in the 12pm-5pm UTC, knowing that a number of people won't be able to make it; alternatively, if your breakout can happen as a repeated instance (e.g. for a tutorial or a demo), please indicate so and we will schedule these instances away from the golden hour
* [optional] constraints on days in which the breakout can run: Monday, Tuesday, Wednesday, Thursday, Friday

=== IAB Europe's Transparency and Control Framework ===
* Proposer: [[User:Benhum|Ben Humphry]] 
* Email address of proposer: humphry@iabeurope.eu
* Summary (one-sentence or so): Internet Advertising Bureau (IAB) Europe to brief W3C members on Transparency and Consent Framework (TCF), developed over many years to capture people’s consent choices and inform multiple parties. [https://github.com/w3c/web-advertising/issues/86/ Web-Advertising Github Issue]
* Type of session: talk and open discussion
* Goals: Explain this existing framework which provides consumers with a transparent and fair mechanism for control of their privacy preferences.
* shortname: TCF
* Additional speakers/panelists: TBD - Experts from IAB Europe
* Apply to be a [[#Public_Breakout]]: yes
* Timeslot: Any of 12pm–5pm UTC.

=== MDN Developer Need Assessments: results and next steps ===
* Proposer: [[User:Dom|Dominique Hazaël-Massieux]] 
* Email address of proposer:  dom@w3.org
* Summary (one-sentence or so): Review outcome of the [https://insights.developer.mozilla.org/ MDN DNA survey 2019], incl recently released [https://mdn-web-dna.s3-us-west-2.amazonaws.com/MDN-Browser-Compatibility-Report-2020.pdf MDN Browser Compat Report] and expectations on MDN DNA Survey 2020
* Type of session: talk and open discussion
* Goals: Inform how large-scale developer input has impacted and should impact standardization priorities
* shortname: mdn-dna
* Additional speakers/panelists: Philip Jägenstedt, Robert Nyman, Chris Mills, Boaz Sender
* Apply to be a [[#Public_Breakout]]: yes

=== Learning from Mini Apps ===
* Proposer: [[User:Tsteiner|Thomas Steiner]] 
* Email address of proposer: tomac@google.com
* Summary: In this breakout session, I will first explain what mini apps are and how to build them, and then move on to an open discussion focused on what Web developers can learn from mini apps and their developer experience. 
* Type of session: Talk followed by discussion.
* Goals: Having a better understanding of mini apps.
* Shortname: miniappslearnings
* [optional] Additional speakers/panelists: You?
* [optional] Apply to be a [[#Public_Breakout]]: Yes.
* [optional] Timeslot: Any of 12pm–5pm UTC.
* [optional] Constraints on days in which the breakout can run: No constraints.

=== Web Packaging ===
* Proposer: [[User:Jyasskin|Jeffrey Yasskin]] 
* Email address of proposer: jyasskin@google.com
* Summary (one-sentence or so): Discuss Web Packaging issues that [https://github.com/WICG/webpackage/issues?q=is%3Aopen+is%3Aissue+label%3Adiscuss need discussion].
* Type of session (e.g.: open discussion, talk, panel, etc.): Open Discussion
* Goals: Resolve or make progress on some open issues with the web packaging design
* Shortname: web-packaging
* [optional] Additional speakers/panelists:
* [optional] Apply to be a [[#Public_Breakout]]: yes
* [optional] Timeslot: 2pm UTC
* [optional] constraints on days in which the breakout can run: No constraints.

=== Memory copies & zero-copy operations on the Web ===
* Proposer: [[User:Fd|François Daoust]] 
* Email address of proposer: fd@w3.org
* Summary (one-sentence or so): In scenarios such as real-time processing of media frames with ML algorithms, memory copies made along the processing pipeline may account for a non negligible part of the overall performance budget of the said processing. See [https://github.com/w3c/machine-learning-workshop/issues/93 Memory copies discussion in the Web and Machine Learning workshop] for context. Could the Web do better?
* Type of session: Open discussion
* Goals: Explore needs to copy memory in various Web technologies (JS, WebAssembly, WebGPU, Machine Learning, WebRTC, Media) and identify possible architectural updates to the Web Platform that could help reduce unneeded memory copies.
* shortname: zerocopy
* Timeslot: 2pm UTC

=== Video Metadata For Moving Objects &amp; Sensors On The Web (WebVMT) ===
* Proposer: [[User:Rjksmith|Rob Smith]] 
* Email address of proposer: rob.smith@awayteam.co.uk
* Summary: Emerging markets in 'mobile video devices' such as dashcams, drones, body-worn video and smartphones are increasing consumer demand for geotagged video on the web and especially with access to moving objects, e.g. distance &amp; speed for vehicles, and sensor data, e.g. heart rate for fitness users. More details at [https://github.com/w3c/sdw/issues/1194 w3c/sdw #1194]
* Type of session: Short talk followed by discussion
* Goals: Identify properties of moving objects &amp; sensors required in a web API to access timed video metadata exported for the web, i.e. WebVMT, from mobile video devices.
* Shortname video-location
* Apply to be a [[#Public_Breakout]]
* Timeslot: 2pm UTC

=== Improve definition of parties and trust relationships across W3C ===
* Proposer: [[User:Jwrosewell|James Rosewell]] 
* Email address of proposer: james@51degrees.com
* Summary (one-sentence or so): First and third party are poorly defined and lack the granularity to resolve many of the problems W3C are working on. Debate definitions of parties considering their relationship with one another, trust, choice, scale and varying conditions in relation to people. See IWA BG issue for commentary and pre session discussion. [https://github.com/w3c/web-advertising/issues/87]
* Type of session: Presentations followed by discussion
* Goals: Agreement on approach to define parties consistently and appropriately across W3C including TAG and PING documents.
* shortname: party-time
* Speakers/panelists: TBD – would like to add advocates for different view points.
* Apply to be a [[#Public_Breakout]] (as a minimum should include Improving Web Advertising Business Group members)
* Timeslot: 2pm to 4pm UTC
* Monday, Tuesday, Wednesday

=== Web Components ===
* Proposer: [[User:rniwa|Ryosuke Niwa]] 
* Email address of proposer: rniwa at apple
* Summary (one-sentence or so): Discussion of various topics related to web components
* Type of session: Multi-topic discussion; Agenda and logistics is tracked at https://github.com/w3c/webcomponents/issues/877
* Goals: Reaching consensus on various topics
* shortname: components
* Apply to be a #Public_Breakout: yes
* Timeslot: 5pm UTC

=== Parts and Template Instantiation ===
* Proposer: [[User:rniwa|Ryosuke Niwa]] 
* Email address of proposer: rniwa at apple
* Summary (one-sentence or so): Discussion of APIs to help instantiate templates.
* Type of session: A presentation followed by discussion
* Goals: Make progress on the proposal and reach some consensus on minimal viable product.
* shortname: components
* Apply to be a #Public_Breakout: yes
* Timeslot: 5pm UTC

=== Declarative Shadow DOM ===
* Proposer: [[User:mfreed|Mason Freed]] 
* Email address of proposer: masonfreed@chromium.org
* Summary (one-sentence or so): Discussion of the declarative Shadow DOM [https://github.com/mfreed7/declarative-shadow-dom/blob/master/README.md proposal]/[https://github.com/whatwg/dom/issues/831 issue]
* Type of session: A presentation followed by discussion.
* Goals: Reach some consensus on the proposal and spec.
* shortname: components
* Apply to be a #Public_Breakout: yes
* Timeslot: 5pm UTC

=== Making math a first class citizen on the Web ===
* Proposer: [[User:Nsoiffer2|Neil Soiffer]] 
* Email address of proposer: neil.soiffer@gmail.com
* Summary: The MathML Refresh CG is forming a WG and we would like to discuss our [https://mathml-refresh.github.io/charter-drafts/math-2020.html proposed charter] with interested parties. The group has coordinated with the CSS WG, WhatWG, and TAG over some issues and there are many remaining open questions involving Shadow DOM, Houdini, Links, the accessibility tree, search and other parts of the Web platform.
* Type of session: open discussion
* Goals: Provoke discussions on some of the subtle issues of including math in the Web platform and get guidance on resolving them.
* shortname: math
* Additional speakers/panelists: Brian Karkell (bkardell@gmail.com)
* Apply to be a [[#Public_Breakout]]: yes
* Timeslot: 3:00pm UTC

=== All your spec are belong to us - irrigating dev resources from specs ===
* Proposer: [[User:Dom|Dominique Hazaël-Massieux]], [[User:Fd|François Daoust]]
* Email address of proposer: dom@w3.org, fd@w3.org
* Summary: Machines read specs too. This breakout session will review existing and possible tools and projects that make use of content automatically extracted from specs.
* Type of session: Talk and open discussion
* Goals: Raise awareness and learn about existing internal and external projects (such as webref, Bikeshed, Respec, MDN, Visual Studio, Web Platform Tests) that depend on content extracted from specs, to irrigate CSS/IDL tests and interface headers in browser codebases, validate cross-references, enrich IDE tools, identify dependencies, detect anomalies, and otherwise improve the quality of the specifications. Clarify what happens when e.g. IDL content is no longer valid or machine-readable. Discuss usage scenarios that additional formalism for writing specs could perhaps enable.
* shortname: specmining
* Apply to be a [[#Public_Breakout]]

=== Maps for HTML Community Group ===
* Proposer: [[User:Prushfor|Peter Rushforth]] 
* Email address of proposer: peter.rushforth@canada.ca
* Summary: The Maps for HTML community recently concluded a successful [https://www.w3.org/2020/maps/agenda#day-1 workshop] about standardizing maps for the Web platform, and we would like to invite those interested to take part in a follow up meeting.
* Type of session (e.g.: open discussion, talk, panel, etc.): Summary presentation of workshop, followed by open discussion.
* Goals: Provide and receive information on specific topics
* shortname: maps4html (used for minting an IRC channel for the breakout)
* Apply to be a [[#Public_Breakout]]: yes
* Timeslot: 2pm UTC

=== EPUB 3 History and Future ===
* Proposer: [[User:Tzviya|Tzviya Siegman]] Tzviya Siegman and Wendy Reid 
* Email address of proposer: tsiegman@wiley.com
* Summary (one-sentence or so): Learn about the 20+ year history of EPUB, how it came to the W3C, and what the new EPUB 3 WG will accomplish.  
* Type of session: talk with time for questions 
* Goals: Provide info about EPUB and Publishing Activity
* shortname EPUB3
* [optional] Additional speakers/panelists: Wendy Reid and (possibly) Shinya Takami
* [optional] Apply to be a [[#Public_Breakout]]: yes

=== Delegated Ink Trails ===
* Proposer: [[User:Mabian|Mario Bianucci]] 
* Email address of proposer: mabian@microsoft.com
* Summary: Delegated Ink Trail Presentation Paradigm: Prototype status and learnings from web developers feedback.
* Type of session: open discussion
* Goals: Discuss the proposed paradigm, and reach consensus on next steps.
* shortname: delegated_ink_trail
* Apply to be a [[#Public_Breakout]]: yes.
* Timeslot: 2pm UTC
* constraints on days in which the breakout can run: Tuesday, Wednesday, Thursday, Friday

=== W3C New York Metro Chapter Meetup ===
* Proposer: Rachel Yager 
* Email address of proposer: rachel@fortunetimesgroup.com / ryager@w3.org
* Summary (one-sentence or so): Inviting Web Community to Join the W3C New York Metro Chapter. W3C Members and Non-Members are Welcome! The Chapter provides a point of presence of W3C within the Metropolitan New York City to build and enhance the Web Community, to assist W3C Members, and to invite W3C Members participation in WebInnovationX Center for World Wide Web research and education initiatives.
* Type of session: Seminar Talks and Presentations
* Goals:  Provide information on W3C NY Metro Chapter Member Benefits, Activities, Events, Strategic Partnership, Leadership, and Technology Innovation Initiatives.
* shortname: WebInnovationX
* Additional speakers/panelists: TBD
* Apply to be a [[#Public_Breakout]]: yes
* Timeslot: 4pm UTC
* constraints on days in which the breakout can run: Wednesday

=== Media Publishers of the Web, Unite! ===
* Proposer: [[User:Rberjon|Robin Berjon]] 
* Email address of proposer: robin.berjon@nytimes.com
* Summary (one-sentence or so): Media publishers have long been absent or under-represented in Web standards, but there is a growing sense that we should speak up in the making of tech and a growing set of members. This session is to share fears, hopes, tips, and more.
* Type of session (e.g.: open discussion, talk, panel, etc.): 
* Goals: Get media publishers to meet and help each other out navigate the strange but beautiful world of standards.
* shortname (used for minting an IRC channel for the breakout): media-pubs
* Apply to be a [[#Public_Breakout]]: yeah
* Timeslot: 2pm UTC

=== Revenue Models for the Web ===
* Proposer: [[User:Ahopebai|Adrian Hope-Bailie]] 
* Email address of proposer: Ali Spivak (ali@coil.com) and Adrian Hope-Bailie (adrian@coil.com)
* Summary (one-sentence or so): There has been a lot of discussion and [[https://webmonetization.org experimentation]] looking at alternatives to advertising for monetization on the Web. In this panel we aim to explore these alternative models, debate whether or not advertising still has a role to play, and discuss the potential for standards to enable a broader set of business models.
* Type of session: Panel followed by open discussion
* Goals: Discuss options for generating revenue on the Web and how standards can enable more options.
* shortname (used for minting an IRC channel for the breakout): monetization
* Additional speakers/panelists: Panel currently being confirmed. Please email the proposers if you wish to join the panel.
* Apply to be a [[#Public_Breakout]]: YES
* Timeslot: 2pm UTC ("the golden hour" - 7am US West Coast, 11pm Japan)

=== Online Harms – a European and UK perspective ===
* Proposer: [[User:Jwrosewell|James Rosewell]] 
* Email address of proposer: james@51degrees.com
* Summary (one-sentence or so): Presentation to cover a) the current state of online harm legislation in the UK and Europe including the Audio-Visual Media Services Directive (AVMS-D) on 1st November 2020; * b) child safety and the impact DNS over HTTPs is having; and c) the role of standards, laws and industry adoption in solutions.
* Type of session: presentation (20 mins) followed by Q&A
* Goals: Inform attendees about a full range of on line harms, the risk of unintended consequences when addressing a narrow set in isolation, and the role that a technical standards body can play in improving the web for all.
* Additional speakers/panelists: Alistair Kelman (ali.kelman@safecast.co.uk)
* Apply to be a #Public_Breakout: yes
* Timeslot: Any of 12pm–5pm UTC.
* Monday, Tuesday, Wednesday

=== Web Monetization and Grant for the Web ===
* Proposer: [[User:Aspivak|Ali Spivak]]
* Email address of proposer: ali@coil.com,  info@grantfortheweb.org
* Summary (one-sentence or so): A deep dive into Grant for the Web's advocacy of the (proposed) Web Monetization standard.
* Type of session: Conversation with opportunity for audience questions.
* Goals: Share Grant for the Web's mission and how early grantees are contributing to the growing Web Monetization ecosystem through use of the (proposed) Web Monetization standard and the Interledger Protocol.
* shortname (used for minting an IRC channel for the breakout) Grant-for-the-Web
* Additional speakers/panelists: Chris Lawrence (Grant for the Web), Ali Spivak (Coil), more participants to be announced.
* Apply to be a #Public_Breakout: yes
* Timeslot: any that are not in conflict with "Revenue Models for the Web" breakout (see above)

=== The Waning Web Platform Engine Diversity ===
* Proposer: [[User:Chriswilson|Chris Wilson]]
* Email address of proposer: cwilso@google.com
* Summary (one-sentence or so): How should the W3C Process adapt to a world with fewer engine implementers, but more browsers and stakeholders? The open source browser projects are shipping tested, interoperable implementations of new specs well before they reach Recommendation.  Horizontal review must happen at the incubation stage or shortly thereafter to have any impact on what browser teams ship. What if anything can the Process do to encourage early engagement by user representatives and horizontal review communities rather than using the PR stage as the checkpoint to ensure this happens? How do we define what web stakeholders should treat as the "real" web standards?
* Type of session (e.g.: open discussion, talk, panel, etc.): open discussion
* Goals: Gather ideas for the future of the W3C Process and incubation process.
* shortname (used for minting an IRC channel for the breakout): engine-scion
* Apply to be a [[#Public_Breakout]]: yes
* Timeslot: 2pm UTC - 6pm UTC

=== What would it mean for W3C to REALLY prioritize end users? === 
* Proposer: [[User:Mchampio2|Michael Champion]] ([[User talk:Mchampio2|talk]]) 01:04, 14 October 2020 (UTC) 
* Email address of proposer: michaelc.champion@gmail.com
* Summary : Prioritizing the interests of end users has been a hot topic lately [https://www.rfc-editor.org/rfc/rfc8890.html in IETF], [https://www.w3.org/2001/tag/doc/ethical-web-principles/ in W3C] ,  and [https://www.eff.org/deeplinks/2020/10/we-fight-users from EFF]. It's  not clear what it would CONCRETELY mean for W3C to prioritize the needs of end-users over those of the platform implementers, website developers, "horizontal" specialists, and researchers who make up most of W3C's membership. This breakout will explore the problem of insufficient end-user input into web standards discussions, and seek consensus on ways to address it.  See https://github.com/WebStdFuture/Users1st for more context and hopefully pre-meeting and post-meeting discussion.  
* Type of session : Open Discussion of https://www.rfc-editor.org/rfc/rfc8890.html and what adopting something similar might mean for W3C
* Goals: Rough consensus whether this is something W3C should do, and what next steps might be
* shortname (used for minting an IRC channel for the breakout): users1st
* [optional] Additional speakers/panelists: Use https://github.com/WebStdFuture/Users1st/issues to request time take a position and request time to present it.
* [optional] Timeslot: 2pm UTC

=== W3C Group calendaring === 
* Proposer: [[User:Jean-gui|Jean-Guilhem Rouel]] 
* Email address of proposer: jean-gui@w3.org
* Summary : Providing groups with a good solution to manage their meetings has been requested for a long time. This breakout will consist in a demo of what W3C is currently working on and a discussion to gather initial feedback from interested parties.
* Type of session : Demo/Open Discussion
* Goals: Present and gather feedback on the current state of the project
* shortname (used for minting an IRC channel for the breakout): group-calendaring
* Additional speakers/panelists: Philippe le Hégaret, Vivien Lacourba
* Timeslot: 2pm UTC
* Days in which the breakout can run: Monday, Tuesday, Thurday, Friday

=== Web of Things (WoT) Applications and Use Cases ===
* Proposer: [[User:Mmccool|Michael McCool]] 
* Email address of proposer: michael.mccool@intel.com
* Summary: Update on Web of Things (WoT) progress in extending web standards to IoT, and a showcase for recent applications and use case scenarios from our online plugfest.
* Type of session: 30m presentation, 30m discussion and Q&A.
* Goals: Present recent practical work on applying WoT to specific use-case scenarios, including from our recent plugfest, and to gather feedback on future priorities and use cases.
* Shortname: wot-breakout
* Apply to be a [[#Public_Breakout]] (breakouts open to the world at large, not just the W3C community)
* Timeslot: 1pm UTC (12pm (noon) UTC *might* be acceptable, but would have to be discussed with the rest of the group).  Unfortunately, conflicts at 2pm UTC.
** potentially would have a second session at an Asian-friendly time, e.g., 5-7am UTC, but concrete time still needs to be identified.
* Day: Tuesday.

=== Connected Vehicle Interface Initiative ===
* Proposer: [[User:Ted|Ted Guild]] ([[User talk:Ted|talk]]) 20:34, 16 October 2020 (UTC) 
* Email address of proposer: ted@w3.org
* Summary (one-sentence or so): Joint GENIVI / W3C workshop on Connected Vehicle Interface Initiative, summary of current standards, technology stack, past roundtables and stakeholder perspectives.
* Type of session: Workshop
* Goals: Establish wider understanding of standards efforts, refinement and agreement on scope of initiative.
* shortname: CVII
* Additional speakers/panelists: [https://www.w3.org/2020/10/GENIVI_AMM_CVII_Working_Sessions.pdf  partial list, will be updated]
* Audience: Restricted to GENIVI and W3C Members plus invitees
* Timeslot: 14-17:30 GMT
* Day: Tuesday

=== The Responsible Use of Geospatial Data ===
* Proposer: [[User:Eparsons|Ed Parsons]] 
* Email address of proposer: eparsons@google.com
* Summary: Progress on developing a framework for the responsible and ethical use of Geospatial tools and data 
* Type of session: Open discussion
* Goals: Present and gather feedback on the work so far
* shortname: ResGeo
* Additional speakers/panelists: Joseph Abhayaratna
* Apply to be a [[#Public_Breakout]] Yes
* Timeslot: 2pm UTC

=== Storage Buckets API ===
* Proposer: [[User:Ayuishii|Ayu Ishii]] 
* Email address of proposer: ayui@chromium.org 
* Summary: Discussion on Storage Buckets API [https://github.com/WICG/storage-buckets/blob/gh-pages/explainer.md proposal]
* Type of session: Presentation followed by discussion 
* Goals: Learn use cases and concerns and reach consensus on proposal
* Shortname: storage-buckets
* Additional speakers/panelists: Victor Costan
* Apply to be a [[#Public_Breakout]]: Yes
* Timeslot: 4pm UTC
* Constraints on days in which the breakout can run: Thursday, Friday

=== MiniApp Standardization in W3C ===
* Proposer: [[User: Angel Li| Angel Li]] 
* Email address of proposer: angelli.laq@alibaba-inc.com
* Summary: Discussion on MiniApp Standardization in W3C 
* Type of session: Presentation followed by discussion 
* Goals: introduce the current progress of MiniApp specifications incubation, discuss possible cooperation with related groups and collect community feedback on the proposed MiniApp WG charter 
* Shortname: MiniApp Standardization
* Apply to be a [[#Public_Breakout]]: Yes
* Timeslot: 2pm UTC

=== Web Install API ===
* Proposer: [[User:Peconn|Peter Conn]] 
* Email address of proposer: peconn@chromium.org
* Summary: Discuss the need, use cases and considerations of a general web install API.
* Type of session: Brief talk followed by an open discussion.
* Goals: Identify appetite and concerns for such an API.
* Shortname: web-install
* Timeslot: 2pm UTC
* Days in which the breakout can run: Monday, Tuesday, Wednesday, Friday

=== WebID, a federated SignIn API ===
* Proposer: [[User: majidvp| Majid Valipour]]
* Email address of proposer: majidvp@chromium.org
* Summary: Discuss the usecases, requirements and explore solution space for a privacy-preserving federates SignIn API.    
* Type of session : Brief talks followed by open discussion / brainstorming 
* Goals: Understand current federated sign-in state on the web and brainstorm various ideas on how to make it more privacy-preserving. Present the current thinking and ideas in [https://wicg.github.io/WebID/README.html WebID proposal] and brainstorm solutions.
* Shortname: webid
* Additional speakers/panelists: Samuel Goto, Ken Buchanan
* Apply to be a [[#Public_Breakout]]: Yes
* Timeslot: 2pm UTC

=== CSS Module Scripts ===
* Proposer: [[User:Daniec|Daniel Clark]] ([[User talk:Daniec|talk]]) 21:01, 16 October 2020 (UTC)
* Email address of proposer: daniec@microsoft.com
* Summary (one-sentence or so): Discuss [https://github.com/w3c/webcomponents/blob/gh-pages/proposals/css-modules-v1-explainer.md CSS Module Scripts] now that they are unblocked by [https://github.com/tc39/proposal-import-assertions Import Assertions].  Confirm positions on the minimal semantics, discuss the status of DocumentOrShadowRoot.adoptedStyleSheets, and potential further steps after initial support, like bundling CSS and exporting other objects from a stylesheet.
* Type of session: Open Discussion.
* Goals: Reach consensus on the minimal semantics and make progress on further directions.
* shortname: components
* Apply to be a #Public_Breakout: yes
* Timeslot: 5pm UTC

=== Virtual Keyboard Control ===
* Proposer: [[User:Pcupp|Bo Cupp]] ([[User talk:Pcupp|talk]]) 08:18, 17 October 2020 (UTC)
* Email address of proposer: pcupp@microsoft.com
* Summary: Discuss the [https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/VirtualKeyboardAPI/explainer.md Virtual Keyboard API] and [https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/VirtualKeyboardPolicy/explainer.md Virtual Keyboard Policy].
* Type of session: Open Discussion
* Goals: Ensure interested parties understand the proposal, build consensus, and seek collaborators interested in helping author a spec.
* shortname: editing
* Additional speakers/panelists: Anupam Snigdha (snianu@microsoft.com)
* Timeslot: 2pm UTC
* Constraints on days in which the breakout can run: Wednesday, Thursday, Friday

=== EditContext API ===
* Proposer: [[User:Shihken|Alex Keng]] ([[User talk:Shihken|talk]]) 08:22, 17 October 2020 (UTC)
* Email address of proposer: shihken@microsoft.com
* Summary: Demo and discussion of the [https://w3c.github.io/editing/docs/EditContext/explainer.html EditContext API].
* Type of session: Open Discussion
* Goals: Provide an update on our progress since the introduction of the API at last year's TPAC.
* shortname: editing
* Timeslot: 2pm UTC
* Constraints on days in which the breakout can run: Wednesday, Thursday, Friday

=== European Publishers Council – Future of the Open Web ===
* Proposer: [[User:Jwrosewell|James Rosewell]] ([[User talk:Jwrosewell|talk]]) 11:03, 18 October 2020 (UTC)
* Email address of proposer: james@51degrees.com
* Summary (one-sentence or so): Phillip Eligio from the [https://www.epceurope.eu/ EPC] will present the high-level summary of their positioning paper on the future of digital include the need for an effective, fair, transparent and privacy-centric identifier and the need for neutral oversight.
* Type of session: talk + Q&A
* Goals: Provide W3C membership and stakeholders with the authoritative position on publishers requirements from the open web.
* shortname: #EPC
* Additional speakers/panelists: Phillip Eligio
* Apply to be a [#Public_Breakout]
* Timeslot: 2pm UTC to 4pm UTC
* Monday, Tuesday, Wednesday

=== Defining a privacy baseline  ===
* Proposer: [[User:Jwrosewell|James Rosewell]] ([[User talk:Jwrosewell|talk]]) 11:03, 18 October 2020 (UTC)
* Email address of proposer: james@51degrees.com
* Summary: Follow on from [https://cryptpad.w3ctag.org/code/#/2/code/edit/4ht9YHtVS9AB4UBlh-oPvHej/ 15th October 2020 PING meeting] a session to debate the need for a privacy baseline definition. If all user agents must appear the same in every way what does this mean for innovation and diversity? If not, what should the comformity baseline be? How are different regional laws assessed to form a global baseline? Does the W3C want or need to create standards that design to, or even exceed, such a legal baseline?
* Type of session: open discussion
* Goals: Understand the gap in participants views on these questions and appetite for defining a privacy a baseline which all W3C members and stakeholders can understand and work to.
* shortname: #privacy-baseline
* Additional speakers/panelists: TBC
* Apply to be a [#Public_Breakout]
* Timeslot: 2pm UTC to 4pm UTC
* Monday, Tuesday, Wednesday

=== User Agent Client Hints  ===
* Proposer: [[User:Jwrosewell|James Rosewell]] ([[User talk:Jwrosewell|talk]]) 11:21, 18 October 2020 (UTC)
* Email address of proposer: james@51degrees.com
* Summary: Opportunity to debate and progress the many [https://github.com/WICG/ua-client-hints/issues open issues] raised in relation to the proposal to introduce [https://github.com/WICG/ua-client-hints client hints for user agent] data and deprecate the HTTP User-Agent field.
* Type of session: Issue debate and resolution
* Goals: Progress resolution of the issues related to the proposal to provide greater clarity to stakeholders.
* shortname: #uach
* Additional speakers/panelists: TBC
* Apply to be a [#Public_Breakout]
* Timeslot: 2pm UTC to 4pm UTC
* Monday, Tuesday, Wednesday

=== Innovative adaptation, personalization and assistive technologies ===

* Proposer: [[User:Matkinson|Matthew Atkinson]] ([[User talk:Matkinson|talk]]) 14:38, 18 October 2020 (UTC)
* Email address of proposer: matkinson@paciellogroup.com
* Summary: The world of research has developed a numbers of super-helpful, user-tailored and also fairly transparent adaptations that could help a wide range of people more easily access devices, computers and the web. This session will introduce a few of these, but the primary goal is to discuss them and seek feedback on how we might incorporate them into the web. You can get a flavour of the adaptations at http://matatk.agrip.org.uk/articles/the-promise-of-personalised-interfaces/
* Type of session: short informal talk to introduce a few key adaptations, followed by open discussion.
* Goals: (1) Raise awareness of some ways that interfaces and content can be adapted that can help a wide range of people; (2) Seek ideas as to how these sorts of adaptations could be applied in the context of the web (standards, content, browsers, ...)
* Shortname: TBC
* Additional speakers/panelists: TBC
* Apply to be a #Public_Breakout
* Timeslot: 12pm-5pm UTC
* Days on which the breakout can be run: Monday, Tuesday, Thursday, Friday

=== Smart Cities ===
* Proposer: [[User:Ashimura|Kazuyuki Ashimura]] ([[User talk:Ashimura|talk]]) 01:49, 19 October 2020 (UTC)
* Email address of proposer: ashimura@w3.org
* Summary (one-sentence or so): Based on the discussion during the [https://www.w3.org/WoT/ws-2019/minutes.html#day2-item02 Second WoT Workshop in Munich], [https://w3c.github.io/wot-usecases/#smart-city use cases on Smart Cities] have been proposed to the Web of Thing IG. However, we need to collect even more use cases and system implmentation experiences of actual smart cities from all over the world, because Smart Cities topic depends on the cities' location, culture, etc., and include various sub-systems from many different vendors. So we'd like to hold discussion on the possible standardization for Smart Cities before forming a concrete discussion group within W3C.
* Type of session: Background description + Open discussion
* Goals:
** identify the stakeholders of Smart Cities standardization to drive the development of Web standards aligned with the real needs of Smart Cities
** and then discuss how to proceed including the possibility of holding a dedicated Workshop and forming a dedicated IG
* shortname: smart-cities
* [optional] Additional speakers/panelists: tbd
* [optional] Apply to be a [[#Public_Breakout]] (breakouts open to the world at large, not just the W3C community)
* [optional] Timeslot: 12pm-4pm UTC (but need to avoid conflicts with the related sessions, e.g., [https://www.w3.org/wiki/TPAC/2020/SessionIdeas#Web_of_Things_.28WoT.29_Applications_and_Use_Cases WoT Applications and Use Cases], [https://www.w3.org/wiki/TPAC/2020/SessionIdeas#Video_Metadata_For_Moving_Objects_.26_Sensors_On_The_Web_.28WebVMT.29 Video metadata] and [https://www.w3.org/wiki/TPAC/2020/SessionIdeas#Voice_Agents Voice Agents]) - Detail on preferred date/time below
** Monday, 12pm-1pm UTC
** Monday, 2pm-3pm UTC
** Tuesday, 12pm-1pm UTC
** Tuesday, 2pm-3pm UTC
** Thursday, 2pm-3pm UTC
** Friday, 12pm-1pm UTC
** Friday, 1pm-2pm UTC
* [optional] constraints on days in which the breakout can run: Monday, Tuesday, Thursday, Friday

=== Voice Agents ===
* Proposer: [[User:Ashimura|Kazuyuki Ashimura]] ([[User talk:Ashimura|talk]]) 01:52, 19 October 2020 (UTC)
* Email address of proposer: ashimura@w3.org
* Summary (one-sentence or so): During [https://www.w3.org/2019/09/18-voice-minutes.html one of the breakout sessions at TPAC 2019] in Fukuoka, there was discusison about needs for improved voice agents for web services. And we'd like to proceed with the preparation for the expectd [W3C Workshop on User-friendly Smart Agents on the Web](https://github.com/w3c/strategy/issues/221)
* Type of session: Background description + Open discussion
* Goals:
** identify people interested as (1) the expected Program Committee for the workshop and (2) participants in the workshop
** also would get insights for the potential agenda for the expected workshop
* shortname: voice-agents
* [optional] Additional speakers/panelists: tbd
* [optional] Apply to be a [[#Public_Breakout]] (breakouts open to the world at large, not just the W3C community)
* [optional] Timeslot: 12pm-4pm UTC (but need to avoid conflicts with the related sessions, e.g., [https://www.w3.org/wiki/TPAC/2020/SessionIdeas#Web_of_Things_.28WoT.29_Applications_and_Use_Cases WoT Applications and Use Cases], [https://www.w3.org/wiki/TPAC/2020/SessionIdeas#Video_Metadata_For_Moving_Objects_.26_Sensors_On_The_Web_.28WebVMT.29 Video metadata] and [https://www.w3.org/wiki/TPAC/2020/SessionIdeas#Smart_Cities Smart Cities]) - Detail on preferred date/time below
** Monday, 12pm-1pm UTC
** Monday, 2pm-3pm UTC
** Tuesday, 12pm-1pm UTC
** Tuesday, 2pm-3pm UTC
** Thursday, 2pm-3pm UTC
** Friday, 12pm-1pm UTC
** Friday, 1pm-2pm UTC
* [optional] constraints on days in which the breakout can run: Monday, Tuesday, Thursday, Friday

=== Cloud Gaming on the Web ===
* Proposer: [[User:Lzm|Zhaoming Li]] ([[User talk:Lzm|talk]]) 08:10, 19 October 2020 (UTC)
* Email address of proposer: lizhaoming@tingyutech.com
* Summary: This session will include a basic introduction about cloud gaming, why cloud gaming is powerful, how cloud gaming run on the web, how can the web help cloud gaming, and shortages we currently have on the browser.
* Type of session: talk and open discussion
* Goals: We are looking to start a community group to work on providing a fast and stable user experience of cloud gaming.
* shortname: cloudgaming
* Additional speakers/panelists: Qingqian Tao, Alicia Nie

=== W3C 2020: Living Standards and Reviews ===

* Proposer: [[User:Plehegar|PLH]] 
* Email address of proposer: plh@w3.org
* Summary: This session will decrypt the new W3C Process to helps editors and participants find their ways. It will also give the latest information on how to do wide reviews and transitions.
* Type of session: talk and open discussion
* Goals: Avoid getting lost into the W3C Process maze.
* shortname: w3cprocess
* Additional speakers/panelists: none

=== NativeIO ===

* Proposer: [[User:Fivedots|Emanuel Krivoy]] ([[User talk:Fivedots|talk]]) 21:39, 19 October 2020 (UTC)
* Email address of proposer: fivedots@chromium.org
* Summary (one-sentence or so): [https://github.com/fivedots/nativeio-explainer NativeIO] is a new storage API that offers direct buffered access to file-like objects and is particularly focused on performance. This session will include a short introduction and a open discussion around current state of the project and next steps.
* Type of session: talk and open discussion
* Goals: Get feedback on next steps (benchmarking strategy, additional use cases, API shape) and gauge interest
* shortname (used for minting an IRC channel for the breakout): nativeio

=== WPT (Web Platform Tests) Coverage ===

* Proposer: [[User:leobalter|Leo Balter]] 21:55, 19 October 2020 (UTC)
* Email address of proposer: leobalter@salesforce.com
* Summary: Test coverage for W3C and WHATWG standards: Approaches and strategies for verifying test coverage of standards/specifications — specifically WPT tests. 
* Type of session: open discussion
* Goals: This session aims for an open discussion on how to tackle coverage at WPT tests to improve contributions and without raising burn for existing members.
* shortname: wptcoverage


=== W3C Focus and Shared Core Values ===
* Proposer: [[Tantek]] (email: tantek at cs dot stanford dot edu)
* Summary: Should W3C focus on building a membership & community based on a shared set of core values?
* type of session: open discussion
* goals of session: Determine from participation and discussion if there are aspects of shared agreement (or even consensus) on (re)focusing W3C membership & community models on a shared set of core values.
* opt-in to be a [[#Public_Breakout]] open to participation from the public at large
* shortname: focusvalues
* default timezone or later ok
* longer description: Should W3C focus on building a membership & community based on a shared set of core values? Recruiting to generate revenue (without regard to how new members' agendas will mesh with the good of the web) rather than reinforcing coherent shared principles and values to move the web forward has led to conflicts about things such as SOAP vs HTTP, DRM vs freely shareable information, and ad revenue vs privacy. When W3C had an active Director that made consistent trusted value judgments, the current W3C hierarchy worked reasonably well, but in a post-Director W3C who makes those judgments? If we expect the W3C community to pick up what the Director left off, it may be necessary to be more explicit about our core values, and be rigorous about applying those values when determining which work to charter and how to resolve objections.

=== IntersectionObserver API extensions for native lazy-loading ===
* Proposer: [[User:Spieters|Simon Pieters]] ([[User talk:Spieters|talk]]) 22:36, 19 October 2020 (UTC)
* Email address of proposer: simon@bocoup.com
* Summary (one-sentence or so): Discuss (1) [https://github.com/w3c/IntersectionObserver/issues/428 Allow dynamically changing rootMargin] (2) [https://github.com/w3c/IntersectionObserver/issues/431 Ability to have automatic rootMargin for all nested scroll containers]
* Type of session (e.g.: open discussion, talk, panel, etc.): open discussion
* Goals: support the needs of native lazy-loading, adhere to [https://extensiblewebmanifesto.org/ the Extensible Web Manifesto], utility for web developers for other use cases, within the constraints of what's implementable in browsers.
* shortname: intersectionobserver
* Apply to be a [[#Public_Breakout]] (breakouts open to the world at large, not just the W3C community)

=== Aligning Foldable and Multi-Screen Proposal ===
* Proposer: [[User:Msw|Mike Wasserman]]
* Email address of proposer: msw@google.com <mailto:msw@google.com>
* Summary: Continue [https://github.com/w3c/secondscreen-wg/issues/1 Second Screen CG discussion] of related proposals:  [https://github.com/webscreens/window-placement Multi-Screen Window Placement], [https://github.com/webscreens/window-segments Window Segments Enumeration API], [https://w3c.github.io/screen-fold/ Screen Fold API], and potentially [https://github.com/WICG/visual-viewport/ Visual Viewport API] 
* Goals:ind opportunities to align and refine these related proposals
* shortname: screenproposals
* Additional speakers/panelists: Kenneth Christiansen, Zouhir Chahoud, Anssi Kostiainen
* Apply to be a [[#Public_Breakout]]