Timothy Hatcher from Apple and Simeon Vincent of Google, are joined by participants that include employees from Apple, Mozilla, and Microsoft, to create what's called the 'WebExtensions Community Group'.
The group that is also called the WECG, and consists of members from each of the major browser developers, aims to forge a common architecture for future web extensions.
As announced by in W3C a website post:
"With multiple browsers adopting a broadly compatible model for extensions in the last few years, the WECG is excited to explore how browser vendors and other interested parties can work together to advance a common browser extension platform."
The WebExtensions Community Group has two goals:
- Make extension creation easier for developers by specifying a consistent model and common core of functionality, APIs, and permissions.
- Outline an architecture that enhances performance and is even more secure and resistant to abuse.
In order for this to happen, the group aims to specify a model, permissions, and a common core of APIs for web browser extensions.
"By specifying the APIs, functionality, and permissions of WebExtensions, we can make it even easier for extension developers to enhance end user experience, while moving them towards APIs that improve performance and prevent abuse."
"Our work will be guided by a common set of HTML and W3C TAG design principles: user-centered, compatibility, performance, security, privacy, portability, maintainability, and well-defined behavior."
Through the group, members can start "working on a specification."
"We aim to identify common ground, bring implementations into closer alignment, and chart a course for future evolution."
Apple, Google, Microsoft and Mozilla are initiating this community group, and are welcoming other browser makers, extension developers, and interested parties to join this effort.
When joining, the group is to set common guidelines, and not everything under specific rules.
"Each browser vendor will continue to operate independently with their own policies."
"We are not aiming to specify every aspect of the web extensions platform or existing implementations. We want browsers to keep innovating and shipping APIs that may serve as the basis for further improvement of the web extensions platform."
"In addition, we don’t plan to specify, standardize or coordinate around extension signing or delivery. Each browser vendor will continue to operate their extension store fully independently, with their own technical, review, and editorial policies."