Re: feedback on use cases and requirements

Thanks for the trust. :-)

However, I think we should review the clock time specification, see
http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/#clock-time

At the moment it follows RTSP, e.g.
t=clock:20090726T111901Z,20090726T112001Z

This can be fairly unreadabe.

I just checked HTML5 and they have done their own variant of the ISO
8601 format, see
http://www.whatwg.org/specs/web-apps/current-work/#dates-and-times

Examples are:
"0037-12-13T00:00Z"      => midnight 13th Dec 37, UTC timezone
"1979-10-14T12:00:00.001-04:00" => 14th Oct 1979, midday plus 1
microsecond, UTC-4hrs

The advantages are that we stay in sync with HTML, it's slightly more
readable, and we provide the possibility of including timezones.

What do others think about this?

Cheers,
Silvia.


2009/8/20 Raphaël Troncy <Raphael.Troncy@cwi.nl>:
> Hi Silvia,
>
>> This is to address my ACTIONs 94, 97, and 98:
>> http://www.w3.org/2008/WebVideo/Fragments/tracker/actions/94
>> http://www.w3.org/2008/WebVideo/Fragments/tracker/actions/97
>> http://www.w3.org/2008/WebVideo/Fragments/tracker/actions/98
>
> Awesome ! Thanks, I have closed these 3 actions in the tracker!
>
>  Raphaël
>
> --
> Raphaël Troncy
> EURECOM, Multimedia Communications Department
> 2229, route des Crêtes, 06560 Sophia Antipolis, France.
> e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com
> Tel: +33 (0)4 - 9300 8242
> Fax: +33 (0)4 - 9000 8200
> Web: http://www.cwi.nl/~troncy/
>

Received on Thursday, 20 August 2009 22:14:30 UTC