13:56:41 <RRSAgent> RRSAgent has joined #tt
13:56:41 <RRSAgent> logging to http://www.w3.org/2013/07/25-tt-irc
13:56:43 <trackbot> RRSAgent, make logs public
13:56:43 <Zakim> Zakim has joined #tt
13:56:45 <trackbot> Zakim, this will be TTML
13:56:45 <Zakim> ok, trackbot; I see SYMM_TTWG()10:00AM scheduled to start in 4 minutes
13:56:46 <trackbot> Meeting: Timed Text Working Group Teleconference
13:56:46 <trackbot> Date: 25 July 2013
13:59:17 <tmichel> tmichel has joined #tt
13:59:45 <plh> plh has joined #tt
14:00:08 <plh> trackbot, start telcon
14:00:10 <trackbot> RRSAgent, make logs public
14:00:12 <trackbot> Zakim, this will be TTML
14:00:12 <Zakim> ok, trackbot; I see SYMM_TTWG()10:00AM scheduled to start now
14:00:13 <trackbot> Meeting: Timed Text Working Group Teleconference
14:00:13 <trackbot> Date: 25 July 2013
14:00:23 <Zakim> SYMM_TTWG()10:00AM has now started
14:00:25 <Zakim> +Plh
14:00:30 <Zakim> +hhalpin
14:00:39 <pal> pal has joined #tt
14:00:45 <tmichel> zakim, dial Thierry-Cip
14:00:45 <Zakim> ok, tmichel; the call is being made
14:00:46 <Zakim> +Thierry
14:01:01 <Zakim> + +44.154.558.aaaa
14:01:06 <plh> zakim, hhalpin is really pal
14:01:06 <Zakim> +pal; got it
14:01:13 <njm> njm has joined #tt
14:01:16 <plh> zakim, aaaa is Sean
14:01:16 <Zakim> +Sean; got it
14:01:39 <mijordan> mijordan has joined #tt
14:01:43 <tmichel> zakim, mute me
14:01:43 <Zakim> sorry, tmichel, I do not know which phone connection belongs to you
14:01:46 <Zakim> +??P12
14:02:25 <Zakim> +??P13
14:02:29 <njm> I have just dialled in
14:02:34 <glenn> zakim, ??p13 is me
14:02:34 <Zakim> +glenn; got it
14:02:48 <Zakim> +[Adobe]
14:02:50 <njm> zakim, ??p12 is me
14:02:50 <Zakim> +njm; got it
14:03:23 <mijordan> zakim, adobe is me
14:03:23 <Zakim> +mijordan; got it
14:03:55 <plh> zakim, mute thierry
14:03:55 <Zakim> Thierry should now be muted
14:04:54 <Sean_> Sean_ has joined #tt
14:05:06 <Sean_> zakim, who is here?
14:05:06 <Zakim> On the phone I see Plh, pal, Thierry (muted), Sean, njm, glenn, mijordan
14:05:08 <Zakim> On IRC I see Sean_, mijordan, njm, pal, plh, tmichel, Zakim, RRSAgent, Sean, glenn, trackbot
14:05:32 <plh> scribe: plh
14:06:24 <plh> Topic: Holiday next week
14:06:44 <plh> Next week meeting is postponed
14:06:58 <plh> Topic: Open actions
14:07:07 <plh> action-88?
14:07:07 <trackbot> ACTION-88 -- Philippe Le Hégaret to make sure the TTML media type is properly registered for Issue-175. -- due 2013-07-31 -- OPEN
14:07:07 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/88
14:07:44 <plh> --> https://tools.iana.org/public-view/viewticket/695904 tracker for medfia type
14:08:00 <plh> action-177?
14:08:00 <trackbot> ACTION-177 -- Glenn Adams to update local copy of xml.xsd to use newer copy based on above link. -- due 2013-07-25 -- OPEN
14:08:00 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/177
14:08:06 <Zakim> +Thomas_Bause_Mason
14:08:16 <tbause> tbause has joined #tt
14:08:19 <plh> Glenn: I have the info but didn't get to it yet
14:08:25 <plh> ation-178?
14:08:28 <plh> action-178?
14:08:28 <trackbot> ACTION-178 -- Sean Hayes to open new issue(s) describing problems with concrete encoding. -- due 2013-07-25 -- OPEN
14:08:28 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/178
14:08:42 <plh> action-178: that's issue 264
14:08:42 <trackbot> Notes added to ACTION-178 Open new issue(s) describing problems with concrete encoding..
14:08:46 <plh> close action-178
14:08:46 <trackbot> Closed ACTION-178 Open new issue(s) describing problems with concrete encoding..
14:09:22 <plh> action-179?
14:09:22 <trackbot> ACTION-179 -- Sean Hayes to follow up with plh on ACTION-88 -- due 2013-07-25 -- OPEN
14:09:22 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/179
14:09:35 <plh> close action-179
14:09:35 <trackbot> Closed ACTION-179 Follow up with plh on ACTION-88.
14:09:42 <plh> action-180?
14:09:43 <trackbot> ACTION-180 -- Glenn Adams to ensure that 10REC errata page is cleared after 10SE is published as REC. -- due 2013-07-25 -- OPEN
14:09:43 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/180
14:09:51 <plh> Sean: waiting on that one
14:09:56 <plh> action-182?
14:09:56 <trackbot> ACTION-182 -- Thierry Michel to create ttml2 and ttml1 short names, to change tracker product labels as needed -- due 2013-07-25 -- OPEN
14:09:56 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/182
14:10:18 <plh> zakim, unmute thierry
14:10:18 <Zakim> Thierry should no longer be muted
14:10:23 <tmichel> zakim, unmute thierry
14:10:23 <Zakim> Thierry was not muted, tmichel
14:10:37 <plh> Thierry: didn't reserve it yet
14:11:16 <plh> Sean: main issue is to separate the two versions
14:11:27 <glenn> zakim, mute thierry
14:11:27 <Zakim> Thierry should now be muted
14:11:37 <plh> action-183?
14:11:37 <trackbot> ACTION-183 -- Sean Hayes to work with plh on TPAC schedule. -- due 2013-07-25 -- OPEN
14:11:37 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/183
14:11:42 <tmichel> zakim, mute thierry
14:11:42 <Zakim> Thierry was already muted, tmichel
14:11:59 <plh> Sean: we're clashing with Web and TV IG
14:12:34 <plh> plh: can we move to Thursday/Friday?
14:12:39 <plh> Sean: clash with HTML WG
14:12:52 <plh> pal: do we need more than one day?
14:15:23 <plh> plh: Sean: could we do Monday and Friday?
14:15:31 <plh> Sean: could we do Monday and Friday?
14:15:50 <plh> Sean: if we get everything done on Monday, we won't need the Friday
14:16:04 <tmichel> I may have a digital publishing meeting on friday
14:16:05 <plh> ... won't clash with WebTV IG and HTML WG business
14:17:16 <plh> zakim, unmute thierry
14:17:16 <Zakim> Thierry should no longer be muted
14:17:17 <tmichel> OK
14:17:22 <plh> zakim, mute thierry
14:17:22 <Zakim> Thierry should now be muted
14:17:32 <plh> ACTION: Thierry to check with Angel if Monday/Friday is ok
14:17:32 <trackbot> Created ACTION-184 - Check with Angel if Monday/Friday is ok [on Thierry Michel - due 2013-08-01].
14:17:44 <plh> close action-183
14:17:44 <trackbot> Closed ACTION-183 Work with plh on TPAC schedule..
14:18:03 <plh> Topic: issue 259
14:18:09 <plh> issue-259?
14:18:09 <trackbot> ISSUE-259 -- Define "closest" -- raised
14:18:09 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/259
14:18:25 <plh> The term "closest" is used a number of times. Does closest mean 12.5 = 12 or 12.5 = 13? Suggest defining closest more precisely.
14:19:16 <plh> pal: hopefully, that's purely editorial. going over the document and making sure we're clear on what closest means
14:19:55 <plh> ACTION: Glenn to go through the spec for issue 259
14:19:55 <trackbot> Created ACTION-185 - Go through the spec for issue 259 [on Glenn Adams - due 2013-08-01].
14:20:05 <plh> issue-260?
14:20:05 <trackbot> ISSUE-260 -- When agent is not @type 'character', then should prohibit actor child. -- raised
14:20:05 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/260
14:21:03 <plh> Glenn: if the type isn't character we shouldn't have an actor child
14:21:16 <plh> ... found the issue when implementing the validator tool
14:21:32 <plh> ... agent can be person, organization, other
14:22:35 <plh> @@: in a dramatic reconstruction, you may have an actor playing a real person
14:22:47 <plh> ... so I would allow actor for person and character
14:22:57 <plh> Glenn: sounds like there is a use case for this then
14:23:14 <plh> ... if we're going to allow for person and other, do we want a restriction at all?
14:23:31 <plh> ... maybe we can tweak the prose...
14:23:45 <plh> ACTION: Glenn to work with Nigel to come up with a resolution for issue 260
14:23:45 <trackbot> Created ACTION-186 - Work with Nigel to come up with a resolution for issue 260 [on Glenn Adams - due 2013-08-01].
14:23:49 <plh> s/@@/Nigel/
14:23:56 <plh> Topic: issue 261
14:24:01 <plh> issue-261?
14:24:01 <trackbot> ISSUE-261 -- signaling docoument profile conformance is separate from decoder presentation requirements -- raised
14:24:01 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/261
14:24:39 <plh> Sean: let's skip this for the moment
14:25:08 <plh> Nigel: from the EBU meeting, we did consider profiling
14:25:20 <plh> ... we'd like to provide some input in our experience about creating EBU-TT
14:25:38 <plh> Sean: I'd like to dedicate a special meeting on profiles, maybe in 2 weeks
14:25:48 <plh> ... misunderstandings about use cases
14:25:53 <plh> ... would that work for EBU?
14:26:00 <plh> Nigel: I doubt we'll be ready by then
14:26:07 <plh> Sean: we can wait then
14:26:31 <plh> ... it's not urgent but need to be addressed at some point
14:26:45 <plh> Nigel: if you want something formal, that would take more time
14:26:58 <plh> ... I'll check with the EBU group
14:27:06 <plh> ... for documentation of the profile issues
14:27:23 <plh> ... we'll make sure that folks can attend
14:27:25 <pal> q+
14:27:44 <plh> ack pal
14:27:54 <plh> Pal: sounds like a great idea but later date better
14:28:08 <plh> ... there is long discussion between Mike Dolan and Glenn on the reflector
14:28:13 <plh> ... did you look at it?
14:28:45 <plh> [...]
14:29:00 <plh> Pal: would be good to take into account the discussion there in the EBU
14:29:46 <plh> Paul: issue 263 is also related
14:30:08 <plh> ... it deals with how to specify mechanically a profile that applies constraints on features
14:30:34 <plh> Sean: we need to understand what we built, if it fits the use cases, and move from there
14:30:56 <plh> ... there are other issues around profile that weren't close properly either
14:31:09 <plh> Pal: look at the original intent from Glenn on profile
14:31:22 <plh> ... fundamental background to understand how it's designed today
14:31:39 <plh> Sean: ok, let me know when folks are ready for this discussion
14:31:57 <plh> Glenn: the list of features in 1.0 was something that I produced during the CR phase of 1.0
14:32:10 <plh> ... in order to refer technical feature that we wish to create tests for
14:32:24 <plh> ... it wasn't something the group did
14:32:32 <plh> ... based on my best reading
14:32:47 <plh> ... but we didn't go through it in details
14:33:00 <plh> ... now we have actual practice feedback
14:33:16 <plh> Sean: they were useful, but we have more experience now indeed
14:33:37 <plh> ... we may divide some of the features, inheritance, etc.
14:33:43 <plh> ... so it's open for ttml 2
14:34:49 <plh> Topic: issue 262
14:34:51 <plh> issue-262?
14:34:51 <trackbot> ISSUE-262 -- tts:extent semantics if value not supported -- raised
14:34:51 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/262
14:35:24 <plh> Sean: Glenn, any more thought?
14:35:50 <plh> Glenn: initial thinking was to mandate support for auto
14:36:16 <plh> ... so if you support extent at all, you need to interpret auto as well
14:36:34 <plh> Nigel: this kind of issue should be part of the discussion on profile
14:36:43 <plh> ... the media support or not needs to be considered there
14:36:47 <plh> Glenn: agreed
14:37:26 <plh> ... we have to draw some line somewhere because we can't specify everything but we need better guidelines on how to interpret those sentences
14:37:32 <plh> Sean: so, part of profile discussion?
14:37:42 <plh> Glenn: related to supported or not.
14:37:53 <plh> ... if the agent doesn't support a value, what does it do?
14:39:09 <plh> Sean: can we resolve this one by removing "supported" in the phrase?
14:39:20 <plh> Glenn: not sure yet
14:39:31 <plh> ... can we do it after we're done with profiles?
14:39:33 <plh> Sean: sure
14:39:42 <plh> Topic: issue 264
14:39:45 <plh> issue-264?
14:39:45 <trackbot> ISSUE-264 -- What XML entities are valid in TTML canonical syntax -- raised
14:39:45 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/264
14:40:15 <plh> Sean: [summarize the issue]
14:40:31 <plh> ... I've seen content through as copy/paste from html
14:40:43 <plh> ... but ttml processors don't deal with those
14:40:56 <plh> ... so we need to clarify what is or isn't supported
14:41:17 <plh> Glenn: appendix N refers to XML 1.0 (or 1.1)
14:41:24 <plh> ... it defines what you get
14:41:32 <plh> ... &nbsp; isn't one of those
14:41:45 <plh> ... we could add a note for readers that don't understand these things
14:41:48 <pal> +1
14:41:56 <plh> ... we could define more, but don't like it
14:42:05 <plh> Sean: I'm fine with a note
14:42:22 <plh> ... will help pointing content people to
14:42:31 <plh> ... as it stands it's a bit open
14:42:42 <njm> +1
14:42:57 <plh> ACTION: Glenn to add a note to appendix N on valid XML entities
14:42:57 <trackbot> Created ACTION-187 - Add a note to appendix N on valid XML entities [on Glenn Adams - due 2013-08-01].
14:43:08 <plh> Glenn: applies to TTML 1.0 and TTML 2
14:43:34 <plh> Topic: issue 150
14:43:37 <plh> issue-150?
14:43:37 <trackbot> ISSUE-150 -- TTML XSD vallidation and extension problem -- closed
14:43:37 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/150
14:43:44 <plh> Sean: is there anything to discuss there?
14:43:55 <plh> Nigel: this is something that has come up as a real world issue
14:44:17 <plh> ... woulde help to have a more granular version in XSD of what's permitted
14:44:29 <plh> Sean: new issue or open the old one?
14:44:49 <plh> Glenn: let's open a new. also related to skip, lax, and strict processing in XSD
14:45:01 <pal> q+
14:45:15 <plh> ... XSD 1.1 helps a bit
14:45:32 <plh> ... we added ##other to resolve issue-150
14:45:54 <plh> ... it allows foreign @ to fall through the schema
14:46:42 <plh> ... also related issue on the purpose of the schema isn't aligned with our definition of validity in the document
14:47:25 <plh> ... our schema is to be used with concrete document instead of abstract valide infoset
14:47:55 <plh> ACTION: Glenn to create an issue to address the use of other namespace vocabulary in the schema
14:47:55 <trackbot> Created ACTION-188 - Create an issue to address the use of other namespace vocabulary in the schema [on Glenn Adams - due 2013-08-01].
14:48:02 <plh> Topic: issue 257?
14:49:06 <plh> Topic: Action items
14:49:40 <plh> ack pal
14:50:31 <plh> close action-61
14:50:31 <trackbot> Closed ACTION-61 Request shortname ttml11 prior to FPWD on TTML1.1.
14:51:23 <njm> q+
14:51:32 <plh> ack njm
14:51:50 <plh> Nigel: issue-179 was discussed in the EBU meeting as well
14:52:05 <plh> ... at the moment, there is one coordinate system in TTML
14:52:33 <plh> ... the graphic plane may have a different resolution than the captions
14:52:55 <plh> ... that's difference is causing some issues about what to do
14:53:21 <plh> ... same issue in the temporal domain as well
14:54:21 <plh> Sean: for the HTML5 to CSS mapping, the graphic plane resolution is independent. there is a logical pixel effectively
14:54:49 <plh> ... I scale down to the video rectangle after that
14:55:00 <plh> ... that gets over the whole issue
14:55:25 <glenn> back
14:55:33 <plh> ... but because TTML has some abstract words around pixel. we could define a default pixel grid
14:55:44 <plh> ... with possibility of overwriting that
14:56:04 <glenn> suggest we use the SVG user coordinate space model
14:56:04 <plh> ... and then transform it to the graphic plane
14:56:33 <plh> Nigel: scaling horizontal/vertical differences
14:56:53 <plh> Sean: different methods to scale
14:57:16 <plh> ... that transformation process is outside the spec. it's for the spec that defines the video media grid
14:57:30 <plh> ... but ttml was keep the logical pixel grid
14:57:36 <plh> s/was/would/
14:57:52 <plh> Nigel: I think I agree re logical coordinate system
14:58:18 <plh> Sean: so action-94 is to write that down
15:00:18 <plh> close action-129
15:00:18 <trackbot> Closed ACTION-129 Draft response to bring back to the group to respond to IANA on MIME type submission..
15:00:21 <Zakim> -mijordan
15:00:30 <plh> action-141?
15:00:30 <trackbot> ACTION-141 -- Sean Hayes to call for Action to identify discrepancies in TTML 1.0 on different profiles. -- due 2013-02-14 -- OPEN
15:00:30 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/141
15:00:43 <Zakim> -Thomas_Bause_Mason
15:01:11 <plh> action-143?
15:01:11 <trackbot> ACTION-143 -- Philippe Le Hégaret to provide location to Glenn for unwrapped schemas. -- due 2013-02-14 -- OPEN
15:01:11 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/143
15:01:56 <plh> plh: we still want to have an unwrapped schema?
15:02:06 <plh> sean: it could create a server issue
15:02:21 <plh> close action-143
15:02:21 <trackbot> Closed ACTION-143 Provide location to Glenn for unwrapped schemas..
15:03:44 <plh> action-164?
15:03:44 <trackbot> ACTION-164 -- Sean Hayes to investigate interop issues using CSS familyName constructs -- due 2013-06-06 -- OPEN
15:03:44 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/164
15:04:34 <plh> issue-33?
15:04:34 <trackbot> ISSUE-33 -- ts:fontFamily and quotedString -- closed
15:04:34 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/33
15:04:42 <plh> issue-223?
15:04:42 <trackbot> ISSUE-223 -- Need to make <familyName> consistent with CSS syntax rules. -- closed
15:04:42 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/223
15:05:41 <plh> Glenn: this was about the \u handling
15:06:03 <plh> ... you'd need to transform into numeric character reference instead
15:06:47 <plh> Sean: we don't define what happen with the family string...
15:07:06 <plh> Glenn: it's in a string, it's treated differently
15:07:29 <plh> Sean: I can't imagine someone using non-generic font types
15:07:39 <plh> Glenn: we define it...
15:08:24 <plh> action-164: this is about the embedded unicode mapping
15:08:24 <trackbot> Notes added to ACTION-164 Investigate interop issues using CSS familyName constructs.
15:09:10 <plh> Pal: there is an app out there that uses non-generic font family
15:09:22 <plh> ... so let's not break backward compatibility...
15:09:43 <plh> ... it reference the SMPTE @@ profile
15:10:10 <plh> ... there is a mapping defined for the font family name to an external font file
15:10:23 <plh> ... I'll be happy to share more details
15:10:59 <plh> ACTION: Pierre to report on the use of font family names to reference external font file resources
15:10:59 <trackbot> Created ACTION-189 - Report on the use of font family names to reference external font file resources [on Pierre-Anthony Lemieux - due 2013-08-01].
15:11:12 <plh> action-165?
15:11:12 <trackbot> ACTION-165 -- Pierre-Anthony Lemieux to investigate use cases for ISSUE-232 -- due 2013-06-13 -- OPEN
15:11:12 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/165
15:11:52 <plh> Pal: there is a spec that allows out there. I'll follow up
15:12:26 <plh> Glenn: wonder if you meant bidi in a vertical context
15:13:35 <plh> action-166?
15:13:35 <trackbot> ACTION-166 -- Mike Dolan to open issue for 1.1 regarding encodings -- due 2013-06-27 -- OPEN
15:13:35 <trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/166
15:15:05 <plh> close action-173
15:15:05 <trackbot> Closed ACTION-173 Fold issue-258 into change proposal 15 and close 258.
15:15:35 <plh> close action-176
15:15:35 <trackbot> Closed ACTION-176 Work with W3T to lengthen scheduled meeting to 2h.
15:16:05 <plh> Topic: AOB
15:16:24 <plh> Nigel: reporting from EBU: we're going to create a liaison communication back to the group
15:16:29 <plh> ... topics
15:16:40 <plh> ... presentation style multi-row line
15:16:49 <plh> ... might be covered by shrink-to-fit
15:16:58 <plh> ... line row padding
15:17:07 <plh> ... metadata
15:17:13 <plh> ... carriage of binary data
15:17:32 <plh> ... profiling
15:17:33 <plh> ... ability to express date
15:17:40 <plh> ... ie add date to the time expression
15:17:59 <plh> ... crossing midnight present some issues
15:18:40 <plh> Sean: we have the ability to do clock expression, but specific dates present challenges due to leap seconds
15:18:55 <plh> Glenn: it's related to the current local time midnight
15:19:08 <plh> ... if you want to related to a different date, you have to do something
15:19:22 <plh> ... you could have + offset but only allow 23 hours
15:19:53 <plh> Sean: I think the idea is to have some metadata to specify the start
15:20:05 <plh> ... then we could use utc offset time
15:20:47 <plh> Nigel: one outcome, but something else as well. you could end up with a 0 crossing issue
15:21:11 <plh> ... no way to indicate that 0 crossing happened
15:21:43 <plh> ... it can happen if you got a reference time scale that goes up but the system might need to reboot...
15:21:54 <plh> Sean: ok, we'll need more details then
15:21:58 <plh> NigeL: understood
15:22:04 <plh> s/NigeL/Nigel/
15:22:40 <plh> ... one more from EBU: to confirm the meaning of a doc with no time expression in it
15:22:50 <plh> ... we think it's externally defined
15:22:52 <plh> ... which is fine
15:23:15 <plh> Glenn: the root container temporal extent is define by the presentation processing context
15:23:29 <plh> ... and body is defined as a parallel construct by default
15:23:50 <plh> ... so any text in the document would leave for as long as the external extent exists
15:24:00 <plh> ... you could follow throught the spec
15:24:11 <plh> ... but maybe not be all in one paragraph
15:24:36 <plh> Pal: Member submission from Movielabs
15:24:57 <plh> ... https://www.w3.org/Submission/2013/02/
15:25:01 <plh> ... happy to answer questions
15:25:13 <plh> ... make sense in the context of the revision of the TTWG charter
15:25:37 <plh> Sean: also input from WebTV IG on the charter
15:25:59 <plh> Pal: goal is not to make life even more complicated by reducing the number of profiles
15:26:09 <plh> ... hope it will be taken up by the group
15:26:18 <plh> Topic: Next meeting
15:26:22 <plh> Sean: in two weeks
15:26:25 <plh> [adjourned]
15:26:27 <Zakim> -njm
15:26:28 <Zakim> -pal
15:26:28 <Zakim> -Plh
15:26:31 <plh> rrsagent, generate minutes
15:26:31 <RRSAgent> I have made the request to generate http://www.w3.org/2013/07/25-tt-minutes.html plh
15:26:32 <Zakim> -glenn
15:26:48 <Zakim> -Sean
15:26:49 <Zakim> SYMM_TTWG()10:00AM has ended
15:26:49 <Zakim> Attendees were Plh, Thierry, +44.154.558.aaaa, pal, Sean, glenn, njm, mijordan, Thomas_Bause_Mason
15:26:52 <plh> Chair: Sean
15:27:03 <plh> rrsagent, generate minutes
15:27:03 <RRSAgent> I have made the request to generate http://www.w3.org/2013/07/25-tt-minutes.html plh
17:03:02 <Zakim> Zakim has left #tt