W3C

– DRAFT –
MEIG monthly meeting

03 October 2023

Attendees

Present
Andreas_Tai, Chris_Lorenzo, Chris_Needham, Francois_Daoust, Hiroki_Endo, Hisayuji_Ohmata, John_Riviello, Kazuyuki_Ashimura, Kinji_Matsumura, Ray_Holton, Ryo_Yasuoka, Tatsuya_Igarashi
Regrets
-
Chair
Chris_Lorenzo, Chris_Needham, Tatsuya_Igarashi
Scribe
cpn, kaz

Meeting minutes

Slideset: https://docs.google.com/presentation/d/10Bh94n-CM7SlDet4TfscHsoWqOLR_QhSIe31hmoiXBI/edit

cpn: first meeting after TPAC
… list of topics there
… anything missing?
… Kaz, you mentioned MEIG Charter review status

Charter review status

AC review results (Member-only)

kaz: We got 21 reviews, 2 suggestions, 4 abstentions, so should be OK for approval. I'll work with PLH on the next steps
… One general comment about this being a long standing charter, so should be updated

cpn: Are changes to the charter needed?

kaz: It should be OK, but I'll follow up on that

cpn: could be good to define more precise scope and objectives for each recharter

Review of TPAC outcomes

DVB liaison on accessibility services

cpn: discussed with various groups during TPAC
… APA WG, MEIG, TTWG
… links for the minutes within the slides
… TTWG focused on subtitle captions and audio description
… We should organize a separate call to discuss other aspects
… screen readability, magnification in the UI
… etc.
… not sure if TTWG has looked into those points
… Andreas, any feedback?

atai: there was some reluctance from DVB to share in public
… possibly due to IPR issues
… depends on their policies
… everybody can join the meeting
… TT is mainly looking into subtitles
… there is overlap with CTA WAVE specs as well
… good to inform today's DVB context

cpn: yes, we should let them know we're reviewing but would need some more time
… TTWG can send a response immediately
… we can send our own response in addition to TTWG too
… just need somebody to contact them
… maybe Kaz as the Team Contact can talk with the TT Contact, Atsushi

atai: maybe Francois also

cpn: we could have a meeting to go through the detail, but not minute it publicly
… to generate some text as the basis for the liaison response
… propose to do that in the next week or two

HTML5 issues on embedded CE devices

cpn: John Riviello presented results of the recent survey by CTA WAVE
… emphasises the continued need for a standardised web based platform across CE devices
… good collaboration with web platform tests
… W3C can work on APIs where gaps for new capabilities are identified
… WAVE would potentially work on collecting those into a platform definition
… W3C give input on WebGPU, Web Assembly, etc., or if there are specific issues with W3C specs
… the other thing we heard are performance issues,
… is there anything we can capture around issues on specific specs?
… do we need to move to different kind of rendering approach if it can't be improved
… John, want to add anything?

john: sure, it's tricky since related to low-power devices moreso than issues with individual specs
… WAVE actually had a meeting yesterday,
… we try to get content providers on board
… to help the discussion get momentum
… also WAVE could define performance related tests

cpn: in the media api cg, there was a draft document on developer guidance
… we should think about revisiting that, could be helpful?

john: good point

cpn: next step, WAVE is looking to get together a group of content providers
… anybody here with interest, I would suggest get in touch with John

john: thanks

TV application development

cpn: one particular need was identified,
… to simplify deployment to devices during app development
… as well as in deployment and installation
… we have draft document outlining the problems

Launching Web Applications on consumer products

cpn: Chris Lorenzo, anything to add?

cl: talking group about standardization
… talking within Comcast, including proprietary approaches
… need discussion with device manufacturers as well
… solution could be wider adoption of DIAL protocol, which was driven by Netflix

cpn: not sure if manufacturers are here today, but we can contact them
… is there also an issue of who is allowed to launch, certification requirements for installation? enabling developer mode?
… good stuff for the next steps

cl: even start with one manufacturer
… write down the steps and talk with the manufacturers

john: WAVE met last week and had discussion
… ATSC is handling something
… HTML entry page description
… ATSC, HbbTV and SDOs from Asia
… they could put the requirements

cpn: interesting
… Louay also mentioned in testing framework, putting the URL in metadata in a transport stream
… it's coming from TV delivery-centric point of view
… so there are those various use cases for launching apps: a broadcaster app associated with a linear channel, a VOD app installed on the device
… on TV devices, whether the app is installed and launched through the remote control or via a companion device
… maybe worth considering about the details
… starting with some of the manufacturers
… I'm thinking of people but don't want to mention concrete names here :)
… any other thought on this?

Cross-industry media distribution

cpn: interesting discussion during TPAC breakout session
… metadata to enable cross-industry media distribution
… organized by NHK with presentation from Endo-san
… and Daihei for the publishing industry as well
… in the discussion, real focus on metadata
… to enable these kind of use cases
… we're open for the next steps
… some questions in the breakout were about media metadata defined by many SDOs
… can we identify the detailed and specific use cases we want to support?
… aspecific issues with the JP market driving this discussion?
… identify particular standards and requirements?
… any additional thoughts, particularly from those participating the session?

kaz: There are at least two viewpoints on this, target areas for metadata usage, broadcasting and OTT video distribution services, in MEIG
… NHK are thinking about broader services, including video distribution, publishing, toys and games, and so on
… Any kind of applications and services based on specific content. A famous comic has characters and products, so the relationship between those products would be in scope as well
… For that purpose, think about how to proceed, broadcasting may be handled by MEIG internally, but other areas might require another group or further liaisons with other SDOs or stakeholders

cpn: interesting
… one of the possible use cases we discussed is a TV program related to some e-book
… or buying a physical product that's related
… not sure how to handle the relationship at the moment
… but may need some metadata
… so that we can identify the cross-references, we'll need to investigate
… so potentially a linked data kind of approach could be used?

kaz: yeah

kaz: PLH described W3C's activities in two categories: browser and data on the web areas, this relates to both

igarashi: have a comment about the idea
… the requirement is only about the JP market?
… also media distribution industry?
… the intention is not only broadcasting but could include publishing
… probably NHK needs to involve people from not only Japan
… also to involve the other industry stakeholders
… that's my suggestion

cpn: we have a good relationship with the publishing group within W3C as well
… could look into their ideas
… e.g., between TV show and related e-book
… also other kind of products
… but to do that would need to get other industry stakeholders too

kaz: I agree, we could start with a smaller discussion as a basis, e.g., collaboration between broadcasting and publishing, and further media mixed services after that
… I'd like to ask NHK guys opinions as well

Ohmata: The proposal covers a wide range in the media and non-media industries
… I think the first steps, we have to discuss a simple use case such as broadcast and OTT
… The next step in the media industry is, for example, TV and e-book
… The last step would be media and other industry
… We had limited time in the breakout so we didn't discuss the detailed metadata issues
… So detailed discussion on the differences between metadata standards between countries, so this could be discussed step by step

cpn: happy to take your guidance around how to proceed
… if you prefer holding a planning meeting privately, happy to do that
… or looking into media metadata more in detail
… we don't need to involve other groups
… focus initially in the media industry
… would that be a good next step?

igarashi: if NHK would like to focus on media industry first, MEIG would be a good place
… Comcast also interested in applications on consumer devices
… I have a question about media use cases
… metadata is one of the industry assets
… does NHK would like to standardize them?
… or interested in the last-mile for OTT services?
… what is your interest?

endo: not answer to Igarashi-san but another comment
… we don't plan to standardize metadata
… specific use cases on media collaborations

endo: We'd like to discuss privately as the next step

kaz: actually, the first point was an answer for Igarashi-san's question :)

igarashi: ok

cpn: we got some clarification
… happy to organize another meeting when you're ready

HDR

cpn: very active topic
… Christopher Cameron from Google presented at TPAC

Cristopher's slides

cpn: kind of layered model
… how to handle WebGL extended range for HDR, CSS media query for HDR headroom
… he is looking to get alignment on the approach
… so the HLG and PQ formats can be handled, as a next step
… if you're interested, please join the meetings

AV Media Formats for Browsers CG

cpn: media capabilities API signaling of Dolby HDR metadata
… prefer bringing into the MEIG
… good to have one place for the discussion

Media WG issues needing MEIG/WAVE input

cpn: Media WG has some issues on support for MPEG CMAF in the Media Capabilities API
… from previous discussion there was a suggestion to create an opensource library to do the mapping
… is there still any spec gap to be addressed?
… don't want to talk about the detail now,
… but would like to hold discussion another time
… display capability and decode capability handled separately in the MC API
… we have CSS media query for TV video plane HDR, but do we also need a query for the video plane pixel ratio or resolution
… for example, a device may play 4K video but have lower graphics plane resolution. how to expose that?

Media WG exploratory work/proposals

cpn: several exploratory topics
… hardware accelerated video capability
… synchronized media playback between users

Kaz: To clarify, synchronized playback between users, is that like bullet-chat, one video content with multiple inputs for subtitles from various users?
… or TV based gaming?

Chris: It's more about different people in different places watching the same content at the same time

Kaz: tx for clarification. In that case, a possible use case is rather remote live session including players all the over the world :)

cpn: yes

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 196 (Thu Oct 27 17:06:44 2022 UTC).