Standards

From MozillaWiki
Jump to: navigation, search

Contents

Welcome to Mozilla’s standards participation page.

Web standards are the technologies web developers use to build websites, are supported by Firefox and other browsers, and are developed in open standards groups. This page serves as a directory of standards organizations and working groups that Mozilla contributes to.

The lists below are organized alphabetically by standards body and working group (if any), with Mozilla participants and specifications they edit/author/contribute to.

If you’re a Mozillian actively & directly participating in a standards body (working group email list, IRC, wiki, and/or f2f meetings), please add yourself to the specific standards body / working group if any), linking to your wiki User: page. If you’re working in multiple working groups or standards organizations, add yourself to each.

Web Standards Coordination

General Participation Guidelines

If you'd like to participate in some of these groups, or at least watch, learn, get up to speed, you can almost always do so by lurking on the public IRC channels and mailing lists that the groups use. Many (most?) standards mailing lists can often be overwhelming in quantity, depth so start with IRC as that's often lighter-weight and easier to watch for quick bits of info/knowledge.

  • Most W3C participation uses GitHub.
    • Create an account, if you don't already.
    • Substantive contributions to W3C specifications are checked by a bot that verifies that you have made the appropriate IPR contributions. Mozilla employees (both corporation and foundation) can request an invitation to the mozilla-standards group on GitHub on the `#standards` slack channel. Membership in this group signals to the W3C bot that Mozilla's IPR commitments cover your contributions by virtue of your employment.
  • Get on Matrix to:
  • Get an IRC client to:
    • Set up a connection to and nickname for irc.w3.org but specifically port 6665 (unprotected, no nickname registration).
    • You may also use W3C IRC’s Web UI: http://irc.w3.org/
  • Get on IndieWeb Chat (IRC, Matrix, or Slack) to:

Ecma International

TC39

Participants:

Specifications: ECMA-262

TC39 - TG2 (Internationalization)

Participants:

Specifications: ECMA-402

IETF

Coordination: Martin Thomson

CALEXT (iCalendar)

HTTP / MASQUE

  • Valentin Gosu

MLS / MIMI

  • Benjamin Beurdouche

PPM (Distributed Aggregation)

  • Simon Friedberger

RTCWEB / MMUSIC

TLS / CFRG

  • Dennis Jackson
  • John Schanck
  • Benjamin Beurdouche

Web Transport

ISOC Advisory Council

Please contact Martin Thomson for any inquiries.

Khronos

WebGL

microformats

https://microformats.org/ and microformats wiki

Community participants:

Specifications:

  • rel=me — used in Mastodon etc. distributed ✅ verification
  • ... and many others.

OWF

http://openwebfoundation.org/

Specifications:

W3C

The W3C (World Wide Web Consortium) has Working Groups (WGs), Interest Groups (IGs), and Community Groups (CGs). See below for details and please add any/all of such groups here in alphabetical order by working group name.

For the sake of focus and brevity, only W3C WGs are listed here inline, along with any complementary IGs or CGs that are paired with them.

Community and Interest Groups

Main article: Standards/w3c-interest-community-groups

W3C CGs or IGs not tied directly to an active WG are documented on a separate page:

Advisory Board

W3C Advisory Board (AB) — elected members

The AB drives W3C process improvements in these groups:

Process Community Group

W3C Process Community Group publicly discusses (wiki, GitHub repo, list), proposes, and makes changes to the W3C Process. Delegated authority from the AB (some members of which overlap with the CG), which retains overall (dis)approval of W3C Process iterations before proposing to the AC.

Vision Task Force

https://www.w3.org/groups/tf/vision/

Advisory Committee

See Advisory Committee Representative Directory (W3C Member-only link) for who else is an AC Rep from which other organizations.

ARIA Working Group

ARIA Working Group homepage and Participants:

Audio Working Group

http://www.w3.org/2011/audio/ and Participants:

The Audio Working Group works in conjuction with the Audio Community Group:

Audio Community Group

https://www.w3.org/community/audio-comgp/ — Participants:

Media Working Group

https://www.w3.org/groups/wg/media — participants:

Audiovisual Media Formats for Browsers Community Group

https://www.w3.org/community/av4browsers/ — participants:

Browser Testing and Tools Working Group

Browser Testing and Tools Working Group homepage, Charter, Mailing list, Mailing list archive. Participants:

Specifications:

  • WebDriver - APIs for remote controlling web browsers
  • (link?) APIs for use in debugging of web applications

CSS Working Group

Cascading Style Sheets Working Group (CSSWG), members, irc, email list

  • Looking for where we prioritize our CSS development? See: CSS:Priorities

Working group members participating on behalf of Mozilla (also on w3c-css-wg)

Additional www-style list participants related to Mozilla (anyone is welcome to join)

Specifications:

For more details see: CSS

GPU for the Web Working Group (WebGPU)

https://github.com/gpuweb/gpuweb — participants:

Everyone listed above is also in the CG below:

GPU for the Web Community Group

https://www.w3.org/community/gpu/ — The following are only in the CG:

  • Erich Gubler (:egubler)
  • Nicolas Silva (:nical)
  • Teodor Tanasoaia (:teoxoy)

Internationalization Working Group

Internationalization Working Group (members), part of Internationalization Activity (i18n)

  • Eemeli Aro
  • Erik Nordin

Pointer Events Working Group

Pointer Events Working Group home page (members). Participants:

Service Workers Working Group

Service Workers Working Group home page (members). Participants:

SVG Working Group

SVG (Scalable Vector Graphics) Working Group, charter expired and WG in-limbo, members. Participants:

  • Jonathan Watt

Specifications: SVG 1.1, SVG 2.0

Web Applications Security Working Group

Participants:

  • Frederik Braun
  • Christoph Kerschbaumer
  • Daniel Veditz
  • Paul Zühlcke
  • Simon Friedberger

Specifications: CSP, Mixed-Content Blocking, SRI, Permission Policy, HTML Sanitizer

Security Web Application Guidelines Community Group

Participants:

  • Frederik Braun

Web Applications Working Group

WebApps WG home page — (members) — participants:

Related incubator group: Web Platform Incubator Community Group

WebAssembly Working Group

WASM:

WebAssembly Community Group

https://www.w3.org/community/webassembly/ (members)

  • Ryan Hunt

Web Authentication Working Group

WebAuthn homepage

Web Editing Working Group

Web Editing WG participants

Web Fonts Working Group

Web Fonts Working Group homepage (members)

  • Jonathan Kew (former editor)

Web Payments Working Group

Web Payments Working Group homepage (members)

  • No one from Mozilla currently.

Web Performance Working Group

https://www.w3.org/webperf/

  • Benjamin De Kosnik
  • Sean Feng

Specifications: Navigation Timing, Paint Timing, Event Timing, Element Timing

Specifications: DOM-adjacent Specifications: Timing control for script-based animations (requestAnimationFrame)

WebRTC Working Group

WebRTC (Web Real Time Communications) Working Group

W3C home page

Specifications:

WebTransport Working Group

WebTransport Working Group

  • Jan-Ivar Bruaroey (co-chair)
  • Randell Jesup (:jesup)
  • Martin Thomson

Specifications: WebTransport

Specifications: Media Capture Stream with Worker Extensions mediacapture-worker APIs

Portable Network Graphics Working Group

https://www.w3.org/groups/wg/png/

Please contact Tantek Çelik if you have specific needs here and I’ll route your request as needed. -t

Technical Architecture Group

  • No current Mozilla participants.

Please contact Tantek Çelik if you have specific needs here and I’ll route your request as needed. -t

WHATWG

Main article: WHATWG

other

Alliance for Open Media (AOM)

The Alliance for Open Media develops next-generation media formats, codecs, and technologies. See also #NETVC.

CA/Browser Forum

The CA/Browser Forum produces standards in the area of best practice and validation for certificate authorities.

  • Kathleen Wilson
  • Ben Wilson

CalConnect

Mozilla is a member of CalConnect, The Calendaring and Scheduling Consortium, which is not actually affiliated w/ IETF or W3C but in practice drives development and interoperability testing of IETF specs:

See their Index to Calendaring and Scheduling Standards for other specific standards that CalConnect is involved with.

eIDAS Regulation

The eIDAS Regulation places requirements on electronic identification and trust services. Our goal is to keep the TLS requirements/framework separate and independent from eIDAS and Qualified Website Authentication Certificates (QWACs).

OASIS

  • No current Mozilla point of contact

XMPP

Mozilla is not formally associated with the XSF but has representation indirectly. http://xmpp.org/

  • No direct involvement by any current Mozillian

C++

C++ is standardized by ISO/IEC JTC1/SC22/WG21 (informally, the "C++ Standards Committee"). All proposals are publically available here.

Botond Ballo is a member of Canada's delegation to the Committee, and has been attending meetings regularly since September 2013. If you have any feedback about any existing proposal, or would like to explore the idea of putting forth a new proposal, please post to dev-platform and cc Botond.

FIDO Alliance

Mozilla is a member of the FIDO Alliance, which produces hardware specifications for Web Authentication.

Emeritus

Main article: Standards/emeritus

See: Standards/emeritus for lists of former Mozillians who worked on standards, and former standards groups or organizations.

subpages of Standards

See Also