ISSUE-42: region attribute unspecified
region attribute default
region attribute unspecified
- TTML 1.0
- Raised by:
- Sean Hayes
- Opened on:
- 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â€™.
<p tts:color="red"begin="0s" end="10s">This text must be red.</p>
<p tts:color="blue"begin="0s" end="10s">This text must be blue.</p>
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.
- Related Actions Items:
- No related actions
- Related emails:
- No related emails
11 Dec 2008, 13:25:52
fixed in TTAF1-DFXP 20090130 updateGlenn Adams, 30 Jan 2009, 08:57:03
Display change log