<cpn> Slides: https://docs.google.com/presentation/d/1L6otorDZtRJ2j2StCLMMxrewyd3R1S_HbLw859mrmoc/edit

Agenda

<scribe> scribenick: kaz

cpn: Two main topics:
... Review the discussion we had last month on media production
... to review the outcome from the call and talk about what we'd like to do next
... and then the other major topic is Rechartering, as our Charter is expiring in a few months.
... Anything else for today?

(none)

Professional media production on the Web

cpn: Last month we had very interesting presentation from Grass Valley
... on browser-based video editrs
... professional codecs, content protection, proxy media editing
... we focused on Web Codecs and decoded frame buffering
... The question is, if it's of interest to members, what to do next?
... It's related to a particular industry area, how to bring two communities together,
... production organizations and Web browsers?
... Possibly organize a W3C workshop?
... One of the benefits is it's open to anyone, so there's no membership issues
... Pre-recorded presentations can be shared,
... then we would go through the materials and have discussion during the workshop meeting itself
... to see what to do next.
... Our emphasis on media production is a slightly different audience from our usual participants.
... We would invite people and companies from those areas, e.g., SMPTE, EBU.
... I ask you for feedback, is this something you and your organization might want to make contributions?
... Any thoughts?
... Those who participated in the discussion are not here today, though...
... We would need to do some outreach.

ys: It's interesting area, and some of the approaches and technologies could apply to the distribution and consumer client areas.
... It's worth having discussion between the two industries.

cpn: Would you suggest to broaden the scope?

ys: Could consider downstream and distribution,
... what we've been discussing is good.

cpn: We've been thinking about making content more personalised, interactive perhaps, thinking about how this affects production
... Wondering if you're thinking about similar sort of media experiences?

ys: Same here

cpn: Francois, any opinions as the next steps for the workshop idea?

fd: Next step could be drafting a call for participation for the workshop,
... and then there is some internal procedure to make it public.
... practical part of the workshop like that
... In parallel, should outreach related companies to see who is ready to present
... We're really happy to get feedback to make sure to make sure the workshop is something useful

cpn: yeah
... If you have any ideas on the potential participants, please let us know
... Pierre, anythig to add?

pal: You covered everything.
... Please share opinions about the potential orgs, we should get contacts with related orgs.

cpn: tx

fd: If we can work on the CfP, it would take some months before we're ready to hold the workshop.

pal: Dealing with other standards organizations might take longer.
... Maybe there is a bit different focus depending on the countries.
... Would be good to outreach related orgs.
... We're especially interested in groups in Asian areas, e.g., ARIB

kaz: I can understand the usefulness for the discussion,
... but the timing is not really great,
... the priority in March/April should be rechartering.
... We could start initial draft discussion and outreaching, though

cpn: You're right, and that leads to the next topic.

Rechartering

cpn: Our current Charter expires April 30
... We propose to renew for 2 years, as we have done before in this group.
... The draft Charter is here:

draft Charter

cpn: We have removed Media Timed Events TF and added Media Integraton Guidelines.
... The document is the same as before, otherwise.
... We have been holding discussions with CTA WAVE as well.
... There's an overlapping area of interest, so should avoid duplication.
... WAVE has been giving feedback on Media WG deliverables such as Media Capabilities.
... One specific feedback was to have more focus on issues from media industry use cases, and bring to relevant W3C groups,
... track issues as they progress, and help drive things forward.
... The other part is that we need input from our members on priorities,
... what are the pain points?
... This could be around connected TV use of HTML5 or more generally.
... Our suggestion is to recharter, in parallel with getting input from members
... We want to hear from you, on your priorities.

kaz: We could look at best practices in addition to use cases,
... andthink about several layers for media distribution, platform, device, content, and could involve the other industry areas

cpn: We can update the draft Charter

rs: What about DataCue? This is something I'm still interested in.

cpn: I would like to get some more technical contributors to help move it forwards.
... Some parts are waiting for me to do some technical investigation. We have good collaboration with DASH-IF.
... When we delivered the IG Note about the Timed Events, identified several topics to progress:
... Changes to HTML, the DataCue inband event mapping for DASH emsg events,
... and Timed Text / WebVTT.
... Do we still need an open TF within the MEIG, or can we include it into general IG business?

rs: It's important to mention the possible spin-off work, otherwise I'm worried it will be overlooked.

pal: You need to get volunteers, there is no magic.

cpn: Yes

pal: I don't think we should write down any specific TF to go in the charter, leave it flexible.

kaz: From the W3C Process viewpoint, we don't have to predefine possible TFs,
... we need to identify our scope and interested areas,
... and can mention that we may create a TF for detailed discussion.

cpn: I think this group is a coordination point on media topics for HTML,
... if we focus on tracking issues, DataCue etc would become one of the items we track.

rs: Yeah

cpn: We've not really used the IG call for that purposes so much, but we can.
... We can also continue with the Monday meeting for the DataCue discussion, which I run really as WICG meetings.
... I would like us to keep the momentum on that.

wl: Talking about the rechartering,
... a core part from the WAVE side is interface for media and TV.
... WAVE is also promoting web as platform for media consumption,
... but we're seeing TVs shifting to native apps.
... Many reasons for this, but primarily there's concerns about performance.
... We want MEIG to capture and acknowledge this gap.
... Make the web less of an academic project, more of a tool that's used by industry.
... Who's got the interest, people who genuinely care?
... We want to involve the major content distributors, Google, Amazon, NBC, Disney, etc.
... What do the companies actually want?
... Do we have the attendance and participation to make it effective?

cpn: I think you're right, this again points to need for outreach,
... talking to those related companies maybe offline.

wl: How to drive the group's work more effectively is the key question.

<cpn> scribenick: cpn

kaz: one possibility might be talking to related organisations even more, get ideas. share ideas about current services, also expected future directions. here we might want to think about the usual 3 orgs: Hybridcast, ATSC, HbbTV, but also other content related companies.

<kaz> scribenick: kaz

cpn: Perhaps discussion between W3C and groups like HbbTV, could help.

pal: The scope of the charter should be broad enough,
... but tasks are different from scope, and the charter puts them in the same Scope section. Can we be less specific on the tasks?

cpn: We have very broad scope, covering end to end media, so I think this part is OK.

fd: To summarize the discussion, the scope is not an issue here, it's more about participation.
... Perhaps we could make the tasks a separate section.
... for example, there is performance issue for media production

cpn: yeah, would clarify driving issues
... Should we seek to extend the Charter to allow us time to talk to more companies?

ws: proactive for each industry?

cpn: the scope is broad enough, I think
... we could add something, though

ys: Another thing for the scope is to have something to explain why people would want to join this group.
... Have something that says what this group will do that doesn't duplicate what other industry groups do.
... For example, some of the groups deals with native apps.
... Have some way for someone who looks at this group to understand the charter and that it's not a copy of some other group.

jr: If companies build native apps on STBs, looking to HTML5, make clear in the clear that's in our scope.

kaz: Yeah, what our pain points are.

cpn: I expect we'll need to send a call for consensus to send the proposed Charter to W3M.
... If we need to extend the charter to cover that time, we'll do that.
... Thanks a lot, everybody, you've given some good feedback.
... We will update the draft Charter based on feedback.
... We should have an updated draft ready in the next week or so.
... If you have anything else, please let us know.

[adjourned]