ISSUE-179: {audio,video} require param child (or equivalent)

av_param

{audio,video} require param child (or equivalent)

State:
CLOSED
Product:
HTML 5 spec
Raised by:
Sam Ruby
Opened on:
2011-09-25
Description:
This issue was raised on behalf of Glenn Adams, based on the following bug: http://www.w3.org/Bugs/Public/show_bug.cgi?id=13333

---

As currently defined, the audio|video elements do not define a mechanism to
permit the content author to specify arbitrary parameters to the user agent to
be used in transporting, decoding, rendering, and controlling the audio|video
content. Prior to HTML5, this was accomplished using the object element while
specifying such parameters using the param element child of object.

In order to maintain continuity and support for such pre-existing usage and to
permit migration from object to the new audio|video elements, the audio|video
elements should similarly support a standardized mechanism by means of which
various arbitrary parameters may be communicated to the user agent.

An important use case for such feature is manifested when using audio|video
elements to refer to content sourced within a UPnP or DLNA ecosystem. In the
usage scenarios employed therein, a ContentDirectoryService (CDS) exposes two
important pieces of information for audio|video content items:

(1) a URL that references the content on a server;
(2) an arbitrary list of {name,value} parameters encoded in the fourth field of
what UPnP refers to as a 'ProtocolInfo' data structure;

In order for an HTML5 user agent to dereference and effect transport, decoding,
playback, and control of such audio|video content, it is necessary to supply
both the URL and this arbitrary set of parameters to the user agent, wherein
the user agent itself semantically interprets those parameters that it
recognizes, while ignoring those it does not recognize.

Due to the arbitrary nature of this parameter set, it is not possible to a
priori define specific attributes to carry the individual parameters
communicated in this fashion; therefore, a standardized parameter mechanism,
such as pre-exists on the object element, should also be supported on
audio|video elements.

Furthermore, the data-* attribute mechanism or a non-standardized use of vendor
specific x-* attributes are not appropriate, since the former is prohibited
from being interpreted by the user agent, and the latter impedes
interoperability and goals of standardization.

Finally, the object element itself cannot be used in this case, merely to
obtain the use of its param children, without abandoning the new, desirable
features supported by the audio|video elements, such as timed text tracks,
media controllers, playback and seek semantics, and so forth.

It is therefore requested that the param element be supported as a child of the
audio|video elements in a fashion identical to the existing support for param
on the object element.

Proposed Changes:

In 4.8.5 (param), change 'Contexts in which this element can be used' to read
as follows:

<quote>
As a child of an audio, video, or object element, before any flow content.
</quote>

also in the subsequent prose of 4.8.5, make the following changes:

<quote>
The param element defines parameters for media components or plugins invoked by
audio, video, or object elements. It does not represent anything on its own.
</quote>

<quote>
If both attributes are present, and if the parent element of the param is an
audio, video, or object element, then the element defines a parameter with the
given name-value pair.
</quote>

<quote>
If either the name or value of a parameter defined by a param element that is
the child of an audio, video, or object element that represents an instantiated
media component or plugin changes, and if that media component or plugin is
communicating with the user agent using an API that features the ability to
update the media component or plugin when the name or value of a parameter so
changes, then the user agent must appropriately exercise that ability to notify
the media component or plugin of the change.
</quote>

In 4.8.6 (video), change 'Content Model' to read as follows:

<quote>
If the element has a src attribute: zero or more param elements, then zero or
more track elements, then transparent, but with no media element descendants.
If the element does not have a src attribute: zero or more param elements, then
zero or more source elements, then zero or more track elements, then
transparent, but with no media element descendants.
</quote>

In 4.8.7 (audio), change 'Content Model' to read as follows:

<quote>
If the element has a src attribute: zero or more param elements, then zero or
more track elements, then transparent, but with no media element descendants.
If the element does not have a src attribute: zero or more param elements, then
zero or more source elements, then zero or more track elements, then
transparent, but with no media element descendants.
</quote>
Related Actions Items:
Related emails:
  1. Re: {minutes} HTML WG telecon 2012-03-22 (from glenn@skynav.com on 2012-03-22)
  2. {minutes} HTML WG telecon 2012-03-22 (from glenn@skynav.com on 2012-03-22)
  3. {agenda} HTML WG telecon 2012-03-22: issue progress, heartbeat drafts, revert request, F2F registration, task force reports (from rubys@intertwingly.net on 2012-03-21)
  4. Working Group Decision: Close ISSUE-179 av_param by Amicable Resolution (from rubys@intertwingly.net on 2012-03-20)
  5. RE: {minutes} HTML WG telecon 2012-03-08: issue progress, heartbeat drafts, other topics (from adrianba@microsoft.com on 2012-03-15)
  6. {agenda} HTML WG telecon 2012-03-08: issue progress, heartbeat drafts, other topics (from mjs@apple.com on 2012-03-14)
  7. RE: Revert Request for 'http+aes' scheme (see also ISSUE-179) (from Paul.Cotton@microsoft.com on 2012-03-13)
  8. Re: Revert Request for 'http+aes' scheme (see also ISSUE-179) (from watsonm@netflix.com on 2012-03-09)
  9. RE: CfC: Close ISSUE-179 av_param by Amicable Resolution (from Paul.Cotton@microsoft.com on 2012-03-09)
  10. Re: CfC: Close ISSUE-179 av_param by Amicable Resolution (from hsivonen@iki.fi on 2012-03-09)
  11. Re: Revert Request for 'http+aes' scheme (see also ISSUE-179) (from kornel@geekhood.net on 2012-03-09)
  12. RE: Revert Request for 'http+aes' scheme (see also ISSUE-179) (from Paul.Cotton@microsoft.com on 2012-03-08)
  13. {minutes} HTML WG telecon 2012-03-08: issue progress, heartbeat drafts, F2F meeting plans, task force reports (from glenn@skynav.com on 2012-03-08)
  14. Re: {agenda} HTML WG telecon 2012-03-08: issue progress, heartbeat drafts, F2F meeting plans, task force reports (from glenn@skynav.com on 2012-03-08)
  15. CfC: Close ISSUE-179 av_param by Amicable Resolution (from Paul.Cotton@microsoft.com on 2012-03-08)
  16. {agenda} HTML WG telecon 2012-03-08: issue progress, heartbeat drafts, F2F meeting plans, task force reports (from Paul.Cotton@microsoft.com on 2012-03-08)
  17. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-07)
  18. Re: Revert Request for 'http+aes' scheme (see also ISSUE-179) (from watsonm@netflix.com on 2012-03-07)
  19. {agenda} HTML WG telecon 2012-03-08: issue progress, heartbeat drafts, F2F meeting plans, task force reports (from Paul.Cotton@microsoft.com on 2012-03-07)
  20. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from lachlan.hunt@lachy.id.au on 2012-03-07)
  21. Re: Revert Request for 'http+aes' scheme (see also ISSUE-179) (from julian.reschke@gmx.de on 2012-03-07)
  22. Re: Revert Request for 'http+aes' scheme (see also ISSUE-179) (from kornel@geekhood.net on 2012-03-07)
  23. Re: Revert Request for 'http+aes' scheme (see also ISSUE-179) (from laura.lee.carlson@gmail.com on 2012-03-07)
  24. Revert Request for 'http+aes' scheme (see also ISSUE-179) (from julian.reschke@gmx.de on 2012-03-07)
  25. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from lachlan.hunt@lachy.id.au on 2012-03-07)
  26. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-03-07)
  27. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-03-07)
  28. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-03-07)
  29. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-07)
  30. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-07)
  31. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from lachlan.hunt@lachy.id.au on 2012-03-07)
  32. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-06)
  33. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-06)
  34. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-06)
  35. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-06)
  36. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kaiserc@google.com on 2012-03-06)
  37. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from lachlan.hunt@lachy.id.au on 2012-03-06)
  38. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-03-06)
  39. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-03-06)
  40. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-06)
  41. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-06)
  42. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-03-06)
  43. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-03-06)
  44. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kaiserc@google.com on 2012-03-05)
  45. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-05)
  46. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-05)
  47. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-05)
  48. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-05)
  49. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kstreete@adobe.com on 2012-03-05)
  50. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-05)
  51. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-05)
  52. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-05)
  53. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-05)
  54. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-05)
  55. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-03-05)
  56. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-05)
  57. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-05)
  58. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-05)
  59. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-03-05)
  60. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-05)
  61. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-05)
  62. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-05)
  63. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-05)
  64. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-05)
  65. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-05)
  66. RE: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from johnsim@microsoft.com on 2012-03-05)
  67. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-05)
  68. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-05)
  69. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-05)
  70. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-05)
  71. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-05)
  72. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-05)
  73. RE: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from johnsim@microsoft.com on 2012-03-05)
  74. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-03-05)
  75. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-03-05)
  76. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-03-05)
  77. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-03-05)
  78. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-03)
  79. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-03-03)
  80. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-03)
  81. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-03)
  82. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from ian@hixie.ch on 2012-03-03)
  83. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kaiserc@google.com on 2012-03-02)
  84. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-03-02)
  85. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bzbarsky@MIT.EDU on 2012-03-02)
  86. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-02)
  87. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-02)
  88. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-02)
  89. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-02)
  90. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from ian@hixie.ch on 2012-03-02)
  91. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-02)
  92. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-02)
  93. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-02)
  94. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bzbarsky@MIT.EDU on 2012-03-02)
  95. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-02)
  96. RE: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from johnsim@microsoft.com on 2012-03-02)
  97. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-03-02)
  98. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bzbarsky@MIT.EDU on 2012-03-02)
  99. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-03-02)
  100. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-02)
  101. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bzbarsky@MIT.EDU on 2012-03-02)
  102. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-02)
  103. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-02)
  104. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from mjs@apple.com on 2012-03-02)
  105. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-02)
  106. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-02)
  107. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-02)
  108. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-02)
  109. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-02)
  110. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-02)
  111. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-03-02)
  112. RE: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from adrianba@microsoft.com on 2012-03-02)
  113. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bzbarsky@MIT.EDU on 2012-03-02)
  114. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-03-02)
  115. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from silviapfeiffer1@gmail.com on 2012-03-02)
  116. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-03-02)
  117. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-03-02)
  118. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-03-02)
  119. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-01)
  120. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from dbaron@dbaron.org on 2012-03-01)
  121. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-01)
  122. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from C.Stevens@CableLabs.com on 2012-03-01)
  123. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-01)
  124. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-03-01)
  125. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-03-01)
  126. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-03-01)
  127. {minutes} HTML WG telecon 2012-03-01: issue progress and heartbeat drafts (from eoconnor@apple.com on 2012-03-01)
  128. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-03-01)
  129. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-29)
  130. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bzbarsky@MIT.EDU on 2012-02-29)
  131. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-29)
  132. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-29)
  133. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-29)
  134. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-29)
  135. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-29)
  136. {agenda} HTML WG telecon 2012-03-01: issue progress and heartbeat drafts (from rubys@intertwingly.net on 2012-02-29)
  137. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bzbarsky@MIT.EDU on 2012-02-29)
  138. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from Smylers@stripey.com on 2012-02-29)
  139. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-29)
  140. RE: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from lrosenth@adobe.com on 2012-02-29)
  141. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-02-29)
  142. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-29)
  143. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-02-29)
  144. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-02-29)
  145. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from Smylers@stripey.com on 2012-02-29)
  146. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-02-29)
  147. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from robert@ocallahan.org on 2012-02-29)
  148. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from robert@ocallahan.org on 2012-02-29)
  149. Re: Chair Review of the Change Proposals for issue 179 (from rubys@intertwingly.net on 2012-02-28)
  150. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-02-28)
  151. Re: Media Stack: closed source only Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-28)
  152. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-28)
  153. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-02-28)
  154. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-28)
  155. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-02-28)
  156. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-28)
  157. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-02-28)
  158. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-28)
  159. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-02-28)
  160. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-02-28)
  161. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-28)
  162. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-02-28)
  163. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-28)
  164. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-28)
  165. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-02-28)
  166. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-28)
  167. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-28)
  168. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-02-28)
  169. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-02-28)
  170. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from Mark_Vickers@cable.comcast.com on 2012-02-28)
  171. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-28)
  172. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-28)
  173. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-02-28)
  174. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-02-28)
  175. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from ddorwin@google.com on 2012-02-27)
  176. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bzbarsky@MIT.EDU on 2012-02-27)
  177. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-27)
  178. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bzbarsky@MIT.EDU on 2012-02-27)
  179. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-27)
  180. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from singer@apple.com on 2012-02-27)
  181. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-27)
  182. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-02-27)
  183. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bzbarsky@MIT.EDU on 2012-02-27)
  184. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-27)
  185. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bzbarsky@MIT.EDU on 2012-02-27)
  186. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-27)
  187. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-27)
  188. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from singer@apple.com on 2012-02-27)
  189. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from Mark_Vickers@cable.comcast.com on 2012-02-27)
  190. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from Mark_Vickers@cable.comcast.com on 2012-02-27)
  191. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from singer@apple.com on 2012-02-27)
  192. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-02-27)
  193. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from C.Stevens@cablelabs.com on 2012-02-27)
  194. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-02-27)
  195. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-02-27)
  196. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-02-27)
  197. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-26)
  198. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bhawkeslewis@googlemail.com on 2012-02-26)
  199. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-02-26)
  200. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from kornel@geekhood.net on 2012-02-26)
  201. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-02-25)
  202. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from Mark_Vickers@cable.comcast.com on 2012-02-25)
  203. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-02-25)
  204. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bzbarsky@MIT.EDU on 2012-02-25)
  205. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from C.Stevens@CableLabs.com on 2012-02-25)
  206. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-25)
  207. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-02-25)
  208. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from john@netpurgatory.com on 2012-02-25)
  209. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-25)
  210. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from john@netpurgatory.com on 2012-02-25)
  211. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-02-25)
  212. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-25)
  213. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-25)
  214. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from john@netpurgatory.com on 2012-02-25)
  215. Re: Open Source implementations Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-25)
  216. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-24)
  217. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from dbaron@dbaron.org on 2012-02-24)
  218. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-02-24)
  219. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-24)
  220. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from john@netpurgatory.com on 2012-02-24)
  221. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-24)
  222. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-24)
  223. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-02-24)
  224. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-24)
  225. RE: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from ian@hixie.ch on 2012-02-24)
  226. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from bzbarsky@MIT.EDU on 2012-02-24)
  227. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-24)
  228. Re: Arbitrary codecs and encryption schemes, was: Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-02-24)
  229. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from B.Lund@CableLabs.com on 2012-02-24)
  230. Re: Arbitrary codecs and encryption schemes, was: Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-02-24)
  231. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-02-24)
  232. RE: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from wayne.carr@intel.com on 2012-02-24)
  233. RE: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from john@foliot.ca on 2012-02-24)
  234. Arbitrary codecs and encryption schemes, was: Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-02-24)
  235. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from hsivonen@iki.fi on 2012-02-24)
  236. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-24)
  237. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-02-23)
  238. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-02-23)
  239. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-02-23)
  240. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-02-23)
  241. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-23)
  242. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-23)
  243. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from jackalmage@gmail.com on 2012-02-23)
  244. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from eric.carlson@apple.com on 2012-02-23)
  245. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from cpearce@mozilla.com on 2012-02-22)
  246. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from chuck@jumis.com on 2012-02-22)
  247. Chair Review of the Change Proposals for issue 179 (from rubys@intertwingly.net on 2012-02-22)
  248. Re: <param> (was Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-22)
  249. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-22)
  250. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from silviapfeiffer1@gmail.com on 2012-02-22)
  251. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-22)
  252. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-22)
  253. RE: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from adrianba@microsoft.com on 2012-02-22)
  254. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from watsonm@netflix.com on 2012-02-22)
  255. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-21)
  256. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-21)
  257. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from glenn@skynav.com on 2012-02-21)
  258. Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from ian@hixie.ch on 2012-02-21)
  259. Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals) (from adrianba@microsoft.com on 2012-02-21)
  260. [minutes] HTML WG telecon 2012-02-16: issue progress (from rubys@intertwingly.net on 2012-02-16)
  261. HTML WG telecon 2012-02-16: issue progress (from Paul.Cotton@microsoft.com on 2012-02-15)
  262. RE: {minutes} HTML WG telecon 2012-02-09: issue progress, task force reports, revert request, new information deadline, F2F (from adrianba@microsoft.com on 2012-02-09)
  263. HTML WG telecon 2012-02-09: issue progress, task force reports, revert request, new information deadline, F2F (from rubys@intertwingly.net on 2012-02-07)
  264. {minutes} HTML WG telecon 2012-01-26: issue progress (from glenn@skynav.com on 2012-02-02)
  265. RE: {agenda} HTML WG telecon 2012-01-26: issue progress (from Paul.Cotton@microsoft.com on 2012-02-02)
  266. Revert Request [was RE: {agenda} HTML WG telecon 2012-01-26: issue progress] (from john@foliot.ca on 2012-02-01)
  267. {agenda} HTML WG telecon 2012-01-26: issue progress (from mjs@apple.com on 2012-02-01)
  268. Re: {agenda} HTML WG telecon 2012-01-19: issue progress, other business (from janina@rednote.net on 2012-01-18)
  269. {agenda} HTML WG telecon 2012-01-19: issue progress, other business (from rubys@intertwingly.net on 2012-01-18)
  270. HTML WG minutes (Re: {agenda} HTML WG telecon 2012-01-12: issue progress, other business) (from mjs@apple.com on 2012-01-12)
  271. {agenda} HTML WG telecon 2012-01-12: issue progress, other business (from mjs@apple.com on 2012-01-12)
  272. ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals (from mjs@apple.com on 2012-01-11)
  273. {minutes} HTML WG telecon 2011-12-15: issue progress, other business (from rubys@intertwingly.net on 2011-12-22)
  274. {agenda} HTML WG telecon 2011-12-15: issue progress, other business (from rubys@intertwingly.net on 2011-12-21)
  275. {minutes} HTML WG telecon 2011-12-15: issue progress, editor's drafts, speech xg (from eoconnor@apple.com on 2011-12-15)
  276. {agenda} HTML WG telecon 2011-12-15: issue progress, editor's drafts, speech xg (from mjs@apple.com on 2011-12-14)
  277. RE: {minutes} HTML WG telecon 2011-12-08: actions, issues and task force reports (from adrianba@microsoft.com on 2011-12-08)
  278. {agenda} HTML WG telecon 2011-12-08: actions, issues and task force reports (from Paul.Cotton@microsoft.com on 2011-12-07)
  279. {minutes} HTML WG telecon 2011-12-01: actions and issues (from eoconnor@apple.com on 2011-12-01)
  280. {agenda} HTML WG telecon 2011-12-01: actions and issues (from Paul.Cotton@microsoft.com on 2011-11-29)
  281. {minutes} HTML WG telecon 2011-11-17: action, issue, and task force updates (from rubys@intertwingly.net on 2011-11-17)
  282. Re: {agenda} HTML WG telecon 2011-11-17: action, issue, and task force updates (from glenn@skynav.com on 2011-11-16)
  283. {agenda} HTML WG telecon 2011-11-17: action, issue, and task force updates (from rubys@intertwingly.net on 2011-11-16)
  284. {minutes} HTML WG telecon 2010-10-20: action and issue updates (from rubys@intertwingly.net on 2011-11-10)
  285. {agenda} HTML WG telecon 2010-10-20: action and issue updates (from mjs@apple.com on 2011-11-09)
  286. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from giuseppep@opera.com on 2011-11-06)
  287. Re: minutes for HTML WG f2f, 2011-11-04, part 1 (from rubys@intertwingly.net on 2011-11-05)
  288. Re: minutes for HTML WG f2f, 2011-11-04, part 1 (from tantek@cs.stanford.edu on 2011-11-05)
  289. minutes for HTML WG f2f, 2011-11-04, part 1 (from mike@w3.org on 2011-11-05)
  290. minutes of HTML WG f2f 2011-11-03 (from mike@w3.org on 2011-11-04)
  291. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from watsonm@netflix.com on 2011-11-03)
  292. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from silviapfeiffer1@gmail.com on 2011-10-31)
  293. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from xn--mlform-iua@xn--mlform-iua.no on 2011-10-30)
  294. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from hsivonen@iki.fi on 2011-10-30)
  295. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from fielding@gbiv.com on 2011-10-30)
  296. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from silviapfeiffer1@gmail.com on 2011-10-30)
  297. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from glenn@skynav.com on 2011-10-30)
  298. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from annevk@opera.com on 2011-10-29)
  299. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from silviapfeiffer1@gmail.com on 2011-10-29)
  300. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from glenn@skynav.com on 2011-10-29)
  301. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from silviapfeiffer1@gmail.com on 2011-10-29)
  302. RE: {minutes} HTML WG telecon 2010-10-27: issue updates, task force reports (from adrianba@microsoft.com on 2011-10-27)
  303. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from silviapfeiffer1@gmail.com on 2011-10-26)
  304. Re: ISSUE-179 av_param: Chairs Solicit Proposals (from glenn@skynav.com on 2011-10-26)
  305. {agenda} HTML WG telecon 2010-10-27: issue updates, task force reports (from Paul.Cotton@microsoft.com on 2011-10-26)
  306. {minutes} HTML WG telecon 2010-10-20: issue updates (from eoconnor@apple.com on 2011-10-20)
  307. {agenda} HTML WG telecon 2010-10-20: issue updates (from rubys@intertwingly.net on 2011-10-19)
  308. RE: {minutes} HTML WG telecon 2011-09-29: Issue progress, Task Force reports (from adrianba@microsoft.com on 2011-09-29)
  309. RE: {minutes} HTML WG telecon 2011-09-29: Issue progress, Task Force reports (from adrianba@microsoft.com on 2011-09-29)
  310. {agenda} HTML WG telecon 2011-09-29: Issue progress, Task Force reports (from rubys@intertwingly.net on 2011-09-27)
  311. ISSUE-179 av_param: Chairs Solicit Proposals (from rubys@intertwingly.net on 2011-09-27)
  312. HTML-ISSUE-179 (av_param): {audio,video} require param child (or equivalent) [HTML 5 spec] (from sysbot+tracker@w3.org on 2011-09-25)

Related notes:

http://lists.w3.org/Archives/Public/public-html/2012Mar/0554.html

Sam Ruby, 20 Mar 2012, 15:18:25

[glenn]: av_param, Agree/Disagree to Amicable Resolution closed Mar 15

22 Mar 2012, 16:05:13

Changelog:

Created issue '{audio,video} require param child (or equivalent)' nickname av_param owned by Sam Ruby on product HTML 5 spec, description 'This issue was raised on behalf of Glenn Adams, based on the following bug: http://www.w3.org/Bugs/Public/show_bug.cgi?id=13333

---

As currently defined, the audio|video elements do not define a mechanism to
permit the content author to specify arbitrary parameters to the user agent to
be used in transporting, decoding, rendering, and controlling the audio|video
content. Prior to HTML5, this was accomplished using the object element while
specifying such parameters using the param element child of object.

In order to maintain continuity and support for such pre-existing usage and to
permit migration from object to the new audio|video elements, the audio|video
elements should similarly support a standardized mechanism by means of which
various arbitrary parameters may be communicated to the user agent.

An important use case for such feature is manifested when using audio|video
elements to refer to content sourced within a UPnP or DLNA ecosystem. In the
usage scenarios employed therein, a ContentDirectoryService (CDS) exposes two
important pieces of information for audio|video content items:

(1) a URL that references the content on a server;
(2) an arbitrary list of {name,value} parameters encoded in the fourth field of
what UPnP refers to as a 'ProtocolInfo' data structure;

In order for an HTML5 user agent to dereference and effect transport, decoding,
playback, and control of such audio|video content, it is necessary to supply
both the URL and this arbitrary set of parameters to the user agent, wherein
the user agent itself semantically interprets those parameters that it
recognizes, while ignoring those it does not recognize.

Due to the arbitrary nature of this parameter set, it is not possible to a
priori define specific attributes to carry the individual parameters
communicated in this fashion; therefore, a standardized parameter mechanism,
such as pre-exists on the object element, should also be supported on
audio|video elements.

Furthermore, the data-* attribute mechanism or a non-standardized use of vendor
specific x-* attributes are not appropriate, since the former is prohibited
from being interpreted by the user agent, and the latter impedes
interoperability and goals of standardization.

Finally, the object element itself cannot be used in this case, merely to
obtain the use of its param children, without abandoning the new, desirable
features supported by the audio|video elements, such as timed text tracks,
media controllers, playback and seek semantics, and so forth.

It is therefore requested that the param element be supported as a child of the
audio|video elements in a fashion identical to the existing support for param
on the object element.

Proposed Changes:

In 4.8.5 (param), change 'Contexts in which this element can be used' to read
as follows:

<quote>
As a child of an audio, video, or object element, before any flow content.
</quote>

also in the subsequent prose of 4.8.5, make the following changes:

<quote>
The param element defines parameters for media components or plugins invoked by
audio, video, or object elements. It does not represent anything on its own.
</quote>

<quote>
If both attributes are present, and if the parent element of the param is an
audio, video, or object element, then the element defines a parameter with the
given name-value pair.
</quote>

<quote>
If either the name or value of a parameter defined by a param element that is
the child of an audio, video, or object element that represents an instantiated
media component or plugin changes, and if that media component or plugin is
communicating with the user agent using an API that features the ability to
update the media component or plugin when the name or value of a parameter so
changes, then the user agent must appropriately exercise that ability to notify
the media component or plugin of the change.
</quote>

In 4.8.6 (video), change 'Content Model' to read as follows:

<quote>
If the element has a src attribute: zero or more param elements, then zero or
more track elements, then transparent, but with no media element descendants.
If the element does not have a src attribute: zero or more param elements, then
zero or more source elements, then zero or more track elements, then
transparent, but with no media element descendants.
</quote>

In 4.8.7 (audio), change 'Content Model' to read as follows:

<quote>
If the element has a src attribute: zero or more param elements, then zero or
more track elements, then transparent, but with no media element descendants.
If the element does not have a src attribute: zero or more param elements, then
zero or more source elements, then zero or more track elements, then
transparent, but with no media element descendants.
</quote>' non-public

Sam Ruby, 25 Sep 2011, 12:46:14

Status changed to 'open'

Sam Ruby, 26 Oct 2011, 12:05:33

Status changed to 'closed'

Sam Ruby, 20 Mar 2012, 15:18:25


Paul Cotton <Paul.Cotton@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, Sam Ruby <rubys@intertwingly.net>, Chairs, Michael[tm] Smith <mike@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $