IRC log of me on 2022-10-04
Timestamps are in UTC.
- 12:54:56 [RRSAgent]
- RRSAgent has joined #me
- 12:54:56 [RRSAgent]
- logging to https://www.w3.org/2022/10/04-me-irc
- 12:55:09 [cpn]
- Meeting: MEIG monthly meeting
- 12:55:13 [cpn]
- scribe+ cpn
- 12:59:34 [ohmata]
- ohmata has joined #me
- 13:00:14 [cpn]
- present+ Hisayuki_Ohmata, Ryo_Yasuoka, Tatsuya_Sato, Chris_Needham
- 13:01:13 [kaz]
- present+ Kaz_Ashimura
- 13:01:21 [cpn]
- present+ Hiroshi_Fujisawa
- 13:01:24 [tatsuya]
- tatsuya has joined #me
- 13:04:18 [tidoust]
- tidoust has joined #me
- 13:04:28 [tidoust]
- present+ Francois_Daoust
- 13:07:39 [kaz]
- present+ Chris_Lorenzo
- 13:07:51 [kaz]
- present+ Kinji_Matsumura
- 13:08:14 [kaz]
- agenda: https://lists.w3.org/Archives/Public/public-web-and-tv/2022Sep/0023.html
- 13:08:26 [kaz]
- scribenick: ka
- 13:08:28 [kaz]
- scribenick: kaz
- 13:08:37 [hfujisawa]
- hfujisawa has joined #me
- 13:08:43 [kaz]
- topic: Agenda
- 13:08:45 [kaz]
- - Welcome
- 13:08:45 [kaz]
- - Brief recap of media discussions at TPAC : 5 mins
- 13:08:45 [kaz]
- - Hybridcast Updates with NHK: 10 mins
- 13:08:45 [kaz]
- - NHK work and proposals for Application Development for Consumer Products TF: 15mins
- 13:08:45 [kaz]
- - Q&A and discussion: 30 mins
- 13:08:46 [kinjim]
- kinjim has joined #me
- 13:08:46 [kaz]
- - AOB
- 13:08:56 [kaz]
- zakim, who is on the call?
- 13:08:56 [Zakim]
- Present: Hisayuki_Ohmata, Ryo_Yasuoka, Tatsuya_Sato, Chris_Needham, Kaz_Ashimura, Hiroshi_Fujisawa, Francois_Daoust, Chris_Lorenzo, Kinji_Matsumura
- 13:09:16 [kaz]
- topic: TPAC 2022
- 13:09:27 [kaz]
- cpn: during the MEIG meeting
- 13:09:36 [kaz]
- ... discussion on TV application development
- 13:09:49 [kaz]
- ... media device specific APIs
- 13:09:57 [kaz]
- ... would move forward
- 13:10:11 [kaz]
- ... should invite interested people
- 13:10:18 [kaz]
- ... will talk more about that
- 13:10:20 [kaz]
- ... then
- 13:10:43 [kaz]
- ... CTA WAVE HTML Application TF and Web Meda API snapshot updates
- 13:10:50 [kaz]
- ... then
- 13:11:05 [kaz]
- ... presentation from Fraunhofer on next generation audio codec support
- 13:11:36 [kaz]
- ... new activity starting up
- 13:12:00 [kaz]
- i/new/... during the joint meeting with WebRTC and Media WG
- 13:12:15 [kaz]
- ... new media architecture in browsers
- 13:12:42 [kaz]
- ... then the new CG on Audiovisual Media Formats
- 13:13:01 [kaz]
- ... everybody is welcome to join to participate in the discussion
- 13:13:04 [kaz]
- ... then
- 13:13:08 [kaz]
- ... Media WG meeting
- 13:13:16 [kaz]
- ... MSE feature prioritization
- 13:13:31 [kaz]
- ... pre-emptive eviction for low memory platforms
- 13:13:46 [kaz]
- ... also DASH emsg support
- 13:14:16 [kaz]
- ... follow up on DASH-IF. still too early with implementations
- 13:14:23 [kaz]
- ... then
- 13:14:34 [kaz]
- ... EME v2
- 13:14:47 [kaz]
- ... aiming for FPWD during the Charter period (May 2023)
- 13:14:59 [kaz]
- ... then
- 13:15:09 [kaz]
- ...Media session
- 13:15:24 [kaz]
- ... agreed to add actions to support slide presentations over WebRTC
- 13:15:38 [kaz]
- rrsagent, make log public
- 13:15:42 [kaz]
- rrsagent, draft minutes
- 13:15:42 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 13:15:46 [kaz]
- ... Audio Focus API
- 13:15:56 [kaz]
- ... music vs notification sound
- 13:16:13 [kaz]
- ... interest from Apple and Mozilla for API
- 13:16:24 [kaz]
- ... use cases for proposed API
- 13:16:29 [kaz]
- ... then
- 13:16:41 [kaz]
- ... WebCodecs and associated metadata
- 13:16:53 [kaz]
- ... analyze the video for, e.g., face detection
- 13:17:01 [kaz]
- ... use a registry approach
- 13:17:21 [kaz]
- ... introduction for document PinP
- 13:17:29 [kaz]
- s/PinP/PinP API/
- 13:17:44 [kaz]
- ... use case might be sharing your custom control
- 13:17:58 [kaz]
- ... that is a brief summary
- 13:18:05 [kaz]
- ... not everything, though
- 13:18:19 [kaz]
- q+
- 13:19:03 [cpn]
- Kaz: Regarding, consumer device TF discussion, as I mentioned at TPAC it would make sense to collect current practices, including from NHK
- 13:19:08 [kaz]
- ack k
- 13:19:23 [kaz]
- i|Regarding|scribenick: cpn|
- 13:19:31 [kaz]
- rrsagent, draft minutes
- 13:19:31 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 13:19:52 [kaz]
- topic: Hybridcast updates
- 13:19:58 [kaz]
- @@@ slides tbd
- 13:20:06 [kaz]
- i/scribenick: kaz/
- 13:20:42 [kaz]
- sato: ToC
- 13:20:46 [kaz]
- ... Updates on IPTVF
- 13:20:48 [kaz]
- ... then NHK
- 13:20:58 [kaz]
- ... [slide 3]
- 13:21:02 [kaz]
- ... [slide 4]
- 13:21:13 [kaz]
- ... Hybridcast diffusion status
- 13:21:36 [kaz]
- ... annual shipments and total ones of Hybridcast TVs
- 13:21:55 [kaz]
- ... available on over 300 TV models
- 13:21:59 [kaz]
- ... [slide5]
- 13:22:08 [kaz]
- ... NHK's services
- 13:22:11 [kaz]
- ... [slide 6]
- 13:22:22 [kaz]
- ... Media service for various devices
- 13:22:38 [kaz]
- ... [slide 7]
- 13:22:39 [kaz]
- ... Video streaming
- 13:22:46 [kaz]
- ... (diagram of their system)
- 13:23:02 [kaz]
- ... broadcast station -> Hybridcast TV
- 13:23:05 [kaz]
- ... [slide 8]
- 13:23:12 [kaz]
- ... Software tools for video streaming
- 13:23:27 [kaz]
- ... developed opensouce softwares
- 13:23:39 [kaz]
- ... Bajoo.js, Relay-miffe, Delivery-miffe
- 13:23:48 [kaz]
- ... [slide 9]
- 13:23:53 [kaz]
- ... Device collaboration
- 13:24:23 [kaz]
- ... Broadcast station -> Hybridcast TV -> Hybridcast Connect -> Devices
- 13:24:29 [kaz]
- ... [slide 10]
- 13:24:39 [kaz]
- ... Linkage between Hybridcast and WoT
- 13:24:54 [kaz]
- ... WoT-enabled TV services using Hybirdcast Connect at TPAC 2022
- 13:25:04 [kaz]
- ... demo during the WoT breakout
- 13:25:12 [kaz]
- ... [slide 11]
- 13:25:20 [kaz]
- ... OSS for Hybridcast Connect lerners
- 13:25:37 [kaz]
- ... opensource software for Hybridcast Connect as well
- 13:26:00 [kaz]
- ... Hybridast Connect TV emulator, SDK, Client sample application
- 13:26:24 [kaz]
- ... can be connected to the Hybridcast TV
- 13:26:36 [kaz]
- ... [slide 12]
- 13:26:36 [kaz]
- ... resources
- 13:26:42 [kaz]
- ... NHK OPEN HOUSE 2022
- 13:26:55 [kaz]
- ... Application GitHub repository
- 13:26:59 [kaz]
- ... tx!
- 13:27:02 [cpn]
- q+
- 13:27:07 [kaz]
- rrsagnt, draft minutes
- 13:27:11 [kaz]
- cpn: really interesting
- 13:27:25 [kaz]
- ... can you explain a bit more about the WoT demo?
- 13:27:30 [kaz]
- ... what's happening here?
- 13:28:25 [kaz]
- sato: (shows their slides on the demo itself)
- 13:28:41 [kaz]
- @@@ slide tbd
- 13:29:00 [kaz]
- sato: presentation during the WoT demo breakout by Endo from NHK
- 13:29:44 [kaz]
- ... demonstration including succor program on TV and an air cleaner
- 13:30:25 [kaz]
- ... air cleaner's noise would be lower depending on the succor game's status
- 13:30:29 [kaz]
- cpn: understood
- 13:31:36 [kaz]
- s|@@@ slide tbd|-> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2022-09-hybrid-f2f/2022-09-14-WoT-F2F-TPAC2022_Breakout-Endo.pdf NHK's slides on their demo during the WoT demo breakout session|
- 13:31:49 [kaz]
- sato: (shows the demo content within the slides)
- 13:32:28 [kaz]
- ... event message sent from the TV side to the air cleaner side depending on the succor game's situation
- 13:32:51 [kaz]
- cpn: is this MTE-based?
- 13:32:54 [kaz]
- sato: yes
- 13:33:21 [kaz]
- ohmata: originally based on the event message from the TV program
- 13:34:00 [kaz]
- ... trigger messages, e.g., start, goal, replay
- 13:34:22 [kaz]
- ... handled by WoT and Hybridcast protocol
- 13:34:28 [kaz]
- cpn: make sense
- 13:34:51 [kaz]
- ... interesting to see the detail of the mechanism
- 13:35:05 [kaz]
- ... don't have enough time today, though
- 13:35:11 [kaz]
- q+
- 13:35:14 [kaz]
- ack c
- 13:35:36 [kaz]
- ... do you have any description to control the TV?
- 13:36:01 [kaz]
- ... wondering if we should discuss the detail during the future calls
- 13:36:07 [cpn]
- s/any description/a WoT Thing Description/
- 13:37:10 [kaz]
- ohmata: WoT protocol and Hybridcast protocol handle the message
- 13:37:31 [kaz]
- kaz: maybe you can show the p9 from Endo-san's slide set to describe the mechanism
- 13:38:17 [cpn]
- Kaz: The TV also has a WoT Thing Desciprtion. Two devices using the WoT mechanism
- 13:38:29 [kaz]
- i/The TV/scribenick: cpn/
- 13:38:30 [kaz]
- q?
- 13:39:30 [cpn]
- Kaz: Good start for collaboration with MEIG and WoT. As discussed with WebTransport people, a use cases is surveillance cameras, adding metadata annotations, handling related devices using WoT and MTE
- 13:39:37 [cpn]
- ... That kind of collaboration would be useful
- 13:39:37 [kaz]
- ack k
- 13:40:11 [kaz]
- cpn: ok. let's have another detailed discussion for this direction again
- 13:40:18 [kaz]
- i/ok/scribenick: kaz/
- 13:40:44 [kaz]
- topic: NHK work and proposals for Application Development for Consumer Products TF
- 13:40:56 [kaz]
- cpn: next proposals for Consumer Products TF
- 13:41:20 [kaz]
- yasuoka: Case studies of Hybridcast application development...
- 13:41:24 [kaz]
- ... [slide 1]
- 13:41:29 [kaz]
- ... Hybridcast
- 13:41:42 [kaz]
- ... already in service around 10 years
- 13:41:46 [kaz]
- ... [slide 2]
- 13:41:55 [kaz]
- ... Stakeholders and their relationship
- 13:42:13 [kaz]
- ... IPTV Forum Japan generates Hybridcast standards
- 13:42:18 [kaz]
- ... and operation guidelines
- 13:42:29 [kaz]
- ... also runs conformance tests
- 13:42:58 [kaz]
- ... for various TV manufactures and application developers
- 13:43:02 [kaz]
- ... [slide 3]
- 13:43:12 [kaz]
- s/3/4/
- 13:43:14 [kaz]
- s/2/3/
- 13:43:16 [kaz]
- s/1/2
- 13:43:29 [kaz]
- ... Performance difference
- 13:43:56 [kaz]
- ... performance difference among various devices is a big issue
- 13:44:09 [kaz]
- ... [slide 6]
- 13:44:22 [kaz]
- ... Case 1: Animation rendering performance
- 13:44:29 [kaz]
- ... focus frame movement
- 13:45:01 [kaz]
- ... need to reduce CSS transition property to avoid the delay
- 13:45:28 [kaz]
- ... asked the TV manufactures to improve the device, but couldn't
- 13:45:48 [kaz]
- ... so had to reduce some of the properties
- 13:46:00 [kaz]
- ... to improve the performance
- 13:46:05 [kaz]
- ... [slide 7]
- 13:46:17 [kaz]
- ... Case 2: Process when switching services
- 13:46:30 [kaz]
- ... requirements for linear video services
- 13:46:45 [kaz]
- ... broadcast => streaming
- 13:46:57 [kaz]
- ... vice versa
- 13:47:22 [kaz]
- ... quick switching after getting the trigger is expected
- 13:47:42 [kaz]
- ...but difficult to control what will be displayed on the screen
- 13:47:59 [kaz]
- ... due to the performance difference
- 13:48:11 [kaz]
- ... [slide 9]
- 13:48:23 [kaz]
- ... Performance test activities (by the IPTVF-J)
- 13:48:37 [kaz]
- ... UX improvement for Hybridcast services
- 13:48:59 [kaz]
- ... test categories: screen rendering, app loading, etc.
- 13:49:03 [kaz]
- ... [slide 10]
- 13:49:10 [kaz]
- ... Test 1: Animation by sprite sheet
- 13:49:24 [kaz]
- ... 8-sec horizontal moveent of an image
- 13:49:36 [kaz]
- ... measured 10 times on 6 different TVs
- 13:49:44 [kaz]
- ... results vary...
- 13:50:11 [kaz]
- ... expectation was 8 sec every time
- 13:50:27 [kaz]
- s/time/time, though/
- 13:50:37 [kaz]
- ... [slide 11]
- 13:50:44 [kaz]
- ... Test 2: Browser launch time
- 13:51:21 [kaz]
- ... time span between launch button pressed and invocation
- 13:51:25 [kaz]
- ... [slide 12]
- 13:51:36 [kaz]
- ... conclusion and discussion
- 13:51:52 [kaz]
- ... past and ongoing challenges on performance issues
- 13:52:15 [kaz]
- ... how can the application developers and TV vendors contribute to the TF?
- 13:52:23 [kaz]
- ... what can they expect?
- 13:52:40 [kaz]
- ... can provide use cases based on our experience
- 13:52:51 [kaz]
- s/use cases/our use cases/
- 13:53:03 [kaz]
- ... questions? comments?
- 13:53:09 [kaz]
- rrsagent, draft minutes
- 13:53:09 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 13:53:12 [kaz]
- cpn: tx!
- 13:53:42 [kaz]
- ... ChrisL, any comments?
- 13:53:58 [kaz]
- cl: interesting discussion on pushing Web and browsers for applications on TV
- 13:54:03 [kaz]
- ... major challenge
- 13:54:17 [kaz]
- ... need to increase the performance for TV apps
- 13:54:36 [kaz]
- ... for transitions and animations, the performance is not enough
- 13:54:46 [kaz]
- ... and need to reduce the animations, etc.
- 13:55:07 [kaz]
- ... not sure if you're aware of Lightning platform which uses WebRTC
- 13:55:18 [kaz]
- ... let me post the resource
- 13:55:24 [ChrisLorenzo]
- ChrisLorenzo has joined #me
- 13:55:37 [kaz]
- cpn: aspects here, we've not considered for the TF discussion
- 13:55:40 [ChrisLorenzo]
- Developer Experience - https://github.com/w3c/media-and-entertainment/pull/92/files?short_path=753fd1d#diff-753fd1d9b2d6cb55d78b5c965fca3387ca62e617d22e89a0121d86ebdf23059b
- 13:55:51 [kaz]
- ... very much consistent with what ChrisL has been mentioning
- 13:56:00 [ChrisLorenzo]
- https://github.com/w3c/media-and-entertainment/blob/master/app-development/charter.md
- 13:56:11 [kaz]
- ... one of the techniques we use is
- 13:56:16 [ChrisLorenzo]
- Framework for performance on TV apps - https://lightningjs.io/
- 13:56:23 [kaz]
- ... enabling features on TV to be tested
- 13:56:40 [kaz]
- ... framework to allow conditionally able/disable the feature
- 13:56:55 [kaz]
- ... if less capable, disable the feature
- 13:57:11 [kaz]
- ... the other thing interesting is start up performance time for Hybridcast applications
- 13:57:27 [kaz]
- yasuoka: (shows the Test 2 results again)
- 13:57:43 [ChrisLorenzo]
- Can we get the link to the slides on here?
- 13:57:44 [kaz]
- cpn: any insights to what the cause of the delays here?
- 13:57:55 [kaz]
- ... how does it vary with the browser implementations?
- 13:58:25 [kaz]
- yasuoka: it's difficult to describe the detail
- 13:59:06 [kaz]
- cpn: any additional measurement where the TV is spending the time?
- 13:59:20 [kaz]
- ... e.g., the browser itself is a large application binary
- 13:59:29 [kaz]
- ... and needs to load big memory at once
- 13:59:45 [kaz]
- ... way to instrument the details?
- 14:00:28 [kaz]
- yasuoka: green part depends on the network connections
- 14:00:43 [kaz]
- s/green/firstly, green/
- 14:01:22 [kaz]
- ... need to dig into the detailed behavior of Hybridcast implementation
- 14:01:39 [kaz]
- crisL: the user press the launch button is time 0
- 14:01:53 [kaz]
- ... the browsers already receive the responnse
- 14:01:58 [kaz]
- s/responnse/response/
- 14:02:07 [kaz]
- ... then HTTP connection
- 14:02:16 [kaz]
- ... then load the page content
- 14:02:27 [kaz]
- ... browsers do that quickly, actually
- 14:02:43 [kaz]
- ... what the difference on A-J here?
- 14:02:45 [igarashi]
- igarashi has joined #me
- 14:02:56 [kaz]
- yasuoka: TV model variations
- 14:03:00 [kaz]
- ... available in Japan
- 14:03:04 [kaz]
- crisL: ok
- 14:03:19 [kaz]
- ... this is very similar with smartphones variation
- 14:03:31 [kaz]
- ... A and J are very fast
- 14:03:39 [kaz]
- cpn: yeah, that's interesting
- 14:03:49 [kaz]
- ... are those faster ones the latest models?
- 14:03:55 [kaz]
- ... or most expensive ones?
- 14:04:04 [kaz]
- yasuoka: newer ones are faster
- 14:04:28 [kaz]
- crisL: WAVE guys are doing similar tests
- 14:04:35 [kaz]
- present+ Tatsuya_Igarashi
- 14:04:55 [kaz]
- ... some TVs have powerful chips
- 14:05:07 [kaz]
- ... and some don't
- 14:05:12 [kaz]
- q+
- 14:05:23 [kaz]
- cpn: interesting approach
- 14:05:30 [igarashi]
- present+
- 14:05:42 [kaz]
- ... not sure if it's within the scope of W3C, though
- 14:06:03 [cpn]
- q?
- 14:06:04 [kaz]
- ... similar to the CTA WAVE's activity
- 14:06:57 [nigel]
- nigel has joined #me
- 14:07:24 [cpn]
- Kaz: TV device performance may be out of scope, but getting this kind of inforation from various areas and SDOs should be useful.
- 14:07:32 [cpn]
- ... We can look into the detailed processing time in this kind of procedure, not the device or network part, but the browser processing time should be clarified.
- 14:07:43 [cpn]
- ... If we can get that kind of clarification and see the actual cause of time delay, we can look with browser vendors to improve
- 14:08:01 [cpn]
- ... As ChrisN metioned, maybe NHK could bring this to CTA WAVE
- 14:08:07 [cpn]
- ... MEIG could look at the results in more detail
- 14:08:13 [kaz]
- ack k
- 14:08:14 [cpn]
- ... such as in TF calls
- 14:08:23 [kaz]
- i/TV device/scribenick: cpn/
- 14:08:34 [kaz]
- rrsagent, draft minutes
- 14:08:34 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 14:08:59 [kaz]
- cpn: happy to spend more time to continue this
- 14:09:42 [kaz]
- i/happy/scribenick: kaz/
- 14:09:56 [kaz]
- ... one of the things interesting is
- 14:10:18 [kaz]
- ... Web Performance WG's activity on measuring the performance
- 14:10:29 [nigel]
- Present+ Nigel_Megitt
- 14:10:42 [kaz]
- ... indication of measurement
- 14:11:01 [kaz]
- ... rendering stability, how the content moves, etc.
- 14:11:31 [kaz]
- ... is this something interesting from our viewpoint?
- 14:12:22 [kaz]
- ... have you started to look at alternate rendering mechanism?
- 14:12:38 [kaz]
- ... e.g., Lightning
- 14:12:45 [kaz]
- ... how would they impact, etc.
- 14:13:34 [kaz]
- yasuoka: this testing activity is done for those kind of mechanisms yet
- 14:13:43 [kaz]
- s/Lightning/WebGPU and Lightning/
- 14:13:55 [kaz]
- ... would like to try them in the future
- 14:14:06 [cpn]
- q?
- 14:14:51 [kaz]
- ... currently, Hybridcast doesn't support WebGPU or WebRTC
- 14:15:45 [kaz]
- ... we'd like to try them but it's kind of difficult at the moment
- 14:15:56 [kaz]
- q+
- 14:16:17 [kaz]
- cpn: too difficult to introduce those new features. right?
- 14:16:25 [kaz]
- ... what kind of help do you expect from W3C?
- 14:17:07 [kaz]
- yasuoka: if those mechanisms could be actual standards for media handling
- 14:17:10 [kaz]
- ... that would be great
- 14:17:59 [kaz]
- ... would like to proceed with to consider those new mechanisms
- 14:18:08 [kaz]
- s/to consider/considering/
- 14:18:33 [kaz]
- ohmata: Hybridcast currently doesn't define those mechanisms as mandated
- 14:19:21 [kaz]
- ... but think it would be useful
- 14:19:46 [kaz]
- cpn: then
- 14:19:51 [kaz]
- ... the question here
- 14:20:03 [kaz]
- ... how can app/product developers contribute to the TF?
- 14:20:18 [kaz]
- ... would like to tackle the issues one by one
- 14:20:38 [kaz]
- ... the discussion we have about launching time, etc.
- 14:20:52 [kaz]
- q?
- 14:21:22 [cpn]
- Kaz: We can start with gathering information on pain points and workarounds based on industry experience
- 14:21:48 [cpn]
- ... We have another example from Chris Lorenzo at Comcast. We can summarise the description also and put them together
- 14:22:02 [kaz]
- ack k
- 14:22:03 [cpn]
- ... We can also ask someone from BBC and Fraunhofer about their experience
- 14:22:15 [kaz]
- i/We can/scribenick: cpn/
- 14:22:22 [cpn]
- ChrisN: Yes, helpful to gather more experience reports
- 14:22:50 [kaz]
- cpn: another question is expected output
- 14:22:59 [kaz]
- i/another/scribenick: kaz/
- 14:23:05 [kaz]
- ... related to your 2nd question
- 14:23:22 [kaz]
- ... What can app/product developers expect from the TF?
- 14:23:38 [kaz]
- ... we want to continue to use the Web technology
- 14:24:07 [kaz]
- ... if the performance improvement can be achieved based on the current Web technology
- 14:24:14 [kaz]
- ... we should identify what to be done
- 14:24:36 [kaz]
- ... this could be an area on Web Performance as well
- 14:25:05 [kaz]
- ... this whole idea i around having tests by application developers and device manufacturers
- 14:25:24 [kaz]
- ... on achievable performance goals
- 14:25:36 [kaz]
- ... could even become a marketing tool
- 14:25:51 [kaz]
- ... having a representative test suite
- 14:26:02 [kaz]
- ... may be a valuable thing
- 14:26:03 [kaz]
- ... and
- 14:26:17 [kaz]
- ... the other area is looking at alternative rendering mechanism
- 14:26:27 [kaz]
- ... instead of DOM-based rendering mechanism
- 14:26:48 [kaz]
- ... we could start to look at canvas-based, WebGL-based, etc.
- 14:27:07 [kaz]
- ... new rendering standard in the future could be developed
- 14:27:19 [kaz]
- ... about how that easily could adopt
- 14:27:27 [kaz]
- ... with HTML-based applications
- 14:27:38 [kaz]
- ... support new technologies
- 14:27:48 [kaz]
- ... would require new open discussions
- 14:28:00 [cpn]
- q?
- 14:28:39 [kaz]
- ... would suggest creating GitHub issues to capture your points
- 14:28:50 [kaz]
- ... and see how to follow up each of them
- 14:29:01 [kaz]
- ... would that make sense?
- 14:29:08 [kaz]
- kaz: +1
- 14:29:17 [kaz]
- crisL: also agree
- 14:29:33 [kaz]
- cpn: so I'll propose to do that
- 14:29:37 [kaz]
- ... really good input
- 14:29:45 [kaz]
- ... thank you for your presentation!
- 14:30:04 [kaz]
- ... something we'd like to continue for collaboration
- 14:30:13 [kaz]
- yasuoka: thank YOU!
- 14:30:25 [kaz]
- rrsagent, draft minutes
- 14:30:25 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 14:30:42 [kaz]
- cpn: would invite you to the discussion
- 14:30:55 [kaz]
- ... happy to have you both
- 14:31:12 [kaz]
- ... would continue to work with you via Kaz
- 14:31:24 [kaz]
- ... anything else for today?
- 14:31:31 [kaz]
- (none)
- 14:31:50 [kaz]
- chair: Chris_Needham, Chris_Lorenzo, Tatsuya_Igarashi
- 14:32:06 [kaz]
- cpn: look forward to see further collaboration
- 14:32:25 [kaz]
- chrisL: to make sure, please upload the slides
- 14:32:29 [kaz]
- cpn: yes
- 14:32:40 [kaz]
- ... please send them to me or Kaz
- 14:32:49 [kaz]
- ... so that we can upload them
- 14:32:55 [kaz]
- yasuoka: will do
- 14:33:01 [kaz]
- cpn: tx
- 14:33:10 [kaz]
- rrsagent, draft minutes
- 14:33:10 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 14:33:45 [kaz]
- i|sato: ToC|scribenick: kaz|
- 14:33:52 [kaz]
- [adjourned]
- 14:33:55 [kaz]
- rrsagent, draft minutes
- 14:33:55 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 14:34:39 [kaz]
- i/We can start/scribenick: cpn/
- 14:34:48 [kaz]
- i/We can also ask/scribenick: kaz/
- 14:34:49 [kaz]
- rrsagent, draft minutes
- 14:34:49 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 14:35:29 [kaz]
- s/We can also ask some/scribenick: cpn/
- 14:35:30 [kaz]
- rrsagent, draft minutes
- 14:35:30 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 14:36:12 [kaz]
- s/scribenick: cpnone/We can also ask someone/
- 14:36:14 [kaz]
- rrsagent, draft minutes
- 14:36:14 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 14:36:24 [kaz]
- i/from BBC/scribenick: cpn/
- 14:36:25 [kaz]
- rrsagent, draft minutes
- 14:36:26 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 14:38:12 [kaz]
- i|next proposals for Con|@@@ slide tbd|
- 14:38:14 [kaz]
- rrsagent, draft minutes
- 14:38:14 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 14:39:42 [kaz]
- s/cpn:/ChrisN:/g
- 14:40:01 [kaz]
- s/crisL:/ChrisL:/g
- 14:40:04 [kaz]
- rrsagent, draft minutes
- 14:40:04 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 14:40:37 [kaz]
- s/yasuoka:/Yasuoka:/
- 14:40:50 [kaz]
- s/cl:/ChrisL:/
- 14:40:53 [kaz]
- rrsagent, draft minutes
- 14:40:53 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 14:41:11 [kaz]
- s/sato:/Sato:/
- 14:41:15 [kaz]
- s/sato:/Sato:/g
- 14:41:29 [kaz]
- s/ohmata:/Ohmata:/g
- 14:41:36 [kaz]
- s/kaz:/Kaz:/
- 14:41:37 [kaz]
- s/kaz:/Kaz:/g
- 14:41:40 [kaz]
- rrsagent, draft minutes
- 14:41:40 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 14:42:22 [kaz]
- s/yasuoka:/Yasuoka:/g
- 14:42:24 [kaz]
- rrsagent, draft minutes
- 14:42:24 [RRSAgent]
- I have made the request to generate https://www.w3.org/2022/10/04-me-minutes.html kaz
- 14:42:41 [cpn_]
- cpn_ has joined #me
- 15:28:48 [tidoust]
- tidoust has joined #me
- 16:25:02 [Karen]
- Karen has joined #ME
- 16:28:32 [Zakim]
- Zakim has left #me
- 16:57:18 [Karen]
- Karen has joined #ME