See also: IRC log
<scribe> scribeNick: nigel
nigel: We have a few topics to
cover today: i18n review, IANA registration, next F2F,
... WebVTT meeting planning, TTML2 Pull Requests etc.
... AOB?
group: No
action-477?
<trackbot> action-477 -- Philippe Le Hégaret to Progress the update to ttml media type registration with iana -- due 2016-09-15 -- PENDINGREVIEW
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/477
nigel: This is pending review -
the IANA page at
http://www.iana.org/assignments/media-types/application/ttml+xml
... shows the updated media type registration as
submitted.
... That's good news, so I think we can close off this piece of
work now. Thanks to everyone for their input here.
close action-477
<trackbot> Closed action-477.
nigel: I think we can remove this agenda item from future meetings.
nigel: r12a has fixed up the
TTML2 repo to notify the www-international mailing list
when
... the i18n label is applied to an issue, or when such an
issue is closed.
... I went along to the i18n meeting and gave them an
orientation introduction to TTML2.
... That seemed to be very helpful to them. Dae was there also.
He did say that there would
... be one issue to be raised on TTML2 which if I remember
correctly is to do with non-combining
... glyphs that need to be specifically aligned. I'm not sure
of the details.
glenn: There are some such things
in Thai but I think Unicode handles them. It would be
... good to prompt Dae to add that issue. There are also line
break issues that I don't believe
... need any extra handling.
... That would be true for all the Indic scripts not just
Thai.
nigel: I've asked if we need to
go back and add the i18n label to already closed issues.
... So they have access to the ED now and are expecting a WD in
a month or so for a proper review.
... We have comparison operators in the condition syntax that
we may need to be careful with.
glenn: That's a good point, I have to go back to see how I defined that operator function, if it's just on numeric values or also strings.
nigel: I think it's on anything.
glenn: Then we should say something about that for sure. Also to include equality and relational operators.
nigel: r12a has just responded - he doesn't want us to add labels to closed issues.
action-480?
<trackbot> action-480 -- Thierry Michel to Request schedule time for horizontal review of ttml2 -- due 2016-09-26 -- OPEN
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/480
nigel: Thierry, what's the status on this action?
<tm> reconnecting hold on ...
thierry: I've done i18n, and have
started to look at the security and privacy
questionnaire,
... so I intend to fill that in and send the draft to the
WG.
... There's also WAI, but that has no special questionnaire.
i18n is starting a questionnaire.
... I will provide the links to this group.
... I'll let you know by tomorrow about those.
... For WAI we have to go through the regular process which is
to ask for review by email,
... which is to be done. Shall I just send a heads up for the
new WD?
nigel: Please send the heads up in advance of the WD in November.
thierry: Okay I will do that, and
we can start handling the privacy questionnaire right
now.
... That's new process so we may be first to experience
that.
nigel: Thank you!
... Let's move on to pull requests...
glenn: My only requirement on the
pull requests is that unless I delegate a task for merging
then
... I will be the one to merge, in case I need to make
editorial changes. More significant changes
... I will make on the appropriate branch for the pull request
for review before merging.
nigel: https://github.com/w3c/ttml2/pull/184
- I updated this based on some feedback.
... This is Add ttp:safeCropArea.
... I fixed the validation error and added the parameter to the
schema.
... From my perspective this is good to merge but there are no
review comments yet.
glenn: I plan to make some
changes there - probably a branch on your branch with a PR
to
... update your branch, to segregate my modifications.
nigel: Sounds like a good
idea.
... https://github.com/w3c/ttml2/pull/185
Augment use of lwsp in ttp:{content,processor}Profiles
(#170).
glenn: I take your comments well
on that one - it sounds like we can simplify things
there.
... I need to review the fine points and make sure it doesn't
break anything we have right
... now and achieves the effect I was trying to achieve in the
first place.
... On this point, while it's true that white space gets
normalized in attributes, the
... syntax still needs to support a single space character.
nigel: That's my proposal - and to remove leading and trailing whitespace.
glenn: We need to be sensitive to
the fact that TTML1 does support LWSP now.
... At the worst case we could add an informative note that the
processing of XML normalized
... attribute values may limit the type of character that could
appear in linear white space.
nigel: Yes, ok.
glenn: I need to go back and look
at the abbreviated information set to see if we require
the
... same processing of white space for non-XML formats, in
other words do we prescribe that
... that occurs on constructing the information set. If you're
not using XML and you're
... constructing the information set for e.g. JSON then it
won't have the same whitespace
... normalization.
nigel: I was hoping that we could
allow processors to be simplified by applying a single
... normalization process that results in no leading or
trailing spaces and all separators being
... exactly one #x20 character, but I see that may already not
be possible.
glenn: In TTV I'm using escaped
character references in test material to insert white
spaces
... like tab, newline, carriage return etc.
... The way we can handle this pull request is to accept it as
is and you could file a new
... issue pointing out that it might be desirable to transition
to the new approach you are
... suggesting if possible, because the current PR satisfies
the original issue as described.
nigel: Ok, let's do that. I'll
update the PR after this meeting and add an issue.
... The last open pull request for now is https://github.com/w3c/ttml2/pull/177
... I think the action is for Glenn to merge this and raise
issues as described on the pull request.
glenn: Yes, I've got that.
nigel: Are there any other issues that anyone else can take?
glenn: There are a variety of
editorial notes that say e.g. "add an example" for a new
style.
... If anyone could spend time doing that then it would be very
useful.
nigel: Some of those might best
be done with TTPE so it would be helpful if someone who
... is used to that could use it to generate them.
glenn: Yes, it might also be a
good homework exercise if someone else could create the
... example TTML content.
... I know that Rohit and Dae have looked at this a bit.
nigel: In the i18n meeting they
did ask for examples of use cases for the new style
attributes,
... and Dae said he would be able to provide those, so this
might be one activity that fulfils
... two actions.
glenn: There are also other
things like padding and border, where it would be useful to
have
... example content that demonstrates those in use, where we
are expanding the role.
nigel: Okay I can have a look at that.
nigel: Thierry has pushed things
forward on this - the proposal is for David to
participate
... in a scheduled TTWG meeting to review the wide review
comment status, alongside Simon
... and Silvia. That will not be until after 20th October, date
to be confirmed.
thierry: 20th October was the
earliest date to allow for Silvia and David to process the
comments
... in advance, so I hope there will be some kind of tagging of
the issues. Then the next goal
... is to have a TTWG meeting dedicated to this. We have no
date agreed for this yet. Either we
... schedule a specific call, or use a scheduled TTWG meeting.
I definitely want people from
... the TTWG to join - this must not be a CG meeting.
pierre: In IMSC 1 we used a specific tool to track the comments - are we doing that here?
thierry: This was an internal
tool that was meant specially for last call, it's pretty
convenient
... to use to track the status of each comment, and then the
nice thing about this tool is that
... it automatically provides the disposition comment. But now
that LC does not exist things
... are less clear what we need to provide now. We just need to
show wide review.
pierre: For IMSC 1 we used that tool even though there was no last call.
thierry: I do not know which tool
will be used. Different repository and issue tracking
tools
... have been used.
pierre: Whatever tool is used the
same process needs to happen for WebVTT before we meet.
... I don't want to meet up without a clear record of the
comments and disposition.
nigel: I agree, we need a clear
process and documentation that we can understand as the
WG.
... I also would note that there is enough substantive change
on the current ED compared to
... the previous WD that a new WD is needed with a new
opportunity for wide review comment.
thierry: I understand the concern
- we can put the date on hold and wait until we see the
... output of this meeting. I am also fine with investing time
in tracking this thing with
... whatever tool we use but I need to have input from the CG
at least for what has been
... done already. I also agree that we need to publish a new WD
because there are some very
... substantive new features like region, CSS etc that need to
be reviewed definitely.
nigel: There's been a request for
a F2F and a proposal to hold it at the BBC - I'm happy to host
this,
... and the next step is to pick a suitable date - February
2017 was mentioned.
... Please let me know any specific date requests - I'm not
sure what else is planned around that time.
... We're out of time for today so I'll carry that forward to
next week. Thanks everyone. [adjoiurns meeting]