Standards: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (Adding myself to the FIDO group)
(→‎WebRTC Working Group: added Karl Tomlinson)
Line 267: Line 267:
* <span class="h-card">Paul Adenot</span>
* <span class="h-card">Paul Adenot</span>
* <span class="h-card">Jan-Ivar Bruaroey</span>
* <span class="h-card">Jan-Ivar Bruaroey</span>
* <span class="h-card">Karl Tomlinson</span>


Specifications: Media capture & [http://www.w3.org/2011/04/webrtc-charter.html streaming APIs]
Specifications: Media capture & [http://www.w3.org/2011/04/webrtc-charter.html streaming APIs]

Revision as of 21:31, 19 August 2022

Welcome to Mozilla's standards participation page.

This is a directory of standards organizations and their working groups, listing who at Mozilla is working with each.

For a technology summary see the technologies page, for Mozilla’s positions on particular specifications, see:

Current discussions of Mozilla positions:

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.

Thanks!

— Tantek

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.

Ecma International

ECMA-402

TC39

Specifications: ECMAScript 5, 5.1, 6, Harmony, etc.

IETF

ADD

  • Martin Thomson
  • Eric Rescorla

CALEXT (iCalendar)

  • Philipp Kewisch

DISPATCH

  • Martin Thomson
  • Eric Rescorla

HTTPbis

  • Martin Thomson
  • Dragana Damjanovic

QUIC

  • Martin Thomson
  • Eric Rescorla

RTCWEB / MMUSIC

  • Randell Jesup
  • Eric Rescorla (EKR)
  • Martin Thomson
  • Maire Reavy

STIR

  • Eric Rescorla

TLS (SSL)

  • Martin Thomson
  • Eric Rescorla

UTA

  • No one from Mozilla currently.

WebPush

  • Martin Thomson

ISOC Advisory Council

Please contact Martin Thomson for any inquiries.

RFC Editor Future Development Program

  • No one from Mozilla currently.

RFC Series Oversight Committee

  • No one from Mozilla currently.

Khronos

WebGL

microformats

https://microformats.org/ and microformats wiki

Community participants:

Specifications:

  • hCard - implemented in Firefox DOM
  • hCalendar - implemented in Firefox DOM
  • ... 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 the:

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.

Advisory Committee

See Advisory Committee Representative Directory for who else is an AC Rep from which other organizations.

Audio Working Group

Participants:

  • Matthew Gregan
  • Paul Adenot (Spec Editor)

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

Audio Community Group

Media Working Group

Browser Testing and Tools Working Group

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

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 WG/CG (WebGPU)

https://github.com/gpuweb/gpuweb

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:

SVG Working Group

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

  • Jonathan Watt

Specifications: SVG 1.1, SVG 2.0

Web Applications Security Working Group

  • Frederik Braun
  • Christoph Kerschbaumer
  • Eric Rescorla
  • Daniel Veditz
  • Tanvi Vyas

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

Web Applications Working Group

WebApps WG home page — (members)

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

  • Dan Veditz

Web Fonts Working Group

Web Fonts Working Group homepage (members)

  • Jonathan Kew (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

  • Maire Reavy
  • Eric Rescorla (EKR)
  • Randell Jesup (:jesup)
  • Paul Adenot
  • Jan-Ivar Bruaroey
  • Karl Tomlinson

Specifications: Media capture & streaming APIs

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

Portable Network Graphics Working Group

(in the process of being chartered)

Second Screen Working Group

http://www.w3.org/2014/secondscreen/ (members)

Technical Architecture Group

Tracking Protection Working Group

http://www.w3.org/2011/tracking-protection/

  • 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.

  • Daniel Nazer (Mozilla's representative on AOM's Board)
  • Jon Bauman (AVIF, Storage and Transport Working Group)

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:

  • RFC 5545 iCalendar (obsoletes RFC 2445).
  • RFC 4791 CalDAV Access protocol

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).

  • Ben Wilson
  • Kathleen Wilson
  • Raegan MacDonald
  • Thyla van der Merwe
  • Udbhav Tiwari

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.

  • Dan Veditz

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

Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Standards&oldid=1243687"