13:57:46 RRSAgent has joined #tt 13:57:46 logging to http://www.w3.org/2014/08/14-tt-irc 13:57:48 RRSAgent, make logs public 13:57:48 Zakim has joined #tt 13:57:50 Zakim, this will be TTML 13:57:50 ok, trackbot; I see SYMM_TTWG()10:00AM scheduled to start in 3 minutes 13:57:51 Meeting: Timed Text Working Group Teleconference 13:57:51 Date: 14 August 2014 13:58:19 SYMM_TTWG()10:00AM has now started 13:58:25 + +1.720.897.aaaa 13:59:32 +[IPcaller] 13:59:33 + +44.192.341.aabb 13:59:35 mike has joined #tt 14:00:01 zakim, aabb is me 14:00:01 +nigel; got it 14:00:06 zakim, aaaa is me 14:00:06 +glenn; got it 14:00:12 jdsmith has joined #tt 14:00:16 +Mike 14:00:39 + +1.425.868.aacc 14:00:57 zakim, who's on the call? 14:00:58 On the phone I see glenn, nigel, [IPcaller], Mike, +1.425.868.aacc 14:01:14 zakim, aacc is jdsmith 14:01:14 +jdsmith; got it 14:01:19 zakim, [IPcaller] has pal 14:01:19 +pal; got it 14:01:56 Topic: Agenda 14:02:02 chair: nigel 14:02:21 scribeNick: nigel 14:02:34 Regrets : tmichel 14:02:55 courtney has joined #tt 14:03:08 Present: glenn, jdsmith, mike, nigel, pal 14:03:48 + +1.408.771.aadd 14:04:03 Present+ courtney 14:04:07 zakim, aadd is courtney 14:04:07 +courtney; got it 14:05:29 nigel: No AOBs noted 14:06:36 glenn: regrets for 11th September 14:06:40 mike: same here 14:07:12 pal: I'm available on 11th September, so we may be able to do some work on that date 14:07:28 nigel: I'll leave 11th Sep in the diary for now, target 1 hour. 14:08:09 Resolution: Cancel 18th September phone meeting 14:08:53 nigel: We'll leave 25th September in the diary, and mark it as a 2 hour meeting. 14:10:13 Topic: F2F meetings 14:10:19 nigel: Geneva meeting wiki https://www.w3.org/wiki/TimedText/geneva2014#Attendees 14:11:11 nigel: I've suggested a 1000 start on the 16th and a 1700 end on the 17th - happy to take requests for modifications to this. 14:12:01 pal: On the Wednesday afternoon there are simultaneous SMPTE meetings so I'd rather not schedule topics that I need to be involved in then. 14:12:07 glenn: I propose a 0900 start on the Wednesday. 14:12:45 pal: I'll arrive on the Monday night. 14:13:02 glenn: I'm hoping to arrive on Monday night but my travel plans are complex! 14:13:27 nigel: By the way the TPAC registration form has now been updated. 14:13:43 Topic: Timeline for TTML2 publications 14:14:12 nigel: Proposed timeline: 14:14:21 ... * Week commencing 22nd September: publish TTML2 editor’s draft as a FPWD. 14:14:30 ... * Wednesday 8th October: ‘last issues' closure date for TTML2 – any new feature issues beyond this point to be addressed after LC or in v.next. 14:14:45 ... * Thursday 20th November: all issues on TTML2 to be closed or deliberately postponed (to v.next or LC review stage). This is 3 weeks after TPAC, to allow time for any resolutions made in TPAC to be implemented and reviewed. 14:15:12 ... * Wednesday 17th December: Last Call doc ready to request for publication. 14:16:10 pal: There are a number of CPs assigned to me and my plan is to get to them as soon as we get to LC on IMSC, so assuming we do that in October I'll be able to start working on the TTML2 issues that are assigned to me. 14:16:44 glenn: I may have already tackled some of the issues associated with those CPs before then, so my plan for getting to 22nd Sep FPWD is to try to crank through all of the open issues regardless of the CP backing them. 14:17:53 Resolution: We will adopt the proposed timeline as outlined above 14:18:50 Action: nigel draft liaisons to relevant organisations for IMSC 1 timeline 14:18:50 Created ACTION-319 - Draft liaisons to relevant organisations for imsc 1 timeline [on Nigel Megitt - due 2014-08-21]. 14:19:18 Topic: MPEG liaison re MIME Codecs parameter 14:20:01 Issue-305? 14:20:01 Issue-305 -- Registry of TTML profiles and short names -- pending review 14:20:01 http://www.w3.org/AudioVideo/TT/tracker/issues/305 14:22:13 glenn: All the action items against Issue-305 were closed a draft registry was published that we can fine-tune. It's in the wiki. 14:22:50 https://www.w3.org/wiki/TTML/CodecsRegistry 14:23:48 mike: Is the intent that it's a 1:1 mapping from the identifier to the designator? 14:24:04 glenn: There's a proposed syntax with a grammar that allows combinations of ANDs and ORs to be expressed. 14:24:25 ... I haven't checked this proposal again after I published the TTML2 profile features. 14:24:38 mike: So these would be content profile designators or processor designators? 14:25:16 ... The note says explicitly 'processor profile'. 14:25:36 glenn: The TTML2 approach allows a processor profile to be inferred from a content profile but not the other way around. 14:25:54 mike: So for pre-TTML2 profiles? 14:26:03 glenn: TTML1 documents always declare a processor profile. 14:26:12 mike: So can you tell the difference in the codecs signalling? 14:27:02 glenn: No, that codec signalling there, as defined, is only signalling processor profile. That raises an issue if its correct that a processor profile differs from what can be inferred from the document's content profile. 14:27:08 ... I didn't address that in the registry definition. 14:27:19 mike: I'll look at that in more detail. 14:27:51 ... Don't we need a process for updating the table. I think we said we'd take it to the group for consensus, but we didn't discuss deleting or modifying the table. 14:28:02 glenn: There is some wording for deleting entries. 14:28:15 mike: We also need a process for adding entries. 14:28:39 glenn: The wiki is open to anyone with the right privileges, which could be anyone with a W3C account. 14:29:42 mike: I'm happy to add some verbiage that you think is appropriate. 14:29:56 glenn: We can do this in parallel. 14:30:28 mike: Although the action to respond to SMPTE was closed it was done hastily so we should reopen that action or make a new one. 14:30:31 action glenn to review https://www.w3.org/wiki/TTML/CodecsRegistry w.r.t. recent ttml2 changes in profile definition mechanisms 14:30:31 Created ACTION-320 - Review https://www.w3.org/wiki/ttml/codecsregistry w.r.t. recent ttml2 changes in profile definition mechanisms [on Glenn Adams - due 2014-08-21]. 14:30:40 s/action/Action: 14:31:05 action-283? 14:31:05 action-283 -- Nigel Megitt to And dsinger to respond to mpeg liaison -- due 2014-05-01 -- CLOSED 14:31:05 http://www.w3.org/AudioVideo/TT/tracker/actions/283 14:31:06 action mike to update https://www.w3.org/wiki/TTML/CodecsRegistry to add proposed language about process for changing registry 14:31:06 Created ACTION-321 - Update https://www.w3.org/wiki/ttml/codecsregistry to add proposed language about process for changing registry [on Mike Dolan - due 2014-08-21]. 14:31:27 http://lists.w3.org/Archives/Public/public-tt/2014Apr/0025.html 14:31:46 a/action/Action: 14:32:35 mike: After Glenn and I have worked on this we should follow up with a link to the wiki. 14:33:08 mike: The liaison was sent after the April meeting and it didn't appear in the June meeting, so I'll check if anyone saw it, and we can take appropriate action depending. 14:34:14 action-290? 14:34:14 action-290 -- Mike Dolan to Describe the history for how we got to the signalling needed for mpeg that came from dece for issue-305. -- due 2014-05-29 -- OPEN 14:34:14 http://www.w3.org/AudioVideo/TT/tracker/actions/290 14:35:21 close action-290 14:35:22 Closed action-290. 14:35:45 nigel: Do we have clear requirements for this request? 14:36:49 mike: I'm not sure - for example the ability to restrict or extend specific features. 14:37:03 glenn: Feature restrictions and extensions are in TTML2. 14:37:36 ... There are also new top level parameters to express the policy for processors to widen or narrow the semantics. 14:38:30 ... For example if you define a color feature extension that is a restriction, but the processor already supports the unrestricted version, it could widen the semantics of the new feature or extension to claim support for the extension. 14:38:37 mike: Okay I'll take a look at this. 14:39:43 glenn: Issue-263 is relevant here too and we were waiting for mike's review on that. 14:39:56 ... That's also pending review. 14:39:58 issue-263? 14:39:58 issue-263 -- profile feature set may not match intended feature constraints -- pending review 14:39:58 http://www.w3.org/AudioVideo/TT/tracker/issues/263 14:40:45 mike: As long as this is now defined then I'm happy with this. 14:41:19 glenn: Do we want to go back and change SDP-US to make use of any of these new mechanisms e.g. to clarify that its definition of the color requirements is a restriction on the existing color feature. 14:41:58 mike: Probably everything using profiles now needs to be revisited, and SDP-US is one example, as is color within that. 14:42:56 nigel: I propose that we open a new issue to update SDP-US when the dust has settled on TTML2. 14:43:39 glenn: SDP-US is only a Note so we would either have to move it to Rec track or issue a new note. That may impact on the charter. 14:43:45 nigel: We're not sanctioned to move it to Rec. 14:44:29 nigel: But updating the note on our SDP-US is in the charter so we can go ahead and do it. 14:45:26 mike: I'm not sure we should spend time on SDP-US when the proponent is no longer active. 14:45:46 mike: That was Sean. 14:46:05 jdsmith: I'm pondering how we keep this up to date. The -US tag indicates alignment with FCC requirements. 14:46:19 mike: Plus there were some provisions that were peculiar to the US. 14:47:11 Action: jdsmith Indicate preference for updating SDP-US for TTML2 14:47:11 Created ACTION-322 - Indicate preference for updating sdp-us for ttml2 [on Jerry Smith - due 2014-08-21]. 14:47:50 mike: The Issue-305 MPEG liaison did get lost - sending to the secretary often doesn't work. Let me know when we're ready to send an update. 14:48:35 reopen action-283 14:48:35 Re-opened action-283. 14:49:04 action-283: This needs to be redrafted and sent via mike, to reflect the draft registry page and updated profile mechanisms. 14:49:04 Notes added to action-283 And dsinger to respond to mpeg liaison. 14:50:47 Topic: Action items 14:50:52 action-295? 14:50:54 action-295 -- David Singer to Socialise the geneva f2f meeting amongst the webvtt community -- due 2014-06-05 -- PENDINGREVIEW 14:50:54 http://www.w3.org/AudioVideo/TT/tracker/actions/295 14:51:23 close action-295 14:51:23 Closed action-295. 14:51:34 https://www.w3.org/2002/09/wbs/34314/TTWG_Geneva_F2F_Planning/results 14:53:35 Courtney: I think we've done all we can do to publicise the meeting in the WebVTT community. Andreas and I can represent the WebVTT side of things for that discussion. 14:53:52 action-309? 14:53:52 action-309 -- Nigel Megitt to Propose a timeline for ttml 2 fpwd -- due 2014-08-14 -- PENDINGREVIEW 14:53:52 http://www.w3.org/AudioVideo/TT/tracker/actions/309 14:54:06 close action-309 14:54:07 Closed action-309. 14:54:11 action-313? 14:54:11 action-313 -- Glenn Adams to Create erratum for issue-314 -- due 2014-08-07 -- PENDINGREVIEW 14:54:11 http://www.w3.org/AudioVideo/TT/tracker/actions/313 14:54:21 issue-314? 14:54:21 issue-314 -- Temporally active is not defined for regions -- closed 14:54:21 http://www.w3.org/AudioVideo/TT/tracker/issues/314 14:54:56 close action-313 14:54:57 Closed action-313. 14:55:22 action-290? 14:55:22 action-290 -- Mike Dolan to Describe the history for how we got to the signalling needed for mpeg that came from dece for issue-305. -- due 2014-05-29 -- CLOSED 14:55:22 http://www.w3.org/AudioVideo/TT/tracker/actions/290 14:55:43 action-307? 14:55:43 action-307 -- Mike Dolan to Assign priorities to change proposals owned by mdolan -- due 2014-07-24 -- OPEN 14:55:43 http://www.w3.org/AudioVideo/TT/tracker/actions/307 14:57:08 https://www.w3.org/wiki/TTML/changeProposal024 14:57:38 courtney_ has joined #tt 14:57:55 issue-167? 14:57:56 issue-167 -- allowing attributes that have no semantics on specific elements -- open 14:57:56 http://www.w3.org/AudioVideo/TT/tracker/issues/167 14:58:16 glenn: I can handle issue-167, so maybe the fix is to change the owner of the CP to me. 14:58:25 mike: Are you going to codify a proposal? 14:58:34 glenn: I'll just do it and then we can review. 14:58:46 mike: What is your intent here? 14:59:16 glenn: It's to add a single sentence paragraph to the header of the style processing semantics explaining that even though attribtues can be present on elements to which they do not apply, 14:59:42 ... for inheritance purposes, then if they are not inherited they are effectively ignored. I'm not sure about prohibiting them from being present. 15:00:36 mike: My issue was to prevent a mass of attributes on the tt:p elements for which they have no meaning and can not be used by child elements. 15:00:45 ... I'm leaning towards forbidding them. 15:01:11 glenn: It's something that could be readily tested in the TTV product but could not be described in the schema so I don't really have a huge problem with it. We can also make it a SHOULD NOT, 15:01:27 ... and they're handled in TTV by issuing warnings as opposed to errors. 15:01:44 ... Also one of the attributes is origin, and we have now defined the meaning of origin and extent on p and div. 15:02:02 mike: At the time that was of no use but people did it and invented semantics for it. That example no longer applies. 15:02:19 glenn: The question is if we make a SHALL NOT or a SHOULD NOT. 15:02:54 mike: I'd be happy with a SHOULD NOT. By the way the schema could be updated for this, though it would be a significant change. I was concerned about attributes that no child can make use of - it should be just wrong. 15:03:24 glenn: For example zIndex and opacity - we've restricted those to regions only, even though opacity would have a CSS mapping. 15:03:44 mike: Maybe they don't all have the same rule. The minimum bar would be SHOULD NOT and on a case by case basis they could be SHALL NOTs. 15:04:15 glenn: Since the semantics are to ignore them there would be no difference in processing between SHOULD NOT and SHALL NOT. The only difference would be, for a validating processor, 15:04:43 ... if we expressed it as SHALL NOT then a validating processor would need to check and potentially reject the document. There would be at most a warning if we make them SHOULD NOTs. 15:05:17 mike: The more mature it is and the more validating tools are out there the less this is a practical concern. 15:05:33 -jdsmith 15:05:43 https://github.com/skynav/ttv/issues/12 15:06:01 +jdsmith 15:06:13 ... Let's go with a sentence providing a warning to authors that there are attributes that have no semantic meaning and are potentially not even inheritable. 15:06:27 glenn: I propose to go with SHOULD NOTs and open an issue on TTV. 15:06:34 jdsmith has joined #tt 15:06:46 mike: I'm okay with that - anything we can do in the spec to make clear that syntactic permission doesn't imply processing behaviour. 15:06:48 see https://github.com/skynav/ttv/issues/12 for TTV issue (already registered) 15:07:28 nigel: Does this need to be pre-FPWD or pre-LC? 15:07:33 glenn: I'll do this pre-FPWD. 15:07:48 nigel: I'll make this a priority 1 then. 15:08:05 action-307: This is a priority 1, and reassigned to glenn 15:08:05 Notes added to action-307 Assign priorities to change proposals owned by mdolan. 15:08:12 close action-307 15:08:12 Closed action-307. 15:08:25 action-311? 15:08:25 action-311 -- Nigel Megitt to Check with mdolan on status of issue-263 and issue-305 etc -- due 2014-08-07 -- OPEN 15:08:25 http://www.w3.org/AudioVideo/TT/tracker/actions/311 15:08:33 close action-311 15:08:33 Closed action-311. 15:08:53 nigel: adjourning until xx:12 15:12:42 nigel: And that's now! 15:13:18 Topic: Issues 15:13:37 issue-263? 15:13:37 issue-263 -- profile feature set may not match intended feature constraints -- pending review 15:13:37 http://www.w3.org/AudioVideo/TT/tracker/issues/263 15:15:23 close issue-263 15:15:23 Closed issue-263. 15:15:40 issue-311? 15:15:40 issue-311 -- Note on progressivelyDecodable is not a sentence -- pending review 15:15:40 http://www.w3.org/AudioVideo/TT/tracker/issues/311 15:16:23 mike: on issue-263 we didn't actually do anything on SDP-US. 15:16:48 glenn: We addressed the requirements for TTML2 but nothing on SDP-US. I'd suggest that this is a new issue, rather than keeping the old one open. 15:17:01 ... For example: "Update SDP-US to make use of new mechanisms to define..." 15:17:57 Action: nigel to update issue-263 to target product TTML2 and open a new one on SDP-US. 15:17:58 Created ACTION-323 - Update issue-263 to target product ttml2 and open a new one on sdp-us. [on Nigel Megitt - due 2014-08-21]. 15:18:20 issue-311? 15:18:20 issue-311 -- Note on progressivelyDecodable is not a sentence -- pending review 15:18:20 http://www.w3.org/AudioVideo/TT/tracker/issues/311 15:18:49 close issue-311 15:18:49 Closed issue-311. 15:18:54 issue-330? 15:18:54 issue-330 -- Is Presented Region a synonym for temporally active region? -- pending review 15:18:54 http://www.w3.org/AudioVideo/TT/tracker/issues/330 15:20:01 close issue-330 15:20:01 Closed issue-330. 15:20:09 issue-334? 15:20:09 issue-334 -- Misuse of style property characteristics with ttp:progressivelyDecodable -- pending review 15:20:09 http://www.w3.org/AudioVideo/TT/tracker/issues/334 15:21:49 glenn: I'm happy with this as long as it doesn't present the parameter with the appearance of a style attribute. 15:21:56 pal: I reverted to the original prose. 15:22:30 glenn: If you look at the current TTML parameter definition we use a particular form of language, which would be good to reproduce. 15:22:56 pal: I'll make a change accordingly. 15:23:04 reopen issue-334 15:23:04 Re-opened issue-334. 15:24:50 issue-334: change language to "If ittp:progressivelyDecoable is not specified, then it must be considered to be equal to ..." 15:24:50 Notes added to issue-334 Misuse of style property characteristics with ttp:progressivelyDecodable. 15:25:11 issue-288? 15:25:11 issue-288 -- Rules for splitting and accumulating documents -- open 15:25:11 http://www.w3.org/AudioVideo/TT/tracker/issues/288 15:25:25 https://www.w3.org/wiki/TTML/changeProposal025 15:27:01 nigel: I have proposed a set of rules and an algorithm for combining documents. 15:27:16 glenn: I'd suggest this as ttm:group to be significant only on the tt:tt element. 15:27:40 ... It may be more effective to define this in terms of an ISD sequence, but I can see applicability beyond that. 15:27:53 nigel: I agree that restricting it to ISD sequences is too restrictive. 15:28:22 glenn: There's a question whether this is a parameter or a metadata item. Parameters are used to direct the processor, and I'm not sure this group mechanism would have processor semantics. 15:28:48 ... Unless we define processor semantics that are mandatory to use in certain circumstances I would make it a metadata attribute because it feels more like that to me. 15:30:10 nigel: It's a specific processor parameter for a 'combiner'. 15:30:34 glenn: That suggests to me that it's not a general parameter but a more specific one, which tells me it's a metadata item not a parameter. 15:30:55 As expressed on the reflector, I remain of the opinion that this feature is not needed. That said, the proposal does no harm provided its semantics are clear. 15:31:02 I have to leave for another meeting 15:31:12 -Mike 15:31:25 glenn: I've been trying to restrict parameters in TTML to things that area applicable to all processing and transformation not a specific set of transformation scenarios. 15:32:34 nigel: I was at pains to make this not affect processing of any single document. 15:32:54 glenn: In that case it would be metadata e.g. in the ttm: namespace. 15:33:17 nigel: I will update the CP, and make it an NCNAME. 15:33:42 issue-307? 15:33:42 issue-307 -- Conformance language and processor profile rather than content profile. -- open 15:33:42 http://www.w3.org/AudioVideo/TT/tracker/issues/307 15:35:24 nigel: I've raised a new CP, CP28 whose main outcome is to create a new text profile that does not include the complexity constraints. 15:36:24 pal: The summary is one thing, but the CP has lots of other statements and proposals that go beyond. 15:37:40 pal: We could just amend the CP to reflect that end result. If that's the desire then it should be captured as such. 15:38:13 glenn: I've renamed the CP to include "IMSC" in the name. 15:38:45 pal: I think we shouldn't jump ahead to the changes needed to achieve the goal. 15:40:23 nigel: I was attempting to be helpful to the editor in proposing the edits needed. 15:40:53 +nigel.a 15:42:17 nigel: Are you objecting to feature designators for the HRM? 15:42:46 pal: I don't think its necessary: another way to achieve the goal is to factor out the HRM section and add it into 4.2 and 4.3, and add 4.4 for Unconstrained Text Profile. 15:42:51 nigel: Okay, that might work. 15:45:12 ... If we want to apply different edits we can change the Edits to Apply section. 15:45:20 pal: Also the CP references issues that haven't yet been filed. 15:45:33 nigel: Agreed, we can take no action on issues that have not been filed. 15:46:42 pal: For example ebutts:linePadding has not been filed as an issue, so we should consider this if it is filed. 15:48:18 nigel: I'm happy to put this on pause until the issues for which it would be of use are raised. 15:50:05 pal: I can make some edits on this CP. 15:51:47 pal: The additional constraints in some distribution mechanisms are orthogonal to the HRM. 15:52:15 nigel: The HRM may block resolution of future issues, but we can wait until those are filed. 15:52:46 pal: You can make highly complex but low data size documents. 15:52:54 nigel: Questions if this is really true. 15:53:27 pal: You can with animations. 15:53:29 glenn and pal: discuss the generation of ISDs as they may be created for animations. 15:54:44 nigel: Happy for pal to make an alternate proposal that we can discuss. 15:55:05 issue-310? 15:55:05 issue-310 -- Forward reference rule doesn't take into account child elements -- open 15:55:05 http://www.w3.org/AudioVideo/TT/tracker/issues/310 15:56:14 glenn: In TTML1 and TTML2 there is no forward referencing defined other than implicitly via the expression of parallel timing. 15:56:24 pal: Can style references be made forwards? 15:57:09 glenn: Content elements can not reference forward style elements however inside of a styling element itself chained referential styling can have forwards references, but not circular ones. 15:57:32 ... That's the only case - we can simply make that require backward references only. 15:57:46 pal: That's what §5.5.2 point 4 is specifically meant to deal with. 15:58:27 glenn: Is that really related to progressive decoding of content though, because you have to have decoded the before you get to the content. 15:58:53 pal: I was told that some implementations would not like forward reference styles. Since it didn't seem a huge burden and in some ways a good thing it doesn't seem harmful. 16:00:03 glenn: To call it out specifically, since there are only two example of potentially non-progressively decodable that we've found: chained styles and timings we could call them out explicitly rather than taking the generic approach. 16:00:25 ... That would make it a little more concrete for authors and implementors to understand. 16:00:42 pal: This is to state points 2 and 4 more concretely? 16:00:54 glenn: Either that or add a note to call out the two cases where those constraints might be validated. 16:01:07 pal: If you can jot that note down it would be a great addition. 16:02:10 action: glenn draft a note for IMSC 1 progressivelyDecodable to make concrete what authors should take into account 16:02:11 Created ACTION-324 - Draft a note for imsc 1 progressivelydecodable to make concrete what authors should take into account [on Glenn Adams - due 2014-08-21]. 16:02:25 -glenn 16:02:43 glenn: there's still an outstanding point about the meaning of 'documents'. 16:03:10 action-324: Also draft wording around which 'documents' are being referred to in the numbered list. 16:03:10 Notes added to action-324 Draft a note for imsc 1 progressivelydecodable to make concrete what authors should take into account. 16:03:18 nigel: adjourns meeting 16:03:22 -[IPcaller] 16:03:24 -courtney 16:03:28 -nigel.a 16:03:45 -jdsmith 16:04:01 rrsagent, make log public 16:04:05 rrsagent, draft minutes 16:04:05 I have made the request to generate http://www.w3.org/2014/08/14-tt-minutes.html nigel 16:06:42 s/Resolution:/RESOLUTION: 16:06:43 s/Resolution:/RESOLUTION: 16:08:21 s|a/action/Action:| 16:08:34 s/action mike/action: mike 16:08:46 disconnecting the lone participant, nigel, in SYMM_TTWG()10:00AM 16:08:47 SYMM_TTWG()10:00AM has ended 16:08:48 Attendees were +1.720.897.aaaa, +44.192.341.aabb, nigel, glenn, Mike, +1.425.868.aacc, jdsmith, pal, +1.408.771.aadd, courtney 16:10:34 rrsagent, draft minutes 16:10:34 I have made the request to generate http://www.w3.org/2014/08/14-tt-minutes.html nigel 16:29:07 nigel has left #tt 16:39:00 Zakim has left #tt 18:52:06 glenn_ has joined #tt 20:19:53 glenn has joined #tt 20:24:21 glenn__ has joined #tt 21:07:27 glenn has joined #tt