See also: IRC log
<trackbot> Date: 18 October 2012
TTML Agenda for 18/10/12 our teleconference is scheduled with reference to Boston Time, the correct time of this teleconference in your locale may change. Please check http://timeanddate.com/worldclock/fixedtime.html?month=10&day=18&year=2012&h our=10&min=0&sec=0&p1=43 Thursdays 15:00-15:00 UTC (10:00am-11:00am Boston local) Zakim Bridge +1.617.761.6200, conference 8865 ("TTML") IRC: server: irc.w3.org, port: 6665, channel: #tt Web gateway to :http[CUT]
Agenda Chair: Sean Hayes Agenda+ Assign Scribe Agenda+ actions and issues on SDP: Agenda+ actions and issues on Second edition:  http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10-sdp-us/Overview.html Reference Tracker (Issues and Actions): http://www.w3.org/AudioVideo/TT/tracker Profile draft: http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10-sdp-us Change proposals: http://www.w3.org/wiki/TTML/changeProposal001 http://www.w3.org/wiki/TTML/c[CUT]
Andreas, courtney, glenn, mijordan, pal, sean, mmartin3
Agenda (see above0
Issues and Agendas
<trackbot> ISSUE-182 -- Allow more than one profile to be used in the SDP-US. Add use of ttp:profile element. -- open
Action Monica Add other features related to ttp:profile to Issue-182.
<trackbot> Created ACTION-117 - Add other features related to ttp:profile to Issue-182. [on Monica Martin - due 2012-10-25].
<trackbot> ISSUE-180 -- regions relative to the root container -- open
<glenn> +Present - irc only
Change from: No more than four lines of text must be selected into all active regions at any given time. Change to: No more than four visible lines of text must be selected into all active regions.
<scribe> New requirement: Origin and extent of a region MUST be authored not to extend outside of the root container.
Resolution: Approve changes.
<glenn> i assume this is SDP-US only, not TTML in general, yes?
<trackbot> ACTION-105 Propose requirement to constrain to the root container in SDP-US (see Action-104 and Issue-180). closed
Yes, only SDP.
<glenn> ok, no objection then
Action Glenn To implement changes proposed for Action-105 for Issue-180, SDP-US only.
<trackbot> Created ACTION-118 - Implement changes proposed for Action-105 for Issue-180, SDP-US only. [on Glenn Adams - due 2012-10-25].
<trackbot> ISSUE-192 -- R0041 doesn't allow for EBT-TT conversion easily. Revise R0041 to a SHOULD. -- raised
Sean: Mike Dolan had raised
... Andreas, can you explain for EBU-TT?
Andreas: Usually have 36-37 characters per line.
Problem for European subtitles.
Sean: Limit to 128 visible characters?
Andreas: To get quality and circulate US, don't split to more lines than originally displayed.
Sean: What happens if you use captions in US?
Andreas: Seems so yes.
Sean: Use 36-38?
Andreas: Will check.
Sean: May increase visible number of characters per line = 38. If US content, 32.
mijordan: CEA-608 is the same.
Sean: Leave as a SHALL..
mmartin3: Regulation talks to 4:3 and 16:9 for 1/32 and 1/42 respectively.
mijordan: Dolan didn't account for other aspect ratios for cinema or full-format movies.
Sean: Leave to default aspect
ratio of root container.
... SHALL for 38, is only for 4:3 aspect ratio content only. Or to total visible characters?
... What does EBU do?
Andreas: 38 is for 4:3 only. No other limitations.
Sean: If you did 16:9 how many would you use?
Andreas: Exchange and use SDL, limited by teletext
Sean: Retain SHALL only for 4:3 aspect ratio of the default grid. Others, limit total character limit.
mmartin3: Make note to accommodate EBU teletext.
Leave open. Monica will update.
<trackbot> ISSUE-191 -- Textoutline doesn't handle specific edge types outlined in R0037. Need to revise requirement and specify in Future Needs sections. -- open
mmartin3: Consistent with comments from SMPTE.
Sean: User agent feature?
Sean: Agree with SHOULD.
mijordan: CEA-708 has those styles.
Sean: Create issue for v.next.
Action mijordan Work on new issue for v.next or to address SMPTE questions for region, border and anchor-point. Need to ensure character edge is part of that user agent feature.
<trackbot> Sorry, couldn't find mijordan. You can review and register nicknames at <http://www.w3.org/AudioVideo/TT/tracker/users>.
courtney: FCC supported in content?
(7) Character edge attributes. All apparatus shall implement captioning such that character edge attributes may be displayed and users are provided the ability to select character edge attributes including: no edge attribute, raised edges, depressed edges, uniform edges, and drop shadowed edges.
scribe: Greater issue than SDP-US.
Sean: Add to Second Edition?
Add to action - what we need to support in TTML (SDP-US).
<glenn> some of these may be accomplished by the currently defined tts:textOutline property, but some cannot without modifying that property
<glenn> i think it would be good to describe how to use this property to achieve these "named" "edge" characteristics
mijordan: Need mechanism for offsetting.
<glenn> textOutline allows specifying offset of outline (shadow) already
<glenn> scratch my prior, mjordan is correct
<trackbot> ISSUE-190 -- Background vs Window Color -- open
<glenn> probably need both offset (x,y) and also multiple outlines (shadows) to apply to achieve desired effects
Sean: Put in SDP.
Resolved to use example in http://lists.w3.org/Archives/Public/public-tt/2012Oct/0028.html.
Action Glenn Implement proposal for Issue-190 http://lists.w3.org/Archives/Public/public-tt/2012Oct/0028.html.
<trackbot> Created ACTION-119 - Implement proposal for Issue-190 http://lists.w3.org/Archives/Public/public-tt/2012Oct/0028.html. [on Glenn Adams - due 2012-10-25].
<trackbot> ISSUE-190 Background vs Window Color closed
<trackbot> ISSUE-189 -- do regions scroll their flowed content? -- open
<Sean> Glenn We will go back to the outlie styles next week
Example + add feature displayAlign
Mike Dolan commented http://lists.w3.org/Archives/Public/public-tt/2012Oct/0032.html
<glenn> we should think about deprecating tts:textOutline, and just introduce new tts:textShadow based on CSS3 Text spec definition
Sean: Previous example didn't
show the region.
... Example is actually roll-up and paint-on.
Mike's example is only roll-up.
scribe: Explains the examples and the differences.
mmartin3: Do we explain more?
Sean: Example with elaboration
... Add lines coming in at the bottom and going out at the top.
... Use Mike's example. Add pictures for SDP-US.
No other issues ready for today.
<trackbot> ACTION-89 -- Glenn Adams to add TTML 1.0 Second Edition reference. -- due 2012-09-13 -- PENDINGREVIEW
mmartin3: Explains references - TTML 1.0 Normative and TTML 1.0 SE as informative. Put in document placeholder manually.
Sean: Preamble text to SE which is emerging.
mmartin3: Work on an updated
proposal then for Action-109.
<Sean> preamble text to the reference to indicate the most recently published version should take precedence
<glenn> any body going to TPAC? i'll be there if anyone wishes to pow wow about TTML
All other actions are related to issues we discussed today.
<trackbot> ISSUE-188 -- Bounding SDP-US rendering complexity -- open
<Sean> only Philippe
No time to discuss.
trackbpt, end meeting
trackbot, end meeting
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: mmartin3 Inferring Scribes: mmartin3 WARNING: No "Topic:" lines found. WARNING: No "Present: ... " found! Possibly Present: Andreas Proposal Sean courtney glenn joined mijordan mmartin3 plh trackbot tt You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Found Date: 18 Oct 2012 Guessing minutes URL: http://www.w3.org/2012/10/18-tt-minutes.html People with action items: WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]