MiniApp Packaging

[xfq]

Wotcher TAG!

I'm requesting a TAG review of MiniApp Packaging.

A MiniApp Package is a ZIP-based container file that wraps a set of files (JS code, components, resources, configurations, styles) comprising the whole MiniApp.

• Explainer¹ (minimally containing user needs and example code): https://github.com/w3c/miniapp-packaging/blob/main/docs/explainer.md
• Specification URL: https://www.w3.org/TR/miniapp-packaging/
• Tests: https://github.com/w3c/miniapp-tests
• User research: None.
• Security and Privacy self-review²: https://github.com/w3c/miniapp-packaging/blob/main/docs/security-privacy-questionnaire.md
• GitHub repo (if you prefer feedback filed there): https://github.com/w3c/miniapp-packaging/
• Primary contacts (and their relationship to the specification):
  • Martin Alvarez-Espinar (@espinr, Huawei, editor)
• Organization(s)/project(s) driving the specification: Huawei
• Key pieces of existing multi-stakeholder review or discussion of this specification:
• External status/issue trackers for this specification (publicly visible, e.g. Chrome Status):

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• Relevant time constraints or deadlines: CR in November 2022
• The group where the work on this specification is currently being done: W3C MiniApps WG
• Major unresolved issues with or opposition to this specification:

We'd prefer the TAG provide feedback as (please delete all but the desired option):

🐛 open issues in our GitHub repo for each point of feedback

[xfq]

Thanks for reviewing this spec! We are discussing possible solutions in w3c/miniapp-packaging#64 . It might be useful to organize a meeting between some members of the MiniApps WG and the TAG to discuss possible solutions. WDYT, @ylafon, @torgo, and others?

/cc @espinr

[torgo]

Noting w3c/miniapp-packaging#64 (comment) which we discussed in today's call.