14:17:52 <RRSAgent> RRSAgent has joined #annotation
14:17:52 <RRSAgent> logging to http://www.w3.org/2015/04/29-annotation-irc
14:17:54 <trackbot> RRSAgent, make logs public
14:17:54 <Zakim> Zakim has joined #annotation
14:17:56 <trackbot> Zakim, this will be 2666
14:17:56 <Zakim> ok, trackbot; I see DPUB_(ANNO)11:00AM scheduled to start in 43 minutes
14:17:57 <trackbot> Meeting: Web Annotation Working Group Teleconference
14:17:57 <trackbot> Date: 29 April 2015
14:48:17 <fjh> fjh has joined #annotation
14:48:32 <fjh> fjh has joined #annotation
14:48:36 <fjh_> fjh_ has joined #annotation
14:49:06 <fjh_> trackbot, start telecon
14:49:08 <trackbot> RRSAgent, make logs public
14:49:10 <trackbot> Zakim, this will be 2666
14:49:11 <Zakim> ok, trackbot; I see DPUB_(ANNO)11:00AM scheduled to start in 11 minutes
14:49:11 <trackbot> Meeting: Web Annotation Working Group Teleconference
14:49:11 <trackbot> Date: 29 April 2015
14:52:40 <azaroth> azaroth has joined #annotation
14:53:39 <azaroth> azaroth has changed the topic to: agenda https://lists.w3.org/Archives/Public/public-annotation/2015Apr/0136.html ; Zakim 2666
14:55:39 <fjh> Agenda: https://lists.w3.org/Archives/Public/public-annotation/2015Apr/0136.html
14:56:02 <fjh> Chair: Frederick_Hirsch, Rob_Sanderson
14:56:06 <fjh> Present+ Frederick_Hirsch, Rob_Sanderson
14:57:49 <Janina> Janina has joined #annotation
14:58:01 <TimCole> TimCole has joined #annotation
14:58:12 <Jacob_> Jacob_ has joined #annotation
14:58:32 <Jacob_> present+ Jacob_Jett
14:58:54 <Zakim> DPUB_(ANNO)11:00AM has now started
14:59:01 <paoloC> paoloC has joined #annotation
14:59:01 <Zakim> +azaroth
14:59:02 <tbdinesh> tbdinesh has joined #annotation
14:59:14 <naod> naod has joined #annotation
14:59:28 <Matt_Haas> Matt_Haas has joined #annotation
14:59:33 <Zakim> +TimCole
14:59:42 <Kyrce> Kyrce has joined #annotation
14:59:53 <Zakim> +[IPcaller]
14:59:58 <fjh> zakim, ipcaller is me
14:59:58 <Zakim> +fjh; got it
15:00:03 <TimCole> Present+ Tim_Cole
15:00:04 <fjh> zakim, who is here?
15:00:04 <Zakim> On the phone I see azaroth, TimCole, fjh
15:00:06 <Zakim> On IRC I see Kyrce, Matt_Haas, naod, tbdinesh, paoloC, Jacob_, TimCole, Janina, azaroth, fjh, Zakim, RRSAgent, renoirb, dauwhe, ivan, shepazu, JakeHart, nickstenn, rhiaro, csillag,
15:00:06 <Zakim> ... oshepherd, bret, ujvari_, dwhly, bigbluehat, stain, judell_, Mitar, KevinMarks, trackbot
15:00:14 <Zakim> +Matt_Haas
15:00:29 <Matt_Haas> Present+ Matt_Haas
15:00:29 <ivan> zakim, dial ivan-voip
15:00:30 <Zakim> ok, ivan; the call is being made
15:00:30 <Zakim> +Ivan
15:00:31 <fjh> Topic: Agenda Review, Scribe Selection, Announcements
15:00:47 <Zakim> +[IPcaller]
15:00:53 <Zakim> +dauwhe
15:00:57 <Zakim> + +1.201.236.aaaa
15:01:17 <dauwhe> Present+ Dave_Cramer
15:01:19 <Kyrce> zakim, aaaa is me
15:01:19 <Zakim> +Kyrce; got it
15:01:24 <tbdinesh> Zakim, aaaa is me
15:01:24 <Zakim> sorry, tbdinesh, I do not recognize a party named 'aaaa'
15:01:27 <Zakim> + +1.617.588.aabb
15:01:32 <Zakim> +Doug_Schepers
15:01:33 <Kyrce> Present+ Kyrce_Swenson
15:01:41 <Janina> Present+ Janina_Sarol
15:01:50 <fjh> Regrets+ Benjamin_Young, Kristof_Csillag, Bill_Kasdorf
15:02:01 <tbdinesh> Present +TB_Dinesh
15:02:04 <azaroth> zakim, who is here?
15:02:04 <Zakim> On the phone I see azaroth, TimCole, fjh, Matt_Haas, Ivan, [IPcaller], dauwhe, Kyrce, +1.617.588.aabb, Doug_Schepers
15:02:07 <Zakim> On IRC I see Kyrce, Matt_Haas, suskudarli, tbdinesh, paoloC, Jacob_, TimCole, Janina, azaroth, fjh, Zakim, RRSAgent, renoirb, dauwhe, ivan, shepazu, JakeHart, nickstenn, rhiaro,
15:02:07 <Zakim> ... csillag, oshepherd, bret, ujvari_, dwhly, bigbluehat, stain, judell_, Mitar, KevinMarks, trackbot
15:02:11 <suskudarli> Present+ Susan_Uskudarli
15:02:16 <Zakim> + +1.202.707.aacc
15:02:18 <fjh> zakim, who is here?
15:02:18 <Zakim> On the phone I see azaroth, TimCole, fjh, Matt_Haas, Ivan, [IPcaller], dauwhe, Kyrce, +1.617.588.aabb, Doug_Schepers, +1.202.707.aacc
15:02:19 <bjdmeest> bjdmeest has joined #annotation
15:02:20 <Zakim> On IRC I see Kyrce, Matt_Haas, suskudarli, tbdinesh, paoloC, Jacob_, TimCole, Janina, azaroth, fjh, Zakim, RRSAgent, renoirb, dauwhe, ivan, shepazu, JakeHart, nickstenn, rhiaro,
15:02:20 <Zakim> ... csillag, oshepherd, bret, ujvari_, dwhly, bigbluehat, stain, judell_, Mitar, KevinMarks, trackbot
15:02:26 <paoloC> Present+ Paolo_Ciccarese
15:02:31 <Zakim> +[Ugent]
15:02:35 <bjdmeest> zakim, Ugent is me
15:02:35 <Zakim> +bjdmeest; got it
15:02:42 <azaroth> zakim, aabb is paoloC
15:02:43 <Zakim> +paoloC; got it
15:02:45 <renoirb> renoirb has left #annotation
15:02:47 <bjdmeest> Present+ Ben_De_Meester
15:02:49 <RayD> RayD has joined #annotation
15:02:52 <fjh> zakim, where is 202?
15:02:52 <Zakim> North American dialing code 1.202 is District of Columbia
15:03:02 <azaroth> zakim, aacc is RayD
15:03:02 <Zakim> +RayD; got it
15:03:06 <Zakim> + +1.650.274.aadd
15:03:23 <RayD> present+ Ray_Denenberg
15:03:36 <ivan> zakim, where is 650?
15:03:36 <Zakim> North American dialing code 1.650 is California
15:03:45 <dwhly> present+ dan_whaley
15:04:04 <tbdinesh> zakim, ipcaller is me
15:04:04 <Zakim> +tbdinesh; got it
15:04:06 <dwhly> zakim, aadd is dwhly
15:04:06 <Zakim> +dwhly; got it
15:04:57 <ivan> scribenick: Kyrce
15:05:05 <Zakim> + +1.434.971.aaee
15:05:26 <davis_salisbury> davis_salisbury has joined #annotation
15:05:51 <davis_salisbury> present+ davis_salisbury
15:06:08 <fjh> Topic:  Minutes
15:06:38 <Kyrce> fjh: suggest we not approve minutes this week, wait until next week and give people time to review them.
15:06:41 <fjh> http://www.w3.org/2015/04/22-annotation-minutes.html
15:06:54 <fjh> F2F summary - https://lists.w3.org/Archives/Public/public-annotation/2015Apr/0157.html
15:07:29 <Kyrce> fjh: sent message with summary of f2f. one day meeting in conjunction with the iAnnotate conference. Looked at LDP work because people had gone to the LDP f2f. much relates to what we are doing
15:08:24 <Kyrce> fjh: update regarding social web which is a solid proposal based on LDP. then talked about client API all linked from link in chat. Decided to proceed with what Nick had done. Lower level js apis are appropriate rather than trying to complicate.
15:08:32 <TimCole> q+
15:09:14 <fjh> nick’s message on text offsets https://lists.w3.org/Archives/Public/public-annotation/2015Apr/0158.html
15:09:15 <Kyrce> fjh: publishing: markup is best. RangeFinder API had some questions. Lots of algorithm choices doesn't necessarily help. Overall- check the minutes, all of this is there.
15:09:30 <fjh> I Annotate, see https://docs.google.com/document/d/1ML3u4hmCF2oeIFNG3To4L1NBjqWnYQ37vYJ5Y2eLUdY/view
15:09:32 <Zakim> +stain
15:09:34 <fjh> q?
15:09:35 <Kyrce> fjh: iAnnotate. A lot of good stuff. There is a page with a summary.
15:09:37 <fjh> ack TimCole
15:10:08 <shepazu> q+
15:10:39 <TimCole> https://rawgit.com/w3c/aria/master/aria/dpub.html#footnote
15:10:49 <ivan> q+
15:11:06 <Kyrce> TimCole: so regarding the footnote issue. there was a call on Monday. as per HTML working group, holding off on footnote pending accessibility. Ancillary attributes and elements. We may want to look at that and the proposed area draft. Draft was published around April 20. This is current thinking.
15:11:28 <fjh> ack shepazu
15:12:24 <TimCole> raised potential footnote element in HTML during DPub IG call.
15:12:40 <TimCole> the sense is that adding this element to HTML is on hold (for various reasons)
15:13:22 <TimCole> one of them being that footnote is a role in WAI-ARIA and both DPub and HTML want to see what happens with that
15:13:40 <fjh> q?
15:13:46 <fjh> ack ivan
15:13:58 <Kyrce> Kyrce has joined #annotation
15:14:03 <TimCole> we may want to look at how this is proposed for implementation in the Digital Publishing WAI-ARIA Module April 20 draft
15:14:22 <azaroth> q+ to ask about ideas on the way forward
15:14:50 <fjh> ivan: fundamental  discussions between formatting & prototocols wg and digital publishing community
15:14:50 <Kyrce> Ivan: referring back to the ARIA reference. Discussion around this. Cannot say when document will move on and how. No technical details here at the moment. We should not rely on it for this working group.
15:14:58 <fjh> ack azaroth
15:14:58 <Zakim> azaroth, you wanted to ask about ideas on the way forward
15:15:09 <shepazu> q+
15:15:36 <ivan> q+
15:15:40 <Kyrce> Azaroth: Ways forward with HTML based for innovations. Should we try to work with the ARIA group and get a role attribute value defined rather than going up to HTML level. or microformats or what
15:15:41 <paoloC> q+
15:15:48 <ivan> ack ivan
15:15:50 <shepazu> q- later
15:16:06 <dauwhe> Hixie on footnotes in HTML: https://lists.w3.org/Archives/Public/public-whatwg-archive/2008Apr/0198.html
15:16:50 <Kyrce> Ivan: So does come back to the discussion we had with publishing community. The publishing community has had the notion of structural semantics. They need a way to implement. That's something that community needs. Close to a hundred different notions for the educational market
15:18:01 <azaroth> q+ to ask about accessibility of annotations in aria
15:18:23 <Kyrce> Ivan: The current work roles to use the ARIA role…. should role attribute only be used for accessibility? or for something larger (eg structurual semantics). If we don't use it then they have to define something new. If this happens, the notions that the digital publishing groups may work for these as well as Rob said. But I have no idea what direction they will take. We should wait.
15:18:48 <Kyrce> Ivan: Driven by accessibility not by browser vendors exclusively. All together.
15:18:53 <fjh> q?
15:18:57 <fjh> ack paoloC
15:19:11 <paoloC> http://www.w3.org/community/openannotation/wiki/RDFa
15:20:20 <Kyrce> paoloC: I don't know about accessibility. We have been experimenting with RDFa. It's not easy. It's a bit ugly at times. Worked with Ivan. Not knowing what is going on in the next six months with other groups, we should keep on top of RDFa and the microdata—and how it can be formalized. Also a backup no matter what happens in other groups. Why not have this also?
15:20:25 <fjh> ack shepazu
15:20:25 <azaroth> +1 to Paolo ; remaining informed and keeping options open is good
15:20:47 <shepazu> suggest concrete ways in which <note> would differ from <aside>, describe functional mechanisms rather than just markup (such as accessibility and navigation), review all decisions about aside and footnotes, make sure to coordinate with WAI and with CSS WG about rendering
15:20:51 <fjh> +1 to paolo
15:22:13 <fjh> rrsagent, generate minutes
15:22:13 <RRSAgent> I have made the request to generate http://www.w3.org/2015/04/29-annotation-minutes.html fjh
15:23:08 <Kyrce> Kyrce has joined #annotation
15:23:08 <fjh> q?
15:23:15 <fjh> ack azaroth
15:23:15 <Zakim> azaroth, you wanted to ask about accessibility of annotations in aria
15:24:04 <Kyrce> azaroth: Ivan i wanted to ask about the accessibility issue. Client displays annotations in the sidebar. How does a screen reader handle this?
15:24:39 <fjh> i/so regarding the footnote issue/Topic: Footnote Markup
15:25:56 <Kyrce> Ivan: Very similar to the other cases that we have right now in pub and accessibility group. I think the answer is: similar to HTML. Requirements can be handled by ARIA. Introducing a separate value should not be allowed. From accessibility POV there is no difference. Fundamental questions about the role of the attribute. Is it just for accessiiblity? or is it for other kind of  "semantics" There are two different views.
15:26:25 <shepazu> q+
15:26:32 <fjh> q+
15:26:39 <Kyrce> Ivan: ARIA role as a much more general feature for accessibility for adding semantics to HTML code. People use classes for, which can clash.
15:26:44 <fjh> ack shepazu
15:26:47 <fjh> q-
15:26:48 <Kyrce> I"m not sure of the direction.
15:27:03 <fjh> q+
15:27:34 <fjh> ack fjh
15:27:37 <Kyrce> Role is not special behavior. Role as a signal to user agents, usually screen readers that they should pay attention, not to do something specific. Role is not the way to go for behavior.
15:28:20 <tbdinesh> +1 to shepazu (although annotator role might make sense)
15:28:21 <Kyrce> fjh: markup should be specific to navigation. Can you explain what you meant by being able to "act"
15:30:18 <Kyrce> ???: obvious example is hyperlink. nav element doesn't do anything just says that this is navigation. Similarly section, article. Details does something. a couple of different types of behavior. examples: wikipedia. when you mouseover a footnote, it pops up a tooltip.
15:30:22 <fjh> q+
15:30:36 <azaroth> s/???/shepazu/
15:30:49 <naod> naod has joined #annotation
15:31:00 <Kyrce> shepazu: one footnote and three references to that footnote. If you navigate from the second reference. it has a state and navigates back.
15:32:56 <paoloC> q?
15:33:03 <paoloC> q+
15:33:05 <Kyrce> shepazu: note element: if you have referenced a news article (A). I write a blog post about it (B). Block quote from article A and talk in context about it in blob B. Another person comes and wants to talk about it in C. It would be powerful if the reference can be linked to both article A and to the blog B. More unification, less fracturing.
15:33:45 <Kyrce> shepazu: make that blockquote an annotation. user agent could store it as both.
15:34:27 <Kyrce> shepazu: sounds abstract but is a powerful feature that is different than HTML. Must be worked on before it's truly compelling.
15:34:29 <fjh> ack fjh
15:34:49 <fjh> ack paoloC
15:35:21 <Kyrce> fjh: very helpful. Suggested that footnotes are useful
15:35:35 <fjh> s/useful/useful and dynamic results
15:35:39 <Kyrce> paoloC: mixing up a lot of different concerns. makes argument abstract. I heard a lot of different things and applications. All different topics and complicated.
15:35:53 <fjh> agree with paolo, we need to review and focus discussion subsequently
15:36:37 <Kyrce> shepazu: for keeping scope. stick with first two examples - navigation to and from a footnote; rendering of footnote in CSS.
15:36:50 <fjh> q?
15:37:16 <Kyrce> shepazu: an aside is unstructured. it's whatever you want. A footnote or note, as an annotation, has some structural pieces. maybe that's how to present it.
15:37:29 <paoloC> q+
15:37:38 <fjh> ack paoloC
15:37:40 <Kyrce> fjh: think about it and review it and focus the discussion. Because as paoloC said, I'm also confused.
15:38:41 <Kyrce> paoloC: specify what is the model part and what is the behavior part, no matter what methodology we want to adopt. good to clarify given what we want to achieve what are the different parts that we would want to define.
15:38:58 <Jacob_> +1 to Paolo
15:38:59 <Kyrce> Ivan: I haven't talked to Mike so I do not know what he expects.
15:39:14 <Kyrce> Ivan: I don't think I can do this. It's not clear enough to me.
15:39:23 <Kyrce> fjh: share on list. Think about what has been said.
15:39:39 <shepazu> q+
15:39:42 <fjh> Topic: Update I Annotate and Hack Days
15:39:44 <fjh> ack shepazu
15:40:13 <fjh> s/Update//
15:40:24 <dwhly> q+
15:40:26 <Kyrce> shepazu: a lot of really great demos during the hack days. Dinesh showed a lot of the cool stuff he's been working on.
15:40:36 <Kyrce> shepazu: i found the demos and the variety interesting.
15:40:39 <fjh> ack dauwhe
15:40:47 <azaroth> ack dwhly
15:42:04 <Kyrce> dauwhe: thanks to all who came to either or both events. No real updates. We will be sending out a post-workshop summary today. The key is a survey which is long overdue. Please help by filling it out. We want to try to understand how to evolve the design to other formats or even more traditional formats. Lots of anecdotal feedback.
15:42:18 <dauwhe> s/dauwhe/dwhly/
15:42:33 <tbdinesh> +1 thanks dwhly
15:42:35 <fjh> Topic: Annotation Sets
15:43:21 <fjh> much thanks to dwhyl and hypothes.is for I Annotate, excellent hosting for Web Annotation F2F
15:43:37 <Kyrce> azaroth: Came up under protocol conversation. If an annotation contains other annotations how does that work with search, etc. We do not have any support from the use case or modeling level.
15:43:48 <fjh> rrsagent, generate minutes
15:43:48 <RRSAgent> I have made the request to generate http://www.w3.org/2015/04/29-annotation-minutes.html fjh
15:44:35 <fjh_> fjh_ has joined #annotation
15:44:41 <paoloC> q+
15:45:09 <shepazu> q+
15:45:10 <Kyrce> azaroth: Strong desire to have the capability to create a set or to add to a set. Focus on gathering ideas and use cases and requirements for this topic. Introduce some use cases or ideas now. How might you use lists of annotations? Brainstorm now; modeling in future call.
15:45:15 <azaroth> ack paoloC
15:45:26 <Jacob_> This seems more like a case for collections and a collection-specific model than something that needs to be handled specifically inside of the annotation model...
15:45:29 <azaroth> q+ to add EPUB UC
15:46:12 <shepazu> q- later
15:47:39 <Kyrce> Kyrce has joined #annotation
15:47:59 <RayD> Question: what's the difference between set and container?
15:48:00 <Kyrce> Kyrce has joined #annotation
15:48:03 <fjh> zakim, who is here?
15:48:03 <Zakim> On the phone I see azaroth, TimCole, fjh, Matt_Haas, Ivan, tbdinesh, dauwhe, Kyrce, paoloC, Doug_Schepers, RayD, bjdmeest, dwhly, +1.434.971.aaee, stain
15:48:07 <Zakim> On IRC I see Kyrce, naod, davis_salisbury, RayD, bjdmeest, Matt_Haas, tbdinesh, paoloC, Jacob_, TimCole, Janina, azaroth, fjh, Zakim, RRSAgent, dauwhe, ivan, shepazu, JakeHart,
15:48:07 <Zakim> ... nickstenn, rhiaro, csillag, oshepherd, bret, ujvari_, dwhly, bigbluehat, stain, judell_, Mitar, KevinMarks, trackbot
15:48:25 <Kyrce> paoloC: I repeat my use cases from f2f: We use them. Slice and Dice according to criteria. Access restriction and tasks. People read documents with specific goals in mind, particular compound, etc.
15:48:38 <Kyrce> paoloC: They annotate these documents and pull them and create a report. They read the same documents with different goals. Don't want to mix up annotations for different goals. Different sets according to tasks. They can also be access controlled, share with one person, group, multiple people. !. task oriented; 2. restricted. many requests to have same annotation in multiple sets. This causes problems.
15:49:17 <Kyrce> paoloC: minimum amount of properties or data attached. If I want to be really structured, attatch structured data as well.
15:49:25 <azaroth> q?
15:49:28 <Kyrce> paoloC: name title description should be enough.
15:49:38 <Jacob_> This feels out-of-scope.
15:49:43 <Kyrce> paoloC: containers seems a little bit generic and not very qualified. Not sure if it matters.
15:49:43 <RayD> thanks!
15:49:45 <Jacob_> This problem is not specific to annotations
15:50:25 <Kyrce> azaroth: difference between annotation sets and containers. Membership vs. identity issues.
15:50:40 <stain> q+ to relate annotation sets to ORE and researchobject.org
15:51:08 <paoloC> :) I would probably exclude the same track multiple times in the same playlist from the metaphor
15:51:08 <Kyrce> azaroth: same track multiple times, or tracks from different albums in same playlists, or you can have the same tracks in different playlists. Creation different than playlists.
15:51:22 <ivan> ack azaroth
15:51:22 <Zakim> azaroth, you wanted to add EPUB UC
15:52:22 <Kyrce> azaroth: We can only answer out of scope when we look at the use cases. Different methods of describing sets we can treat it as out of scope. With search, we are going to end up with lists of annotation in some format. So it would be in scope for the working group
15:53:44 <Kyrce> azaroth: to add a use case; in the work that we did with the idpf to define annotations for ePub. There was a need for annotations for individual epubs so that you could distribute them and have them show up on your reader. Third-party annotations for sale or for free to be added. Like: author notes, teacher notes, cliff notes, summaries, etc. etc.
15:54:16 <Kyrce> azaroth: without sets, you would have to distribute each annotation (and charge for each) individually.
15:54:16 <azaroth> q?
15:54:22 <azaroth> ack shepazu
15:56:06 <Kyrce> shepazu: use case and solution from f2f:  when asked, shepazu said no. he felt that chained annotations satisfied their use case. See the use case for sets in the protocol that paoloC referred to. Not sure if it's part of the data model. Or even if that is what is being suggested.
15:56:10 <paoloC> q+
15:56:43 <Kyrce> azaroth: no that is what we are talking about. That there should be a construct for sets of annotations in the data model. Readers don't need to implement multiple ways of grouping annotations.
15:56:44 <stain> http://www.researchobject.org/
15:56:45 <azaroth> ack stain
15:56:45 <Zakim> stain, you wanted to relate annotation sets to ORE and researchobject.org
15:58:13 <Kyrce> stain: when we were developing the research object model (group of docs, presentations with annotations). Strong need to have a unit for a group of annotations because they have a purpose. Who made this collection? Who is talking about this resource or set of resources?
15:58:34 <azaroth> +1 to Stain
15:58:39 <Jacob_> The thing is, the set model is not dependent upon the contents of the set all being annotations or even if any of them are annotations at all. We might look around and see if there are not, in fact, models that already do this work. ORE, EDM, Schema all come to mind.
15:58:53 <Kyrce> stain: you have the containers but you don't have a way of accessing it without the protocol. It should be lightweight. The aggregation itself has a value. you can give it a title, a purpose.
15:58:53 <azaroth> q?
15:58:56 <azaroth> ack paoloC
15:59:02 <davis_salisbury> +1 to stain
15:59:05 <stain> we also used OA annotations in our Research Object bundle: https://w3id.org/bundle/#manifest-annotations
15:59:51 <Zakim> - +1.434.971.aaee
15:59:57 <Kyrce> paoloC: I've been struggling with Annotation sets for a long time. Some clients know how to handle annotation sets. Some don't. I think having a protocol and model, if lightweight would help implementations.
16:00:19 <tantek> tantek has joined #annotation
16:00:39 <Kyrce> paoloC: it's complicated and you don't know what the client understands. In the case of sets it becomes complicated. Hard to implement graceful degradation.
16:01:02 <Zakim> -dauwhe
16:01:16 <Zakim> -dwhly
16:01:30 <Zakim> -RayD
16:01:32 <Zakim> -stain
16:01:35 <Zakim> -Ivan
16:01:36 <Zakim> -paoloC
16:01:37 <Zakim> -azaroth
16:01:37 <fjh> thank you Kyrce for scribing, thanks
16:01:38 <Zakim> -TimCole
16:01:40 <Zakim> -fjh
16:01:40 <Zakim> -bjdmeest
16:01:42 <Zakim> -Kyrce
16:01:44 <fjh> thanks everyone
16:01:45 <ivan> rrsagent, draft minutes
16:01:45 <RRSAgent> I have made the request to generate http://www.w3.org/2015/04/29-annotation-minutes.html ivan
16:01:53 <ivan> zakim, who is here?
16:01:54 <Zakim> -Matt_Haas
16:01:54 <Zakim> On the phone I see tbdinesh, Doug_Schepers
16:01:55 <Zakim> On IRC I see tantek, Kyrce, suskudarli, davis_salisbury, RayD, tbdinesh, TimCole, Janina, azaroth, fjh, Zakim, RRSAgent, dauwhe, ivan, shepazu, JakeHart, nickstenn, rhiaro,
16:01:55 <Zakim> ... csillag, oshepherd, bret, ujvari_, dwhly, bigbluehat, stain, judell_, Mitar, KevinMarks, trackbot
16:02:03 <Zakim> -tbdinesh
16:02:12 <ivan> zakim, who is here?
16:02:13 <Zakim> On the phone I see Doug_Schepers
16:02:14 <Zakim> On IRC I see tantek, Kyrce, suskudarli, davis_salisbury, RayD, tbdinesh, TimCole, azaroth, fjh, Zakim, RRSAgent, dauwhe, ivan, shepazu, JakeHart, nickstenn, rhiaro, csillag,
16:02:14 <Zakim> ... oshepherd, bret, ujvari_, dwhly, bigbluehat, stain, judell_, Mitar, KevinMarks, trackbot
16:02:25 <ivan> trackbot, end telcon
16:02:25 <trackbot> Zakim, list attendees
16:02:25 <Zakim> As of this point the attendees have been azaroth, TimCole, fjh, Matt_Haas, Ivan, dauwhe, +1.201.236.aaaa, Kyrce, +1.617.588.aabb, Doug_Schepers, +1.202.707.aacc, bjdmeest, paoloC,
16:02:29 <Zakim> ... RayD, +1.650.274.aadd, tbdinesh, dwhly, +1.434.971.aaee, stain
16:02:33 <trackbot> RRSAgent, please draft minutes
16:02:33 <RRSAgent> I have made the request to generate http://www.w3.org/2015/04/29-annotation-minutes.html trackbot
16:02:34 <trackbot> RRSAgent, bye
16:02:34 <RRSAgent> I see no action items
16:02:36 <Zakim> -Doug_Schepers