- From: Nigel Megitt <nigel.megitt@bbc.co.uk>
- Date: Thu, 22 Dec 2016 16:20:36 +0000
- To: "public-tt@w3.org" <public-tt@w3.org>
- Message-ID: <D481AA94.338EA%nigel.megitt@bbc.co.uk>
Thanks everyone for attending today's meeting. Minutes can be found in HTML format at https://www.w3.org/2016/12/22-tt-minutes.html
Our next meeting is the F2F in London on 12/13 Jan – you have one day to register if you have not already, by adding your name to https://www.w3.org/wiki/TimedText/F2F-jan-2017
To help prepare for that meeting please review all the open TTML issues and mark the first comment with a heart reaction if you care about it, and any proposals you like with a +1 (or don't like with a –1) on the individual comments in the github repo. I will be using this data to prioritise the issues for the agenda in the early part of the week beginning 9th Jan.
In the meantime, best wishes over the festive season.
Minutes in text format:
[1]W3C
[1] http://www.w3.org/
Timed Text Working Group Teleconference
22 Dec 2016
See also: [2]IRC log
[2] http://www.w3.org/2016/12/22-tt-irc
Attendees
Present
Nigel, Glenn, Pierre, Mike
Regrets
Thierry, Andreas
Chair
Nigel
Scribe
nigel
Contents
* [3]Topics
1. [4]This Meeting
2. [5]F2F planning
3. [6]IMSC
4. [7]TTML
* [8]Summary of Action Items
* [9]Summary of Resolutions
__________________________________________________________
<scribe> scribe: nigel
This Meeting
nigel: Today we have F2F final planning, IMSC, TTML. Any other
business?
Pierre: In the F2F planning we should consider TTML1 issues too
nigel: Ok, noted, thanks.
group: No other business
F2F planning
-> [10]http://www.w3.org/wiki/TimedText/F2F-jan-2017
[10] http://www.w3.org/wiki/TimedText/F2F-jan-2017
nigel: Since last week I iterated through all the open TTML2
issues and categorised them,
... which you can see on the wiki page. Pierre I guess your
question is should we go through
... TTML1 issues as well?
Pierre: Ideally we should try to get TTML1 right since people
are using it today. At least we
... should reach conclusion on the issues on github, which
would provide some kind of
... guidance, even if it takes longer to publish errata. We
can't close on TTML2 without
... solving some of the TTML1 issues.
Glenn: During the F2F we should focus on the problems as Pierre
suggested, resolving the
... issue in our minds and getting a good gameplan in
approaching it, and then its a matter
... of implementing in both TTML1 and TTML2. Clearly the issue
on region association
... needs to be discussed.
... Are there other high priority items?
Pierre: There are only 34 issues on the tracker right now, and
some have an impact on TTML2.
... For example lineHeight (#220), textDecoration (#219),
origin and extent applied to padding rectangle (#221) etc.
nigel: In several cases we have matched TTML2 and TTML1 issues
so they should already be there.
Pierre: It would be useful to have the Chair's view of which
issues are high priority so that
... we can prepare better.
nigel: I'm happy to do that and would welcome input, since I
can not be sure what is important to each member.
Pierre: I'm happy to send you a list.
nigel: I think that since TTML2 is a superset of TTML1 almost
all TTML1 issues also impact
... TTML2 so I will make sure there are matching issues, and we
can consider the whole set together.
Pierre: The only TTML1 issues that are not relevant to TTML2
are where the section they apply
... to has been rewritten completely in TTML2.
action-491?
<trackbot> action-491 -- Nigel Megitt to Generate detailed
(timed) agenda for f2f to allow people to prepare in advance --
due 2016-12-22 -- OPEN
<trackbot>
[11]http://www.w3.org/AudioVideo/TT/tracker/actions/491
[11] http://www.w3.org/AudioVideo/TT/tracker/actions/491
action-491: Still in progress, some work done categorising
issues.
<trackbot> Notes added to action-491 Generate detailed (timed)
agenda for f2f to allow people to prepare in advance.
Pierre: We could ask everyone to come prepared on every issue.
Dae: Issue 221 seemed to lose some momentum. Are we going to
just propose the last resolution and check that's okay?
nigel: Yes we will do it by consensus.
Pierre: Of course some people may not care about some issues.
nigel: If you are preparing then it would be useful to state
your preference/interest on the
... issue itself so other people can respond.
... Ok here's a quick proposal: if you care about an issue
please could you add a Heart reaction so we can gauge interest
and priority?
... Click on the little smiley face on the very first comment
and mark it.
... Just do it on the first comment on the issue please.
Pierre: Also a friendly amendment: if you agree with a comment,
give it a thumbs up.
Nigel: Yes, that's useful too.
... So first, please do comment on issues and mark how much you
care, and then I will
... go through them in the week before the meeting and try to
sort them into some kind of order.
... Summarising, we will deal with TTML1 and TTML2 issues
together, and we will have
... an updated ED by Jan 5 at the latest for review.
Glenn: Yes.
nigel: And IMSC topics we will finalise early in the week based
on liaison input.
... In terms of meeting logistics, I plan to order food to come
to the room if that's okay.
... I haven't done anything about any evening meals, but could
help facilitate if anyone wants me to.
... Mike, do you need a dial-in?
mike: Yes please, if you can do that it would be great.
Thursday not before this time would work.
nigel: Okay that's enough for me to plan with, thanks.
... If anyone else needs a dial-in for any of the meeting
please let me know - by default I
... will not open one unless asked.
IMSC
nigel: Thanks Pierre for responding to Shervin at Unicode.
Pierre: Yes I replied so now I think it's down to him to come
back with questions or comments.
nigel: There are 4 new issues, any to discuss now?
Pierre: No, I started trying to make a pass through these and
plan to do it before the meeting
... including prioritising.
... On the errata we need Thierry because the version in the
repo does not match what is in /TR.
... It's fixed on /TR for sure.
nigel: What is to stop you from copying the /TR version and
pushing it to the repo?
Pierre: Mechanically nothing but I just want to check there
isn't a separate source somewhere.
Glenn: Generally I don't think he does keep a separate source.
nigel: You've pinged Thierry on the issue, so there's nothing
more to do on this. It's a housekeeping issue, right?
Pierre: Yes absolutely.
TTML
nigel: Can we see if we can close some issues?
->
[12]https://github.com/w3c/ttml2/issues?q=is%3Aopen+is%3Aissue+
label%3A%22to+close%3F%22
[12] https://github.com/w3c/ttml2/issues?q=is:open+is:issue+label:"to+close?"
-> [13]https://github.com/w3c/ttml2/issues/124 Use of content
encoding #124
[13] https://github.com/w3c/ttml2/issues/124
Glenn: I don't recall why I put that in, maybe it is useful as
opposed to necessary. As you
... point out it can be used whether or not we say it can.
nigel: OK to close?
Glenn: Go ahead.
nigel: Done.
-> [14]https://github.com/w3c/ttml2/issues/109 Allow negative
times to be used in fragment begin times #109
[14] https://github.com/w3c/ttml2/issues/109
Glenn: I'm not ready to close this.
... Actually, no, go ahead, I may put a comment in there.
<inserted> nigel: OK I closed it
-> [15]https://github.com/w3c/ttml2/issues/97 Style attribute
to prevent overflow by shrinking text to fit on a line #97
[15] https://github.com/w3c/ttml2/issues/97
nigel: There's consensus to close I think, but should we leave
it for ttml.next?
Glenn: Just close it.
nigel: Done, note added.
-> [16]https://github.com/w3c/ttml2/issues/53 Inline space #53
[16] https://github.com/w3c/ttml2/issues/53
Pierre: This came from digital cinema. I think if we can
document why we cannot achieve
... negative lengths that could be a good reason, but it would
be good to explain if/why we
... are not going to support it.
Glenn: [checks what we actually specified for ipd] It is
restricted to be non-negative.
... Negative space is usually used to adjust layout manually.
For example it is used in Latec -> PDF.
... In CSS you cannot specify width on inline non-replaceable
elements, so I'm not exactly
... sure how you would express it in CSS either.
nigel: Okay I've added a comment for now.
-> [17]https://github.com/w3c/ttml2/issues/47 Individual
character rotation #47
[17] https://github.com/w3c/ttml2/issues/47
nigel: I think textOrientation fulfils this.
Pierre: I'm happy with this if it meets the requirement.
Nigel: Okay I'll close.
... done!
Dae: I will check this and raise an issue separately - I have a
feeling there are certain half width kanji characters that may
need special handling.
Glenn: Let's talk offline about that.
-> [18]https://github.com/w3c/ttml2/issues/38 The values for
alpha in rgba() don't correspond to CSS3 Color definitions #38
[18] https://github.com/w3c/ttml2/issues/38
Pierre: Happy to close.
nigel: Glenn has already indicated he is happy to close also.
... Closed!
... We're now down to 1 issue marked as "to close?".
... Okay thanks, that felt productive! We're out of time for
today so I'll wish everyone a
... happy festive season whatever you are doing, and good
travels to London for our next
... meeting. [adjourns meeting]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes formatted by David Booth's [19]scribe.perl version
1.148 ([20]CVS log)
$Date: 2016/12/22 16:18:35 $
[19] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[20] http://dev.w3.org/cvsweb/2002/scribe/
----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
---------------------
Received on Thursday, 22 December 2016 16:21:01 UTC