View source for TPAC/2015/SessionIdeas

We encourage attendees to start brainstorming [[TPAC2015]] Wednesday '''Technical Plenary Day''' [http://www.w3.org/2015/10/TPAC/#breakouts Breakout sessions] in advance of the meeting. 

<span style="color:#ff0000">'''The sessions that made it are in the [https://www.w3.org/wiki/TPAC/2015#Session_Grid breakouts grid], as well as minutes and summaries '''</span>

See the [http://www.w3.org/wiki/TPAC2015/FAQ TPAC 2015 FAQ] for more information.

'''Note''': During TPAC week, working groups may [https://www.w3.org/wiki/TPAC/2015/ad-hoc-meetings schedule] [http://www.w3.org/2015/10/TPAC/#adhoc Ad-hoc meetings].

== How to use this page ==

Please use this page to:

* Propose sessions you wish you lead
* Propose sessions you wish others to lead
* Indicate whether you plan to attend a session (helps with scheduling)
* '''Please place new proposal at the bottom of this document'''

== How to propose a session ==

Please provide:
<ul class="show_items">
* session name (as a === subhead === )
* session proposer (optional: name a desired session leader, can be yourself)
* one sentence session summary
* type of session: (e.g.: talk, panel, open discussion, etc.)
* goals of session
* additional speakers/panelists
</ul>

== Proposed sessions ==

=== Generic Sensor API ===
* Proposer: Tobie Langel
* Summary: Status update of spec and implementation, discussions around new use cases and future plans
* Type: short presentation followed by an open discussion
* Background materials:
** [https://w3c.github.io/sensors/ Generic Sensor API spec]
** [https://github.com/w3c/sensors/issues Generic Sensor Issue Tracker]
* Minutes: [http://www.w3.org/2015/10/28-dap-minutes.html Generic Sensor API TPAC 2015 breakout 28 Oct 2015] (note: attendees information in draft minutes is incomplete, there were in total ~35 participants)

=== AMP and HTML ===
* Proposer: Chris Wilson
* Summary: Discussion of what AMP is and is not, what the future of AMP looks like, and how it fits with HTML
* Type: short (!) presentation followed by an open discussion
* Background materials:
** [https://github.com/ampproject/amphtml AMP project]
* [http://www.w3.org/2015/10/28-amp-minutes.html minutes]

=== Getting your hands dirty with the automatic publication system (and later celebrating how that little investment of time pays off in the end, by saving you time and headaches), or the convenience or writing succinct titles ===
* '''Proposer''': [[User:Antonio | Antonio]], on behalf of [http://www.w3.org/People/domain/systeam Systeam].
* '''Summary''': discussion about the [https://github.com/w3c/echidna/wiki/FAQ automatic publication system] and related tools.
* '''Type''': moderately geeky discussion.
* '''Background materials''': none, but some familiarity with [https://github.com/w3c/echidna Echidna] & [https://github.com/w3c/specberus Specberus] is desirable.
* '''Constraint''': ideally, at at a time when all systeamers (Ted, Vivien, Yves) and other interested parties (Philippe, Dom, fantasai) can attend.
* Check out the <span style="background-color: #ffff80;">wiki page about this session</span>, which includes links to the '''slides''' and to the '''minutes''': [[TPAC2015/session-echidna|<code>TPAC2015/session-echidna</code>]]
* [http://www.w3.org/2015/10/28-pub-minutes.html minutes]

=== W3C Web API ===
* '''Proposer''': Vivien Lacourba on behalf of [http://www.w3.org/People/domain/systeam W3C  Systeam].
* '''Summary''': The W3C Web API exposes W3C public data (Specifications, Groups, ...) in a JSON format.<br />During this session I will present the project, demo some of the available data, showcase prototype of groups home page backed by the W3C Web API.
* '''Type''': presentations, discussion
* '''Background materials''': [http://www.w3.org/2015/10/web-api-tpac/ Slides], [https://github.com/w3c/w3c-api W3C API GitHub project]
* '''Minutes''': [http://www.w3.org/2015/10/28-webapi-minutes.html W3C Web API TPAC 2015 Breakout session - 28 Oct 2015]

=== Business side of Verticals ===
* '''Proposer''': Alan Bird, W3C Global Business Development Lead
* '''Summary''': What is the business side of Verticals (aka Industry Engagement Meetings)? We need global voices in our detailed work as well as our Strategic Industry discussions.
* '''Type''': discussion
* '''Background materials''': TBD
* '''Constraint''': 30 minute session

=== Project FoxEye ===
* Proposer: [[User:Glaxy | Chiahung Tai]] and [[User:kakukogou | Tzuhao Kuo]] from Mozilla.
* Summary: demo, prototypes of FoxEye project.
* Type: presentations, discussion
* More detail: [https://wiki.mozilla.org/Project_FoxEye FoxEye]
* goals of session: The goal of this project is bringing the power of computer vision and image processing to the Web.
* [https://www.w3.org/wiki/TPAC2015/session-foxeye summary]

=== CJK (China / Japan / Korea) Web Leadership Forum ===
* Proposer: CJK W3C Advisory Board members (Soohong Daniel Park, Judy Zhu and Jay Kishigami)
* Summary: strategic thoughts and plan
* Type: open discussion based on AB material(Industry Group) with plh
* More detail: TBD
* goals of session: aiming to dig out any ideas to share W3C strategic information with various industries leaders in CJK, listen and learn about their requirements in specific.

=== Open Data with Local Community ===
* Proposer: Taisuke Fukuno, jig.jp
* Summary: App demos with Open Data by Japanese local communities. There are 160+ cities published Open Data in Japan. For 2020 Tokyo Olympic, how to create friendly city for all? Enjoy Sapporo, Hokkaido with Open Data of the Hokkaido!
* Type: presentation + open discussion
* More detail: TBD
* goals of session: Try to find the best practice to spread Linked Open Data world wide.
* Background materials:
** [http://www.w3.org/TR/dwbp/ Data on the Web Best Practices]
** [http://www.w3.org/2015/spatial/wiki/Main_Page Spatial Data on the Web Working Group]
** [http://www.pref.hokkaido.lg.jp/ss/jsk/opendata.htm Hokkaido Open Data]
* [http://www.w3.org/2015/10/28-opendata-minutes.html Minutes]

=== The Path to a W3C Credentials Working Group ===
* Proposer: Manu Sporny
* Summary: Discuss current status and future plans to start a Credentials Working Group at W3C
* Type: short presentation followed by an open discussion
* What this is: this group will be narrowly focusing the expression, storage, and retrieval of verifiable attributes about an entity via the Web Platform.
* What this is not: A discussion about FIDO, Hardware Security Modules, or "solving the Identity Problem on the Web" (those are nice initiatives, but different from what this group will focus on.)
* Background materials:
** [https://docs.google.com/presentation/d/1644G7jJZbUTpyEGALWj6t4m5kJc-bt90QCfRmW5IRuk/edit?usp=sharing W3C TPAC Credentials Presentation]
** [https://docs.google.com/document/d/1Nq543-Am1hQUIZ2hhzAFl8KexvIEBwDDc_f3Ikz1opQ/edit Credentials Executive Summary]
** [http://manu.sporny.org/2015/credentials-retrospective/#goals Credentials Ecosystem Goals and Capabilities]
** [https://www.youtube.com/watch?v=eWtOg3vSzxI Credentials on the Web (video)]
** [http://manu.sporny.org/2015/credentials-via-w3c/ The Case for Standardizing Credentials via W3C]
* [http://www.w3.org/2015/10/28-credentials-minutes.html minutes]

=== Text editing in the browser ===
* Proposer: Johannes Wilm
* Summary: Discuss about remaining issues for contentEditable=typing
* Type: open discussion
* Background: Standardization of browser's text editing features has been discussed for the past year in the Editing Task Force. We have come a long way in creating a specification that both editor makers and browser makers see as a viable solution going forward. Unfortunately the discussion on some points related to the name of the event needed (beforeInput/Input or beforeEdit/Edit) and some questions on whether or not it will be possible to move the caret to another part of the document as a result of beforecomposition events were not finished at the F2F meeting in Paris in August, and it would be of great help to get final clarification of these things here.
* Background materials:
** [https://w3c.github.io/editing/ Editing task force proposed specs]

=== Getting more people involved ===
* '''Proposer''': Yoav Weiss.
* '''Summary''': The Web platform needs people to help maintain and evolve it. Let's discuss ways to make that happen.
* '''Type''': Discussion
* '''Background materials''':
** [https://www.w3.org/community/wicg/ Web platform Incubator Community Group]

=== Cross-device Synchronization ===
* Proposer: François Daoust
* Summary: How to synchronize media and non-media data across devices. What is already possible. What could be standardized. The Timing Object proposal.
* Type: presentation followed by an open discussion
* Background materials:
** [https://webtiming.github.io/timingobject/ Timing Object spec]
** [https://github.com/webtiming/timingobject/issues Issues tracker]
** [https://www.w3.org/community/webtiming Multi-Device Timing Community Group]
* Slides/Minutes (added after the meeting):
** [http://www.w3.org/2015/Talks/fd-timing-tpac-breakout/ Presentation slides]
** [http://www.w3.org/2015/10/28-sync-minutes.html Breakout session minutes]

=== Web Payments Architecture ===
* Proposer: Ian Jacobs
* Summary: Help the new Web Payments WG build a great architecture
* Type: presentation + open discussion
* Background materials:
** [http://w3c.github.io/webpayments-ig/latest/charters/payments-wg-charter.html Web Payments WG Charter]
* '''Note''': The Web Payments WG does not yet exist formally, but we are planning to hold a meeting on Thursday and Friday. This breakout session gives those who will be present on Wednesday but not Thursday or Friday to provide some input to the early WG discussions.
* Nbreds demo on Web Payment demo: IOT Combined Service using Web Payment Standards (15 mins, Andy)
* [http://www.w3.org/2015/10/28-wpay-minutes.html minutes]

=== Web Authentication and Security ===
* Proposer: Wendy Seltzer, with Jeff Hodges, Virginie Galindo, and David Rogers
* Summary: Two new streams of security work have been proposed to W3C, one based on the FIDO Alliance's strong authentication specs; another based in hardware security features. We propose a session to discuss this work. 
* Type: brief presentation + open discussion
* Background materials:
** Web Authentication DRAFT charter: https://w3c.github.io/websec/web-authentication-charter
** Hardware-Based Security DRAFT charter: https://w3c.github.io/websec/hwsec-charter
* '''Note''': Ideally, these should not conflict with payments or mobile sessions, because of overlapping participants' interests.
* [http://www.w3.org/2015/10/28-websec-minutes.html minutes]

=== Web Platform Testing ===
* Proposer: fantasai + gsnedders
* Summary: Make a plan of all the stuff we need to do to get everyone running all the latest tests, and figure out who can do it
* Type: open discussion
* Output: Laundry list of tasks, some people assignments, list of interested corporate contacts for additional resources
* [http://www.w3.org/2015/10/28-testing-minutes.html minutes]

=== CSS Validation in the Browser ===
* Proposer: Takeharu Igari
* Summary: A NEW APPROACH of CSS validation. That can validate in the browser after JavaScript and can validate computed style and can validate matching of style and style. I'll introduce "Style Validator" that I developed which works as a Chrome Extension or JavaScript Bookmarklet.
* Type: presentation and demonstration
* Constraint: 30 minute session
* Background Materials:
** [http://www.slideshare.net/TakeharuIgari/style-validator-at-breakout-session-of-tpac2015 Slide used on session]
** [https://style-validaotr.github.io/Style-Validator/ Style Validator Official WebSite]
** [https://github.com/Style-Validator Github]
** [https://chrome.google.com/webstore/detail/style-validator/aaeahhnjkelemfcdmkcpaggdhfaffeod?hl=ja Chrome Extension]
* irc: #css-validation
* [http://www.w3.org/2015/10/28-css-validation-minutes.html Minutes]

=== Web of Things mapping ideas based on GW model ===
* Proposer: Kazuo Kajimoto, Yoshikazu Ishii + others
* Summary: Introducing GW to cover different logical and different physical protocols in market, Web of Things Servient can provide not only interoperability but other features such as safety and privacy.
* Type: presentation and demonstration
* Background Materials:
** [https://www.w3.org/wiki/images/1/19/TPAC_Breakout_WoT_Panasonic.pdf Slide used on session]
* [http://www.w3.org/2015/10/28-wot-breakout-minutes.html Minutes]

=== WebGPIO, WebI2C API ===
* Proposer: Koichi Takagi
* Summary: Introduction and discussion regarding low level APIs for web Runtime on embedded computers  
* Type: short presentation and discussion
* Background materials:
** [https://www.w3.org/community/browserobo/ Browsers and Robotics Community Group]
** [https://rawgit.com/browserobo/WebGPIO/master/index.html Draft of WebGPIO API]
** [https://rawgit.com/browserobo/WebI2C/master/index.html Draft of WebI2C API]
** [http://mozopenhard.mozillafactory.org/ Reference Implementation : mozOpenHard CHIRIMEN]
* irc: #webi2c
* [http://www.w3.org/2015/10/28-webi2c-minutes.html minutes]

=== Interacting with the Networking Layer (please keep early in the day due to participants constraints)===
* Proposer: Dominique Hazael-Massieux
* Summary: the Web platform offers more and more ways to interact with the network (XHR, Server-sent events, WebSockets, WebRTC, HTTP2, Push), and network technologies are themselves undergoing several major evolutions (LTE, 5G, NFV, SDN, MEC, etc); this breakout will present some of the recent work that has happened in this space and try to identify opportunities to start standardization work at the intersection of the networking and application layer
* Type: presentations followed by discussions
* Presentations:
** Dominique Hazael-Massieux: introduction to the needs and constraints of getting apps and networks to work together
** Natasha Rooney: report from the recent [https://www.iab.org/activities/workshops/marnew/ MaRNEW workshop] and experience of networking Task Force in Web & Mobile IG
** Ilya Grigorik: apps and network collaborating
** Kensaku Komatsu: WebRTC : P2P communication
* Background materials (links TBD@@@):
** Adapting to network conditions
** [https://www.iab.org/activities/workshops/marnew/ MaRNEW workshop outcome]
** [https://github.com/w3c-webmob/network-evolution-roadmap/blob/master/roadmap.md Network evolution Roadmap]
** Data Plan Info API
** [https://lists.w3.org/Archives/Public/public-web-mobile/2014Dec/0009.html Optimizing with the network]
* [http://www.w3.org/2015/10/28-network-minutes.html minutes], [https://www.w3.org/wiki/TPAC2015/session-network-interaction summary]

=== Space, Time and Sensor Semantics in the Web of Things ===
* Proposer: Kerry Taylor, Ed Parsons, Phil Archer and others from the SDW Working Group
* Type: open discussion
* Goals: The [http://www.w3.org/2015/spatial/charter Spatial Data on the Web Working Group] meets the [http://www.w3.org/WoT/ Web of Things Interest Group] to share progress and to better align developing outcomes
* Detail: The SDW is developing best practices for publishing and consuming spatial data on the web, and this includes streaming sensor data. In addition to  location and space, we are developing ontologies for Time (based on OWL-Time) and Sensing (based on SSN). Also we are dealing with remote sensing (Coverages). We have several IoT use cases and requirements, including a requirement for a lightweight API. We would particularly like to discuss activation.
* Background Materials [http://www.w3.org/2015/spatial/wiki/Main_Page SDW wiki], [http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html  FPWD Use Cases ]
* [[sdwmeetswotattpac2015|Agenda, meeting notes]], [http://www.w3.org/2015/10/28-swot-minutes.html minutes]

=== How to bring trust and confidence to Peer2Peer transactions===
* Proposer: Cyril Vignet
* Summary: a new concept to secure transactions using existing standards with specific workflow
* Type: short presentation followed by an open discussion
* Background materials: TBD

=== Transitioning to HTTPS ===
* Proposer: TAG
* Summary: Discussion of issues and proposals for moving the web to HTTPS
* Type: open discussion
* Background materials: [http://www.w3.org/2001/tag/doc/web-https], [http://webappsec-test.info/~bhill2/DifferentTakeOnOE.html]
* [http://www.w3.org/2015/10/28-https-transitional-minutes.html minutes]

=== Social Web ===
<span id="Are_you_Social.3F_We_need_you.21">Are you Social? We need you!</span>
* '''SCHEDULED: 10:30 room 108!'''
* Proposer: Ann Bassetti + {{rhiaro}} + {{tantek}}
* Summary: Overview of Social Web WG and IG activities; seeking participants
** '''Ask The Social Web WG/IG anything'''
* Type: short presentation followed by an open discussion
* IRC: irc://irc.w3.org:6665/social
* Background materials:
** [https://www.w3.org/wiki/Socialwg Social Web WG wiki]
** [https://www.w3.org/wiki/Socialig Social Web IG wiki]
* Problem statement: <blockquote>The TPAC page, http://www.w3.org/2015/10/TPAC/Overview.html, has a Twitter logo and promotes tweeting yet they're not even here at TPAC. People here are posting on Twitter, not their own website(s). That is the tip of the iceberg that the Social Web WG is dealing with.</blockquote>
* Minutes: http://socialwg.indiewebcamp.com/irc/social/2015-10-27#t1445996391422
* Wiki: [https://indiewebcamp.com/TPAC2015_Social_Web TPAC2015 Social Web]
* Photo: [http://tantek.com/2015/300/t1/social-web-session-w3c-tpac2015 https://igcdn-photos-b-a.akamaihd.net/hphotos-ak-xaf1/t51.2885-15/e35/12145332_1662314194043465_2009449288_n.jpg]

=== HTML5 Testing ===
* Proposer: Judy Zhu、Charles McCathie Nevile
* Proposed time slot: 10:30 ~ 12:00
* Summary: Requirements about HTML5 compatibility testing and performance testing, discussions around future plans
* Type: short presentation followed by an open discussion
* Background materials:
**http://testthewebforward.org/
* [http://www.w3.org/2015/10/28-html5perftesting-minutes.html minutes]

===Machine readable permissions and constraints - how far should W3C go?===
* Proposer: Phil Archer, Irina Bolychevsky, Ralph Swick, [http://www.big-data-europe.eu/ BigDataEurope project]
* Summary: The members will soon be asked to consider a draft charter for a Working Group to create an Open License Expression language. Taking the work of the ODRL Community Group as its starting point. Good idea? Bad idea? What should be in scope, what is out of scope?
* Type: introduction followed by an open discussion
* Background materials:
** [http://w3c.github.io/ole/charter.html Draft charter]
** [https://www.w3.org/community/odrl/ ODRL Community Group] (includes links to mature work in this area)
* [http://www.w3.org/2015/10/28-ole-minutes minutes]

=== Media Capture ===
* Proposer: TAG
* Summary: Discussion of issues coordinating various media capture APIs
* Type: open discussion
* Background materials: [https://github.com/w3ctag/spec-reviews/issues/57]

=== Web Platform Testing on Embedded Systems such as TV=== 
* Proposer: Fumitaka Watanabe, Yusuke Maehama, Shoko Okuma
* Summary: Embedded systems sometimes don't make WPT runnable because of the limited resources and different types of input devices, even though web browsers are implemented. What should we do on this? We'll demonstrate the WPT runner customized for TV, share the issues and have an open discussion to improve WPT for embedded systems.
* Type: Short presentation, demonstration and open discussion
* Goal of session: Find ways for better WPT on various types of devices
* Background materials:
** [https://www.w3.org/2011/webtv/wiki/Face-to-face_meeting_during_TPAC_2015#Agenda_Monday_October_26_.28tentative.29 Web and TV IG f2f meeting]
** [https://www.w3.org/2011/webtv/wiki/DevMeetupTokyo Developer Meetup in Tokyo]
** [https://github.com/wpt-on-tv-tf/web-platform-tests WPT-on-tv-tf]
* [http://www.w3.org/2015/10/28-wptontv-minutes.html minutes]

=== Federation between Web-based IoT platforms === 
* Proposer: Oleg Mezhvynskyi
* Summary: While WoT standards are under high development velocities in W3C to bring better interop to the IoT world, IoT platforms are rapidly emerging in various industries, creating silos already. However, some of them have adopted Web standards to improve the situation: They are called Web-based IoT platforms.<br/>In this session, I'll briefly show you the essence of a full Web-based IoT platform, which uses HTML5, WebRTC, etc. to maximize the portability of IoT apps, and would like to discuss with audience if Web-based IoT platforms and federation between them can help better the interop of IoT for the time being. If it helps, what kind of standards will we need?
* Type: Short presentation, demonstration and open discussion
* Goal of session: To seek the momentum to standardize federation features
* [http://www.w3.org/2015/10/28-iotpf-minutes.html minutes]

=== The Interledger Protocol (ILP) ===
*'''Proposer''': Adrian Hope-Bailie
*'''Leaders''': Stefan Thomas, Evan Schwartz
*'''Summary''': demo, presentation, discussion about the recently published [http://interledger.org/interledger.pdf Interledger Protocol (ILP) proposal], a protocol to link ledgers and payment networks.
*'''Type''': Demo of open-source reference implementations and discussion of the protocol and next steps for the CG
*'''Goals''': Demonstrate the protocol, discuss next steps, recruit participants for the [https://www.w3.org/community/interledger/ Interledger Payments Community Group].
*'''Background materials''': [http://interledger.org interledger.org] and the [https://www.w3.org/community/interledger/ Interledger Payments Community Group]

=== Secure communication with local network devices ===
*'''Proposer''': Mark Watson
*'''Leaders''': Mark Watson
*'''Summary''': Pages loaded in a secure context may wish to communication with local network devices (for example devices discovered using [http://dial-multiscreen.org DIAL]). Such devices may not have DNS names or long-lived certificates chained to a public CA to enable the use of standard PKI. How can we secure such communication such that the security promises of the "green padlock" are maintained.
*'''Type''': Brief presentation of the problem, open discussion
*'''Goals''': Establish the problem as one that W3C might work on, identify venue(s) for further discussion
* [http://www.w3.org/2015/10/28-local-minutes.html minutes]

=== New Funding opportunities for W3C? ===
* Proposer: Ann Bassetti
* Summary: I am frustrated that the W3C struggles for funding, when A) this work is so foundational to the functioning of the web; and B) so many others in the web tech industry are making big bucks. What new options can we think of?
* Type: brief intro followed by open discussion & brainstorming
* Background materials: none

=== Location-Based Service ===
* Proposer: Qing An
* Summary: Overview of use cases about Location-Based Service; discussions around future plans
* Type: short presentation followed by an open discussion
* Background materials: http://wiki.projects.genivi.org/index.php/IVI_NavigationW3CUseCasesAndGENIVIAPIs
* Minutes: [http://www.w3.org/2015/10/28-auto-minutes.html W3C Location-Based Service TPAC 2015 Breakout session - 28 Oct 2015]

=== Web Annotations  ===
* Proposer: Rob Sanderson
* Summary: The Web Annotation WG has been making strong progress towards a set of specifications that will enable interoperable annotations on the Web.  If you have any interest in Annotations, comments, tags, notes, reviews, or even just letting users create links between resources, this is the session to be at.
* Type: Brief presentation followed by an open discussion
* Background materials: 
** http://www.w3.org/TR/annotation-model/ 
** http://www.w3.org/TR/annotation-protocol/  
** http://www.w3.org/TR/findtext/
* [http://www.w3.org/2015/10/28-annotation-minutes.html minutes]

=== How blockchain could change the Web-based content distribution ===
* [https://www.w3.org/wiki/images/0/07/How_blockchain_could_change.pdf Presentation material]
* Proposer: Shigeru Fujimura, Hiroki Watanabe
* Summary: Introduction of the concept of the Web-based content distribution using blockchain and discussions about its potential
* Type: presentation followed by an open discussion
* [http://www.w3.org/2015/10/28-BCWCD-minutes.html Minutes]

=== Accessibility and Device Independent Interaction  ===
* Proposer: Cynthia Shelly, Rich Schwerdtfeger
* Summary: Accessibility APIs on a number of platforms have been used for device independent interaction and to perform automated testing. 
* Type: Overall discussion on what has been discussed earlier in the week, existing draft specifications, and a discussion as to what would be needed for addressing more mainstream use cases would be covered. The intent is to create more portable code that requires less work by the author to support accessibility.
* [http://www.w3.org/2015/10/28-jsapi-minutes.html minutes]

=== Requirements for Embedded Browsers needed by Web-based Signage ===
* [https://www.w3.org/wiki/images/4/41/Requirement_for_Signage-Presentation%2BResult.pdf Presentation material (including the result) ]
* Proposer: Kiyoshi Tanaka and Shigeru Fujimura
* Summary: The embedded browser used by web-based signage has definitely different requirements in the view point of security model. After describing such requirements and API ideas in the session, we will discuss proper WGs for their standardization.
* Goal of session: Identification of the right place in which each requirement is standardized. The result will be provided to Web-based Signage BG, and the newly identified standardization items will be discussed in future created Web-based Signage WG.
* Type: short presentation followed by an open discussion
* [http://www.w3.org/2015/10/28-websigns-minutes.html minutes]

=== Digital Marketing ===
* Proposer: Wendy Seltzer + Chad Hage
* Summary: Last month's [http://www.w3.org/2015/digital-marketing-workshop/agenda.html Digital Marketing Workshop] highlighted the importance of '''integrity''' in digital
marketing: security of web ad delivery mechanisms, application and page context, and viewability; robust and auditable data measurement; reliable marketing asset tracking and product description; and user privacy assurances. This breakout will discuss next steps to move digital marketing work forward in W3C and beyond.
* Background materials:
** http://www.w3.org/2015/digital-marketing-workshop/agenda.html with minutes
* [http://www.w3.org/2015/10/28-digimarketing-minutes.html minutes]

=== Technical Reports Design Project ===
* Proposer: fantasai
* Summary: TR Restyling Effort
* Background materials:
** https://github.com/w3c/tr-design
** https://www.w3.org/2002/09/wbs/1/tr-design-survey-2015/results
* [http://www.w3.org/2015/10/28-restyle-minutes.html minutes]

=== Re-decentralizing the web ===
* Proposer: Irina Bolychevsky + Andrei Sambra
* Summary: There is a movement of people looking to redecentralize the web - to preserve privacy, innovation, competition and resilience. We'll talk about some of the new technologies - mesh networking, blockchains, plug & play self hosting, distributed hash tables  - and the challenges and opportunities that come with them. 
* Type: Introduction then open discussion
* Background materials: 
** http://redecentralize.org/
** [http://www.wired.co.uk/news/archive/2014-02/06/tim-berners-lee-reclaim-the-web Tim Berners-Lee: we need to re-decentralise the web]
** [http://www.newyorker.com/tech/elements/the-mission-to-decentralize-the-internet The Mission to Decentralize the internet]
* [http://www.w3.org/2015/10/28-redecentralize-minutes.html minutes]

=== Future of HTML ===
* Proposer: Chaals McCathie Nevile
* Summary: What does the future of HTML look like at W3C?
* Type: Open discussion
* Goal: Gather suggestions and ideas about taking HTML forward.
* Presenters: Chaals McCathie Nevile, Léonie Watson, Adrian Bateman
* [http://www.w3.org/2015/10/28-html-minutes.html minutes]

=== Distributing Web Applications Among Devices ===
* Proposer: Mark A. Foltz
* Summary:  There are a number of device-centric APIs in various stages of development, including the [Presentation API https://w3c.github.io/presentation-api/], [Web Bluetooth API https://webbluetoothcg.github.io/web-bluetooth/], [Web NFC API https://w3c.github.io/web-nfc/], [Sensors API https://w3c.github.io/sensors/].  This session describes potential use cases for  Web applications that use nearby devices to distribute input, output, sensing and control, and how to improve interoperability among these APIs to make them possible.
* Type: Short presentation followed by an open discussion
* Presentation [https://docs.google.com/presentation/d/1M4Hph5ZWODlUI6QPd31ujDDQI8cR7XZrXh1lGxwRqsM/edit?usp=sharing]
* [http://www.w3.org/2015/10/28-dist-minutes.html minutes]

=== Webex: How's it going? Schedule to void clash with Machine readable permissions and constraints === 
* Proposer: Ralph Swick &amp; Nigel Megitt
* Summary: Earlier in the year we switched the organization's tool for teleconferencing from Zakim hardware to WebEx. This session is to gather feedback about how it has been going.
* Type: Open discussion
* Goal: to discover how Webex is working for Working Groups, share new Best Practices and discuss what would improve the fit with W3C practices.
* Moderator: Nigel Megitt
* Minutes: http://www.w3.org/2015/10/28-webex-minutes.html
* Summary: https://www.w3.org/wiki/TPAC2015/Webex

=== HTMLCue - a generic Text Track Cue that can use all of the UA's rendering capabilities ===
* Proposer: Nigel Megitt
* Summary: The only widely implemented Text Track Cue is VTTCue, which is extendable but includes unnecessary interfaces for the general case. How could we design a general use Text Track Cue that just has a payload that is a fragment of HTML, whose onenter() just attaches the payload HTML to a target element, and onexit() clears it?
* Type: Introduction then design workshop
* Goal: to generate a set of ideas that could be used to specify an HTMLCue extension
* Chair: Nigel Megitt
* Minutes: http://www.w3.org/2015/10/28-htmlcue-minutes.html
* Summary: https://www.w3.org/wiki/TPAC2015/HTMLcue

=== Egocentric Architecture ===
* Proposer: BigBlueHat (aka Benjamin Young)
* Summary: These days, all our data moves away from us. We comment in someone else's site. We store our photos behind lengthy terms of service. We scatter our digital selves across the cloudy online landscape.
Let's explore the self-centered world of offline-first applications, extend the Web (and the Cloud) beyond themselves to places closer to ourselves--with or without network access.
* Type: Introduction then open discussion
* Background materials: 
** https://speakerdeck.com/bigbluehat/egocentric-architecture
** http://offlinefirst.org/
** http://pouchdb.com/
** http://ipfs.io/
* Goal: To introduce ideas around offline-first Web app building, replication, and "cloudless" design thinking.
* Related Break Outs: [https://www.w3.org/wiki/TPAC/2015/SessionIdeas#Are_you_Social.3F_We_need_you.21 Are you Social? We need you!], [https://www.w3.org/wiki/TPAC/2015/SessionIdeas#Re-decentralizing_the_web Re-decentralizing the Web], [https://www.w3.org/wiki/TPAC/2015/SessionIdeas#Web_Annotations Web Annotations]
* [http://www.w3.org/2015/10/28-annotation-minutes.html minutes]

=== EPUB Zero ===
* Proposer: dauwhe (aka Dave Cramer)
* Summary: Can we make ebooks using only HTML? Can we implement all of the functionality of EPUB 3.X without multiple custom XML vocabularies and endless duplication? How much overloading can the nav element handle? 
* Type: open discussion
* Background materials: 
** https://github.com/w3c/dpub-pwp
** http://epubzero.blogspot.com/2013/07/straw-man-spec.html
** https://docs.google.com/document/d/1kWFN1z1RO7WImYtmDzQ39ssWKIGtZ642OkKmMwCMEYk/edit?usp=sharing
* Goal: to convert caffeine into rejected ideas
* [http://www.w3.org/2015/10/28-e0-minutes.html minutes]

=== Device APIs and Privacy/Permissions ===
* Proposer: jyasskin (aka Jeffrey Yasskin)
* Summary: How do we give websites access to devices (USB, NFC, Bluetooth, etc) in a way that's comprehensible to users and lets them protect their privacy and security? 
* Type: open discussion
* Background materials: 
** https://webbluetoothcg.github.io/web-bluetooth/#security-and-privacy
** http://w3c.github.io/web-nfc/security-privacy.html#introduction
** https://webbluetoothcg.github.io/web-bluetooth/use-cases.html#security_privacy
* Goal: familiarize everyone with the difficult issues; gather ideas.
* Minutes: http://www.w3.org/2015/10/28-web-bluetooth-minutes.html

=== Data Visualization ===
* Proposer: chunming hu
* Summary: We share datasets on the Web. But sometimes, we want the data not only in a boring list, but also with some of fancy ways. Bar chart, line chart, or other new visualization ways are widely adopted in media, scientific websites, statistical pages. Many visualization apps using js-libs (D3, echart, or other lib providers) to generate the vis result, but app developers have to binding to the lib implementation provider on unique datamodel, apis, and interaction. 
* Type: open discussion
* Background materials: 
** DataVis CG: https://www.w3.org/community/datavis/
** Wiki page of DataVis CG: https://www.w3.org/community/datavis/wiki/Main_Page
** Minutes on Sept 20 meetup at Beijing: http://www.w3.org/2015/09/20-datavis-minutes
* Goal: find usecases and requirements; discuss the goal of datavis standardization; gather ideas.
* Minutes: http://www.w3.org/2015/10/28-datavis-minutes.html

===Standards for Personal Assistants ===
* session proposer: Debbie Dahl
* This session will talk about what's needed to support personal assistant functionality within the Open Web Platform.
* summary: There are several proprietary personal assistants in common use, including Siri, Cortana, Google Now, Amazon Alexa and Facebook M. Similar, intelligent assistant functionality for specific enterprises is also being provided by other platforms, although these platforms are less commonly known. What is needed to create similar kinds of intelligent assistant applications with the Open Web Platform? In the discussion we ended up focusing on semantic assistance, for example, intelligent interpretation of web pages and displaying them in a way that's consistent with the user's preferences. This is independent of the specific modalities the user uses to access the information.
* type of session: open discussion
* goals of session
* [http://www.w3.org/2015/10/28-pa-minutes.html minutes]

===High Dynamic Range===
* session proposer: Mark Watson
* What does High Dynamic Range and Wide Color Gamut mean for the web paltform?
* type of session: presentation and open discussion
* minutes: http://www.w3.org/2015/10/28-hdr-minutes.html

Note : a Haiku challenge is running here https://www.w3.org/wiki/TPAC/2015/haiku