14:48:35 RRSAgent has joined #dpub 14:48:35 logging to http://www.w3.org/2016/05/02-dpub-irc 14:48:37 RRSAgent, make logs public 14:48:37 Zakim has joined #dpub 14:48:39 Zakim, this will be dpub 14:48:39 ok, trackbot 14:48:40 Meeting: Digital Publishing Interest Group Teleconference 14:48:40 Date: 02 May 2016 14:48:54 Agenda: http://www.w3.org/mid/DCA57555-8379-4BC7-BCFF-CA7417D474B2@gmail.com 14:49:10 ivan has changed the topic to: agenda telco 2016-05-02: http://www.w3.org/mid/DCA57555-8379-4BC7-BCFF-CA7417D474B2@gmail.com 14:49:21 Chair: Markus 14:49:48 Regrets+ Ayla, Heather, Daniel, Vlad, Jean 14:53:25 mgylling has joined #dpub 14:55:05 TimCole has joined #dpub 14:56:40 clapierre has joined #DPUB 14:58:12 NickRuffilo has joined #dpub 14:59:11 Present+ Ivan 14:59:14 present+ dauwhe 14:59:29 Present+ Tim_Cole 14:59:35 present+ 14:59:41 Bill_Kasdorf has joined #dpub 15:00:34 pkra has joined #dpub 15:00:58 present+ Markus_Gylling 15:01:28 scribenick: dauwhe 15:01:40 present+ astearns 15:02:30 brady_duga has joined #dpub 15:02:33 laudrain has joined #dpub 15:02:37 present+ duga 15:02:42 present+ Bill_Kasdorf 15:02:55 mgylling: major topic today is annotations 15:03:00 present+ Luc Audrain 15:03:02 ... but rob is stuck in traffic 15:03:15 ... tim, ivan... is this a reason to reschedule? 15:03:23 ivan: I think we can manage 15:03:32 Bill_Kasdorf: can we move it to the end? 15:03:35 mgylling: sure 15:03:45 bjdmeest has joined #dpub 15:03:51 ... OK. Let's do everything else first 15:03:57 https://www.w3.org/2016/04/25-DPUB-minutes.html 15:03:58 ... minutes from last week 15:04:05 ... any objections to approving? 15:04:21 ... minutes approved. 15:04:40 ... it's conference season. Next week many of us will be in Chicago for IDPF 15:04:48 ... so I suggest we cancel the meeting on the 9th 15:04:55 lrosenth has joined #dpub 15:05:02 ... and there's another conference in Stockholm the next week 15:05:03 Present+ Ben_De_Meester 15:05:13 present+ Leonard 15:05:15 ... let's wait on deciding about the 16th 15:05:17 present+ Peter Krautzberger. 15:05:24 Regrets+ Tzviya 15:05:33 ... we should be back to normal week of May 23 15:05:45 ... which is the week of the virtual F2F 15:05:52 https://www.w3.org/dpub/IG/wiki/May_2016_Virtual_F2F 15:05:54 ... so we need to work on the agenda for the virtual F2F 15:06:25 ... so let's spend some time on this 15:06:38 ... they are sometimes great and sometimes not 15:07:01 ... which topics are most critical to cover? 15:07:18 ... we've already mentioned documents that are nearly finished 15:07:29 ... Charles, Deborah, and their team finished the a11y note 15:07:39 q+ 15:07:45 ... the main topic would be the use cases collection 15:07:51 ... are there other things we should add? 15:07:52 ack ivan 15:08:00 ivan: on the previous comment 15:08:08 ... I've made a new version of the pwp draft 15:08:23 ... which merged with locator work and jettisoned the use cases 15:08:30 ... it's on a separate branch 15:08:37 ... if you think it's ok I can merge 15:08:45 ... or I can merge now then respond to issues 15:08:51 mgylling: is this a f2f topic? 15:08:58 ivan: no, this is about documents 15:09:14 q? 15:09:22 david_stroup has joined #dpub 15:09:47 ivan: I think that the use case document is the absolutely highest priority document 15:09:51 cmaden21 has joined #dpub 15:09:58 ... i don't mind if this is the only topic 15:10:01 +present Chris_Maden 15:10:02 mgylling: i agree 15:10:10 ivan: we can talk about the manifest format 15:10:15 ... but that has a lower priority 15:10:26 lrosenth: and we need a straw man 15:10:36 mgylling: straw man of what? 15:10:40 ivan: manifest 15:10:50 ... the real issue is format and syntax of manifest 15:11:48 mgylling: we could ask dave and hadrien to discuss BFF manifest work 15:12:04 q+ 15:12:04 ... in order to see what topics within the use cases we should focus on 15:12:09 ... manifest is one 15:12:16 ... we've talked about portability and packaging 15:12:25 q- 15:12:31 ... why do you need portable docuemnts when you have the web? 15:12:36 ... what are those high-level use cases? 15:12:50 ... we've been touching on what are the requirements of the package itself? 15:13:01 ... like streamability, random access, digital signatures, etc 15:13:06 ... we have some work to do there 15:13:13 q+ 15:13:14 ... and maybe manifests is a sub-discussion there 15:13:17 ivan: I think so 15:13:28 q? 15:13:51 ... when you talk to web people, the question is why isn't the web enough? 15:14:08 ... that's the general question to which we have to have very good answers 15:14:18 ... including business cases, production flows, etc 15:14:30 ... the packaging format (zip vs nonzip) is secondary 15:14:31 ack lrosen 15:14:35 lrosenth: I agree 15:14:43 ... i think the use cases will address a lot of that 15:14:55 ... to both package and offline cases 15:15:12 ... one of which being stuff we put to the side--the package and offline scenario 15:15:29 mgylling: packaging, manifest... do we want a 3rd and 4th topic? 15:15:32 ivan: security 15:15:45 ... i'm not taking about the D-word 15:15:48 mgylling: privacy? 15:16:06 ivan: the security in terms of hacking into a publication, javascript as security issue, etc 15:16:10 security in terms of rights 15:16:23 lrosenth: in some ways they're related 15:16:47 ... both fall into the category of surprising the user 15:16:58 ... they're used to web pages, and what they can and can't do 15:17:08 ... they're used to publications, and what they can and can't do 15:17:12 ... but now we're blending 15:17:22 ... are people used to movies in publication, touch events 15:17:31 ... but how do users feel about analytics? 15:17:38 ... about publications that phone home? 15:17:47 ... that's where security and privacy come together 15:18:00 present+ Chris_Maden 15:18:01 ... we're creating publications that are different than they've ever been 15:18:07 ivan: these are all important points 15:18:14 q+ 15:18:40 ack dave 15:18:45 ack dau 15:18:55 present+ Charles_LaPierre 15:19:12 q+ 15:19:22 ack lros 15:19:25 rdeltour has joined #dpub 15:19:36 dauwhe: we should learn from the problems of EPUB. Single origin is core of web security, and that might not work here 15:19:50 lrosenth: we also need to consider the environments, like package and manifest 15:20:05 ... how is this material exposed? The origin model may vary 15:20:31 mgylling: OK. packaging with manifest as sub-discussion. Security/Privacy. Those may be enough. 15:20:35 rebecaruiz has joined #dpub 15:20:41 ... we don't want to be shallow. We want to work and prose and materials. 15:21:04 ... so we probably want an interactive editing environment, like google docs 15:22:24 mgylling: Dave, would you agree that the f2f is is a good time to do an introduction to manifest? 15:22:42 dauwhe: I'm worried we'd get lost in the weeds 15:22:46 q+ 15:22:50 q? 15:22:54 ack cla 15:23:06 clapierre: do we just go and add ourselves as participants to the f2f? 15:23:12 mgylling: On wiki page? Sure. 15:23:19 ... ivan, is that the intent? 15:23:20 q+ 15:23:25 ivan: yes. 15:23:34 BTW I would be happy to talk about note / noteref / notegroup at the f2f if the agenda feels thin. 15:23:51 ack rebe 15:24:25 q+ 15:24:29 ack rdel 15:24:36 mgylling: we probably have enough of an agenda so we probably couldn't get to noteref 15:24:40 rdeltour: can you hear me? 15:25:03 ... remind us of the timeframe for the f2f on the wiki page? Starts at 12 UTC? 15:25:09 ivan: yes, it lasts four hours 15:25:28 brady_duga: does it conflict with epub meeting 15:25:30 mgylling: yes 15:25:36 ... but they should move :) 15:25:39 q? 15:25:44 ... anything else about the virtual f2f 15:25:49 s/brady_duga/???/ 15:26:09 s/???/Charles_LaPierre 15:26:27 q+ 15:26:36 ack rdel 15:26:44 q+ 15:27:10 ack rdel 15:27:13 https://rawgit.com/w3c/dpub-pwp-ucr/index-update/index.html 15:27:18 rdeltour: quick comment on use cases 15:27:24 ... heather is working on this branch 15:28:10 that never happens! 15:28:31 mgylling: we've wanted to talk with annotations wg for a while 15:28:48 ... can you describe where you are? A brief recap? 15:29:00 rebecaruiz: hello 15:29:19 mgylling: can you introduce yourself 15:29:31 rebecaruiz: I work for cormac, a publishing service company 15:29:43 s/cormac/Cornac Servicios Editoriales/ 15:29:49 ... we are very focused on syntax and typography in Spanish text 15:30:07 ... we hope to work in this group a lot 15:30:15 https://www.w3.org/TR/annotation-model/ 15:30:20 It's Cornac, not Cormac… Sorry 15:30:23 http://w3c.github.io/web-annotation/ 15:30:27 https://www.w3.org/TR/annotation-vocab/ 15:30:32 mgylling: tim, would you like to give us an intro 15:30:36 present+ rebecaruiz 15:30:39 https://www.w3.org/TR/annotation-vocab/ 15:30:47 TimCole: (silence) 15:31:03 ivan: why don't I start 15:31:09 ... I hope he hears us 15:31:36 ... I have put in the URL for the github because that includes the references to the three docs we've published 15:31:45 ... we had a charter that included some other items 15:32:03 ... we could not get on with them as we didn't the right people etc 15:32:14 ... the work that we started 15:32:33 ... we started with the work done in the CG 15:32:40 present+ rebecaruiz 15:32:56 ... that's more-or-less what we went on with, the data model and the vocab 15:33:16 ... plus we have the annotation protocol between a server and client exchanging annos and data structures 15:33:29 ... the biggest difference between what we have now and the CG doc 15:33:40 ... is that we've made a cleaner separation between the model and vocab 15:33:50 ... and between the serialization in JSON, and the RDF vocab 15:33:58 ... the main reason being we wanted to have a doc 15:34:09 ... that is readable acceptable useable by web app devs 15:34:24 ... the web anno data model is describing data model in pure json 15:34:45 ... we had lots of discussion on what terms to use to make it palatable to json users and js 15:34:53 ... it's actually json-ld but we don't fuss about that 15:35:05 ... we also have web anno vocab, which is clearly rdf 15:35:10 ... with examples in turtle 15:35:25 ... there is also a json-ld context file which maps between json and rdf 15:36:08 ... i will hand it over to tim in a minute, for the diffs between the cg and the current doc 15:36:14 azaroth has joined #DPUB 15:36:16 ... the fundamentals of the models is the same 15:36:33 ... an anno is a small json structure 15:37:37 azaroth: the model is quite straightforward 15:37:45 ... there's an anno, which is a web resource 15:37:48 present+ 15:37:52 ... it has a body, which is the comment or the tag 15:38:01 ... and it has the target, which the comment is about 15:38:09 ... there's the intention, the body, and the target 15:38:26 ... each of those can have provenance, such as creator, license, intended audience 15:38:37 ... there can be multiple bodys and multiple targets 15:38:46 ... and any could have any format 15:38:53 ... you could have a video about an image 15:39:01 ... that hasn't changed from the CG work 15:39:08 ... we've just added some more metadata 15:39:13 cmaden2 has joined #dpub 15:39:28 ... the new work is based around the community group's efforts on descriptions of parts of resource 15:39:44 ... most annos will be about some fragment of something 15:39:55 q? 15:40:04 ... like a range of text on an html page 15:40:14 ... so we have several selectors to find the content of interest on a page 15:40:26 ... and there are workflow stuff like a state class 15:40:40 ... that lets you record the http headers that were sent 15:40:53 ... so if you had a single resource with a uri which gives both html or pdf 15:41:08 ... then the selectors for how to retrieve the text would be different 15:41:23 ... so you need to know if user was looking at html or pdf when they made the anno 15:41:45 TimCole: we've also clarified how to do very simple text annotations, made easier for json 15:41:50 Jean_K has joined #dpub 15:42:07 ... we also refined the idea of motivations, the role of the body esp. if you have multiple bodies 15:42:13 ... like in a copyedit environmen 15:42:27 ... you can distinguish between replacement text and commenting on substance 15:42:52 ... we anticipate that communities may focus on parts of the model most interesting to them, and develop them further 15:43:08 azaroth: talk about protocol? 15:43:08 q+ 15:43:24 TimCole: you can do server to server... 15:43:39 ... the question is how this would play out in pwp, take books offline, then come online 15:43:47 ack ivan 15:43:48 ... we don't quite know how this will play out 15:43:53 ivan: one more thing 15:43:59 Model: https://www.w3.org/TR/annotation-model/ 15:44:11 http://w3c.github.io/web-annotation/selector-note/index-respec.html 15:44:12 ... rob has already talked about the selectors and states as being very powerful in selecting parts of a resource 15:44:18 Protocol: https://www.w3.org/TR/annotation-protocol/ 15:44:31 ... we also made a separate note which makes it clear that that part of the model can be used outside annotations 15:44:42 .... it's general approach to selecting parts of a complex resource 15:45:01 ... it extracts it and makes it available to people who aren't interested in annotations 15:45:05 q+ 15:45:21 ... could be an alternative to CFI 15:45:36 ack TimCole 15:45:38 ... we've also put CFI as a possibility to express a fragment 15:45:44 TimCole: in terms of where the group is 15:45:48 ... charter ends oct 1 15:45:54 ... we have these three mature WDs 15:46:00 q+ 15:46:12 ... we have an upcoming f2f in berlin to move these forward, get them to CR this summer 15:46:25 ... try to get to rec by the end of the charter 15:46:31 ... we don't have as much on client side API 15:46:39 ... we may have a note about html serialization 15:47:05 ... and there is work on privacy, on publishing annotations that everyone see 15:47:29 ... you can signal behaviour with robots.txt, but this is beyond our scope 15:47:31 ack lrosen 15:47:47 lrosenth: could you talk about implementation status? 15:47:55 ... how many are known, both client and server? 15:48:08 azaroth: because of the CG's work in the past 15:48:16 ... there are a lot of implementations of the CG spec 15:48:28 ... there are fewer implementations of the WG spec, as it's not yet CR 15:48:42 ... Europeana has implemented the model and the protocol 15:48:51 ... for cultural heritage 15:49:03 .... ??? has upgraded from the CG to the WG, they have a client 15:49:14 s/???/pund.it/ 15:49:18 ... Hypothesis has not yet released their version that implements the model 15:49:24 ... but I've seen it 15:49:35 q+ 15:49:38 ... that's the client, and they're working on the protocal 15:49:57 ... the AAAF?? community is commited to moving from the CG spec to the WG spec 15:50:04 q+ 15:50:10 ... that would be both model and protocol 15:50:17 s/AAAF/IIIF/ 15:50:18 that was great - thanks! 15:50:28 mgylling: does this mean your exit criteria fears are no longer something to fear 15:50:39 azaroth: I'm still a bit afraid, but we hope to 15:50:44 TimCole: lots of work to do on testing 15:50:54 azaroth: there's still work around the edges 15:51:19 ... things like intended audience and license and provenance that we've added in the WG, there are fewer implementations 15:51:20 ack ivan 15:51:26 there are some concerns about testing ;-) 15:51:29 ivan: let me add to the long list two items 15:51:46 ... one is that I had a discussion with EDRL lab 15:51:56 ... it's on their plans to implement and add to readium 15:52:01 ... it's not clear when it will happen 15:52:15 ... we are hopeful they can do it, and help with testing for CR 15:52:27 ... the other one which is more a kind of hope 15:52:41 ... the new version of bluefire will have very good annotation facilities 15:52:41 IIIF: http://iiif.io/ and in particular: http://iiif.io/api/presentation/2.1/ is the spec that uses the Annotation work 15:52:54 ... for the time being this is their own thing, but might migrate to spec 15:53:08 mgylling: there are a few other epub implementations that use the CG version 15:53:16 ... I can try to dig up the list 15:53:32 ... rob and tim, rob, you helped us with epub adoption of CG spec, which is still a draft 15:53:41 @dauwhe: Please do!!! I'm interested to know the extent of implementation. 15:53:48 ... which is now waiting to be updated to the WG 15:53:58 q? 15:53:59 ... is it ready now? 15:54:12 azaroth: I don't think there are significant areas that will change 15:54:29 ... maybe after Berlin F2F would be the time to start work on that, it's when we hope to go to CR 15:54:38 ack mgylling 15:54:47 ... there are a few minor things we need to discuss that might result in trivial changes 15:54:50 mgylling: cool 15:55:12 ivan: the epub version put the emphasis on JSON, which is part of our current rec 15:55:26 ... the other thing is that one of the work items 15:55:38 ... the json schema done for epub should be reused and updated 15:55:49 q+ 15:55:51 ... the testing mechanism will use that schema 15:55:53 (maybe). 15:55:58 ack lros 15:56:04 q+ 15:56:32 lrosenth: your comments are around EPUB, but we're not far enough along with PWP to talk about that 15:56:40 ivan: the rec is about anything 15:56:43 ack mgyl 15:56:58 mgylling: so you have this note with frag selectors 15:57:06 ... so you won't require implementation 15:57:20 ... but 90% of it is exactly the same as the rec itself 15:57:40 ... the only thing which is not in the rec is a mapping onto fragment identifiers 15:57:57 ... so people who are not interested in annos can use the same stuff for other uses 15:58:13 mgylling: so an implementaiton of the rec will have to support xpath and css selectors 15:58:19 ivan: that is correct with one caveat 15:58:30 ... is that not all selectors make sense with all media types 15:58:36 q? 15:58:44 ... so implementions may concentrate on particular media types 15:59:16 mgylling: the w3c has tried before to introduce new selectors 15:59:21 ... and it hasn't gone well 15:59:31 ... do you see a dependancy on browsers here? 15:59:39 ivan: long term, yes. It's a big unknown. 15:59:51 ... implementations can do internally what they want 16:00:01 ... ideally this would be implemented in browsers 16:00:13 azaroth: in the meantime, everything can be implemented in JS 16:00:23 ... if browsers were to take up heavy lifting 16:00:32 ... it would make impl much easier 16:00:44 mgylling: have you had any expression of interest with browsers 16:00:55 TimCole: we've had a long conversation about text 16:01:02 ... interest but no action 16:01:07 q? 16:01:10 mgylling: we're at the top of the hour 16:01:37 azaroth: this is a good time for feedback 16:01:43 s/azaroth/TimCole/ 16:01:45 mgylling: review the EDs 16:02:03 possible new avenue for dealing with new selectors: https://drafts.csswg.org/css-extensions/#custom-selectors 16:02:13 mgylling: thanks everyone 16:02:24 ... next week meeting is cancelled 16:02:38 rrsagent, draft minutes 16:02:38 I have made the request to generate http://www.w3.org/2016/05/02-dpub-minutes.html ivan 16:02:43 trackbot, end telcon 16:02:43 Zakim, list attendees 16:02:43 As of this point the attendees have been Ivan, dauwhe, Tim_Cole, ShaneM, Markus_Gylling, astearns, duga, Bill_Kasdorf, Luc, Audrain, Ben_De_Meester, Leonard, Peter, Krautzberger., 16:02:44 clapierre has left #dpub 16:02:47 ... Chris_Maden, Charles_LaPierre, rdeltour, rebecaruiz, Bert 16:02:51 RRSAgent, please draft minutes 16:02:51 I have made the request to generate http://www.w3.org/2016/05/02-dpub-minutes.html trackbot 16:02:52 RRSAgent, bye 16:02:52 I see no action items