W3C home > Mailing lists > Public > public-tt@w3.org > December 2008

RE: timeContainer default value for body and div

From: Patrick Schmitz <cogit@ludicrum.org>
Date: Fri, 12 Dec 2008 22:22:33 -0800
To: "Sean Hayes" <Sean.Hayes@microsoft.com>, "Philippe Le Hegaret" <plh@w3.org>, "Glenn A. Adams" <gadams@xfsi.com>
Cc: <public-tt@w3.org>
Message-ID: <ENEGINNFOHPGHPIICCFJGEFMKBAB.cogit@ludicrum.org>

Originally in the XHTML+SMIL work, body defaulted to seq to align to SMIL.
The default for div should have been par (I think it was in XHTML+SMIL), as
that follows our common use-cases.

Patrick

> -----Original Message-----
> From: public-tt-request@w3.org [mailto:public-tt-request@w3.org]On
> Behalf Of Sean Hayes
> Sent: Friday, December 12, 2008 3:51 PM
> To: Philippe Le Hegaret; Glenn A. Adams
> Cc: public-tt@w3.org
> Subject: RE: timeContainer default value for body and div
>
>
>
> I think the thrust of the discussion was that less timing
> annotation could be achieved with body = par, div = seq and
> relative durations
>
> <div>
>   <p begin='1s' dur='1s' >Caption 1</p>
>   <p dur='1s' >Caption 2</p>
>   <p dur='1s' >Caption 3</p>
>   <p dur='1s' >Caption 4</p>
>   <p dur='1s' >Caption 5</p>
> </div>
>
> However I grant you that in all the content I am seeing, explicit
> begin and end timing seems to be the norm and this kind of
> relative authoring is somewhat uncommon, so perhaps par
> everywhere makes the most sense for interop with current tooling.
>
>
> Sean Hayes
> Media Accessibility Strategist
> Accessibility Business Unit
> Microsoft
>
> Office:  +44 118 909 5867,
> Mobile: +44 7875 091385
>
> -----Original Message-----
> From: Philippe Le Hegaret [mailto:plh@w3.org]
> Sent: 12 December 2008 22:37
> To: Sean Hayes; Glenn A. Adams
> Cc: public-tt@w3.org
> Subject: timeContainer default value for body and div
>
> On Fri, 2008-12-12 at 12:50 -0500, Geoff Freed wrote:
> > SH:  Next:  default timeContainer for <body>.  Currently is
> sequential.  Seems to be a mistake.
> >
> > GA:  It's the default of par on div.  Should be the other way
> around.  In general, divs are going to be targeted to a single
> region and the text that goes into a given region is going to be
> sequential by default.  Content to multiple regions are going to
> be in parallel.  For some reason we got it backwards.
>
>
> <div timeContainer='par'>
>   <p begin='1s' end='2s'>Caption1a</p>
>   <p begin='2s' end='3s'>Caption1b</p>
> </div>
>
> Caption1a is from 1s to 2s and then Caption1b from 2s to 3s.
>
> <div timeContainer='seq'>
>   <p begin='1s' end='2s'>Caption2a</p>
>   <p begin='2s' end='3s'>Caption2b</p>
> </div>
>
> Caption2a is from 1s to 2s and then Caption2 from 5s to 6s.
>
> So, I believe that the default value for div, which is par, is correct.
> That's what the implementations are doing.
>
> However, the default value for body, which is currently seq, is
> incorrect. We'd like the children to be displayed simultaneously, so we
> need to change the default to par as well.
>
> Philippe
>
>
>
>
>
Received on Saturday, 13 December 2008 06:23:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 2 November 2009 22:41:39 GMT