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 27307 - In the DASH section, the track id attribute needs to be unique across Periods
Summary: In the DASH section, the track id attribute needs to be unique across Periods
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Sourcing In-band Media Resource Tracks (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Bob Lund
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-11 23:35 UTC by Bob Lund
Modified: 2014-11-12 21:44 UTC (History)
5 users (show)

See Also:

Attachments

Description Bob Lund 2014-11-11 23:35:04 UTC 
Bug 26921 [1] proposed setting the track id so that the id would be unique across periods. In comment 2 of that bug is was agreed to set the id to the tuple ("Period@id","AdaptationSet@id"[,"ContentComponent@id"]). This change didn't make it into the PR that closed bug 26921.

This change still needs to be done.


[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=26921
Comment 1 Bob Lund 2014-11-12 21:44:17 UTC 
(In reply to Bob Lund from comment #0)
> Bug 26921 [1] proposed setting the track id so that the id would be unique
> across periods. In comment 2 of that bug is was agreed to set the id to the
> tuple ("Period@id","AdaptationSet@id"[,"ContentComponent@id"]). This change
> didn't make it into the PR that closed bug 26921.
> 
> This change still needs to be done.
> 
> 
> [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=26921

Thinking some more about this bug, why does the application need the HTML track id have to contain the id of the current Period? Why can't the HTML track id be the media resource track id? Seems like only one Period is active at a time and media resources require track ids to be unique.