Meeting minutes
<cpn> https://
Agenda
cpn: Media Content Metadata demo from Interop Tokyo - Hiroki Endo (NHK)
… Media WG rechartering status
… MEIG rechartering (our current charter expires 31 October)
… TPAC plans
… AOB?
RobSmith: I've made some progress with DataCue, I sent you an email an hour ago
Media Content Metadata demo from Interop Tokyo - Hiroki Endo (NHK)
<kaz> Media Content Metadata Japanese (MCM-JP) CG
<kaz> Endo-san's slides
Endo: I'm here as the chair of the MCM-JP CG, I'll give an update on our demo and presentation at Interop Tokyo 2025, and next steps towards TPAC
… Our goal is to promote metadata interop across industries. We collect use cases across industries, specs, operational rules and challenges
… We gather and share metadata specs and provide interoperability examples. We don't define any standards or create new schemas or ontologies
… We connect existing standards and practices, not reinvent them
… At Tokyo Interop 2025, we demonstrated interop scenarios using metadata, cross-indusrty metadata linkage. It was showcased in the W3C booth at Japan's largest interop event
… We developed 6 PoCsto validate metadata interoperability, covering multiple domains: broadcasting, publishing, event information, etc
… Each prototype combines metadata from different industries to demonstrate practical interoperability
… [slide 6]
… This example shows event information service, named "Eventia", linked with broadcasting and publishing metadata
… Event details are displayed based on date and location. Related broadcasting and publishing metadata is dynamically shown.
… This shows how the user experience can be enhanced by exchanging the metadata
… Demo video
… It shows the integration with event information with publishing and broadcasting metadata
… The metadata is derived from in-practice metadata from each industry
… [slide 8]
… Key elements include evnet info (address, coordinates, and date and time in ISO8601 format, or ARIB standard)
… We also identified issues such as different interpretation of fields and lack of a controlled vocabulary
… Example of geolocation coordinatinates
… At TPAC this year we'll host a breakout session with live demos and technical deep dive
… We invite MEIG members to give feedback and to collaborate
… To summarise, our focus is on connecting and sharing, and we demonstrated interoperability at Tokyo, and we'll be at TPAC
Leonard: On the technical details of the demo, I saw mentioned proprietary formats used. Which open metadata standards is the Japanese industry using, and which your organisation is promoting?
Kaz: This is a CG and they're gathering proprietary approaches from industry as a starting point. The next steps would be thinking about a concrete standard platform
Leonard: So are they using IPTC or EXIF, is the focus on proprietary formats?
Kaz: They also use those formats but each company uses the formats a bit differently
Endo: They originally used open standard formats, but nowadays more proprietary formats are used. We shared the status that we can't only exchange with open standards, it's important that we share the status
Chris: Who are the main stakeholders who've contributed so far?
Endo: For media content, as mentioned, IPTC, TV Anytime forums, they have some challenges
… CG members include NHK and other broadcasters from the broadcasting industry, and Japan's broadcasting metadata provider
… From publishing industry, the four major publishers, Shogakukan, Kodansha, Kadokawa
… For geolocation prototypes, browser vendor, Access, contributed
cpn: At what point do you see this moving to specification work?
… Are you ready to look at controlled vocabularies, or are you in the requirements gathering phase?
Chris: Is there more to do in requirements gathering phase, or are you ready to look at potential new specs, e.g., on schema vocabulary?
Endo: The demos show that we can identify these common issues
Kaz: The gathering of best practices from these industry silos, there's a CG report mentioning the pain points and potential solutions. We'd like to publish as official report at some point
… We'll translate into English
<kaz> draft CG report
Chris: I wonder about other geographies and whether industries there have similar issues
Kaz: Each industry has its own standard, ARIB, Schema.org, so the industries are siloed. Advanced providers like NHK would like to use all the metadata, from broadcasting, events, location, publishing, and IME inputs, and integrate all the information as a consolidated kind of database
… And have some mechanism for indexing
Leonard: It would be useful also to present what's missing from standards that has pushed the industry towards proprietary solutions
Kaz: And that could include handling of service IDs and trust of data
Media WG rechartering status
Chris: [shares Media WG Charter on screen]
… Charter was approved by the AC.
… Scope is mostly the same as before.
… Same specifications, work continues on those.
… Most of the specs are at WD status
… The goal is to get as many to CR as we can.
… Many features shipped in browsers already, if we don't have CR status
… then we don't necessarily have the IPR commitments on the latest changes,
… and we want to drive increased interoperability within each of these features.
… The AC review feedback generated comments largely around EME.
… The Charter talks a bit about a narrow scope of work with EME,
… whereas the feature scope is more flexible with the other specs.
… With EME we would require rechartering to do anything out of the tight scope of the EME section.
… The AC prefers to stay with that approach rather than being more open-ended about the
… scoping of the work we do on EME.
… There's text under WebCodecs about including a way to represent encrypted audio and video
… chunks in WebCodecs.
… If you move to a world of low latency delivery using WebTransport and MoQ, there isn't
… necessarily the equivalent capability to protect high value commercial content on the web.
… Perhaps you're using WebCodecs as you're decoder to feed into a canvas rendering pipeline.
… The Charter gives us permission to investigate what this looks like in a WebCodecs context.
Leonard: The original Charter had Images, but the group didn't do anything about it?
Chris: There is an Image decoder in WebCodecs.
Leonard: Is it implemented?
Chris: I think so, I haven't used it myself.
… [looks up on caniuse] Yes, it's implemented.
… Image Decoding is §10 of WebCodecs.
<kaz> WebCodecs - 10. Image Decoding
Leonard: Wonderful, I didn't know about that.
Chris: It seems like it's not implemented in Safari, but it is in other engines.
… This caused a bit of concern especially from TAG about extending the scope of encrypted media.
… Some feedback from Nick Doty who is a privacy specialist.
… Concerns about the risks of access to online media in general and privacy issues.
… The WG has work to do to navigate this and find solutions that everyone will be happy with.
… The Charter is approved for the next 2 years.
… Hopefully moving more specs towards CR.
… Happy to answer any questions around that.
… This group has an important role to play in terms of industry liaisons.
… We have feedback we need to follow up on, e.g. discussions with SVTA about their
… implementation experience of using MSE and EME.
… I'm hoping we can follow up with them fairly soon - it's important implementation feedback.
MEIG rechartering (our current charter expires 31 October)
<kaz> MEIG Charter
Chris: Our group's Charter ends at the end of October, before TPAC this year.
… We will start the process of requesting rechartering very soon so we can get something
… approved ideally or Kaz, if we need to ask for an extension?
Kaz: Since it's an IG the Chairs and I can come up with a new charter draft.
… We may need one or two months extension, but 3 months can easily be got.
… We need the status in September.
Chris: I'm proposing a continuation, unless anyone wants to propose a change of scope or direction.
… At the moment we are very broadly focused around anything related to media industry interests.
… Primarily audio and video assets.
… We're a home for standardisation requirements and use cases.
… As you've seen today we talked about metadata for exchange.
… In other cases we've talked about how to build TV applications using web technologies.
… How do we apply web technologies in a content production environment?
… Quite a broad range.
… I'm happy to support continuing this broad range.
… If we think a narrower focus is needed then we can consider that as well.
… Absent specific feedback the proposal will be to take it to AC largely as a continuation of what we are doing.
… Not sure if I have a lot else to say...
… There is wider discussion about whether IGs are a good thing in general for W3C, or if this
… should be a community group rather than an interest group.
… If you have opinions on that, either way, I would be interested to hear from you.
… We will produce an updated charter and come back with something for you to review.
… The success of the group depends on you - we rely on you to bring relevant and motivating
… topics that give us opportunities to represent industry group interests into other W3C groups.
… Thank you to all of you for your continued support.
Nigel: The charter at the moment has a long list of external organisations. Any thoughts for reviewing those, any new ones to add or ones to remove? OASIS as example. SVTA, ISO/IEC JTC1/SC 29, I sent a liaison to them recently. Suggest refreshing the list
Chris: I very much agree. Interesting that we're not in active conversation with these groups.
… We could do more of that, deliberate outreach to these groups.
… They're there because at one point we've had exchange with them,
… but not necessarily an ongoing dialogue. That could be a healthy thing for us to bring back,
… to build and maintain those relationships.
… Some work very well. like CTA and WAVE, we have very good relations with.
… Point taken, I agree.
Kaz: I agree with both of you.
… The starting point should be a copy of the current Charter applied to the current Charter Template.
Chris: Let's do that. Thank you.
… Any other comments on this topic?
DataCue
Rob: A quick update, in our July meeting, Ken presented the Sync on the Web CG, and a DMX lighting use case, for live screenings (staged event relayed to remote locations such as a cinema or theatre)
… and the local lighting is sent to the remote event
… Low latency needed
… Seemed like an ideal candidate for VMT and DataCue. We've been discussing over the last month or so. Ken released a demo, and I have an updated DataCue demo
… We're developing it further, exploring possibilities. It's a positive constructive collaboration, we're moving forwards on this aspect of DataCue
… It's a novel application of VMT that I hadn't considered
… The VMT engine allows access to access to timed metadata. I have a demo that surfaces MISB binary data in a browser, synchronised, delivered as Uint8Array
… Metadata packets are stripped from the video using an offline utility
… https://
TPAC
<kaz> TPAC 2025 schedule page
Chris: The meeting schedule has been published, next step for us is creating the agenda
IMSC 1.3
<kaz> IMSC Text Profile 1.3
Nigel: We've removed the image profile from this version of the spec, adds Japanese characters, super/subscript, and removes the IMSC HRM to another spec
… We've resolved to publish another snapshot of DAPT, hopefully the last before going to Rec. The test suite is complete and there's an implementation report
Next meeting
Chris: September 2. I'll be in touch before then on scope of the topics we've just discussed today
[adjourned]