Media Capabilities issue review

Hi Media WG,

Following our last WG meeting on Media Capabilities, I've done a review of the open issues, closed a few, added comments and summaries to some, and added milestones based on my understanding of our current priorities.

V1 milestone: Issues and PRs within current existing API scope. This is not to say that every issue needs to result in a spec change, but these are the ones that I think we should prioritise. It includes spec clarifications, HDR metadata support, privacy considerations.

Issues: https://github.com/w3c/media-capabilities/issues?q=is%3Aopen+is%3Aissue+milestone%3AV1

Pull requests: https://github.com/w3c/media-capabilities/pulls?q=is%3Aopen+is%3Apr+milestone%3AV1

I have also added labels:


  *   Issues where the next step is to create a PR are labelled "pr-needed": https://github.com/w3c/media-capabilities/issues?q=is%3Aissue+is%3Aopen+label%3Apr-needed


  *   Issues needing further input on GitHub or group discussion are labelled "agenda": https://github.com/w3c/media-capabilities/issues?q=is%3Aopen+is%3Aissue+label%3Aagenda

V2 milestone: Issues and PRs that may result in additions to current API scope. This includes text track capability detection, transitions between configurations, and a dedicated API for audio rendering (as opposed to decoding) capabilities.

Issues: https://github.com/w3c/media-capabilities/issues?q=is%3Aopen+is%3Aissue+milestone%3AV2

Pull requests: https://github.com/w3c/media-capabilities/pulls?q=is%3Aopen+is%3Apr+milestone%3AV2

No milestone: General questions or feature suggestions not currently agreed to be in scope.

Issues: https://github.com/w3c/media-capabilities/issues?q=is%3Aopen+is%3Aissue+no%3Amilestone

Feel free to suggest a different priority for any of these. I suggest we discuss the "agenda" labelled items in our next WG meeting on January 9.

Many thanks,

Chris