W3C

– DRAFT –
MiniApps WG Call

23 September 2021

Attendees

Present
Aaron_Wentzel, Angel, Canfeng_Chen, changhao_liang, Martin_Alvarez, max, Ming_Zu, QingAn, Tengyuan_Zhang, tomayac, Wenli_Zhang, xfq, yanyumeng, Zitao_Wang
Regrets
-
Chair
Zitao_Wang
Scribe
xfq

Meeting minutes

https://github.com/w3c/miniapp/tree/gh-pages/specs#wg-documents

Lifecycle

Zitao_Wang: issues and PRs

https://github.com/w3c/miniapp-lifecycle/issues/15

Zitao_Wang: the TAG gave us feedback

QingAn: sent a PR

https://github.com/w3c/miniapp-lifecycle/pull/16/files

Zitao_Wang: maybe you can restructure this document
… @@
… mapping to existing Web specifications such as Service Workers and Page Visibility

QingAn: I can add some text about relationship with Manifest in the Abstract

QingAn: any thoughts?

xfq: We did not document the installation process in the document

martin: In the Manifest spec we have the "start page" as launch page. In the Packaging spec, we include the algorithm to fetch and load/launch a MiniApp. We can include cross references among specifications.

QingAn: do you think we should add some text in Packaging first?

martin: should link to Packaging and perhaps the other way around
… indicating the algorithms are in the other spec
… I volunteer to do it next week

TAG feedback 3: "It doesn't look like you're referencing ServiceWorker either - is there a Miniapp state which makes use of ServiceWorker?"

QingAn: I will add "Whenever possible, the specification should provide a mapping to existing Web specifications such as Service Workers and Page Visibility." to the Abstract of the spec

Zitao_Wang: I agree

TAG feedback 4: "When a Miniapp is launched what origin can it be said to have, with regard to the web's security model? That would seem to be important from a lifecycle point of view."

QingAn: the origin concept in miniapps is quite different from websites
… any thoughts?

Zitao_Wang: the security of a miniapp is controlled by the hosting platform

Zitao_Wang: I'm not very sure if we need to reflect this in the Lifecycle spec

QingAn: we need somewhere to say the super app or the OS should be responsible to check the app's origin and security
… could be in the explainer
… not sure it should be in the spec

xfq: it's a valid concern for other specs as well

QingAn: we can update the explainers of the specs
… and add something in the white paper

Zitao_Wang: I agree
… we can reflect it in the white paper

QingAn: we can add this in our white paper revision plan

TAG feedback 5: "We also note that the Page Lifecycle document that you point to as comparison is out of date and itself needs to be updated (in particular to reflect installation via Manifest, which is missing)."

QingAn: I did not find a newer version than the one in the explainer

QingAn: need help from xfq

xfq: I will look into it

Manifest

https://w3c.github.io/localizable-manifests/

Zitao_Wang: we need to add security, privacy, and accessibility sections to all the normative specifications

https://github.com/w3c/miniapp-manifest/pull/33

xfq: I added a pull request template based on Web App Manifest. Can we merge this?

Zitao_Wang: great work

Zitao_Wang: we can add it to other specs

xfq: I'll merge this PR

https://github.com/w3c/miniapp-manifest/pull/29

[martin introduces the changes]

Zitao_Wang: reviewed this
… LGTM
… any objections?

[Silence]

Zitao_Wang: we'll merge it then

martin: thank you

Packaging

https://github.com/w3c/miniapp-packaging/pull/34

martin: mainly editorial changes
… the current status is to assume that we use standard HTML CSS and so on
… we're splitting the spec into the packaging itself and its content
… template, markup etc.
… agree we should include accessibility section
… not very relevant for this spec though
… in my opinion this is solid to move forward
… when we add the accessibility section

Zitao_Wang: I reviewed it
… we agreed to split this spec into two specs
… do you this is mature enough for FPWD?

martin: @@

xfq: we need a CfC

Zitao_Wang: any objection to merging this PR and move it to FPWD?

[Silence]

Widget

https://github.com/w3c/miniapp-widget/issues/2

Canfeng_Chen: We'll add more use cases on more examples of MiniApp platforms

Canfeng_Chen: Regarding the second point, we don’t quite understand what Dan meant

Ming_Zu: Dan is on vacation

TPAC Planning

<Angel> https://www.w3.org/wiki/TPAC/2021/GroupMeetings

https://github.com/w3c/miniapp/issues/172

xfq: TPAC 2021 Meeting Registration is now open

https://www.w3.org/2021/10/TPAC/#participation

xfq: please propose agenda items

xfq: such as the white paper

xfq: will look into the possibility of joint meetings

angel: infoshare
… the miniapps CG will use the second hour of our TPAC meeting time
… Oct 28 2021, 12:00 UTC
… xfq can send the invitation

[Adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 147 (Thu Jun 24 22:21:39 2021 UTC).