[![W3C][1]][2] # Web Annotation Working Group Teleconference ## 06 May 2015 See also: [IRC log][3] ## Attendees Present Frederick_Hirsch, Matt_Haas, Benjamin_Young, Miguel_, Aragón, Tim_Cole, Janina_Sarol, Kristof_Csillag, Randall_Leeds, Davis_Salsbury, Takeshi_Kanai Regrets Rob_Sanderson, Bill_Kasdorf, Jacob_Jett, Dave_Cramer, Ben_De_Meester, Ray_Denenberg, TB_Dinesh Chair Frederick_Hirsch Scribe TimCole ## Contents * [Topics][4] 1. [Agenda Review, Scribe Selection, Announcements][5] 2. [Minutes Approval][6] 3. [Rangefinnder API][7] 4. [WebEx][8] 5. [Adjourn][9] * [Summary of Action Items][10] * * * Date: 06 May 2015 Agenda: [https://lists.w3.org/Archives/Public/public- annotation/2015May/0010.html][11] ### Agenda Review, Scribe Selection, Announcements ScribeNick: TimCole Request for Search/Query use cases, [https://lists.w3.org/Archives/Public/public-annotation/2015May/0008.html][12] Miguel joined WG, [https://lists.w3.org/Archives/Public/public- annotation/2015May/0009.html][13] (I'm just lurking on IRC today) Plans to switch from zakim to webex for calling in, next week should be message on list in advance of next week’s call fjh: Call on 20th will be cancelled. ... we will have a call next week. ### Minutes Approval (Note: Webex' Java client is not known to work too well on 64-bit Linux) fjh: can we approve the f2f minutes? proposed RESOLUTION: F2F minutes from 22 April 2015 approved, see [http://www.w3.org/2015/04/22-annotation-minutes.html][14] proposed RESOLUTION: Teleconference minutes from 29 April 2015 approved, see [http://www.w3.org/2015/04/29-annotation-minutes.html][15] **RESOLUTION: F2F minutes from 22 April 2015 approved, see [http://www.w3.org/2015/04/22-annotation-minutes.html][14]** and **RESOLUTION: Teleconference minutes from 29 April 2015 approved, see [http://www.w3.org/2015/04/29-annotation-minutes.html][15]** fjh: Doug will briefly introduce the new draft re RangeFinder API ### Rangefinnder API [https://specs.webplatform.org/rangefinder/w3c/master/][16] shepazu: will send instructions for annotating the new draft [http://w3c.github.io/rangefinder/][17] shepazu: updated version is currently at temporary location, will be in proper location this week. ... annotating is relatively straightforward fjh: on web platform it is not obvious how to annotate shepazu: will fix this. obvious with icon on github.io draft shepazu: this is a radically simplified version of what was posted previously ... examples have not been updated for syntax, but the ideas are still illustrated in the examples ... there are now 2 interfaces: rangefinder and edit-distance ... the latter is just a helper interface, though it can be used stand-alone. ... the rangefinder itself: you still set certain parameters ... you can say you are willing to accept an edit distance of X ... if you don't set an edit distance than it will be treated as a string literal ... you can set case-folding, unicode-folding, page-folding, etc. ... most modern specs use algorithms; reduces questions, ambiguity ... but they are not the most user friendly to read ... so this draft includes an explanation of the algorithms used ... this is helpful for laying out the ideas of the algorithm as we go (i.e., to help write the algorithm) ... two other items with this spec: ... 1 - scope, which says I want to limit the search to a particluar part of a document ... scope and start range are no longer define various selectors but relay on Range from DOM4, which need to be manually created ... should be less work to implement this approach ... removed the custom and blocking / non-blocking stuff ... changed the search method. Once you've filled in the parameters you say search. ... a promise is returned, which is like a call-back ... with chaining this should allow someone to introduce their own search algorithm ... promise is less work than a simple call back ... still lets you do strict searching and fuzzy search ... spec calls for consistency in how the results of the search are presented -- how search is done by the browser behind this is not specified. fjh: should we defer discussion of the issues now or defer. shepazu: probably should defer. ... if anyone wants to talk about the issues in the current draft, please annotate or talk on list fjh: ### WebEx fjh: currently we use Zakim. You call in. ... voice portion of call will change. ... for WebEx you will call differently, but we will continue to use IRC as now ... we will not use other features of WebEx except for the voice -- so we will not use WebEx chat, whiteboard, etc. ... we want to try this sooner rather than later to identify any issues. ... you will be able to call up to 10 minutes early. shepazu: we have until June to switchover, but by starting earlier we can discover any issues. fjh: the first time you use it WebEx may need to install software, so give yourself some lead time. ... we'll adjourn now. Talk next week. Week after is cancelled. ### Adjourn ## Summary of Action Items [End of minutes] * * * Minutes formatted by David Booth's [scribe.perl][18] version 1.135 ([CVS log][19]) $Date: 2009-03-02 03:52:20 $ [1]: http://www.w3.org/Icons/w3c_home [2]: http://www.w3.org/ [3]: http://www.w3.org/2015/05/06-annotation-irc [4]: #agenda [5]: #item01 [6]: #item02 [7]: #item03 [8]: #item04 [9]: #item05 [10]: #ActionSummary [11]: https://lists.w3.org/Archives/Public/public- annotation/2015May/0010.html [12]: https://lists.w3.org/Archives/Public/public- annotation/2015May/0008.html [13]: https://lists.w3.org/Archives/Public/public- annotation/2015May/0009.html [14]: http://www.w3.org/2015/04/22-annotation-minutes.html [15]: http://www.w3.org/2015/04/29-annotation-minutes.html [16]: https://specs.webplatform.org/rangefinder/w3c/master/ [17]: http://w3c.github.io/rangefinder/ [18]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [19]: http://dev.w3.org/cvsweb/2002/scribe/