W3C home > Mailing lists > Public > public-media-fragment@w3.org > January 2010

Re: Aligning NPT syntax with RTSP

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Wed, 27 Jan 2010 22:23:25 +1100
Message-ID: <2c0e02831001270323x6a79c5ev841de3d2a519b516@mail.gmail.com>
To: Philip Jägenstedt <philipj@opera.com>
Cc: public-media-fragment@w3.org
On Wed, Jan 27, 2010 at 10:09 PM, Philip Jägenstedt <philipj@opera.com> wrote:
> http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/#npttime
>
> This is what I mentioned in the teleconf. As it is, '0.' would not be a
> valid production of npttime but it is a valid production of npt-sec from
> RTSP [1]. The same is true of '00:00:00.'. The difference is in digits after
> the decimal point.

We currently have:

npttime	   ::=   	( 1*DIGIT [ "." 1*DIGIT ] [ timeunit ] ) |
			( 1*DIGIT ":" 2DIGIT ":" 2DIGIT [ "." 1*DIGIT] )

which I think you are proposing to change to

npttime	   ::=   	( 1*DIGIT [ "." *DIGIT ] [ timeunit ] ) |
			( 1*DIGIT ":" 2DIGIT ":" 2DIGIT [ "." *DIGIT] )

Correct?


> I would suggest simply importing npt-sec and npt-hhmmss from RFC2326,
> dropping the 's' completely for simplicity. Since it isn't needed to
> disambiguate and any existing software should tolerate omitting the s,
> removing it shouldn't be a problem, right?

IIRC, we added the "s" to be more compatible with some existing
implementations such as the YouTube spec.

I'm not sure if we have a record of that decision though.

> [1] http://www.ietf.org/rfc/rfc2326.txt

Cheers,
Silvia.
Received on Wednesday, 27 January 2010 11:24:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:37 GMT