Eemeli Aro

The base requirements for message formatting and localization are experiencing some significant advancements as the MessageFormat 2 spec is being defined in the Unicode Consortium, and the Intl.MessageFormat API is being defined in TC-39 for JavaScript.

Building on these, work should start on defining a localization system for HTML that's reactive rather than imperative, and which allows for localization without any JS dependency. At Mozilla, we've been using a similar system based on Fluent to localize Firefox and our other projects, and have learned much about what works and what doesn't. Some of our ideas have been collected as a draft of what this could look like in practice.

1. Collect comments on the proposal.

2. Recruit interests to work on the standards development.

3. Discuss the most appropriate forum for further work.

• W3C Calendar

• slides

• minutes

• Session proposal on GitHub

Wendy Reid

As a follow-up to the first part of Meeting Facilitation Training (video is online at [link here]), this session will be an in-person and remote discussion covering the second part of the training. Participants in this session will be expected to have watched the first part of this training in advance of the session.

This session is open to all meeting facilitators (chairs, taskforce leads, or aspiring to be), and will be a collaborative session covering tip and tricks participants use to make running meetings easier, and discussion on how to handle difficult discussions or situations as a chair or meeting facilitator.

Due to the nature of topics that might come up during the meeting, we will not be minuting the part of the session on difficult conversations, but will minute the tips and tricks discussion.

Post-TPAC note: No minutes were taken at this session.

Meeting Facilitator Training

• W3C Calendar

• Session proposal on GitHub

Daniel Murphy

We have a number of rough areas, and while we might not be ready to figure out a solution yet, we would love to chat about the current issues we are seeting. @b1tr0t and @beverloo have most of the context here (although @beverloo won't be at TPAC this year)

• Abuse / spam / requiring install for notifications

  • Chromium is seeing a large quantity of abuse across the ecosystem. We don’t believe gating notifications to installed use is the answer for reasons.

  • We are considering rate limiting and other countermeasures

  • Are there opportunities for standards revisions that might help?

• "important" notifications (VOIP). @beverloo notes:

  • MSFT already working on this:

  • Intent to Prototype on blink-dev, explainer, initial implementation

  • Example hero use-case - empower Skype on the Web.

  • On Android this would require a permission (FOREGROUND_SERVICE_PHONE_CALL) that we probably don’t want to issue to Chrome itself. Limiting this functionality to installed experiences seems good in either case, as otherwise there would be complicated incentives.

• Notification sounds (ringing?)

  • Related to important notifications, some apps might want a ringing sound

  • Somewhat limited by OS support of custom notification sounds, however, may be possible to create a “Safe” set of standard notification sounds for developer to choose from e.g. “Chime” “Ringing” “Alarm”, and perhaps others

  • @beverloo notes: This was part of a Microsoft proposal that we provided feedback on

    • Explainer

    • Long story short, a (admittedly brief) joint investigation showed that very few sounds would actually be consistent across operating systems, which is hard to explain to developers. It’s important that these are OS-consistent: ideally an e-mail in Apple Mail and one in Gmail alert Apple users in exactly the same way.

    • For Chromium to support arbitrary sounds, the media team advised that the best way to achieve that would be to load a (background) tab with a element in which we play the developer-provided URL. That’s a significant system health cost.

    • On Android such sounds are tied to the notification channel as opposed to individual notifications, and actually cannot be set for individual notifications anymore.

• Notification channels.

  • Allow sites to register and send to specific channels, similar to capabilities offered on Android and iOS platforms

    • Can be a useful way for users to reduce unwanted notification volume, for example on a messaging app like IG the user could choose to allow DMs but not receive notifications about new posts in the feed

  • beverloo@ note:

    • ChromeOS is also very interested in this, would like to see something like this supported. We might be able to mimic support in Windows through grouping.

      • Nuances to consider on Android: channels are declared once and are then permanent, i.e. updating the importance, sound, vibration etc. of a channel should not happen after it’s been created, even when the channel’s name changes.

• Reducing notification energy use (currently need to spin up JS)

  • The current web notifications spec was designed with maximum flexibility as the objective. With the current spec, notifications require a Service Worker and when a notification is received, the ServiceWorker wakes and can then take some action.

  • The solution is an amendment to the notification specification that optimizes for the most common notification usage pattern of simply displaying a notification on the user’s device. This change will improve performance and energy usage of notification delivery.

  • @beverloo note: We’ve always been supportive of receiving push messages and showing notifications w/o involving the service worker, this would bring major system health benefits.

    • There has been some resistance from partners to support this as they need the SW / analytics logic to run for monetization.

    • Android would be able to support high priority notifications in a declarative path. This is important because the framework deprioritises notifications for an entire app (i.e. the browser) based on show and interaction rates, which means that currently a single misbehaving site can negatively impact the holistic browser notification experience.

    • Big +1 to doing this if we can get broader ecosystem adoption.

Share issues with current notification spec & ecosystem, possibly connect to problem solve in the future.

• W3C Calendar

• slides

• minutes

• live google doc minutes

• Session proposal on GitHub

Christos Bacharakis, Dr. Humera Noor Minhas, Cornelius Witt

When we speak about sustainability and climate change, we think about long-haul flights and solar panels. We do not realize that our day-to-day digital behavior, like mindless scrolling, dark vs bright backgrounds, and the online advertisements we see, also contributes to our carbon footprint. This open discussion is about how we, the people on the web, can build products and technologies that are sustainable and positively impact the user behavior in a way that contributes to a greener environment.

Understand how we can build technologies and products that contribute to our fight against carbon emissions

Agenda

• W3C Calendar

• slides

• minutes

• live google doc minutes

• recording

• Session proposal on GitHub

Phil Archer

The first barcode went beep at a checkout in Ohio almost 50 years ago (1974-06-26T08:01:00+05:00). GS1, the global organization behind the numbering system embedded in billions of barcodes around the world, is working with industry to replace it with higher-capacity, more functional alternatives. You won't be surprised to learn that in many cases this will be a QR code that contains a URI. But the URI has additional structure that encodes not just the basic product identifier but things like batch numbers, serial numbers, expiry dates and more. The ambition is that by the end of 2027, the original 1970s barcode can begin to retire.

This presents substantial opportunities for the Web. Some claim it also presents opportunities for bad actors. This breakout session is about:

1. How do I recognize a "GS1 Digital Link URI" when I see it? (example: https://example.com/01/09506000134352/10/ABC)

2. What can I do with it? Linked Data? HATEOS? (try https://id.gs1.org/01/09506000134352/10/ABC?linkType=all)

3. Whaddyamean the domain name isn't part of the identifier?? That's nuts! (it's also true)

4. How does this tie in with product conformance certificates, trade digitization, the forthcoming EU Digital Product Passport regulation, traceability, sustainability and generally 'selling more stuff'

5. Ah, forget it, it's a URL so I can do what I like... (true)

To discuss the future possibilities - good and bad - that the change to Web-enabled barcodes offer. How it ties in with DIDs and VCs, and how it can be used to improve consumer experiences online.

One specific question: does putting URIs with additional structure into QR codes on millions of products create a massive security headache?

Agenda

• W3C Calendar

• slides

• minutes

• Session proposal on GitHub

Daniel Ehrenberg, Samina Husain

ECMAScript is core to the Web Platform, so collaboration between the W3C and Ecma International has been key for many evolution initiatives on both sides. Ecma TC39, the committee were ECMAScript (a.k.a. JS) is standardized, has an efficient and inclusive process for standards development, which shares many qualities with the W3C process.

The organizations have a formal liaison relationship (enabling representatives of one organization to participate in the other, for example), but on the ground, Ecma TC39 has relied heavily on certain individuals in each organization to bridge the gaps. Many TC39 proposals have significant architectural impact on the Web Platform, and these impacts have been reviewed in WHATWG HTML threads as well as W3C TAG reviews.

Like the W3C, Ecma is expanding in its work areas. For example, Ecma has a new initiative to standardize source maps in TC39-TG4. Overall, new work in the web space within Ecma tends to take TC39's success as a model to repeat. This is going well for source maps so far.

The idea of this session is to start with a short presentation of where Ecma and TC39 are today and how we work together, and then proceed to an open discussion about how we can work in the future, in what areas and working modes, etc.

Identify areas and ways to work together in the future

Agenda

• W3C Calendar

• slides

• recording

• Session proposal on GitHub

Fernando Serboncini, Chris Harrelson

Exploration of the modern use cases for web vector graphics, the current solutions and their limitations, and potential future improvements. Responsive vector graphics. Parametric Shapes. Better CSS integration.

Figure out potential plan for vector graphics moving forward

• W3C Calendar

• slides

• minutes

• Session proposal on GitHub

Tzviya Siegman, Wendy Reid, Chris Wilson

An overview of AB projects and priorities, focusing on those to which W3C Members, Team, and IEs are invited and encouraged to participate. These include:

• W3C Process and Process CG

• Vision

• Incubation

• Code of Conduct and PWE CG

Post-TPAC note: This session did not take place.

Share information about how general membership can contribute to the work of the Advisory Board

• W3C Calendar

• Session proposal on GitHub

Andreu Botella, Daniel Ehrenberg

AsyncContext is a stage 2 TC39 proposal that allows propagating values across an async execution flow, much like Node.js's AsyncLocalStorage. However, when building this capability into the web platform we must consider the integration with web APIs – should setTimeout propagate the async context from the point it is called into the callback? What about event registration?

Furthermore, Chrome has been working on associating script-initiated actions from their causes further up the async call stack (tracking a task's attribution), which is useful browser-internally to enable metrics and web API improvements that would not be possible otherwise. Task attribution is the same as propagating browser-internal values across an async execution flow, so if we can ensure all of the task attribution use cases are covered by AsyncContext, the former could be built on top of the latter, in the specs and in browser engines.

Get feedback from browser vendors and other interested parties as to which web APIs should propagate the async context.

• W3C Calendar

• Session proposal on GitHub

Hiroki Endo

A huge amount of media content is produced every day, including TV and radio programs, ebooks, and news articles. These are provided through various online distribution and broadcasting services.

However, the reach of such content is limited by the means of provision. This reduces the opportunity for users to access information.

Content providers expect that content will be widely distributed among media industries and other industries such as tourism, education and health care, thus creating an ecosystem in which users consume various types of media content through their daily life.

In this session, we will share use cases and challenges where media content is utilized across services and industries and consider how metadata can facilitate an advanced and evolving collaboration among media industry.

The focus of the session will be on the possibilities of utilizing metadata across industries and its challenges by sharing ideas from different media industries. Technical discussion such as metadata formats, schemas and ontologies within and outside of the W3C is positioned as a future activity.

Share the use cases and issues where media content utilizes metadata to distribute across industries, and identify hints for future cooperation across the media industry

• W3C Calendar

• slides

• minutes

• Session proposal on GitHub

Dmitri Zagidulin, nightpool ., James Gallagher

Continuing the SocialWeb Test Suite discussion, including test suite challenges and strategies, as well as demos of the in-progress test suite approaches.

Apprise the SocialWeb developer community of the current test suite status

• W3C Calendar

• minutes

• Session proposal on GitHub

Sangwhan Moon, Lea Verou, Daniel Appelquist

Powerful APIs have been 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 application runtimes such as Electron becoming popular, the potential and user needs of this is clear - but how we can deliver such functionality while providing the security and privacy guarantees of a browser remains an unsolved problem.

As a simple 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 serious applications against. Is there a path where we can have a standardized replacement for Electron, and if so, what kind of fundamental architectural changes would that entail?

This session would like to invite members of the community who are interested in contributing towards a solution to this. Of the participants, 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 problem space, and compile a set of principles 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 current or former members of the TAG.

The task force would be identifying ways to bridge the gap between the Web Platform and native application 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 need to ensure this effort has multi-stakeholder interest, while ensuring cross-browser and platform support.

Solicit feedback on problem space, iterate on focus area for task force, and recruit participants.

• W3C Calendar

• slides

• minutes

• live google doc minutes

• Session proposal on GitHub

Tab Atkins Jr.

Compare the current spec of CSS Anchor Positioning and the alternative proposal by Apple, list the individual issues where the current spec can be improved, and try to reach consensus or resolve those issues.

Close the gap between the current spec and the proposal as much as possible.

Agenda

• W3C Calendar

• minutes

• Session proposal on GitHub

Reinaldo Ferraz, Diogo Cortiz, Hartmut Richard Glaser

ePub format is a powerful open web technology for digital books. Considering the standard's possibilities, digital books can be more interactive and provide different experiences without letting accessibility best practices out of this scenario.

In this session, we will present some experiments with ePub books and discuss the potential of ePub technology and the challenges and opportunities for publishers and users. Participants are welcome to present experiments to enrich the discussion.

To facilitate the discussion, we will work with three main questions the participants can discuss.

• How a more interactive book can improve or get worse the publication accessibility?

• What are the challenges and opportunities for publishers in this field?

• How can authors explore this kind of experience in digital books?

Post-TPAC note: No minutes were taken at this session.

The session aims to share use cases and best practices about the ePub technology and discuss the challenges and opportunities for developers, publishers, and users. We encourage people to submit experiments to a showcase platform.

• W3C Calendar

• slides

• Session proposal on GitHub

Dmitri Zagidulin, nightpool ., James Gallagher

Coordination discussion for exporting and importing SocialWeb data, including accounts, contacts and social graphs, posts and other content, bookmarks, lists, and various metadata.

Identify use cases and coordinate timeline

• W3C Calendar

• minutes

• Session proposal on GitHub

Ege Korkan

Home Assistant is a smart home platform with a very strong community. The W3C Web of Things standards can be used within Home Assistant in different ways and bring two communities together with the following potential benefits:

• Easier integration of future IoT devices to Home Assistant

• Cross Ecosystem Communication

• Other ways to communicate with Home Assistant

• Getting wider feedback and use cases for WoT standards

There is interest for this session by @mmcool, @joshco and @relu91. We will decide later for co-chairs.

WoT integration proposals to Home Assistant

• W3C Calendar

• slides

• minutes

• Session proposal on GitHub

Harry Wang, Selen Xu

Haptic feedback technologies, which stimulates the users' sense of touch through vibration, motion, and forces, has enormous potential to make digital experiences more enriching and accessible.

In this session, we will explore the current state of haptics technology and dive into its applications for improving user experiences and accessibility in various digital contexts. We will also discuss the challenges and opportunities in integrating haptic technologies into WebApps and Native Apps.

Topics may include:

• Current status of haptics APIs, hardware capabilities, and global standardization efforts in this field;

• Experimental exploration in using haptics to convey non-visual information/experiences, such as directional navigation, notifications, etc;

• Design considerations for using haptics in a way that works for diverse users and latest research achievements;

We welcome everyone to participate in this brainstorming session to explore how to make full use of haptic technologies and benefit the community.

See Intro video

The session aims to 1) share use cases, best practices, and innovative approaches about haptic technology and its potential; 2) discuss opportunities and challenges in standardizing haptics for Web, the possibility to offer a new sensory channel for accessibility; 3) create a platform for collaboration and communication, to encourage adoption of the haptic technologies.

• W3C Calendar

• slides

• minutes

• Session proposal on GitHub

Daniel Appelquist

This session will be a precursor to our upcoming workshop, Secure the Web Forward, which aims to increase the overall security of web applications by addressing the need for clear, guidelines for web developers, identifying key emerging technologies and gaps.

Potential discussion points include:

• the web developer security issues that were highlighted in the recent survey

• encouraging collaboration between web standards and open-source security initiatives

• better documentation and guides for web developers

• updates in commonly used libraries and web standard APIs

• potential for a new security-focused task force between W3C and other organisations focusing on software security such as the OpenSSF, OWASP and OpenJS Foundations

Raise awareness of the different aspects of the security topic, get people talking to each other, raise awareness of the upcoming workshop

Agenda

• W3C Calendar

• slides

• minutes

• Session proposal on GitHub

Reilly Grant, Jeffrey Yasskin

Most popular user agents support “enterprise management” features which gives device owners control over the user agent. These features can modify the user-facing behavior of the user agent, such as by automatically configuring bookmarks or the home page, or by disabling features such as integrated developer tools. They may also affect web-exposed behavior of the user agent such as by automatically granting or denying permissions. Recent incubations have also proposed new APIs which would only be exposed to sites when running on a managed browser.

Explore how to approach standardization when these management features have web-exposed behavior.

• W3C Calendar

• slides

• minutes

• live google doc minutes

• Session proposal on GitHub

Thomas Steiner, Diego Gonzalez-Zuniga, Kenneth Christiansen, Marcos Caceres

In the first part of this session, the various browser vendors and browser contributors discuss their current understanding and implementation status of the concept of Installable Web Apps, including, but not limited to and not requiring, prerequisites for enabling "powerful features".

A stretch goal would be to get aligned on nothing less than the cross browser future of Installable Web Apps, per Web Manifest and related standards. A more realistic goal is the continuation of a dialog on the matter, and getting everyone at the same table as to potential areas of future standardization.

Agenda

• W3C Calendar

• slides

• minutes

• live google doc minutes

• Session proposal on GitHub

Khushal Sagar

View Transitions allows developers to create animated transitions for DOM changes. The spec currently defines the feature for DOM changes within the same Document but we're actively working on extending this to cross-document navigations.

This session would go into the details of concepts being added for View Transitions on cross-document navigations and a few other extensions/feature requests we're evaluating.

Feedback on API shape for cross-document View Transitions

• W3C Calendar

• slides

• minutes

• Session proposal on GitHub

Kazuyuki Ashimura

In 2021, W3C organized a workshop on Smart Cities, and identified the stakeholders around Smart City standardization and reasonable applications for Smart City technologies. In addition, we got initial input on how to organize the draft Charter for a potential Interest Group for further discussions.

Then in 2022, based on the the workshop results, we organized a breakout session during TPAC 2022 with invited key stakeholders from related SDOs, e.g., ECHONET, IPA DADC, IEC SC3D, ISO/IEC JTC1 WG11, ITU-T SG20 and OGC.

During the session, we saw related SDOs' standardization activities so far, and identified the following:

• "Digital Twins" should be the key concept for Smart Cities standardization.

• Web standards, e.g., Web of Things (WoT), Decentralized Identifiers (DID) and Verifiable Credentials (VC), should be considered as possible key modules for the possible Web-based Digital Twins framework.

• Standard vocabulary for semantic interoperability is also required for the platform.

• Collaboration by related SDOs is necessary for further discussion, and W3C should become the central hub for the discussion given Web standards play very important roles.

Based on the discussion so far, we've been discussing how to improve the draft Charter of the proposed Web-based Digital Twins for Smart Cities Interest Group, and would like to get input during this session at TPAC 2023 to finalize the draft Charter.

Following the breakout discussion during TPAC 2022, we'll summarize the discussion around Smart Cities within W3C so far, share the latest draft Charter for the proposed Web-based Digital Twins for Smart Cities IG, and get input from stakeholders for the proposed IG to finalize the draft Charter

Agenda

• W3C Calendar

• slides

• minutes

• Session proposal on GitHub

Peter Thatcher

You can encode and decode using WebCodecs. But how do you send the encoded media over the network? You need to serialize it first. A container format like CMAF is overkill. If you're interested in WebCodecs and would like to send encoded media over the network is a lightweight way, come to this breakout room.

• Related interest in a WebCodecs MoQ Media Format in the IETF

• Related Open Screen Protocol work

See who is interested; Figure out requirements; Maybe discuss high-level solutions

• W3C Calendar

• minutes

• Session proposal on GitHub

Pierre-Antoine Champin, Ege Korkan

A large variety of schema languages exist, defined inside or outside of W3C; to name a few: [RDF-Schema], [OWL], [SHACL], [ShEx], [XML-Schema], [JSON-Schema]... Each of these languages have been favored by different categories of users, who in turn ignore, neglect, sometimes even despise the other languages, deemed "too complicated", "less powerful" or simply "not fit for purpose".

It might be tempting to consider that any schema language is worth any other, and that the "best" one is a matter of technological preferences. We argue on the contrary that these languages differ in their core purpose, and should be seen as complementary rather than competitors. More precisely:

• ontology languages such as [RDF-Schema] and [OWL] focus on the conceptual modelling of the domain,

• shape languages such as [SHACL] and [ShEx] focus on the logical modelling of the data,

• structural schema languages such as [XML-Schema] and [JSON-Schema] focus of the physical modelling of exchange formats.

Sticking to one schema language to cover all these aspects is therefore suboptimal. Creating bridges between their user communities, to allow cross-fertilization and combined use, is a promising approach.

But it is also challenging, because it creates the need to maintain consistency across schemas at different levels. We will present different tools and methods that have been proposed to deal with this problem, and discuss the standardization opportunities in this area.

[RDF-Schema]: https://www.w3.org/TR/rdf-schema/

[OWL]: https://www.w3.org/TR/owl2-primer/

[SHACL]: https://www.w3.org/TR/shacl/

[ShEx]: http://shex.io/shex-primer/index.html

[XML-Schema]: https://www.w3.org/TR/xmlschema-1/

[JSON-Schema]: https://json-schema.org/specification.html

We will discuss the complementarity of various schema languages, and which tools are available (or missing...) to make them work together.

• W3C Calendar

• slides

• minutes

• Session proposal on GitHub

Christopher Cameron

Discussion rendering of existing HDR content (images/video), proposed HDR APIs (canvas/WebGL/GPU), the need for more expressive media queries, and interactions with CSS colors.

Slides.

Specific issues:

• Review of definitions of HDR displays and HDR content

• Standardize rendering of HDR content (issue)

• Add CSS property to limit HDR brightness (issue, proposal)

  • Default behavior for HDR content (no issue)

• More expressive queries about HDR screen capabilities (issue)

• WebGPU HDR support

  • Extended range support (proposal)

  • Tone mapped support to match HLG and PQ (no issue filed)

• 2D Canvas and WebGL HDR support

  • WebGL floating point support (drawingBufferStorage proposal)

  • 2D Canvas and ImageData floating point support (issue, proposal)

  • 2D canvas HDR support (proposal), or alternatively use same metadata from WebGPU proposal

Continue to converge on a vision for High Dynamic Range (HDR) on the web.

• W3C Calendar

• slides

• minutes

• Session proposal on GitHub

Diego Gonzalez-Zuniga

We will discuss about options to install applications using the web platform. API? Install banners? cross platform support? tracking campaign ids? Let's discuss what installation on the web looks like.

Aligning views on installing apps from the web

• W3C Calendar

• minutes

• Session proposal on GitHub

Naomi Yoshizawa

A breakout session to report on the progress of the member relations program offered by W3C to its members. Panelists and participants will discuss how W3C can contribute to the community of the members.

• Do members want country or region-specific networking?

• Any issues when you joined?

• What is "Ambassador"? What is the environment in which they are created?

• Mutual aid among members?

• What support would members like W3C to provide?

• What do we want Chapters for members?

W3C Member Relations will give shape to ideas from the members and return them to the members.

Agenda

• W3C Calendar

• slides

• minutes

• Session proposal on GitHub

Elika Etemad

W3C specifications use a common set of stylesheets and markup conventions, which are documented at https://www.w3.org/StyleSheets/TR/2021/README and maintained at https://github.com/w3c/tr-design (Bikeshed and ReSpec output this format.)

In this breakout session we will:

• Do a quick review of what capabilities are already built into our site-wide CSS and HTML conventions, so that you can use them effectively (and avoid custom styles)

• Discuss when to put custom styles in your own CSS vs when to upstream them for everyone

• Answer questions about our technical report styling and templates

• Discuss possible improvements, and maybe draft some up!

Part 1: Educate editors and Team Contacts; Part 2: Design and code improvements

• W3C Calendar

• minutes

• Session proposal on GitHub