See also: IRC log
<scribe> scribe: Nigel
<glenn> https://www.w3.org/TR/CSS22/visudet.html#inline-non-replaced
nigel: Apologies, after our
discussion on Friday last week I moved the meeting an hour
later
... as discussed, however I clearly did not make this obvious
enough in the agenda, and
... some folk joined at the (old) time. I understand there was
some useful discussion.
Thierry: Regarding IMSC1.1, I
explained that we have discovered that we can publish a new
FPWD using the same short name,
... then we would go for a Wide Review, then CR, then have an
implementation suite for the
... two new features, along the regular Rec track
process.
... So the good news is that we can publish a FPWD with the
same short name.
... Pierre has provided a draft with the additional insertion
of those two features, so I asked
... him to make it clear in the SOTD or in the Introduction
that the difference between that spec
... and the former Rec are those two optional new
features.
... And then Pierre would like to publish this as soon as
possible, so he was thinking about
... next week or the week following. If we want to do that we
need to have WG agreement
... for publication.
Nigel: Let's short-cut that slightly - I'll record the Proposal in the minutes here now:
PROPOSAL: Publish a FPWD of the updated IMSC 1 version under the short name ttml-imsc1
Nigel: The group should review
the latest ED so that we can come to a resolution on this as
soon as possible.
... The nature of this is that the FPWD already could be
claimed to meet CR requirements
... since the changes are directly derived from liaison input.
However I would suggest a short Wide Review period.
Thierry: I would make the FPWD
separate from the CR so that there is time to arrange the
... transition call. The real concern is to publish something
soon.
Nigel: Yes, I support that.
... I see from recent emails that Pierre has already been
working on issues and a pull request.
-> https://github.com/w3c/imsc/pull/202
Nigel: I also put a note on the
agenda that we should focus on those semantics that
affect
... backgrounds on span.
Glenn: I plan to propose some
spec text immediately after completing the pull request I
... am working on now, which is to address https://github.com/w3c/ttml2/issues/232
... which concerns applying border and padding to images,
including background images.
Nigel: While we're on TTML2, I'd like to call up my ACTION:
action-494?
<trackbot> action-494 -- Nigel Megitt to Mark the ttml2 issues as discussed and agreed where we've discussed and agreed their equivalent ttml1 issues. -- due 2017-01-20 -- PENDINGREVIEW
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/494
Nigel: I went through all the
TTML1 issues we agreed last week and marked up the
equivalent
... TTML2 issues as discussed and agreed. There weren't very
many, since some do not seem
... to have equivalent issues. I'm not sure if they should, or
if the same problems no longer
... exist in TTML2.
Glenn: I plan to go through all of the TTML1 issues and double check against TTML2, so I will catch those.
close action-494
<trackbot> Closed action-494.
Nigel: Thank you!
action-492?
<trackbot> action-492 -- Thierry Michel to Publish the updated ttml profile registry at https://w3c.github.io/tt-profile-registry/ by 2017-01-19 -- due 2017-01-19 -- PENDINGREVIEW
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/492
close action-492
<trackbot> Closed action-492.
Nigel: Thank you Thierry for publishing the updated profiles registry.
Thierry: Yes, I did publish it
yesterday, which the auto-publisher permitted despite a broken
link,
... and today Mike told me that DECE has fixed the link with a
redirect so now the link is not broken.
Nigel: Great, thanks both!
... Thanks both, and everyone who joined early, apologies
again. I'll adjourn now - next week I'll keep it at 1100 Boston
time (primary), 1600 UK time, 1700 Europe time, and whatever
time that is in all the other time zones...
... [adjourns meeting]