11:56:52 RRSAgent has joined #miniapp 11:56:54 logging to https://www.w3.org/2021/12/16-miniapp-irc 11:57:28 Meeting: MiniApps WG/CG Teleconference 11:57:33 present+ 11:57:38 scribe: xfq 11:57:47 rrsagent, make log public 11:57:49 rrsagent, make minutes 11:57:49 I have made the request to generate https://www.w3.org/2021/12/16-miniapp-minutes.html xfq 11:58:44 present+ Dan_Zhou 11:59:27 rrsagent, make minutes 11:59:27 I have made the request to generate https://www.w3.org/2021/12/16-miniapp-minutes.html xfq 12:00:05 present+ tomayac 12:00:17 present+ Zitao_Wang 12:00:31 present+ Yulu_Chao 12:02:19 present+ Qing_An 12:02:43 QingAn has joined #miniapp 12:04:31 angel_ has joined #miniapp 12:05:52 xfq_ has joined #miniapp 12:06:04 present+ Canfeng, angel_ 12:06:18 present+ martin, hax 12:06:23 qing: @@ 12:06:48 ... IoT 12:07:18 ? 12:07:21 q? 12:07:47 present+ yanyumeng 12:08:18 ... ui component 12:08:44 [zitao shares his screen] 12:09:13 zitao: we have solicited feedbak 12:09:29 martin has joined #miniapp 12:09:30 ... would like to reuse w3c esiting standard 12:09:48 ... martin had some comments 12:09:58 ... maybe we can reuse web components 12:10:18 ... i reviewed martin's comments and i think it makes sense 12:10:29 ... think we should move in this direction 12:11:05 ... want to discuss the scope and method with the CG and WG 12:11:15 ... want to hear feedbakc from other vendors 12:12:18 s/w3c esiting standard/existing standards in W3C/ 12:12:56 https://github.com/w3c/miniapp-components/issues/2 12:13:43 martin: The challenges are not limited to these, but here are the more important challenges. 12:14:33 ... should adopt the proposals in the Open UI CG or jump into their discussions 12:15:06 ... another important challenge is that there is overlap with existing html elements 12:15:30 ... some of them are the same, like div 12:16:11 ... If they are really different, the elements could extend the HTML elements using inheritance 12:16:34 ... reuse the attributes and behavior of the existing html elements 12:16:43 ... if they are the same, just adopt HTML 12:17:33 ... Basic MiniApp components with a minimum set of non-standard attributes like disable, focusable.. 12:18:02 ... we can create of a basic, essential MiniappElement that extends the HTMLElement with the specific requirements 12:18:07 ... as the base of all elements 12:18:35 ... the fourth challenge, MiniApp events that are similar to existing standard ones 12:19:20 ... we should adopt the existing standards if we can 12:19:45 ... New events on the MiniApp components (e.g., longpress, swipe…) 12:19:53 ... somewhat controversial 12:20:20 ... i think we can document the use cases to see if they're really necessary 12:20:48 ... if so, we can define new CustomEvents based on the standard DOM interfaces 12:21:08 ... so far we don't have specific features for accessibility in MiniApp components 12:21:21 ... like alternative text for images 12:21:38 ... in this case we adopt existing html css dom standards 12:21:48 ... because they already covered a11y features 12:22:37 ... please feel free to comment 12:22:46 ... we can iterate this 12:23:37 zitao: i think we want to discuss open ui and other related work 12:23:51 ... need to make the gaps and challenges clearer 12:24:30 ... want to call for participation from other miniapp vendors 12:25:46 qing: today in the WG we have three specs in development 12:26:24 ... i think the ui component work is very essential 12:26:34 ... personally i'm in favor of the direction 12:26:53 ... also need to consider the APIs 12:27:07 ... gap analysis on miniapp APIs and web APIs 12:28:02 ... we can incubate the ui component work in the CG 12:28:33 zitao: i solicited feedbak from developers 12:28:52 ... they think our current work is good, but not enough 12:29:03 +1 to analyze the MiniApp APIs/WebAPIs similarities 12:29:04 ... standardized ui component and APIs are useful 12:29:14 ... we can update our white paper 12:30:08 qing: I agree 12:30:16 q? 12:30:20 ... any comment on ui component? 12:31:07 ... we can continue the discussion in github issue 12:31:11 zitao: ok 12:32:13 canfeng: we have further update on the widget requirement 12:32:34 https://github.com/w3c/miniapp-widget/pull/3 12:32:53 ... we have started writing an explainer 12:32:59 ... still a draft 12:33:11 ... contains three parts 12:33:40 ... 1. explain what is a widget 12:33:48 ... @@ 12:34:20 ... hope to upload an initial draft of widget spec before the next meeting 12:35:06 qing: we can look at it before the next meeting 12:35:54 qing: are we satisfied with https://github.com/w3c/miniapp-widget/pull/3 ? 12:36:14 ... dan has expressed her support 12:37:06 +1 12:37:09 zitao: +1 12:37:09 +1 12:37:31 +1 12:39:36 xfq: publish @@ 12:39:58 https://github.com/w3c/miniapp-widget/issues 12:43:56 canfeng: @@ 12:45:11 dan: @@ 12:47:12 dan: i think #2 can be closed 12:47:47 canfeng: checked with yinli about #1 12:47:50 ... it can be closed 12:48:35 s/... it can be closed// 12:49:37 present+ taofengping 12:50:16 +1 Jan 13 12:50:18 next cg call: Jan 13 12:51:17 qing: switch to WG meeting after the break 12:51:25 [10min break] 12:54:15 rrsagent, make minutes 12:54:15 I have made the request to generate https://www.w3.org/2021/12/16-miniapp-minutes.html xfq_ 12:58:01 chair: Qing, Zitao 13:00:41 zitao: wg meeting 13:01:13 ... lifecycle 13:01:31 qing: no big update for lifecycle 13:01:39 ... try to share more in the next meeting 13:01:48 zitao: manifest 13:01:54 martin: a few changes 13:02:01 ... some comments from xfq 13:02:15 ... regarding the examples 13:02:41 ... i fixed the issue raised by xfq 13:03:16 ... we also need to consider the URL story in the future 13:04:34 ... feel free to comment 13:05:07 zitao: packaging 13:05:38 ... xfq filed https://github.com/w3c/miniapp-packaging/issues/42 13:06:28 ... we want to discuss whether we need to document this in the packaging spec 13:06:51 ... or we need to define it in a seperate document? 13:07:32 martin: yes, it's something we need to discuss 13:08:08 zitao: for sub-packaging we need to document it 13:08:26 ... for streaming, it's another format 13:08:41 ... do we want to document it in the packaing spec or another spec 13:09:28 martin: it may affect the future of the packaging spec 13:10:35 dan: i suggesta we put streaming and sub-packaging in the packaging spec 13:10:41 ... i can ask tengyuan to help the streaming part 13:11:15 zitao: great 13:11:22 We really appreciate as much input as possible, thanks! 13:11:58 zitao: addressing 13:11:59 https://github.com/w3c/miniapp-addressing/pull/4 13:12:17 dan: i have answered yongjing's question 13:13:31 ... comments welcome 13:14:29 zitao: i noticed that you mentioned why miniapp:// is introduced, but you did not mention platform:// 13:15:42 ... maybe you can explain why you designed the URL like this 13:16:13 dan: i'm not sure the deep linking technology can appear in a w3c note 13:16:16 ... need your help 13:17:00 chaals has joined #miniapp 13:17:14 zitao: encourage folks to help dan revise the draft 13:17:24 ... this spec is impoartant for miniapps standardization 13:17:48 zitao: widget 13:18:08 ... anything else, canfeng? 13:18:21 canfeng: nothing for widget 13:18:25 ... white paper? 13:18:31 zitao: it's the next agenda item 13:21:22 zitao: white paper 13:21:27 [xfq shares his screen] 13:21:32 zitao: maybe we can add miniapp API 13:23:07 canfeng: in the upcoming widget spec we will write some concrete API proposals related to widget 13:23:51 [qing introduces his changes] 13:24:48 qing: miniapps for iot 13:24:53 ... miniapps for TV 13:25:38 ... if you think it needs more content, please let me know 13:26:13 zitao: we can have 1-2 weeks to review this 13:26:43 qing: lifecycle 13:27:39 canfeng: i updated the widget part 13:27:50 ... currently mixed chinese and englighs 13:27:58 .... wil translate into english later 13:28:27 ... in the first paragraph i described the widget requirement document 13:28:47 ... in the second paragraph i gave a very very brief introduction of the widget spec 13:29:42 ... it's the first time i get involded in a white paper work in w3c 13:29:56 ... advice needed 13:32:02 ... any open issues against the white paper? 13:32:09 xfq: https://github.com/w3c/miniapp/issues?q=is%3Aissue+is%3Aopen+label%3A%22white+paper%22 13:33:34 canfeng: when we complete the widget spec we can write more next year 13:34:30 zitao: next meeting time 13:35:34 ... joint meeting CG/WG? 13:35:53 jan 27 is too close to chinese new year 13:36:21 canfeng: i prefer separate meetings 13:36:31 ... jan 20? 13:36:44 qing: fine by me 13:36:45 +1 Jan 20 13:37:28 topic: aob 13:37:31 martin: will include a section about a11y for manifest and packaging 13:39:33 zitao: a11y joint meeting? 13:39:36 xfq: @@ 13:40:04 zitao: need to add the a11y, security, priviacy sections 13:40:30 ... does the WG htink we can add these sections before the next meeting? 13:40:45 martin: i can add them, but i think we have gaps in a11y 13:42:45 +1 to early review 13:43:01 xfq: @@ early review 13:43:59 canfeng: yinli said the widget plan issue can be closed 13:44:09 ... other "plan" issues were also closed 13:46:51 rrsagent, make minutes 13:46:51 I have made the request to generate https://www.w3.org/2021/12/16-miniapp-minutes.html xfq_ 14:03:17 xfq_ has joined #miniapp 15:06:37 Zakim has left #miniapp