See also: IRC log
<trackbot> Date: 22 January 2015
<scribe> scribeNick: nigel
nigel: I've updated the TTML2 timeline - see the agenda.
<scribe> ACTION: pal Update publication timeline diagram [recorded in http://www.w3.org/2015/01/22-tt-minutes.html#action01]
<trackbot> Created ACTION-368 - Update publication timeline diagram [on Pierre-Anthony Lemieux - due 2015-01-29].
action-363?
<trackbot> action-363 -- Nigel Megitt to Format and send itu-r liaison response -- due 2015-01-15 -- PENDINGREVIEW
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/363
close action-363
<trackbot> Closed action-363.
nigel: I sent this to ITU-R and got an acknowledgment back. Thanks all for contributions.
action-366
<trackbot> action-366 -- Nigel Megitt to Review change proposal 14 in the light of closure of issue-10. -- due 2015-01-22 -- PENDINGREVIEW
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/366
issue-10?
<trackbot> issue-10 -- Allowing pointers to pre-rendered audio forms of elements -- closed
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/10
nigel: The TTML2 implementation meets the needs of this CP for now, so I closed it.
close action-366
<trackbot> Closed action-366.
action-367?
<trackbot> action-367 -- Nigel Megitt to Review change proposal 27 in the light of closure of issue-303. -- due 2015-01-22 -- PENDINGREVIEW
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/367
issue-303?
<trackbot> issue-303 -- Permit HTML-style <a> elements to contain href links -- closed
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/303
nigel: The TTML2 implementation meets the needs of this CP for now, so I closed it.
close action-367
<trackbot> Closed action-367.
action-360?
<trackbot> action-360 -- Nigel Megitt to Send liaison request on behalf of w3c ttwg to arib -- due 2014-12-18 -- OPEN
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/360
nigel: I've prepared an update to
the liaison, waiting for Daniel D of W3S to approve.
... And I've worked through how to send this, in conjunction
with the contact from ARIB.
action-365?
<trackbot> action-365 -- Pierre-Anthony Lemieux to Review change proposal 21 in the light of closure of issue-229. -- due 2015-01-22 -- OPEN
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/365
pal: I sent an email to the
reflector about this, waiting to hear back from the Editor on
this.
... So leave open for now.
... I saw that nigel had some comments on the approach to ruby,
but the thread went quiet,
... so I guess you're happy with it?
issue-228?
<trackbot> issue-228 -- Ruby text support -- closed
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/228
nigel: This one's closed - I don't expect or need any further changes.
pal: What would the alternative be - to introduce new content elements?
nigel: Exactly - that's what Glenn wants to avoid.
pal: No substantial update this week - work in progress here.
issue-366?
<trackbot> issue-366 -- xml:id uniqueness needs to be broken for some uses of condition -- raised
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/366
reopen issue-366
<trackbot> Re-opened issue-366.
nigel: I expect this to be
resolved editorially, by an edit to the style set processing,
and by the
... documentation of the processing model.
... And by allowing IDREFS on region attributes.
pal: So there's a way to achieve what you wanted without duplicating xml:id values?
nigel: Yes, exactly.
issue-224?
<trackbot> issue-224 -- Support text placement in 3D coordinate spaces (not zIndex compositing). -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/224
nigel: Glenn and I are still
discussing this one.
... I wonder how 3D images should be handled?
pal: It's the same as text - it's
the same image, but rendered at different horizontal
positions.
... That's for stereoscopic rendering. This approach is limited
to stereoscopic rendering.
issue-243?
<trackbot> issue-243 -- smpte:information (source material information) -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/243
pal: I think we've covered this
before - there's an Editor's note on this, but the definition
isn't
... yet synonymous with the SMPTE definitions. There's more
work to do to define the syntax
... of all the named items.
issue-243: Further definition of the syntax is marked as an Editor's Note - this issue depends on completion of that task.
<trackbot> Notes added to issue-243 smpte:information (source material information).
reopen issue-243
<trackbot> Re-opened issue-243.
issue-278?
<trackbot> issue-278 -- Tightening schema support for foreign vocabulary. -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/278
issue-289?
<trackbot> issue-289 -- For TTML created for overlay on top of video, signal the aspect ratio of the video the TTML was created for -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/289
atai: With XML Schema 1.0 I think
there's probably no way to be more restrictive,
especially
... for attributes.
... That's why Glenn's TTV tool does these additional
checks.
nigel: Is it the general view
that we do partial XSD validation and on top of that use
special
... software?
pal: I think that's the only way.
The right way to achieve complete coverage is with
reference
... code or something similar, ultimately.
close issue-278
<trackbot> Closed issue-278.
issue-289?
<trackbot> issue-289 -- For TTML created for overlay on top of video, signal the aspect ratio of the video the TTML was created for -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/289
nigel: He has a targetAspectRatio, but it's hard to tell exactly what the solution was here.
pal: I think aspect ratio is somewhat in flux.
nigel: I think the same goes for active format descriptor and intendedTargetBarData
atai: I need to review this more.
issue-364?
<trackbot> issue-364 -- Relax constraint between the extents of the root container and the dimensions of the related video object frame -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/364
pal: The CR version of IMSC 1 did
not permit the renderer to scale images, forcing the
creation
... of multiple versions of the same image profile document,
one for each target related video
... object resolution. That makes the job of the renderer
easier, but the feedback, including
... from Simon Hailes, is that scaling by renderers isn't a big
issue, but having a large number of
... images is more of a problem.
... Formally we can respond to Simon with this. I'll generate
some additional test cases to cover this.
... The edit was deceptively simple: The sentence tying the
tts:extent to the video object's
... size was removed.
... Also the following sentence was removed: "ittp:aspectRatio
shall not be present if tts:extent is present"
... Now you can specify aspect ratio and tts:extent.
... And the scaling rules still apply that say that the
rendering plane is as big as it can be within
... the video object.
jdsmith: I'd like to have a look at the complexity of scaling images.
pal: I see that there's been reflector discussion with the gentleman in Croatia.
nigel: I don't think there's
anything more we can do there - we've provided all the help we
can.
... It seems to be an implementation issue.
... Thanks everyone - we're back for an hour next week.
[adjourns meeting]