- From: Kouichi Uchimura <Kouichi.Uchimura@jp.sony.com>
- Date: Tue, 31 Jul 2012 12:19:53 +0900
- To: Glenn Adams <glenn@skynav.com>, "public-tt@w3.org" <public-tt@w3.org>
- Cc: Kouichi.Uchimura@jp.sony.com
Dear Glenn
Thank you for your reply. It is very helpful for me!
If I could ask some more for (a) and (c). (b) and (d) are clear.
(a)
What I'm asking is
because tts:backgroundColor is NOT inheritable.
Therefore I would like to know what text content or region(?)
will be affected by tts:backgroundColor specified in tt:body.
as like...
<definition of region r1... with tts:backgroundColor="red">
<body tts:backgroundColor="green">
<div region="r1">
<p backgroundColor="white">
text1
</p>
<p>
text2
</p>
</div>
</body>
What is background color of r1, text1 and text2?
And what is filled by green color?
(c)
> assuming for a moment that both regions r1 and r2 and the above content elements are temporally active over the interval of interest,
Yes. This was my assumption. Sorry for missing.
And thank you for considering this!
> "oh" will appear in both r1 and r2
The association of content and region is specifed in 9.3.2.
there is process to be applied. because <p> element does not
specify the region attribute inline (in step1).
Processer will find its ancestor elements(in step2).
As you can see my sample, there are no ancestor elements
defined the regoin, therefore process goes to step3.
My question is semantics of step3. It states
<snip>
if the element contains a descendant element that specifies a
region attribute, then the element is associated with the region
referenced by that
attribute;
</snip>
In my sample, the element (<== <p> element) contains
two decendant elements specify the regions.
> <p>
> oh
> <span region="r1">
> my
> <span region="r2">
> god
> </span>
> </span>
My interpretation here is the text
if the element contains a descendant element that specifies a
region attribute
does not apply to this case...
If your interpretation is intented by specificaton, it should be
if the element contains descendant elements that specifies
region attribute, the element si associated both region referenced by
each attribute
Please let me know the reason "oh" appears both r1 and r2.
best regards,
Uchimura
On Tue, 31 Jul 2012 01:25:55 +0900
Glenn Adams <glenn@skynav.com> wrote:
> uchimura-san, thanks for the good questions, which i attempt to answer inline below
>
> regards, glenn
>
> On Sun, Jul 29, 2012 at 6:41 PM, Kouichi Uchimura <Kouichi.Uchimura@jp.sony.com<mailto:Kouichi.Uchimura@jp.sony.com>> wrote:
> Hi,
>
> I have some questions to TTML specificaton.
> I appriciate if you reply my questions.
> Forgive me if there were same questions in archive...
>
> (a) What is expected if tts:backgroundColor is applied to body element?
>
> according to step (6) of [1], body is logically mapped to an outer fo:block element, which, in turn, would have as its children the fo:block elements mapped from tt:div; therefore, if tts:backgroundColor is specified on tt:body, it would apply to that outer fo:block;
>
> keep in mind that an implementation doesn't have to use XSL-FO directly; rather, the TTML spec uses XSL-FO as only a specification mechanism to define formatting semantics
>
> [1] http://www.w3.org/TR/ttaf1-dfxp/#semantics-region-layout-step-2
>
>
> (b) What is correct understanding of PRUNE (E) (defined in 9.3.2)
> ==>
> prune the element and its descendant elements
> or
> prune the element and set its parent element as parent element of
> its child elements
>
> the first: "prune the element and its descendant elements"; note well that the traversal order for pruning is postorder (see step 2 of the first set of rules in 9.3.2 [2]), and not preorder, which means that children are processed (and possibly pruned) before their parent
>
> [2] http://www.w3.org/TR/ttaf1-dfxp/#semantics-region-layout-step-1
>
>
> (c) region reference
> what is expected in following example?
>
> <definitions of regions>
> <body>
> <div>
> <p>
> oh
> <span region="r1">
> my
> <span region="r2">
> god
> </span>
> </span>
> </p>
> </div>
> </body>
> ==> which region(s) "oh" will be appeared?
> both r1 and r2? or will "oh" not be appeared?
>
> assuming for a moment that both regions r1 and r2 and the above content elements are temporally active over the interval of interest, then "oh" will appear in both r1 and r2; however, "god" appears in neither region due to the parent span being pruned under r2;
>
> constructing the intermediate document using the first set of rules in 9.3.2 [2] we have:
>
> <tt>
> <head>
> <layout>
> <region xml:id="r1">
> <body>
> <div>
> <p>
> oh
> <span>
> my
> <!-- <span region="r2"> god </span> pruned -->
> </span>
> </p>
> </div>
> </body>
> </region>
> <region xml:id="r2">
> <body>
> <div>
> <p>
> oh
> <!-- <span region="r1"> my <span region="r2"> god </span> </span> pruned -->
> </p>
> </div>
> </body>
> </region>
> </layout>
> </head>
> </tt>
>
> keep in mind that 9.3.2 step 2 says "postorder" traversal, and not "preorder", which means that children will be pruned prior to their parent; also, keep in mind that step 4 refers to the "original" body element, and not the replicated body elements reparented to region elements in step 3
>
>
> (d) region style prop inheritance
> what is expected in following example?
> <definition of r1 and r2 (no tts:color definitions in both)...>
> <body>
> <div region="r1" tts:color="red">
> <p begin="1s" end="2s">
> text1
> </p>
> <p region="r2" begin="1s" end="2s">
> text2
> </div>
> </body>
> ==> what is the color of "text2"?
>
> according to [3], style inheritance operates on the intermediate synchronic document
>
> For the purpose of determining inherited styles, the element hierarchy of an intermediate synchronic document form of a TTML document instance must be used, where such intermediate forms are defined by 9.3.2 Intermediate Synchronic Document Construction<http://www.w3.org/TR/ttaf1-dfxp/#semantics-region-layout-step-1>.
>
> Note:
>
> The intermediate synchronic document form is utilized rather than the original form in order to facilitate region inheritance processing.
>
> [3] http://www.w3.org/TR/ttaf1-dfxp/#semantics-style-inheritance
>
> however, due to the intermediate document construction rules described above, "text2" will never appear since it will be pruned from region r1 (since it is explicitly associated with r2) and will be pruned from region r2 (since its ancestor div is explicitly associated with r1);
>
>
--
Consumer Products & Services Group
Home Entertainment Business Group
Home Entertainment Development Div.
Section1 Dept.7
Sony Corp.(Japan)
Kouichi Uchimura <Kouichi.Uchimura@jp.sony.com>
Received on Tuesday, 31 July 2012 03:21:18 UTC