14:30:07 RRSAgent has joined #annotation 14:30:07 logging to http://www.w3.org/2016/07/08-annotation-irc 14:30:09 RRSAgent, make logs public 14:30:09 Zakim has joined #annotation 14:30:11 Zakim, this will be 2666 14:30:11 ok, trackbot 14:30:12 Meeting: Web Annotation Working Group Teleconference 14:30:12 Date: 08 July 2016 14:30:35 Agenda: http://www.w3.org/mid/018401d1d884$d8134800$8839d800$@illinois.edu 14:52:53 tbdinesh has joined #annotation 14:54:39 azaroth has joined #annotation 14:55:06 TimCole has joined #annotation 14:57:44 uskudarli has joined #annotation 14:59:06 Regrets: Paolo Ciccarese 14:59:25 Janina_ has joined #annotation 14:59:31 Regrets: Frederick Hirsch 14:59:48 Regrets: Dan Whaley 15:00:04 Regrets+: Dan Whaley 15:00:30 Regrets+ Dan Whaley 15:00:33 Present+ Rob_Sanderson 15:00:42 Present+ Ivan 15:00:47 Regrets+ Frederick Hirsch 15:01:05 Regrets+ Paolo Ciccarese 15:01:28 Regrets+ Randall_Leeds 15:01:34 Jacob has joined #annotation 15:01:35 Present+ Benjamin_Young 15:01:39 Regrets+ Ben_De_Meester 15:01:43 Present+ Jacob_Jett 15:01:59 Regrets+ Shane_McCarron 15:02:20 Present+ TB_Dinesh 15:02:30 Regrets+ Randall Leeds 15:03:06 Regrets+ Ben De Meester 15:03:13 Present+ Tim_Cole 15:04:52 PROPOSED RESOLUTION: Minutes of the last WG call are approved: https://www.w3.org/2016/06/24-annotation-minutes.html 15:04:58 +1 15:05:02 +1 15:05:09 +1 15:05:11 scribenick: azaroth 15:05:22 RESOLUTION: Minutes of the last WG call are approved: https://www.w3.org/2016/06/24-annotation-minutes.html 15:05:36 Topic: CR Status 15:05:58 Ivan: We have two published specs, model and vocab, on Tuesday. Went out with no problems 15:06:07 takeshi has joined #annotation 15:06:34 ... Had a hiccough with the TAG issue that wasn't properly handled, but we got closure on Wednesday, and have everything to get it published 15:06:41 ... Have a reply this morning that the document is ready to go 15:06:52 ... So don't expect any problems and it will be published on Tuesday next week 15:06:53 I added a countdown for 7/12 12:00am (#5867) 15:07:16 ... Editors and Chairs will be on the hook for any issues that might come up, as I'll be on vacation 15:07:40 ... Have some editorial feedback (Rob and Benjamin) already, but will deal with it after tuesday 15:07:49 TimCole: Any further comments? 15:08:10 Rob: Hooray! :) 15:08:20 Tim, Ivan: A very important milestone :) 15:08:22 Topic: Testing 15:08:58 TimCole: There was some notes from Shane, that he has closed his pull request 15:09:14 Benjamin: He had been asked to squash the commit history into a single commit 15:09:45 ... He was going to try and squash down to only the important commits, and rename to be more consistent 15:10:11 ... The reason to do it is to not have the master list expanded by many new commit messages that overwhelm other messages in the history 15:10:32 ... Shane now cleaning up his local history and will send a new PR 15:10:44 ... Hopefully doesn't restart the process, but it is blocked on Shane's work 15:11:09 TimCole: Trying to get local version up, ran into some issues. Also confused about spec-ops and w3c test environments 15:11:13 ... Are they the same thing? 15:11:31 bigbluehat: He has write access to spec-ops, w3c are the gatekeepers with the PR requirements 15:11:40 ... If not added there, then not part of the W3C test suite 15:11:49 TimCole: Relationship to our own annotation-test repo? 15:12:02 bigbluehat: Canonical source of where we keep the schema and tests, regardless of the infrastructure 15:12:12 ... decided to do that to avoid getting blocked on WPT if there's other tools 15:12:32 ... WPT can pull from it periodically, but regardless of how those politics go, we still have our schema for testing 15:12:44 TimCole: Test scripts are tailored for the runner? 15:12:56 bigbluehat: Yes, but could write code to handle those too. 15:13:12 TimCole: Have some runner scripts, as you can't test without a runner 15:13:50 bigbluehat: Best to keep them in web anno tests. If WPT fails, which doesn't seem likely just a little slowed, having our tests is useful to have in our own repo, so more tools can benefit 15:13:52 q? 15:14:00 ... they're not dependent on any run time, just descriptive docs 15:14:08 TimCole: This has been about the data model 15:14:15 q+ 15:14:25 scribenick: TimCole 15:14:58 azaroth: when and how can we get the annotations that ??? produces to test? 15:15:14 bigbluehat: Are you wanting a place to past these examples? 15:15:40 azaroth: yes, so that we can demonstrate end-to-end, albeit incomplete. 15:15:53 http://shane.spec-ops.io:8000/ 15:15:59 ... the sooner we get that done the sooner we get more implementations 15:16:23 bigbluehat: we can use Shane's server in the short term 15:16:56 ivan: in many respects from the CR point of view what counts is to get back an implementation report from ??? 15:17:06 ... in a format that Greg K. can process 15:17:15 ack azaroth 15:18:04 azaroth: given Shane is not on the call and has to worry about the WPT process, can someone help with this first end-to-end 15:18:11 scribenick: azaroth 15:18:25 TimCole: It looks simple, but there were some difficulties 15:18:33 ... the runner doesn't work in my install 15:18:40 ... it gets hung making the manifest 15:18:44 ... What OS are you using? 15:18:51 bigbluehat: Windows, and ran into compile trouble 15:19:43 TimCole: I just cloned the repo and it started okay, but it got stuck. If someone was able to get it running, and we had the japanese examples, we could then generate a report to send to Gregg 15:19:46 +1 15:20:09 ... Wondering if we need a place to save the annotations? 15:21:01 Rob: With the intent to save them and rerun with new tests, or a different feature matrix 15:21:51 Ivan: No analogy to it in other groups. No harm to storing them, closer to the tests would be good. Nice to have, not a requirement 15:23:18 TimCole: You were thinking of starting with the japanese demo? 15:23:32 Rob: Yes, did an implementation of a client for IIIF, could do the round trip test 15:23:44 TimCole: Should identify a folder in the Web Anno Test repo for storing annotations to test 15:24:11 kamazaki annotator does not seen to work... for me. 15:24:19 ... Seems simple enough. 15:24:26 Rob: Separate per implementation 15:25:27 Dinesh: That implementation doesn't work for me. It just says preparing, it doesn't allow annoting the image 15:25:39 Rob: I tried only with the example images they have 15:25:51 Dinesh: Will try more and write a report 15:26:12 TimCole: I know shane has other things going on, I wonder if we need an implementation of the platform we can use? 15:26:28 bigbluehat: Need to know what Gregg needs for the report. Then just running AJV over it several times 15:26:44 TimCole: Let's try and get that going. Need implementations to get started with the tests as soon as we can 15:27:02 q? 15:27:30 Ivan: Would be worth reaching out to people we know are planning to implement to get them rolling 15:27:42 TimCole: Need to give them something to work with. Europeana is anxious to start 15:27:56 ... Need somewhere to put the annotations and how to run the tests. 15:28:09 ivan: Might be worth talking to the Pund.it people, what they plan to do 15:28:21 ... They said they want to transition to the model, but don't remember about timing 15:28:56 (FYI: it throws this error after a while. will write to him. image-annotator?u=http://static.zerochan.net/Uchiha.Sasuke.full.678195.jpg:31 Uncaught ReferenceError: tiledesc is not defined ) 15:29:10 Rob: Don't recall if they were clean on timing 15:29:41 Ivan: Europeana, Pundit, Hypothes.is, IIIF all good targets 15:29:57 TimCole: That gives us some work to do while Ivan is on vacation :) 15:30:03 ... Benjamin, protocol testing? 15:30:26 bigbluehat: I've begun reorganizing the tests I have, and the tests for the tester, based on the PR that Rob and I went through with the plan to put in after CR 15:30:33 ... Easier to test. 15:30:39 TimCole: Just editorial? 15:30:47 bigbluehat: Yes, just clearer and better structured 15:31:01 ... the code in WPT can be run separately from the wpt-serve system 15:31:17 ... server could be made standalone and generate its own reports, if we need to 15:31:45 ... protocol tester project has come a long way, so intend to finish that out and have people use to test protocol implementaitons 15:31:55 ... then finish my protocol implementation to let clients test against that 15:32:02 TimCole: Is it in github yet? 15:32:09 bigbluehat: Yes, in a weird spot at the moment 15:32:22 ... a work in progress 15:32:24 https://github.com/Spec-Ops/web-platform-tests/pull/3 15:32:40 ... in need of rebasing 15:32:57 ... :tophat: 15:33:18 TimCole: thoughts on the issues with WPT PRs 15:33:44 bigbluehat: When you work with someone else's code, they have opinions about how it should all be done 15:34:06 ... not sure how broken it is. Sounds like he knows what's needed, just needs to have the time to do it 15:34:22 ... some of his commits are in front of my PR, so you can see what he was trying to curate 15:34:56 TimCole: For what you're doing and for the model, when do we go forwards? Only have a small percentage of the schemas written 15:35:09 bigbluehat: So long as the test structures don't change wildly, no need to wait 15:35:28 ... should ensure he can work on things when he has time, and not pulled off in other directions 15:35:37 ... How are you testing the scripts now? 15:35:43 TimCole: ajv command line 15:35:53 bigbluehat: Could write those up, and in lieu of WPT, could point at the readme 15:36:04 +1 bigbluehat 15:36:05 ... or wrap the commands in a script 15:36:26 TimCole: Other thing we've been doing is saving incorrect annotations to make sure the schema catches them 15:36:46 ... so can say annotation doesn't correctly implement as it leaves out a required key 15:36:57 ivan: same for the protocol. THere's a number of MUSTs that need to be checked 15:37:16 ... the changes, should wait until Tuesday before committing 15:37:32 TimCole: We won't talk about them till after Tuesday :) 15:38:09 ivan: I won't be here, so I created a Release in GH. If someone can create a protocol release that would be good. 15:38:41 ... the changes on the protocol spec are good, fully behind it. I ran into the same problems understanding the paging. 15:38:53 ... Made me realize my toy implementation is buggy :) 15:39:16 ... That's the real value of CR 15:39:31 TimCole: Both model and protocol for the next couple of weeks, we'll have something to point implementers to 15:39:37 ... that's what we're shooting for? 15:39:57 ... combination of documentation and a little client/server tester 15:40:05 bigbluehat: Ship everything as soon as possible 15:40:12 TimCole: Don't want to miss the window of interest 15:40:23 ... where are we on vocab testing? Primarily the context doc? 15:40:50 ivan: Already have a test ... forgot to update the context and the new one works for the japanese demo 15:40:54 TimCole: A good data point 15:41:31 ivan: Not all the implementations will use the context. Most won't be RDF based. I know the guy is semantic, so he did some testing by putting the data into an RDF store 15:41:36 ... That can be documented 15:41:37 q+ 15:41:42 ... same will hold for Europeana 15:42:04 Rob: At least transform through RDF on the way in and out 15:42:24 ivan: vocab testing is really about that -- the context reflects the vocabulary the way it should. A bit shallow but good data points 15:42:30 ... Need to record them. 15:42:36 scribenick: TimCole 15:42:44 azaroth: similart vocab data point 15:43:16 ... recent updates to my implementation of protocol transforms both ways json-ld to rdf to json-ld via context and frames 15:43:25 ... turtle to json-ld and vice versa 15:43:45 ... I could extract code and make stand-alone as a demo of ability to do this 15:43:57 ivan: yes, this is good, 15:44:00 scribenick: azaroth 15:44:08 TimCole: Would be good to document it 15:44:23 Ivan: Do you have a feeling of the RDF terms we define are in use? 15:45:00 scribenick: TimColle 15:45:12 azaroth: client implementation is just images 15:45:36 ... so svg selector, uses format, textual body, created, no creator yet 15:45:47 ... all the core stuff, but not the text stuff 15:46:11 ivan: adding a single table that these are the terms that have been used by x implementation(s) 15:46:25 ... we asked each of the implementations to keep track 15:46:39 ... to help us keep track, nothing else than an HTML table 15:46:58 ... so when skos was defined it was always a question about actual usage of the vocabulary 15:47:10 azaroth: yes, I can generate such a table. 15:47:11 +1 15:47:21 scribenick: azaroth 15:47:26 TimCole: Anything else about vocab testing? 15:47:49 Ivan: can document usage and context mapping. That's what we said we'd do on the transition call 15:48:08 TimCole: What else today? 15:48:10 q? 15:48:15 ack azaroth 15:48:57 present+ takeshi 15:49:02 we have tried a bit. will see if i can put together a "team" :) 15:49:03 ... Nothing else? 15:49:32 ... should we invite the japanese and europeana folks to one of our calls to discuss testing with them? 15:49:41 ... assuming we have something for them to use 15:49:47 +1 to hearing from implementers we know about 15:50:16 takeshi++ for being awesome 15:50:16 takeshi has 1 karma 15:50:21 Rob: Hard for the combination of Europe and Japan! 15:50:28 takeshi++ for being way more awesome than 1 karma point! 15:50:29 takeshi has 2 karma 15:50:35 TimCole: By email then when we have something to show 15:50:45 ... Can adjourn unless there's other business 15:51:01 ... will make progress on the schemas. If anyone wants to help, please jump in 15:51:27 ivan: By the time I come back from vacation... ? 15:51:33 TimCole: Should at least have some test results :) 15:51:36 ivan: you've earned this vacation to be sure! 15:51:38 ... When do you come back? 15:51:41 +1 15:51:45 ivan: 1st of August 15:51:49 q+ 15:52:00 ack takeshi 15:52:05 ack take 15:52:20 takeshi: Checking the json-ld, and looked at the RFC for the profile URI 15:52:38 ... have developed a profile URI in the protocol, and should provide the information to the RFC 15:52:44 https://tools.ietf.org/rfc/rfc7284.txt 15:52:53 scribenick: TimCole 15:53:13 azaroth: at TPAC last year we discussed with Heather whether it would be possible to register 15:53:27 ... a profile without registering a media type 15:53:52 ... so we could register a profile 15:53:56 there's a separate profile registry iirc 15:54:01 ... we should do that 15:54:06 oh...right RFC7284 >_> 15:54:09 ivan: do we know how to do that 15:54:23 azaroth: not clear since no one has registered a profile URI yet 15:54:26 start now, I'd say 15:54:39 ivan: this worries me, having been through some of this before 15:54:51 ... there is no way to register a fragment id propertly 15:55:10 ...which means its not an official thing yet 15:55:16 ... not fully up to date with ietf, but this is just an informational document by Markus 15:55:18 https://datatracker.ietf.org/doc/rfc7284/ 15:55:21 full status ^^ 15:55:36 ... I presume Rob was in contact with Markus on some of this 15:55:55 ... so perhaps Rob should contact Markus directly to ascertain status 15:56:09 send it to me, I'll +1 it and send it back. promise 15:56:12 azaroth: in Example 3 of the document there is a sample registration submittal 15:56:29 ivan: with regard to media types there is a W3C agreement with ietf 15:56:45 ... such that media type defined in W3C document gets properly registered 15:56:55 ... not sure if it works the same way for profile 15:57:17 azaroth: will make an issue in git hub (PR milestone) to get in touch with ietf 15:57:22 q? 15:58:21 rrsagent, draft minutes 15:58:21 I have made the request to generate http://www.w3.org/2016/07/08-annotation-minutes.html ivan 15:58:31 trackbot, end telcon 15:58:31 Zakim, list attendees 15:58:31 As of this point the attendees have been Rob_Sanderson, Ivan, Benjamin_Young, Jacob_Jett, TB_Dinesh, Tim_Cole, takeshi 15:58:39 RRSAgent, please draft minutes 15:58:39 I have made the request to generate http://www.w3.org/2016/07/08-annotation-minutes.html trackbot 15:58:40 RRSAgent, bye 15:58:40 I see no action items