Re: Track "id" format?

I agree on using a string, and personally lean toward using a hex representation.

The reason for using a hex number would be that it doesn't have any other obvious implications to most people. It's just an Id.

I was also leaning toward a requirement that the id start with a number character, which would prevent clashes with user-defined ids. This requirement has been dropped from html5 though…

From: Bob Lund <B.Lund@CableLabs.com<mailto:B.Lund@CableLabs.com>>
Date: Monday, November 11, 2013 2:07 PM
To: Brendan Long <b.long@cablelabs.com<mailto:b.long@cablelabs.com>>, "public-inbandtracks@w3.org<mailto:public-inbandtracks@w3.org>" <public-inbandtracks@w3.org<mailto:public-inbandtracks@w3.org>>
Subject: Re: Track "id" format?
Resent-From: <public-inbandtracks@w3.org<mailto:public-inbandtracks@w3.org>>
Resent-Date: Monday, November 11, 2013 2:08 PM



From: Brendan Long <B.Long@cablelabs.com<mailto:B.Long@cablelabs.com>>
Date: Monday, November 11, 2013 11:54 AM
To: "public-inbandtracks@w3.org<mailto:public-inbandtracks@w3.org>" <public-inbandtracks@w3.org<mailto:public-inbandtracks@w3.org>>
Subject: RE: Track "id" format?
Resent-From: <public-inbandtracks@w3.org<mailto:public-inbandtracks@w3.org>>
Resent-Date: Monday, November 11, 2013 11:54 AM

mkvinfo<http://www.bunkus.org/videotools/mkvtoolnix/doc/mkvinfo.html> is the only program I've been able to find so far that displays the TrackUID, and it displays it as a decimal number.


________________________________
From: Brendan Long [B.Long@cablelabs.com<mailto:B.Long@cablelabs.com>]
Sent: Monday, November 11, 2013 11:37 AM
To: public-inbandtracks@w3.org<mailto:public-inbandtracks@w3.org>
Subject: Track "id" format?

I'm trying to implement the "id" attribute for in-band tracks<https://bugzilla.gnome.org/show_bug.cgi?id=711522>, and I'm wondering how IDs should be formatted.

For example, MPEG-TS's PID<https://en.wikipedia.org/wiki/MPEG_transport_stream#PID> is 13 bits, but I'm not sure if there's a standard non-binary way of representing it. Matroska / WebM have an arbitrary sized unsigned integer TrackUID<http://matroska.org/technical/specs/index.html#TrackUID>. Should we represent them as decimal, hexidecimal, or something else?

Id is DOMSTRING. Why not a string representation of the id as a decimal number? Could also allow hex if the representation conformed to 0xNNN.



I assume we should use whatever formatting is common for each format, but I don't know what this is. Is there a good way to decide on this, or even better, an already-existing standard?