Chris Needham

> would it be correct to interpret that the current expectation is all emsg would be a single Track exposed for consumption? That's the current thinking, yes. But this does...

I have done some experiments with this, will post the results here soon.

@mavgit A slight variation on those scenarios you describe, but if those programs are followed by some other program, then we _would_ need to update the cue end time, to...

> In some scenarios, it may be valuable for the mp4 parser to itself do parsing on the contents of the 'emsg' box for some URNs and pass simplified data...

You're right, that's an oversight. I suggest we change `ArrayBuffer data` in the table to hold the parsed data.

> How does a webpage know whether the data field is the raw data or parsed data? My idea for this was in my previous comment, where we could have...

Yes, that's exactly it. I'll update the explainer.

I have updated the explainer, which hopefully clarifies handling of parsed vs unparsed data. Do we still need to look at how to support exposing subsets of the message data?

We discussed on the call yesterday ([minutes](https://www.w3.org/2020/06/15-me-minutes.html#item04)) that having both `data` and `value` fields seems redundant, and that applications could simply check if the `value` is an `ArrayBuffer` to determine...

I'll close, having updated the explainer. Please take a look, and feel free to re-open if there's anything I've missed.