See also: IRC log
<scribe> scribenick: nigel
nigel: There's a small change for
the profiles registry, some stuff on TTML2, and maybe a bit at
the end on IMSC.
... Any other topics?
... One AOB from me is next f2f planning
nigel: One new issue: https://github.com/w3c/tt-profile-registry/issues/26
... The IANA registration has been updated in place. There's an
RFC change issue as above.
mike: This does not impact us
technically, it's more a housekeeping thing. At the
moment
... our document says one thing and the IANA one says another
so that seems reason to
... update it.
nigel: I think so, yes.
... Thierry has already made the pull request: https://github.com/w3c/tt-profile-registry/pull/27
tmichel: I did this - there were 2 occurrences of this RFC to fix.
mike: I haven't looked at what was done yet.
tmichel: I changed the RFC number and also the URLs because the location is different.
mike: I'll look at it, but I see no reason not to go ahead.
nigel: There are 3 other issues open.
mike: They are unrelated to the media type registration but it would be good to look at them.
nigel: https://github.com/w3c/tt-profile-registry/issues/17
... This just needs someone to follow the agreement from May to
add some recommendation text.
mike: The more we write the more developers can get reasonable expectations of what to do.
nigel: The next one is https://github.com/w3c/tt-profile-registry/issues/13
... The two tables in ยง4 have no explanatory text.
mike: It would be good to have a volunteer for this.
nigel: I volunteer.
... The next one is https://github.com/w3c/tt-profile-registry/issues/8
... which is to merge the profiles document with the note on
TTML versions, which is my issue also.
...
https://dvcs.w3.org/hg/ttml/raw-file/5ee90ec0d897/ttml-status/index.html
group: Discussion of what to do
with the "TTML Recommendations" snaphot note.
... Conclusions: 1. Make sure the information is available via
the group home page
... 2. Remove the document.
mike: We should check in with Cyril too on this.
nigel: Agreed.
... I've added a note to the issue on the profile registry and
closed it.
mike: I'll check the pull request and merge it.
tmichel: It will then be updated on github.
action-481?
<trackbot> action-481 -- Glenn Adams to Provide nigel with a list of new features in ttml2 to begin reviewing -- due 2016-09-26 -- OPEN
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/481
glenn: There is already http://w3c.github.io/ttml2/spec/ttml2-changes.html
nigel: The action is to editorialise this into something more useful for reviewers.
action-481: [Meeting 2016-10-06] Glenn points to http://w3c.github.io/ttml2/spec/ttml2-changes.html as a technical list.
<trackbot> Notes added to action-481 Provide nigel with a list of new features in ttml2 to begin reviewing.
nigel: Okay I'll draft something if Glenn will review that draft text.
Action-481: Nigel to draft high level summary, Glenn to review.
<trackbot> Notes added to Action-481 Provide nigel with a list of new features in ttml2 to begin reviewing.
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
tmichel: i18n was initiated with
TPAC, and some questions have been answered.
... Then there's the accessibility review - I sent a heads-up
notice to them and have not heard back yet.
... There are two new questionnaires: one is from TAG but I
don't think we need to go through
... that - I discussed with Philippe and Yves and it does not
seem to be mandatory.
... The other is about security - I responded to that for TTWG
review. Nigel added a few
... remarks, so it is still pending. I do not know if I should
send the response with Nigel's
... updates.
pal: What's the latest version?
nigel: https://lists.w3.org/Archives/Public/public-tt/2016Oct/0005.html
glenn: I would also add to q3.6 that we do not consider condition to be a scripting language.
nigel: I agree with that.
pal: We could ask them in q3.6 is only about script loading and script execution.
nigel: Good idea.
... That would help us understand how to answer this, since we
do allow loading of resources, just not scripts, and the
question as worded is ambiguous.
glenn: It is true that we have
indirectly brought in fetch semantics by the introduction of
external resource loading.
... Also the addition of links on spans that can have
hyperlinks. Those two things are probably
... worth pointing out somewhere.
pal: Somehow they are presumably
interested in cross-origin. Maybe in 3.6 we should
mention
... that the specification introduces external resources and
let them deal with that.
glenn: There's nothing in TTML2
now that discusses fetch processing. I've given it some
... thought and I think we are probably going to need to put
something in. I want to make it
... as minimal as possible.
... My plan is to delegate this to the document processing
context.
nigel: We need some words for 3.6. Thierry, do you have enough to write this?
tmichel: I think so, I can craft something.
nigel: Thanks, Thierry if you can edit the responses and recirculate that would be helpful.
tmichel: Yes, will do.
glenn: I want to go over the pull requests that are in process and how to proceed on safe crop area.
nigel: There is an action on https://github.com/w3c/ttml2/issues/150#issuecomment-249206753 to submit an issue on CSS - I'm not sure who should take that.
glenn: My preference is for
someone active in CSS to file this, because it's more likely
that something would happen.
... I'll review a draft issue report.
nigel: Okay, thanks, I'll prepare one.
glenn: I just submitted a new
pull request last night, to add new feature designations
in
... Appendix E for most/all of the new features.
... I have also processed all of the editorial notes that
propose new features.
nigel: I think it's too soon to
have review comments on this - my concern would be that
we
... get the right level of granularity.
glenn: I am sure that we will tweak this list as we advance towards PR.
nigel: What we need to worry
about now is if anyone wants to hold back on a merge of
this
... to allow extra time for review?
... Well it seems that noone does, so go ahead in 2-3 days and
merge if you need to Glenn.
glenn: By the way if problems are
raised later they would still be fair game for addressing
later.
... On Safe Crop Area, I plan to create a new pull request with
different wording and
... incorporate the points raised by Pierre as well as Nigel's
original intent.
pal: I have three concerns: 1)
Safe Crop Area is not a good term. I would call it Active
Area.
... 2) Should vs Shall. I think it should all be
'should'.
... 3) We have to make sure it works correctly preserving
aspect ratio of the root container.
group: [discussion of these points - too fast for scribe (who is involved!) to write down, most of which are also in the pull request review comments]
glenn: I propose to separate mandation from feature definition, using feature designation.
pal: I would need to see the pull request to understand if that works for me in this case.
glenn: I think I have enough information to take a stab at text that we can move forward with. Let me do that and I will create a pull request for that purpose.
nigel: I am still offering BBC in
February for the next F2F meeting, dates currently tbc,
... but also want to note that I will likely be at the CSUN
conference in San Diego from 1-3 March
... so having a meeting in California around that time would be
a logistical possibility at least
... for me.
... Okay, we took an extra half hour today - thanks all who
were able to linger, for your flexibility. [Adjourns
meeting]