W3C home > Mailing lists > Public > public-tt@w3.org > January 2009

Re: semantics of unbound region attribute.

From: Glenn A. Adams <gadams@xfsi.com>
Date: Fri, 30 Jan 2009 17:00:09 +0800
To: Sean Hayes <Sean.Hayes@microsoft.com>, Public TTWG List <public-tt@w3.org>
Message-ID: <C5A8E299.8FE6%gadams@xfsi.com>

Actually, the text in 9.3.1 effectively defines the algorithm for
associating content elements with regions. See the REGION-OF() pseudo
function. However, since this was an example of an implementation of the
(prose) description of the algorithm just above the example, what we need to
do is add normative text that defines this association. I have done that in
the just posted draft, and marked Issue #42 as closed.

Note that the example you give below of:

<body region="r1 r2">

is not presently supported, since the value of the region attribute must be
a single IDREF.


On 12/11/08 1:20 AM, "Sean Hayes" <Sean.Hayes@microsoft.com> wrote:

> Another issue that has concerned me lately is what it means when the region
> attribute is unspecified. According to the spec, this simply means the
> sub-tree does not show up in the rendering, Which is fine and simple to
> understand and implement; however Iım wondering if it should perhaps instead
> have the special meaning of Œany regionı.
> For example:
>  <body>
>    <div region="r1">
>      <p tts:color="red" begin="0s" end="10s">This text must be red.</p>
>    </div>
>      <div region="r2">
>          <p tts:color="blue" begin="0s" end="10s">This text must be blue.</p>
>      </div>
>   </body>
> In this case, clearly the intent is that div 1 shows up in r1 and div 2 shows
> up in r2, however without specifying <body region="r1 r2">  this wonıt happen.
> In complex scenarios I can imagine the amount of region attributes getting
> quite tedious. 
> Also, if as we have discussed, we are going to allow the idea of an anonymous
> default region, which I think most of the test suite now relies on, we will
> need some sort of rule like this anyway in order to get content to be targeted
> at that anonymous region.
> We could still allow that an explicit declaration of no region <body
> region=""> means that it will show up in no region at all to retain the
> current semantics.
> Sean Hayes
> Media Accessibility Strategist
> Accessibility Business Unit
> Microsoft
> Office:  +44 118 909 5867,
> Mobile: +44 7875 091385
Received on Friday, 30 January 2009 09:00:53 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:24:03 UTC