+1 for consistency, but defer to @Djuffin

It's unusual to add fields unless there is at least one implementation that makes use of them. But in this case compatibility with Encoded Transforms seems like a pretty good reason to add these fields.

I think we can even rename SvcOutputMetadata into something more relevant to video frames, Output doesn't seem to convey a lot of meaning outside of webcodecs' context.

The Encoded Transform metadata has now been updated. However, it still is not completely compatible with the WebCodecs extended SVC metadata proposal.

ed note: @aboba to send PR and @Djuffin to review.

A summary of where we are now.

Here is the RTCEncodedVideoFrameMetadata dictionary:

Here is what is in WebCodecs Section 6.7:

Here is what was in the extended WebCodecs SVC metadata proposal:

@pthatcherg @alvestrand Can you take a look?

Minutes from 11 Apr 2023 Media WG meeting: https://www.w3.org/2023/04/11-mediawg-minutes.html#t03