[encrypted-media] "valid MIME type" does not link to the definition of a valid MIME type

ddorwin has just created a new issue for https://github.com/w3c/encrypted-media:

== "valid MIME type" does not link to the definition of a valid MIME type ==
In the [`contentType` defintion](http://w3c.github.io/encrypted-media/#dom-mediakeysystemmediacapability-contenttype), the link for "valid MIME type" currently links to [1]. The definition of "valid MIME type" is actually at [2].

Note that while other sections in the page at [1] link to [2], the section at [1] does _not_ link to [2]. It only references [3].

[1] is nice because it provides a media-specific view of MIME types, including mention of RFC 6381, but it does not define validity. It would be nice if there was a definition for "valid media MIME type." In the meantime, we may want to change the wording.

Related to this, the actual [algorithm](http://w3c.github.io/encrypted-media/#get-supported-capabilities-for-audio-video-type) that processes `contentType` does not reference a definition for "invalid or unrecognized MIME type." We may want to apply the same fix there.

[1] https://www.w3.org/TR/html51/semantics-embedded-content.html#mime-types.
[2] https://www.w3.org/TR/html51/infrastructure.html#valid-mime-type
[3] https://www.w3.org/TR/html51/infrastructure.html#mime-type

Please view or discuss this issue at https://github.com/w3c/encrypted-media/issues/415 using your GitHub account

Received on Friday, 9 June 2017 04:15:30 UTC