See also: IRC log
<scribe> scribe: nigel
Nigel: Today, we can cover any
additional thoughts re TPAC, TTML2 HR (not sure how much
... there is to discuss there), and I'm not sure what else. One
AOB from me:
... To remind everyone to associate their GitHub accounts with
their W3C accounts so that
... IPR can be tracked.
Tool for connecting W3C account to GitHub account
Nigel: Please could everyone make
sure they have done this.
... Any other topics to cover today, or any other business?
Thierry: I had another reminder about TPAC registration.
Thierry: Please if you intend to
come to TPAC register as soon as possible; also it is
difficult
... to find hotels so if you are having difficulties let me
know. We are 6 weeks from TPAC,
... so the registration price will go up in ~2 weeks. I will
send a reminder call email too.
Andreas: Question re hotel
location. I assume that some may not stay in the hotel, and
go
... to it using public transportation or a car. Do you know if
there is an additional parking
... fee at the hotel, and how much it is?
Thierry: I don't know, but I'll check after the call and let you know.
Andreas: Thank you.
Action-504?
<trackbot> Action-504 -- Nigel Megitt to Send csswg an invitation reminder by 2017-09-07 -- due 2017-09-07 -- PENDINGREVIEW
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/504
Nigel: I've sent the reminder, and it's logged on the action in tracker.
close action-504
<trackbot> Closed action-504.
Nigel: I still have had no
responses from any CSS WG members though!
... Are there any suggestions for the agenda for us?
group: no suggestions right now.
Nigel: Logistics-wise, please let
me know if you need remote dial-in - I have to request
... this in the next few weeks.
... I have completed the AV WBS for TPAC for TTWG and currently
have not asked for a Polycom phone.
... If necessary I can update my responses.
action-506?
<trackbot> action-506 -- Thierry Michel to Draft a wiki page explaining our review and disposition steps and labels -- due 2017-09-21 -- OPEN
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/506
Nigel: I think Thierry had the action from last week to link the wiki page to the GitHub repo labels?
Thierry: That's not how I
understood my action - I thought the action was to go
through
... the comments and assign an appropriate label. I thought we
had agreed on the labels
... I proposed in the wiki.
Nigel: I didn't think there were any proposals.
Thierry: Yes, I did!
... I have gone through all the comments and assigned a label.
I sent an email just before this
... call. I have a few outstanding ones. If we agree with those
labels then I will add them on
... GitHub.
Nigel: Okay, thank you!
Thierry: On the wiki page the proposed label is in the brackets.
https://www.w3.org/wiki/TimedText/TTML2_Wide_Review
Nigel: Oh that's what they are - I hadn't realised!
Thierry: There are lots of
comments that are still pending and need further
discussion.
... We can maybe discuss them next week or the week after, when
the review period has closed.
Nigel: Have you created the labels in the ttml2 repo?
Thierry: No not yet. If we are
satisfied with the labels then I will add them into
GitHub.
... I think we should have a prefix for each label like WR for
Wide Review, which will ease filtering later.
Nigel: Sounds reasonable to me.
Thierry: At least we know then those labels are assigned for the Wide Review.
Nigel: So there's an action on
everyone to look at the email you sent and check that the
... proposed labels are correct?
Thierry: Yes, and I will finalise the remaining incomplete ones maybe today.
Cyril: Do you have an example of a GitHub issue to which you added a label?
Thierry: No, sorry, I was not
clear enough. I have only done added the labels on the
email,
... but not added the labels on the GitHub Issues yet. I will
do that when we have agreed on
... the labels.
Cyril: OK, got it, thank you! I
hadn't seen the email.
... On the wiki, there are several that are "resolved" but on
the email the first one is "resolved".
... Which one is it?
... I think that we should have different labels for 1.3 and
1.4 because they both include "resolved".
... For example call 1.4 "Spec Updated".
... And disambiguate 1.5 and 1.6.
... Each issue can have both a processing by group label and a
commenter status label?
Thierry: Yes. Good idea to fix the labels, I will do that.
Cyril: I'm editing the wiki page just so they are clear.
Thierry: Thank you.
Cyril: Does "spec update" mean an update has been made or one is required?
Thierry: It means "updated already".
Cyril: I'll change it to
"updated" then.
... And you want the commenter labels to be prefixed WR
too?
Thierry: Yes, thank you Cyril.
Cyril: I will update the wiki page.
Thierry: Then I will update the email and send it.
Nigel: Thank you - I will take the lead on checking the email's proposed labels.
Cyril: I've made the changes.
Thierry: "Partial" approval is WG approval of part of the commenter's proposal. That needs to be clear.
Nigel: Ah thank you that wasn't
clear to me.
... Thanks, that's great. Is action-506 done?
Thierry: Leave it open until next week when we can finalise everything.
Nigel: Ok will do.
github: https://github.com/w3c/ttml2/issues/406
Nigel: Since last week I have
completed the set of sub-issues with proposed mappings
that
... are CSS-based alternatives to the current XSL-FO semantics.
I'd still really appreciate a
... review of all of those if anyone is able to check them
before I complete the work to put
... them in a pull request. Obviously the pull request is
another opportunity for review, but
... it's quicker to make fixes earlier.
... For example with text-decoration, I found that XSL 1.1
makes an addition to the CSS
... semantic that I cannot see anywhere in CSS: it sets the
position of underline based on
... the language.
Cyril: A quick question on this
issue in general - it is not going to change the TTML2
... publication timeline?
Nigel: I don't see why it should.
Cyril: It's an annex only?
Nigel: Yes, and also it is informative.
Cyril: I was wondering how we
proceed with the CSS changes and CSS WG without adding
... delay to the TTML2 publication timeline?
Nigel: I think it's in our domain
to approve the equivalent semantic mapping for XSL
semantics
... that are in CSS, so we are in control of the timeline
there.
... For new semantics that we're requesting in CSS but that are
not available now, I think we
... can probably go ahead without them in TTML2 and at a later
stage issue an update
... incorporating new CSS semantics when they are
referenceable.
... At least that would be my first proposal.
Cyril: I'm happy with that.
Thierry: Fine with me.
Andreas: Me too.
Thierry: The WebVTT wide review
ends tomorrow, on the 22nd, and I've invited David to
... join our next telecon - he replied that he may have an AB
meeting and he will let us know.
... I see also that Andreas has sent some wide review comments
today - 8 comments.
Andreas: Yes, I wasn't exactly
sure about the process because in the WR process email
you
... said comments should be sent to the reflector. In my case
it was easiest to open the issues
... on GitHub and then send an email listing them. Is that
ok?
Thierry: No problem, yes, that fits.
Nigel: We've hit the end of our agenda, so unless there are any other points we will adjourn.
Thierry: Is next week's meeting 2 hours?
Nigel: It's marked as 2 hours - maybe a good idea if we are to discuss WebVTT also.
Thierry: I will remind David, and
also ask if it would help to make the WebVTT a timed
... agenda item.
... I think Sylvia also should participate, so I'll copy her
also.
Nigel: This time might be
horrible for her if she's in Australia, so another alternative
would be
... to set up a specific meeting at a better time for everyone
who wants to participate.
Thierry: Yes, I'll propose that too.
Nigel: I'm happy either way, for
it to be part of this meeting slot or at a different
time.
... Thanks everyone! [adjourns meeting]