WinterTC

• Upcoming
• Tentative
• Breakout Sessions

Web platform APIs are typically specified having web browsers as their main target. However, there is a large set of JavaScript runtimes that benefit from having a common API surface with the web platform.

WinterTC is a new Ecma Technical Committee focused on the needs of such runtimes, particularly in the server side. This TC is an evolution of the previous WinterCG W3C Community Group, to focus on standardizing a minimum subset of the web platform APIs that all such runtimes would support (the WinterTC Minimum Common API).

Aside from publishing its own standards, however, WinterTC also aims to propose changes to existing W3C and WHATWG standards to better support the needs of server-side runtimes. For example, in browsers, origins are a fundamental security primitive, and it makes sense that, for example, the fetch() API has cross-origin restrictions. But since server-side runtimes don't have this security primitive, these restrictions are unnecessary in such environments, which is why they all willingly violate the spec. WinterTC aims to fix this in the web standards by adding conformance modes for server-side runtimes.

Agenda

Chairs:
Andreu Botella

Description:
Web platform APIs are typically specified having web browsers as their main target. However, there is a large set of JavaScript runtimes that benefit from having a common API surface with the web platform.

WinterTC is a new Ecma Technical Committee focused on the needs of such runtimes, particularly in the server side. This TC is an evolution of the previous WinterCG W3C Community Group, to focus on standardizing a minimum subset of the web platform APIs that all such runtimes would support (the WinterTC Minimum Common API).

Aside from publishing its own standards, however, WinterTC also aims to propose changes to existing W3C and WHATWG standards to better support the needs of server-side runtimes. For example, in browsers, origins are a fundamental security primitive, and it makes sense that, for example, the fetch() API has cross-origin restrictions. But since server-side runtimes don't have this security primitive, these restrictions are unnecessary in such environments, which is why they all willingly violate the spec. WinterTC aims to fix this in the web standards by adding conformance modes for server-side runtimes.

Goal(s):
Explore the collaboration between W3C/WHATWG and WinterTC, including adding support in W3C/WHATWG specs for the needs of server-side runtimes.

Materials:

• Session proposal on GitHub

Joining Instructions

Instructions are restricted to W3C users . You need to log in to see them.

Export options

Personal Links

Please log in to export this event with all the information you have access to.

Public Links

The following links do not contain any sensitive information and can be shared publicly.

• Download as ics