This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24986 - Add examples for return values from Video.kind and Audio.kind
Summary: Add examples for return values from Video.kind and Audio.kind
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: CR HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Silvia Pfeiffer
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 25044 25133
  Show dependency treegraph
 
Reported: 2014-03-10 16:29 UTC by Bob Lund
Modified: 2014-06-06 05:15 UTC (History)
8 users (show)

See Also:


Attachments

Description Bob Lund 2014-03-10 16:29:59 UTC
New use cases for setting @kind for in-band video and audio tracks for several media resources have been identified in the in-band tracks community group [1]. [2] shows new examples to be added to the existing "Return values for AudioTrack.kind() and VideoTrack.kind()" in [3].

[1] https://www.w3.org/community/inbandtracks/wiki/Main_Page
[2] https://www.w3.org/community/inbandtracks/wiki/Main_Page#Audio_and_video_kind_table
[3] http://www.w3.org/TR/html5/embedded-content-0.html#audiotracklist-and-videotracklist-objects
Comment 1 Silvia Pfeiffer 2014-03-17 07:23:50 UTC
I've expanded the section on AudioTrackList and VideoTrackList objects inside "4.7.10.10 Media resources with multiple media tracks" and included your feedback.

The patch is prepared here:
https://github.com/w3c/html/commit/9bed8bd1a939ec27c9627c49e5b3df0ef9397f17

Can you please check if that finds your approval before I merge it and ask the WHATWG to apply, too.
Comment 2 Bob Lund 2014-03-17 16:32:13 UTC
(In reply to Silvia Pfeiffer from comment #1)
> I've expanded the section on AudioTrackList and VideoTrackList objects
> inside "4.7.10.10 Media resources with multiple media tracks" and included
> your feedback.
> 
> The patch is prepared here:
> https://github.com/w3c/html/commit/9bed8bd1a939ec27c9627c49e5b3df0ef9397f17
> 
> Can you please check if that finds your approval before I merge it and ask
> the WHATWG to apply, too.

This looks good.
Comment 3 Silvia Pfeiffer 2014-04-08 01:56:05 UTC
@Bob could you comment on whether you'd be happy with having these mappings in a wiki page - or maybe even a separate W3C note (needs to be discussed with chairs)?
Comment 4 Bob Lund 2014-04-08 02:24:02 UTC
(In reply to Silvia Pfeiffer from comment #3)
> @Bob could you comment on whether you'd be happy with having these mappings
> in a wiki page - or maybe even a separate W3C note (needs to be discussed
> with chairs)?

Since this type of information was already in the HTML5 spec, it seemed natural to add to it, making it more complete. This information is really specific to HTML5.  There has been a lot of discussion on the proposed additions but the amount of new text is not really that large.

With that said, moving all of the information to another W3C document might make it easier to maintain. I wouldn't want to see some of the information in the HTML5 spec and other portions in another place. If it were moved, what find of reference would there be? A Wiki doesn't strike me as being appropriate - this is really normative behavior.

The above also applies to your comment on 24997 [1].


[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=24997#c14
Comment 5 Silvia Pfeiffer 2014-04-08 02:27:05 UTC
I think any of the options are possible. When we move that text out into another document (a W3C note or a wiki page), then we would tidy this up in the spec of course.

Would you mind explaining on the WHATWG bug which part you think is absolutely necessary to be in the HTML spec? I'd like to have this discussion with Ian. Thanks.
Comment 6 Cyril Concolato 2014-04-08 15:21:20 UTC
Would it make sense to have a registry of media formats for the HTML5 media elements (similarly to the MSE registry) and to define the normative behavior when those formats are supported there?
Comment 7 Bob Lund 2014-04-08 18:53:56 UTC
(In reply to Cyril Concolato from comment #6)
> Would it make sense to have a registry of media formats for the HTML5 media
> elements (similarly to the MSE registry) and to define the normative
> behavior when those formats are supported there?

I think this is a reasonable idea. I suggested it in response to Ian's question here https://www.w3.org/Bugs/Public/show_bug.cgi?id=25133#c2
Comment 8 Silvia Pfeiffer 2014-05-05 07:20:06 UTC
There is now a draft mapping spec available at http://rawgit.com/silviapfeiffer/HTMLSourcingInbandTracks/master/index.html . Feedback welcome.
Comment 9 Paul Cotton 2014-05-14 14:37:24 UTC
(In reply to Silvia Pfeiffer from comment #8)
> There is now a draft mapping spec available at
> http://rawgit.com/silviapfeiffer/HTMLSourcingInbandTracks/master/index.html
> . Feedback welcome.

See the Chairs recommendation on how to publish this document and how to reference it from the HTML5 spec:
http://lists.w3.org/Archives/Public/public-html-admin/2014May/0030.html

/paulc
HTML WG co-chair
Comment 10 Bob Lund 2014-05-15 19:48:44 UTC
(In reply to Paul Cotton from comment #9)
> (In reply to Silvia Pfeiffer from comment #8)
> > There is now a draft mapping spec available at
> > http://rawgit.com/silviapfeiffer/HTMLSourcingInbandTracks/master/index.html
> > . Feedback welcome.
> 
> See the Chairs recommendation on how to publish this document and how to
> reference it from the HTML5 spec:
> http://lists.w3.org/Archives/Public/public-html-admin/2014May/0030.html
> 
> /paulc
> HTML WG co-chair

Bug 25733 [1] has been opened to add an HTML5 reference to the sourcing spec.

[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=25733
Comment 11 Silvia Pfeiffer 2014-06-06 05:15:22 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:

   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description:
https://github.com/w3c/html/commit/792b76480c731e69327d997b40097d3631b61b64

Rationale: All of the examples for how to source attributes for in-band audio and video tracks is now in a new spec.