The MiniApps Ecosystem Community Group provides a forum for the global community to discuss, incubate, and propose MiniApp-related standard ideas to bring more interoperability and robustness to the MiniApp ecosystem.
MiniApp as a new form of mobile application, leveraging both Web technologies (especially CSS and JavaScript) as well as capabilities of native applications, is gaining more and more popularity in Asian countries such as China. To enhance the interoperability between different MiniApp platforms (AKA the super application or host application), mainstream MiniApp vendors have been working together in W3C Chinese Web Interest Group since May 2019 and published a MiniApp Standardization White Paper in September 2019 as the initial standardization exploration for MiniApp technologies.
As more global companies get interested in joining the MiniApp-related discussion, the MiniApp Ecosystem Community Group was proposed and approved during TPAC 2019 so the global Web community can join the discussion.
The MiniApp Ecosystem Community Group aims to discuss proposals for MiniApp features that would benefit the interoperability and robustness of the MiniApp ecosystem, including:
The group does not intend to discuss ideas related to the MiniApp platform operation.
Based on the MiniApp Standardization White Paper and previous discussion in the W3C Chinese Web Interest Group, the following projects have been proposed as initial standardization exploration of MiniApp.
New projects or status changes are communicated to the group through the public mailing list. Chairs and editors should publish status updates to the public mailing list to allow group participants to monitor progress without having to watch every repo directly.
It is anticipated that the group will collaborate with appropriate W3C Working Groups and WHATWG work streams in order to transition spec proposals to the Recommendation or Living Standard track. This group will probably get into collaboration with the following groups:
The group operates under the Community and Business Group Process. Terms in this charter that conflict with those of the Community and Business Group Process are void.
As with other Community Groups, W3C seeks organizational licensing commitments under the W3C Community Contributor License Agreement (CLA) (Proposals in this Community Group charter are applicable "Specification" in the CLA). When people request to participate without representing their organization’s legal interests, W3C will in general approve those requests for this group with the following understanding: W3C will seek and expect an organizational commitment under the CLA starting with the individual’s first request to make a contribution to a group deliverable. The section on Contribution Mechanics describes how W3C expects to monitor these contribution requests.
The group tends to have monthly teleconferences and conducts its work on the public mailing list public-miniapps@w3.org as well as its GitHub repository for technical discussions. Other communication tools are allowed if a considerable number of the group participants decide to embrace them.
Membership of the group is open to everybody but all participants will have signed the W3C Community Contributor License Agreement. Chairs and editors of feature proposals must ensure that no contributions are adopted from anyone who is not a member of the Community Group.
Specifications created for proposals in the Community Group must use the W3C Software and Document License.
All Github repositories attached to the Community Group must contain a copy of the CONTRIBUTING and LICENSE files.
Note: this CG will not use a contrib mailing list for contributions since all contributions will be tracked via Github mechanisms (e.g., pull requests).
This group will seek to make decisions when there is consensus. Consensus will be recorded through meeting minutes or its GitHub repo issue list with assistance from the Chairs.
Any technical specification that is planned to be proposed to a W3C Working Group should require:
This Charter can be amended by the Chairs with consultation of the Community Group.
The following table lists details of all changes from the initial Charter.
| Charter Period | Start Date | Changes |
|---|---|---|
| Initial Charter | 5 December 2019 | N/A |
| Charter Update | 6 November 2023 |
|