11:58:19 RRSAgent has joined #miniapp 11:58:19 logging to https://www.w3.org/2022/10/27-miniapp-irc 11:59:49 xueyuan has joined #miniapp 12:00:51 rrsagent, make log public 12:00:53 present+ 12:00:55 scribe: xfq 12:01:13 martin has joined #miniapp 12:01:18 present+ martin 12:01:30 present+ Zitao_Wang, Dan_Zhou, QingAn 12:01:40 present+ Xiaoping_Zhao 12:02:28 chair: Zitao_Wang 12:03:08 Topic: Lifecycle 12:03:33 qing: trying to solve the issues by PING 12:03:45 ... based on additional comments from zitao and dan 12:03:51 ... I made some changes 12:04:05 ... hopefully we can get some consensus from today's meeting 12:05:08 [QingAn describes the PR] 12:05:32 Meeting: MiniApps WG Teleconference 12:05:48 https://github.com/w3c/miniapp-lifecycle/pull/33 12:06:06 present+ Tianyang_Xu 12:07:34 dan: there's global lifecycle and page lifecycle in MiniApps 12:08:26 qing: how about have some separate section to show the example code? 12:08:37 ... it can include global and page lifecycle 12:08:52 dan: sounds good to me 12:08:59 qing: I'll work on it 12:10:41 https://github.com/w3c/miniapp-lifecycle/issues/35 12:10:48 martin: I commented on the issue today 12:12:41 ... @@1 12:12:42 [martin explains the comment] 12:15:39 dan: MiniApps have an unload lifecycle event 12:16:09 ... developers need it 12:16:40 qing: dan and martin prefer to specify the unload event 12:16:59 ... if there's no objections, I'll move forward 12:17:56 s/... @@1/Following the explainer, we included a destroy event for marking when the app is removed from the system. We can include this state (destroyed/unloaded) but also recommending that user agents should clean the resources after meeting some criteria (time spent in background or resources loaded in memory). 12:18:36 zitao: is it optional? 12:18:56 s/Following the explainer/... Following the explainer 12:19:04 qing: I'd like to add it 12:19:13 zitao: the devs can choose whether to use it or not 12:19:57 Topic: Manifest 12:20:41 3 PRs (https://github.com/w3c/miniapp-manifest/pulls) 12:21:13 https://github.com/w3c/miniapp-manifest/pull/58 (already approved by @xfq) This would close issue #7 (https://github.com/w3c/miniapp-manifest/issues/7) 12:21:13 https://github.com/w3c/miniapp/pull/7 : fix the order of ar_support image's label 12:22:13 martin: already approved by xfq 12:22:30 ... if there's no comments, I think we can merge this 12:22:56 #59 Clarification of differences with Web app manifest (editorial note) https://github.com/w3c/miniapp-manifest/pull/59 Will close issue #54 (https://github.com/w3c/miniapp-manifest/issues/54) 12:22:57 https://github.com/w3c/miniapp/issues/59 : Unicode support for appName 12:22:57 [silence] 12:22:58 https://github.com/w3c/miniapp/pull/54 : add MIME type for 'package' 12:23:23 martin: this is for the privacy review 12:23:43 ... differences between wam and mam 12:24:15 ... editorial changes 12:24:42 zitao: I reviewed this 12:24:54 ... I think it's good 12:25:26 #60 Privacy clarifications while checking app_id Suggestion by privacy review to verify integrity of the app. Added a generic text that links to the digital signatures included in the ZIP container that could help to guarantee the trust chain. https://github.com/w3c/miniapp-manifest/pull/60 Will close issue #55 (https://github.com/w3c/miniapp-manifest/issues/55) 12:25:26 https://github.com/w3c/miniapp/issues/60 : Testing policy 12:25:27 martin: if there's no objection, i'll merge it 12:25:27 https://github.com/w3c/miniapp/pull/55 : add 'ZIP' clarification and other editorials 12:25:45 martin: this is also from the privacy review 12:28:12 ... any comment, or any idea about whether we should modify the constraints? 12:28:25 dan: I have comments on the case folding issue 12:29:00 ... in some dev practise I found some system is case-insensitive 12:29:14 ... this can cause some bug in some developer's systems 12:29:34 martin: the id is for identifying a miniapp 12:32:04 dan: I'll give you some examples 12:32:08 ... I'll comment on the issue 12:33:38 #9 Proprietary extensions of the manifest (https://github.com/w3c/miniapp-manifest/issues/9) My proposal: https://github.com/w3c/miniapp-manifest/issues/9#issuecomment-1240629485 12:33:39 https://github.com/w3c/miniapp/pull/9 : comments from uni-app 12:34:02 martin: this is an old issue 12:34:08 ... I added a proposal 12:34:14 ... similar to web app manifest 12:35:33 ... I don't know if you like this idea, but I think this is a simple solution 12:35:56 ... if ther's no objection, I can close this issue and we can edit the wiki, and add links to it 12:36:12 #43 Consider consolidating MiniApp's app_id with Web App Manifest's id member (https://github.com/w3c/miniapp-manifest/issues/43) 12:36:13 https://github.com/w3c/miniapp-packaging/issues/3 : Discussion of page configuration file 12:36:43 martin: I raised some comments in the WAM repo 12:37:00 ... they're expecting the id to be a URI 12:38:04 ... any comments on this? 12:38:17 ... the app_id is not a URI 12:39:17 zitao: I agree this is the main difference of miniapp's app_id and web app's id 12:39:22 This is the discussion with PWA Manifest: https://github.com/w3c/manifest/issues/1048#issuecomment-1292783565 12:40:22 #56 What sessions are? (https://github.com/w3c/miniapp-manifest/issues/56) Related to one discussion in Lifecycle #35 (https://github.com/w3c/miniapp-lifecycle/issues/35 12:40:23 https://github.com/w3c/miniapp/issues/56 : Do we really need 'app' as the root folder? 12:40:23 https://github.com/w3c/miniapp/pull/35 : editorial fix 12:41:11 martin: we need to clarify what is a session 12:41:29 ... this is covered in the discussion about the Lifecycle 12:41:43 ... once we have the new state, I'll clarify this 12:42:11 ... other issues are still pending 12:43:05 Topic: Packaging 12:43:08 One pull request after privacy review #63 (https://github.com/w3c/miniapp-packaging/pull/63) 12:43:09 https://github.com/w3c/miniapp/pull/63 : Manifest explainer update 12:43:43 martin: it's about file names within the package 12:44:04 ... the guidance is from the i18n WG 12:44:49 ... I mentioned the guidance from i18n WG 12:44:51 This would close issue #61 (https://github.com/w3c/miniapp-packaging/issues/61) 12:44:52 https://github.com/w3c/miniapp/issues/61 : i18n review 12:45:35 ... no big changes 12:45:54 xfq: I think we can merge this 12:46:15 New issue opened this week regarding the TAG review: https://github.com/w3c/miniapp-packaging/issues/64 https://github.com/w3ctag/design-reviews/blob/main/reviews/miniapp_packaging_feedback.md 12:47:55 martin: this is something we need to discuss 12:48:30 ... we don't define any specific mechanism for digital signatures 12:49:04 ... we should clarify how to perserve the origin 12:49:42 ... I propose that we have a meeting with the wpack folks 12:50:05 ... cbor vs zip 12:50:55 ... any comments on this? 12:51:10 zitao: maybe other people don't have time to review this yet 12:51:22 ... maybe we can find a way to address this issue 12:51:30 ... thank you for introducing this 12:52:29 dan: I need to read this after the meeting 12:53:13 Topic: Addressing 12:53:29 dan: no progress 12:53:41 ... I'll update the explainer 12:54:37 Topic: Recharter 12:56:10 dan: I think we should add widget spec to 'other deliverables', but xfq said it should be a normative deliverable 12:58:31 zitao: what do you think, xiaoping? 12:58:38 xiaoping: normative deliverable 12:58:57 zitao: you need to have a relatively mature draft 12:59:47 xiaoping: ok 13:00:20 zitao: about UI component 13:00:37 ... martin, do you think we can add some work about UI component in the WG charter? 13:00:55 martin: I'll do some work this week and next week 13:02:19 Topic: White Paper 13:02:20 https://github.com/w3c/miniapp-white-paper/pull/9 13:02:39 A table with the comparison of MiniApp Components: https://github.com/w3c/miniapp-white-paper/pull/9 13:04:07 zitao: I think it's very cool 13:04:14 ... thank you 13:04:25 [martin introduces the PR] 13:04:55 https://github.com/w3c/miniapp-white-paper/pull/8 13:05:33 martin: some clarification of the text 13:06:17 ... this is from July 13:06:42 ... if there's no comments, we can merge this 13:07:13 Topic: AOB 13:08:00 martin: events in Europe 13:08:10 ... I had some discussions with the w3c spanish chapter 13:08:28 ... they're interested in MiniApps, PWAs, and W3C in general 13:08:51 ... to organise an event about MiniApps and other Web technologies 13:09:04 ... the event is in Spanish, but can include some sessions in English 13:09:12 ... the discussions with them is positive 13:09:24 ... we can discuss this internally 13:09:37 ... I'll share more information with you this week 13:09:46 ... to include more people in the group 13:10:31 Next meeting, November 24 13:10:37 rrsagent, make minutes 13:10:37 I have made the request to generate https://www.w3.org/2022/10/27-miniapp-minutes.html xfq 14:30:51 Zakim has left #miniapp