ACTION-205: Forward this solution to relevant implementers for their input

Forward this solution to relevant implementers for their input

State:
closed
Person:
Michael Jordan
Due on:
September 26, 2013
Created on:
September 19, 2013
Associated Issue:
extent and origin on blocks
Related emails:
  1. TTML Minutes for 15/11/13 (from nigel.megitt@bbc.co.uk on 2013-11-21)
  2. {minutes} Halloween TTML Meeting and Thank You Sean (from plh@w3.org on 2013-10-31)
  3. RE: TTML Agenda for 31/10/13 (from Sean.Hayes@microsoft.com on 2013-10-31)
  4. TTML Agenda for 31/10/13 (from nigel.megitt@bbc.co.uk on 2013-10-30)
  5. {minutes} TTML Meeting of 24/10/13 (from glenn@skynav.com on 2013-10-24)
  6. RE: TTML Agenda for 24/10/13 (from mdolan@newtbt.com on 2013-10-23)
  7. TTML Agenda for 24/10/13 (from nigel.megitt@bbc.co.uk on 2013-10-23)

Related notes:

Adobe has implemented. Glenn's proposal is different from CP2.

Action is now for Adobe and CPC to review Glenn's proposal and respond accordingly in time for TPAC session.

Nigel Megitt, 31 Oct 2013, 15:04:10

I sent an email to Jason Livingston at CPC requesting comment on Glenn's change proposal.

One difference I notice in the CPC output from the examples outlined in http://www.w3.org/wiki/TTML/changeProposal002 is that each p with tts:origin and tts:extent from CPC has an explicitly defined target region attribute, which makes it easier to understand the target region for positioning.

<tt xml:lang="en" xmlns="http://www.w3.org/ns/ttml" xmlns:tts="http://www.w3.org/ns/ttml#styling" xmlns:ttm="http://www.w3.org/ns/ttml#metadata" xmlns:ttp="http://www.w3.org/ns/ttml#parameter" ttp:timeBase="media" ttp:frameRate="24" ttp:frameRateMultiplier="1000 1001">
<head>
<styling>
<style xml:id="basic" tts:color="white" tts:backgroundColor="black" tts:fontFamily="monospace" tts:fontSize="80%" tts:fontWeight="normal" tts:fontStyle="normal"/>
</styling>
<layout>
<region xml:id="pop1" tts:backgroundColor="transparent" tts:showBackground="whenActive"/>
</layout>
</head>
<body>
<div>
<p begin="nn:nn:nn:nn" end="nn:nn:nn:nn"
region="pop1"
style="basic"
tts:origin="10% 84.67%" tts:extent="50% 5.33%">
The quick brown fox
</p>
</div>
</body>
</tt>

I'm not sure that this makes a difference with Glenn's concerns regarding the potential for confusion over the meaning of the properties and how they should be applied.

Michael Jordan, 1 Nov 2013, 20:11:13

Resolved at TPAC, so that the existing implementations continue to work, the syntax used in existing implementations and described in http://www.w3.org/wiki/TTML/changeProposal002 will be accepted as a shorthand for defining inline regions on a contact block as described in http://www.w3.org/AudioVideo/TT/tracker/issues/176. This should be clarified with completion of http://www.w3.org/AudioVideo/TT/tracker/actions/215.

Michael Jordan, 15 Nov 2013, 02:16:31

Display change log.


David Singer <singer@apple.com>, Nigel Megitt <nigel.megitt@bbc.co.uk>, Chairs, Thierry Michel <tmichel@w3.org>, Philippe Le H├ęgaret <plh@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.323 2013-12-19 14:47:09 dom Exp $