BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Sabre//Sabre VObject 4.5.8//EN CALSCALE:GREGORIAN LAST-MODIFIED:20230923T163543Z BEGIN:VTIMEZONE TZID:Europe/Madrid BEGIN:STANDARD DTSTART:20221030T010000 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 TZNAME:CET END:STANDARD BEGIN:STANDARD DTSTART:20231029T010000 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 TZNAME:CET END:STANDARD BEGIN:DAYLIGHT DTSTART:20230326T010000 TZOFFSETFROM:+0100 TZOFFSETTO:+0200 TZNAME:CEST END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:6d209c82-549d-4506-bc36-764ac4326b14 DTSTAMP:20230923T163543Z SUMMARY:The Future of Powerful APIs on the Web Platform DTSTART;TZID=Europe/Madrid:20230913T121500 DTEND;TZID=Europe/Madrid:20230913T131500 DESCRIPTION:https://www.w3.org/events/meetings/6d209c82-549d-4506-bc36-764a c4326b14/\n\nPowerful APIs have been a constant source of contention when balancing the needs of making the web platform competitive while still pro viding the fundamental guarantees such as security and privacy. Given the trend of web-platform derivative application runtimes such as Electron bec oming popular\, the potential and user needs of this is clear - but how we can deliver such functionality while providing the security and privacy g uarantees of a browser remains an unsolved problem. \n\n\n\n\n\n\n\nAs a s imple example of this being a problem - fundamental platform functionality \, such as accessing files is still in an unsatisfying state\, leaving the web platform as a less desirable platform for developers to target seriou s applications against. Is there a path where we can have a standardized r eplacement for Electron\, and if so\, what kind of fundamental architectur al changes would that entail? \n\n\n\n\n\n\n\nThis session would like to i nvite members of the community who are interested in contributing towards a solution to this. Of the participants\, we would like to create a task f orce to identify unmet user needs on the web platform\, attempt to find a path forward to tackle this problem space\, and compile a set of principl es and requirements that solutions developed to address these needs should follow. This venture will function as a TAG-endorsed task force\, and the participants will be invited by the TAG chairs. Members may include curre nt or former members of the TAG.\n\n\n\n\n\n\n\nThe task force would be i dentifying ways to bridge the gap between the Web Platform and native appl ication platforms\, while protecting security and user privacy\, aligning with the TAG's Ethical Principles\, Design Principles\, the in-development Privacy Principles and the Privacy & Security Questionnaire. We would nee d to ensure this effort has multi-stakeholder interest\, while ensuring cr oss-browser and platform support.\n\nAgenda\n\n**Chairs:**\nSangwhan Moon\ , Lea Verou\, Daniel Appelquist\n\n**Description:**\nPowerful APIs have be en a constant source of contention when balancing the needs of making the web platform competitive while still providing the fundamental guarantees such as security and privacy. Given the trend of web-platform derivative a pplication runtimes such as Electron becoming popular\, the potential and user needs of this is clear - but how we can deliver such functionality wh ile providing the security and privacy guarantees of a browser remains an unsolved problem. \n\n\n\n\n\n\n\nAs a simple example of this being a prob lem - fundamental platform functionality\, such as accessing files is stil l in an unsatisfying state\, leaving the web platform as a less desirable platform for developers to target serious applications against. Is there a path where we can have a standardized replacement for Electron\, and if s o\, what kind of fundamental architectural changes would that entail? \n\n \n\n\n\n\n\nThis session would like to invite members of the community who are interested in contributing towards a solution to this. Of the partici pants\, we would like to create a task force to identify unmet user needs on the web platform\, attempt to find a path forward to tackle this proble m space\, and compile a set of principles and requirements that solutions developed to address these needs should follow. This venture will functio n as a TAG-endorsed task force\, and the participants will be invited by t he TAG chairs. Members may include current or former members of the TAG.\n \n\n\n\n\n\n\nThe task force would be identifying ways to bridge the gap between the Web Platform and native application platforms\, while protecti ng security and user privacy\, aligning with the TAG's Ethical Principles\ , Design Principles\, the in-development Privacy Principles and the Privac y & Security Questionnaire. We would need to ensure this effort has multi- stakeholder interest\, while ensuring cross-browser and platform support.\ n\n**Goal(s):**\nSolicit feedback on problem space\, iterate on focus area for task force\, and recruit participants.\n\n\n**Materials:**\n- [slides ](https://docs.google.com/presentation/d/1-1Q-2206wTjWadU0NtXozEWyGZbnaz1A BHCWL_MCNaM/edit#slide=id.p)\n- [minutes](http://www.w3.org/2023/09/tpac-b reakouts/76-minutes.pdf)\n- [live google doc minutes](https://docs.google. com/document/d/1vRO6xher_AiHDOkQIClgz4wCI8tEAJdHifLU-M2epOI/edit#heading=h .xxa48zxk3cpj)\n- [Session proposal on GitHub](https://github.com/w3c/tpac 2023-breakouts/issues/76) STATUS:CONFIRMED CREATED:20230905T140310Z LAST-MODIFIED:20230923T163543Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda V - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT END:VCALENDAR