14:29:12 RRSAgent has joined #annotation 14:29:12 logging to http://www.w3.org/2014/09/24-annotation-irc 14:29:14 RRSAgent, make logs public 14:29:16 Zakim, this will be 2666 14:29:17 Meeting: Web Annotation Working Group Teleconference 14:29:17 Date: 24 September 2014 14:29:18 Zakim has joined #annotation 14:49:08 Agenda: http://lists.w3.org/Archives/Public/public-annotation/2014Sep/0040.html 14:49:23 fjh has changed the topic to: zakim code 3627 +1.617.761.6200 agenda http://lists.w3.org/Archives/Public/public-annotation/2014Sep/0040.html 14:49:57 Chair: Frederick_Hirsch, Rob_Sanderson 14:50:08 Present+ Frederick_Hirsch, Rob_Sanderson 14:50:46 Regrets+ Doug_Schepers 14:51:20 Regrets+ tripu 14:52:51 fjh: http://www.w3.org/People/Antonio/ 14:53:00 cheers 14:53:08 s/cheers// 14:53:17 s/fjh: http.*/ 14:53:23 s/fjh: http.*// 14:53:39 azaroth has joined #annotation 14:53:49 Morning folks! 14:53:57 (or at least it is for me) 14:53:59 Regrets- tripu 14:54:01 Regrets+ Antonio_Olmo_Titos(tripu) 14:54:22 Hi Frederick :) 14:55:57 zakim, code? 14:55:57 sorry, fjh, I don't know what conference this is 14:56:28 zakim, this is annotation 14:56:28 sorry, fjh, I do not see a conference named 'annotation' in progress or scheduled at this time 14:57:10 zakim, this is DPUB_(ANNO) 14:57:10 azaroth, I see DPUB_(ANNO)11:00AM in the schedule but not yet started. Perhaps you mean "this will be DPUB_(ANNO)". 14:57:10 zakim, this is anno 14:57:12 fjh, I see DPUB_(ANNO)11:00AM in the schedule but not yet started. Perhaps you mean "this will be anno". 14:57:24 zakim, code? 14:57:24 sorry, fjh, I don't know what conference this is 14:57:29 zakim, this will be DPUB_(ANNO) 14:57:29 ok, azaroth; I see DPUB_(ANNO)11:00AM scheduled to start in 3 minutes 14:57:35 zakim, this will be 2666 14:57:35 ok, fjh; I see DPUB_(ANNO)11:00AM scheduled to start in 3 minutes 14:57:43 zakim, code? 14:57:43 the conference code is 2666 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), fjh 14:57:56 TimCole has joined #annotation 14:58:12 DPUB_(ANNO)11:00AM has now started 14:58:19 +[IPcaller] 14:58:20 zakim, ipcaller is me 14:58:21 +fjh; got it 14:58:31 +azaroth 14:59:03 zakim, who is here 14:59:03 azaroth, you need to end that query with '?' 14:59:05 zakim, who is here? 14:59:05 On the phone I see fjh, azaroth 14:59:07 On IRC I see TimCole, azaroth, Zakim, RRSAgent, dauwhe, fjh, KevinMarks, ivan, Mitar, bigbluehat, JakeHart, dwhly, tripu, nickstenn, stain, MarkS, trackbot, renoirb 14:59:17 Am I supposed to record this meeting? I have the software at hand. 14:59:27 +TimCole 14:59:27 matt has joined #annotation 14:59:32 JakeHart: that would be great if possible 14:59:38 Cool. Will do. 14:59:40 Kyrce has joined #annotation 14:59:57 +dwhly 15:00:02 +dauwhe 15:00:09 +Matt_Haas 15:00:16 Jacob has joined #annotation 15:00:26 g'morning lord zakim 15:00:28 +Kyrce 15:00:52 fjh has changed the topic to: 2666 agenda http://lists.w3.org/Archives/Public/public-annotation/2014Sep/0040.html 15:00:53 + +1.617.768.aaaa 15:00:59 fjh has changed the topic to: code 2666 agenda http://lists.w3.org/Archives/Public/public-annotation/2014Sep/0040.html 15:01:04 matt is me +Matt_Haas (Is this statement the corrected protocol?) 15:01:49 rayd has joined #annotation 15:01:49 zakim, dial ivan-aix 15:01:49 ok, ivan; the call is being made 15:01:50 +Ivan 15:01:51 zakim, who is here? 15:01:51 On the phone I see fjh, azaroth, TimCole, dwhly, dauwhe, Matt_Haas, Kyrce, +1.617.768.aaaa, Ivan (muted) 15:01:53 On IRC I see rayd, Jacob, Kyrce, matt, TimCole, azaroth, Zakim, RRSAgent, dauwhe, fjh, KevinMarks, ivan, Mitar, bigbluehat, JakeHart, dwhly, tripu, nickstenn, stain, MarkS, 15:01:53 ... trackbot, renoirb 15:02:03 bjdmeest has joined #annotation 15:02:07 zakim, aaaa is Matt_Haas 15:02:07 +Matt_Haas; got it 15:02:14 TimC has joined #annotation 15:02:17 +[IPcaller] 15:02:31 BillKasdorf has joined #annotation 15:02:34 zakim, Matt_Haas is unknown 15:02:34 +unknown; got it 15:02:39 zakim, who is here? 15:02:39 On the phone I see fjh, azaroth, TimCole, dwhly, dauwhe, unknown, Kyrce, Matt_Haas.a, Ivan, [IPcaller] 15:02:41 On IRC I see BillKasdorf, TimC, bjdmeest, rayd, Jacob, Kyrce, matt, TimCole, azaroth, Zakim, RRSAgent, dauwhe, fjh, KevinMarks, ivan, Mitar, bigbluehat, JakeHart, dwhly, tripu, 15:02:41 ... nickstenn, stain, MarkS, trackbot, renoirb 15:02:49 +[IPcaller.a] 15:03:08 +[Ugent] 15:03:12 +Bill_Kasdorf 15:03:14 +rayd 15:03:53 zakim, Ugent is me 15:03:53 +bjdmeest; got it 15:03:56 Present +JakeHart 15:03:59 Present+ Bill_Kasdorf 15:04:09 zakim, mute me 15:04:10 bjdmeest should now be muted 15:04:16 present+ Ray Denenberg 15:04:25 Present+ Rob Sanderson 15:04:37 Zakim, IPcaller.a is me 15:04:37 +nickstenn; got it 15:04:41 comme ca? 15:04:49 :) 15:04:53 Present+ Tim_Cole 15:04:57 present+ nickstenn 15:05:04 Present+ bjdmeest 15:05:35 https://www.w3.org/annotation/wiki/Scribe_List 15:05:38 MGU has joined #annotation 15:05:54 Any volunteers to scribe? 15:05:55 Topic: Administrative, Scribe, Announcements and Minutes Approval 15:05:58 i'm happy to scribe, but i've never done it before 15:05:59 Or shall we pick someone? 15:06:08 zakim, pick a victim 15:06:08 Not knowing who is chairing or who scribed recently, I propose TimCole 15:06:17 present +Matt_Haas 15:06:21 paoloC has joined #annotation 15:06:31 zakim, [IPcaller] is paoloC 15:06:31 +paoloC; got it 15:06:34 scribenick: TimCole 15:06:41 present+ Paolo_Ciccarese 15:06:47 zakim, who is here? 15:06:47 On the phone I see fjh, azaroth, TimCole, dwhly, dauwhe, unknown, Kyrce, Matt_Haas.a, Ivan, paoloC, nickstenn, bjdmeest (muted), Bill_Kasdorf, rayd 15:06:49 On IRC I see paoloC, MGU, BillKasdorf, TimC, bjdmeest, rayd, Jacob, Kyrce, Matt_Haas, TimCole, azaroth, Zakim, RRSAgent, dauwhe, fjh, KevinMarks, ivan, Mitar, bigbluehat, JakeHart, 15:06:49 ... dwhly, tripu, nickstenn, stain, MarkS, trackbot, renoirb 15:07:02 renoirb has left #annotation 15:07:23 fjh: Make your arrangements for TPAC soon. 15:07:24 marriot not full monday night 15:08:19 + +1.617.768.aabb 15:08:34 zakim, aabb is TimC 15:08:35 +TimC; got it 15:08:48 Topic: approve minutes 15:09:36 draft RESOLUTION: Minutes from last week approved 15:09:41 -paoloC 15:09:54 RESOLUTION: Minutes from last week 17 Sept are approved 15:10:07 Topic: Charter review 15:10:21 see http://www.w3.org/annotation/charter/ 15:11:01 fjh: Charter will run 2 years 15:11:08 +[IPcaller] 15:11:12 ... iimportant to note that the Charter is public 15:11:33 s/iimportant/important/ 15:11:36 ... members and non-members do have different permissions, but we want to engage as many people as possible 15:11:46 ... it's really simple, we are working in public 15:12:30 ... we can still be respectful of people wanting to maintain details of implementation private 15:12:51 ... for TPAC we will meet all day Tuesday 15:13:07 ... value of annotation discussed in charter and are self-evident 15:13:29 ... we are targeting particularly browser and reading systems 15:13:43 ... need to cognizant of testing, interop, etc. 15:14:20 ... first 2 deliverables build on work of OA CG 15:14:36 ... short timeline, but OA CG gives a good strong 15:14:58 azaroth: Let's summarize briefly first, then go back through to ascertain interest 15:15:36 fjh: benefits sometimes to working separately, sometimes together 15:16:07 ... first 2 deliverables --abstract model and serialization 15:16:24 ... then HTTP API and Client Side API 15:16:42 ... finally the robust link anchoring 15:17:12 ... the last will be done in collaboration with Web Apps WG -- so probably a Task Force 15:17:42 ... success criteria: we will have 2 'real' implementations (as is typical) 15:18:05 ... implementations must be independent -- different underlying code libraries. 15:18:33 ... we need to be clear about what is an 'implementation' 15:19:01 ... for browser we may not expect a fully deployed in the browser 15:19:10 ... out of scope is user interface 15:19:41 ... if it makes sense we can combine documentation to cover the deliverables 15:19:53 ... the charter lays out a timeline 15:20:06 ... for example a working draft of the model by December 15:20:23 ... working drafts should be complete, but don't have to be perfect 15:20:45 ... in February next 4 deliverables, an aggressive timeline. 15:21:03 q+ 15:21:06 q- 15:21:16 present+ Paolo_Ciccarese 15:21:47 ... by the end of next year we should have specs that are stable and in good shape 15:22:02 ... implementations earlier are better since they inform us as we go along 15:22:30 ... timeline suggests a possible f2f in February 15:22:52 +??P10 15:23:03 Ivan: we put this into the charter, but f2f are more advice rather than requirements 15:23:31 ... will be up to us to decide when we need f2f, should make decision later 15:23:54 ... there is a rule that f2f date must be agreed in the group at least 8 weeks ahead of date for f2f 15:24:35 -??P10 15:24:38 fjh: Dependencies and liaisons 15:24:55 +??P10 15:25:01 ... we have a large number of liaisons, we may be able to take advantage of TPAC to start these 15:25:17 -??P10 15:25:23 ... we also need to liaison with closely with EPub 15:25:48 s/EPub/DPUB IG/ 15:25:48 Ivan: we have good overlap with DPub IG which has close relations with EPub 15:26:03 fjh: not clear how best to liaison with the OA CG 15:26:21 ... when should we ask for discussion on the CG? 15:26:37 ... can we clear about what we need to discuss there rather than here 15:27:14 azaroth: we should relay information to CG as we can, but for discussion about work the WG is doing, best to do that on the WG lists 15:27:48 Paolo: agree. CG is good for acquiring implementation feedback, community clustering, use cases, CG a good venue for that 15:28:01 ... leave the discussion about deliverables to the WG lists 15:28:09 +1 to Rob & Paolo's ideas 15:28:09 +1 to paoloC 15:28:37 fjh: participation, active is good, not active doesn't help 15:28:58 ... we have a home page, but wiki is becoming important. 15:29:23 +??P10 15:29:40 -??P10 15:29:41 ... if we do a resolution, it is provisional for 5 days. this gives people who couldn't make the call time to comment 15:30:12 ... this approach obviates the need for some of higher overhead, more formal mechanisms for consensus 15:30:37 azaroth: please give a +1 for consensus, +0 don't understand, etc. 15:31:06 fjh: we will first do informal agreement to make sure everyone understands 15:31:27 ... when we do bigger things, e.g., documents, we will do formal call for consensus 15:31:54 ... if we use +1 approach the more formal approvals will flow naturally. 15:32:27 ... not going into patent processes in detail, but please be aware of the terms and conditions 15:32:39 ... these matter, please look at offline and be sure you understand. 15:32:47 q? 15:33:58 azaroth: First deliverable is the Abstract Data Model, starting point is the OA CG model 15:34:20 ... there were some things that are mature and some things that need more work 15:34:39 +1 15:34:39 +??P10 15:34:40 +1 15:34:41 +1 15:34:42 +1 15:34:43 ... who is interested in abstract data model? 15:34:49 +1 15:34:50 +1 15:34:50 +1 15:34:52 +0 15:34:54 +0 15:34:55 +1 15:34:56 -??P10 15:35:00 +0 15:35:00 +0 15:35:02 +0 15:35:12 +0 15:35:35 azaroth: 2nd deliverable is a vocabulary for expressing the data model 15:35:37 +1 15:35:39 +1 15:35:39 +1 vocab 15:35:41 +1 15:35:43 +1 15:35:43 +1 15:35:44 +1 15:35:45 +1 15:35:47 +0 15:35:48 +0 15:35:49 +1 15:35:51 +1 15:35:56 +0 15:36:06 +1 15:36:32 azaroth: 3rd model is serialization. there are some obvious choices and some less obvious choices like how does this play with HTML5 15:36:40 +1 15:36:43 +0 15:36:43 +1 15:36:50 +1 15:36:50 +0 15:36:55 ... do we need a note element in HTML5, how does it work in RDFa 15:36:56 +1 15:37:03 +0 15:37:05 ... who is interested in serialization 15:37:07 +1 15:37:12 +0 15:37:12 +1 15:37:14 +1 15:37:18 +1 15:37:25 +1 serialization 15:37:34 azaroth: 4th topic is HTTP API 15:37:52 +1 15:37:57 +0 15:37:57 ... this about interaction between annotation clients and tools 15:37:58 +1 http api 15:38:01 +0 15:38:01 +0 15:38:02 +0 15:38:04 +0 15:38:05 +1 15:38:06 +0 15:38:09 +0 15:38:11 +0 15:38:11 +0 api 15:38:15 +1 15:38:21 +1 http api 15:38:43 azaroth: 5th topic is javascript / Client side API for browsers and reading systems to implement to make it easier to implement annotation client 15:38:47 +1 15:38:49 +1 :) 15:38:50 +0 15:38:51 +0 15:38:51 +1 15:38:53 +1 15:38:54 +0 15:38:54 +1 client side 15:38:56 +1 15:38:58 +0 15:39:09 +0 15:39:13 azaroth: I am +1 on everything. 15:39:14 +1 15:39:51 azaroth: Final topic is robust anchoring, how do we know that when future user comes to resource they still know where the annotation is anchored 15:39:52 +1 15:39:53 +1 15:39:54 +1 15:39:55 +0 15:39:57 +0 15:39:58 +1 anchoring 15:39:58 +0 15:40:00 +0 15:40:01 +0 15:40:02 ... HTML is first topic, others as time allows 15:40:04 +0 15:40:06 +0 15:40:07 +0 15:40:13 +1 15:40:25 +1 15:40:37 azaroth: Turning to implementations 15:41:01 +??P4 15:41:02 ... what is state of implementations you have or are developing 15:41:33 zakim, who is making noise? 15:41:39 -??P4 15:41:44 fjh, listening for 10 seconds I heard sound from the following: azaroth (66%), ??P4 (24%) 15:41:45 azaroth: these should demonstrate that features can be implemented (as opposed to exercises in futility) 15:42:03 ... can it be implemented independently by separate parties 15:42:11 q+ 15:42:20 q+ 15:42:31 q+ 15:42:43 ack paoloC 15:42:47 ack paoloC 15:42:48 ack paoloC 15:42:55 Annotopia 15:43:04 https://github.com/Annotopia 15:43:07 q+ 15:43:12 paoloC: at MGH we have been working in last 6 month on Annotopia -- open source OA annotation server 15:43:39 ... allows you to save and retrieve annotations, have a dashboard for information about the annotations, etc. 15:44:17 ... includes specalized annotations for biomedical use cases 15:44:33 ... works with HTML, etc. 15:44:46 ... Works with multiple clients 15:45:02 ... will also support the annotator js format 15:45:12 ... will also support text mining 15:45:14 two client implementations, not sure of names 15:45:33 Domeo and Utopia 15:45:45 paoloC: we will keep up with specs as developed by the WG 15:45:45 Domeo is from MGH/Harvard 15:45:51 Utopia is from Manchester 15:46:06 q? 15:46:09 fantastic 15:46:14 ack nickstenn 15:46:25 nickstenn: working on Annotator 15:46:45 ... while Annotator is easily mappable to OA data model 15:46:52 ... keen to make it more compatible 15:47:18 ... first by making a client side implementation of OA data model, this will require working through serialization 15:47:21 q+ 15:47:46 ... 2nd part is a server side implementation -- annotation storing, retrieving, etc. 15:48:09 ... very interested in Client Side implementation goes. 15:49:04 scribenick: azaroth 15:49:14 azaroth: will be extremely important for advancing client side implementations 15:49:14 ack TimCole 15:49:35 ack paoloC 15:49:47 paoloC: in our experience selectors are important for interoperability 15:50:29 TimCole: Not independent, using annotator codebase for our work on digitized book materials, both image and text 15:50:59 ... backend is from U Queensland, updated to work as backend for annotator, plus image plugins 15:51:29 ... use case is annotating scholarly materials, scholars of renaissance materials. Working in test at the moment. 15:51:30 nick notes summary - 1) Annotator client-side work, 2) Server-side implementation, 3) Polyfill for whatever the DOM APIs end up looking like 15:51:32 scribenick: TimCole 15:51:36 q? 15:51:39 ack azaroth 15:51:43 q+ 15:52:10 azaroth: Stanford is also very keen to work with others, have ongoing engineering work to build a LD back end for annotations 15:52:39 azaroth: interest in cultural heritage materials, born digital scholarly materials, etc. 15:53:04 ... want to make sure implementations are compatible, best of breed. 15:54:05 +[IPcaller.a] 15:54:06 fjh: question: are we using things from other places -- how independent? 15:54:39 aron_ has joined #annotation 15:54:50 Zakim: IPcaller.a is aron_ 15:54:52 TimCole: use plugins for extensibiilty, also forked annotator code 15:54:59 … to handle images differently 15:55:11 … implememtations overlap, makes maintenance a challenge 15:55:11 Zakim, IPcaller.a is aron_ 15:55:11 +aron_; got it 15:55:42 … not wholly independent on client side, server side is more shared 15:56:16 yes, Lorestore 15:56:51 azaroth: logistics of workflows before closing, discuss more on the mailing list 15:57:10 ivan: we have options at W3C for working collaboratively 15:57:37 ivan: CVS still available, newer is github 15:57:49 ... W3C also has a mercurial repository 15:58:04 ... I would propose we agree to work on github for all of our documents 15:58:14 +1 for github 15:58:23 +1 for github 15:58:24 I'm +1 to git, +0 for GitHub 15:58:24 +1 for github 15:58:32 +1 for github 15:58:41 ... if we use github, user accounts are not bound to W3C, so each member must communicate by email to ivan their github account 15:58:41 +1 for hg :) 15:58:43 ...and -INT_MAX for CVS 15:58:47 +1 for github 15:59:04 ... we set up main branch as gh_pages 15:59:06 -dauwhe 15:59:34 ivan: do we need to discuss or can we agree now? 15:59:41 question: is there a W3C backup of the GitHub repository? 16:00:01 RESOLUTION: WG use github for repository 16:00:14 ivan: will set up a github repository this week. 16:00:49 ivan: W3C has a tracker set up, advantage of tracker is bound to IRC 16:00:53 q+ 16:00:54 Agree with you nickstenn re: backup 16:01:10 ... this allows us to setup actions etc. via irc and email 16:01:29 ivan: the other possibility is to use github issue handling. 16:01:52 Apologies, I need to drop out for a different call 16:01:58 ivan: may need to discuss issue tracking on the email list this week 16:02:09 -azaroth 16:02:23 q? 16:02:26 ack fjh 16:02:27 nicksteen via fjh: what is risk of losing data on github 16:02:47 we should explore automating pull of github for w3c archive as backup mechanism 16:02:48 ivan: W3C is planning to capture periodically, but not in place yet 16:03:11 ... real risk, if we keep local archives up to date, is minimal. 16:04:07 -TimC 16:04:42 Topic: Adjorn 16:04:59 -rayd 16:05:00 -Matt_Haas.a 16:05:00 -fjh 16:05:01 -aron_ 16:05:03 -TimCole 16:05:04 -Bill_Kasdorf 16:05:05 -[IPcaller] 16:05:05 -nickstenn 16:05:06 rrsagent, draft minutes 16:05:06 I have made the request to generate http://www.w3.org/2014/09/24-annotation-minutes.html ivan 16:05:07 -bjdmeest 16:05:08 Kyrce has left #annotation 16:05:10 TimCole has left #annotation 16:05:14 -Ivan 16:05:15 -dwhly 16:05:31 MGU has left #annotation 16:06:04 -unknown 16:06:05 -Kyrce 16:06:41 zakim, who is here? 16:06:41 On the phone I see no one 16:06:43 On IRC I see paoloC, TimC, rayd, azaroth, Zakim, RRSAgent, dauwhe, fjh, KevinMarks, ivan, Mitar, bigbluehat, JakeHart, dwhly, tripu, nickstenn, stain, MarkS, trackbot 16:06:48 trackbot, end telcon 16:06:48 Zakim, list attendees 16:06:48 As of this point the attendees have been fjh, azaroth, TimCole, dwhly, dauwhe, Kyrce, +1.617.768.aaaa, Ivan, unknown, Bill_Kasdorf, rayd, bjdmeest, nickstenn, paoloC, 16:06:51 ... +1.617.768.aabb, TimC, [IPcaller], aron_ 16:06:56 RRSAgent, please draft minutes 16:06:56 I have made the request to generate http://www.w3.org/2014/09/24-annotation-minutes.html trackbot 16:06:57 RRSAgent, bye 16:06:57 I see no action items