- From: Conrad Parker <conrad@metadecks.org>
- Date: Wed, 27 Jan 2010 20:35:45 +0900
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Cc: Philip Jägenstedt <philipj@opera.com>, public-media-fragment@w3.org
2010/1/27 Silvia Pfeiffer <silviapfeiffer1@gmail.com>: > 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. Only partly, doesn't YouTube also allow an m, eg. 5m42s > I'm not sure if we have a record of that decision though. I don't recall a decision to include the YouTube syntax either, though we have surely talked about it. Conrad.
Received on Wednesday, 27 January 2010 11:36:32 UTC