- From: Bob Lund <B.Lund@CableLabs.com>
- Date: Mon, 11 Nov 2013 23:19:46 +0000
- To: Brendan Long <B.Long@cablelabs.com>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- CC: Eric Winkelman <E.Winkelman@cablelabs.com>, "public-inbandtracks@w3.org" <public-inbandtracks@w3.org>
On 11/11/13 4:16 PM, "Brendan Long" <B.Long@cablelabs.com> wrote: >> No, it's not "just a string" - it's a DOMString, which is defined as a >> sequence of code units, commonly interpreted as UTF-16 encoded >> strings: > >> I'd recommend to follow the Javascript/ECMAScript toString() method: >> >>https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_ >>Objects/Object/toString > >I think encoding is only an issue for Ogg Skeleton. My question was >mainly about how we handle integers (Matroska) or unspecified binary >(MPEG-TS). > >To give you an idea of what I mean, I'm looking for something like: > > * Matroska / WebM: "id" should contain the TrackUID formatted as a >decimal number (example: id="81"). > * MPEG-TS: "id" should contain the PID, formatted as "0x"-prefixed >hexadecimal (example: id="0x51"). > * Ogg: "id" should contain the Name header, decoded from UTF-8, if it >exists, otherwise it should be the stream serial number, formatted as a >decimal number. Why not use the above and specify it in the CG spec? > >Note that decimal formatting might be better for MPEG-TS too. This is >just an example.
Received on Monday, 11 November 2013 23:20:16 UTC