[Slides]

cn: [Media&entertainment iG: New Name]
... why are we changing from web&tv to media&entertainment?
... it's not just TV!
... media-related topics in general
... liaison with hbbtv, atsc, etc.
... CTA as well
... partnership with a CG
... comments so far?

jeff: one way to frame this
... created web&tv ig several years ago
... clear scope on video, movies, etc.
... as technology evolves
... who are the different stakeholders who care media and entertainment on the web?
... objectives of w3c?
... specific tech needs?
... relationship with the other orgs, e.g., HbbTV, ATSC?
... how do we engage with the world?

george: merger with IDPF
... synchronize book and audio
... fabulous for learning

cn: combining media and synchronization

mark: many industry standards
... HbbTV, ATSC and related things
... make right liaison with groups

cn: function for the IG?

mark: familiar with the industry roadmap

cn: historically that has been happening in the IG
... interest in other groups to work together
... would like to invite people to get suggestions
... web incubator cg
... that's something to bring attention
... and color on the web cg
... what's the best way to cooperate with it?
... expertise in the broadcast industry
... solution for HDR
... if we want to have support for high color and hdr

iga: why don't you add those ideas directly to the slides on the screen?

cn: media capabilities api
... color on the web
... what would be web-friendly api?
... adds "cloud browser"
... somebody suggested 4k video
... integration with UHD video

john: MSE v.next?

cn: adds "MSE v.next"

iga: what's the main point for that?

john: multiple source buffer, etc.

iga: any other ideas?

cyril: multi tracks

cn: support for captioning

cylil: captioning is included but not implemented

giri: HTML media element in-band events
... interactive tv event data

cyril: (shows his resource)
... ISO/IEC JTC1/SC29/WG11 N17242

<MarkVickers> msg kaz I'm also on the queue

cyril: draft from Macau
... organisation internationale de normalisation
... coding...
... synchronization
... timed web assets
... overlay html tracks

fd: what is the origin?

<MarkVickers> CTA WAVE submitted MSE use cases: https://www.w3.org/wiki/images/8/8c/Mse-eme-v2-use-cases-reqs-wave.pdf

mv: CTA WAVE submitted use cases on the web page
... as above

iga: could you please summarize that?

mv: client side add insertion into soft part
... on-demand content
... also
... issues on playback content
... and EME
... encoded in live content
... and section on driving them

cn: progress with those issues?

mv: best way is WICG

<MarkVickers> I think the best way to progress on these issues is the WICG

cn: role of the IG?

mv: we interface with the related groups
... gather input and data
... working with WGs and CGs
... as we've been doing
... bringing people into the WICG
... as discussed at TPAC 2 years ago

cn: Chris Wilson gave presentation there

iga: ok
... so people are encouraged to join the WICG as well
... we should also join the CG

cn: rather communication with the CG?
... we have monthly calls for the IG
... outcome represents our opinions

fd: what to specify for HTML media?

cyril: intended behavior

fd: HTML5 as the entry point?

cyril: yes
... 2 use cases in the document
... if you don't have an entry point, you could have additional video

fd: offline web package
... manifest for the entry point?

cyril: no manifest
... listing resources

iga: we should not dive into that kind of details at the moment
... maybe "Web media packaging"
... like the work by digital publishing guys

cyril: (shows his resource again)
... another document
... N17098
... several ways to notify information to users
... problem is...
... can share this document
... this is public
... client should not download for only record but playback
... HTTP headers
... mimetype supported
... manifest
... mime ty[es
... codecs parameter
... getting longer and longer
... should we go for additional parameters?
... like shcemetypes
... 3D capability, etc.
... or general profiles parameter?
... related to the media capability api
... query the platform
... has to match the info
... what is the best way?
... simple mapping
... discussion at IETF
... here
... and MPEG
... this IG could be a good place for synch

george: issues with packaging?

cyril: how to signal the packaging inside
... whatever kind of codecs
... related to royalty format
... licensing things

md: we could extend the work of the ig
... there is work ongoing within w3c
... need in the media area
... web vr, etc.
... and 5G network arriving
... how it could benefit media and entertainment?

cn: what the impact would be

fd: workshop next year

iga: what would be the impact in your mind?

md: possibility of using better transfer environment
... increasing the bandwidth
... better quality
... no clear points but we should consider that

iga: I myself listed "media synchronization"
... timing object cg
... companion remote screen in mind

cn: timed text
... do we want to encourage to see direct integration by browser?
... wider attention

eric: having interest in the issue doesn't necessarily means web browser vendors' support

[adjourned]