08:03:56 RRSAgent has joined #dpub 08:03:56 logging to http://www.w3.org/2016/09/19-dpub-irc 08:04:24 Chair: Tzviya 08:04:31 present+ 08:05:46 boris_anthony has joined #dpub 08:05:47 present+ HeatherFlanagan 08:05:50 present+ duga 08:05:55 present+ Charles_LaPierre 08:06:07 present+ George_Kerscher 08:06:10 present+ BorisAnthony 08:06:20 lrosenth has joined #dpub 08:06:31 present+ Avneesh 08:07:30 rrsagent, set draft public 08:07:30 I'm logging. I don't understand 'set draft public', ivan. Try /msg RRSAgent help 08:07:33 pkra has joined #dpub 08:07:41 trackbot, star telcon 08:07:41 Sorry, ivan, I don't understand 'trackbot, star telcon'. Please refer to for help. 08:07:48 trackbot, start telcon 08:07:49 garth has joined #dpub 08:07:50 RRSAgent, make logs public 08:07:52 Zakim, this will be dpub 08:07:52 ok, trackbot 08:07:53 Meeting: Digital Publishing Interest Group Teleconference 08:07:53 Date: 19 September 2016 08:08:00 Agenda: https://www.w3.org/dpub/IG/wiki/Sep_2016_F2F_Logistics_and_Details#Agenda 08:08:19 Meeting: Digital Publishing Interest Group F2F First day 08:08:42 scribenick: HeatherF 08:09:31 sam has joined #dpub 08:11:15 rego has joined #dpub 08:12:00 rdeltour has joined #dpub 08:12:36 dauwhe has joined #dpub 08:12:51 bobbytung has joined #dpub 08:14:38 Bill_Kasdorf has joined #dpub 08:14:40 chaals has joined #dpub 08:14:49 laurentlemeur has joined #DPUB 08:15:07 cabanier has joined #dpub 08:15:23 present+ 08:15:26 present+ Bill_Kasdorf 08:15:42 Paul_B has joined #dpub 08:15:59 VST-Rick has joined #dpub 08:16:03 liam has joined #dpub 08:16:10 takeshi_ has joined #dpub 08:16:12 bob has joined #dpub 08:16:29 present+ Leonard 08:16:39 present+ Garth 08:16:45 present+ Rick 08:17:03 it is quiet in here. present+ Peter 08:17:04 present+ Liam 08:17:10 danimrq has joined #dpub 08:17:13 tzviya: LEt's talk about that word: Package. package is not just books; it could be journal articles, encyclopedias, church notes 08:17:15 present+ Peter 08:17:16 present+Paul 08:17:18 Present+ Takeshi_Kanai 08:17:34 ... anything we read that isn't just a blog (though maybe a its a blog, too) 08:17:46 present+ bobbytung 08:17:50 present+Paul_Belfant 08:18:05 Rebeca has joined #dpub 08:18:07 s/package/publication 08:18:27 present+Laurent Le Meur 08:18:32 tzviya: Don't want to discuss "portable" right now. Will discuss in next session. EPUB has a pretty clear description. 08:19:10 ... we might want to use other words than portability, packaging. We need to be flexible as our use of certain terminology is confusing to certain people. 08:24:34 Florian has joined #dpub 08:26:03 q? 08:26:25 lrosenth_ has joined #dpub 08:29:20 glazou has joined #dpub 08:29:42 ... there will have to be compromise and consensus on final words and outcome. 08:30:47 ... so while there seems to be tension on the github issues list between publishers and web people, it is a really good conversation to have 08:30:49 duga has joined #dpub 08:33:28 laurentlemeur has joined #dpub 08:33:54 ... Some of the other issues to cover this week will be less controversial. 08:34:03 https://www.w3.org/dpub/IG/wiki/Sep_2016_F2F_Logistics_and_Details#Agenda 08:34:13 marcosc has joined #dpub 08:35:15 ... we will have meetings with other groups this week. Instead of talking about our other documentation, we're going to discuss issues against the pwp-ucr. 08:35:44 LHulse has joined #dpub 08:35:49 ... Service Workers has been a hot topic. Jake will join via WebEx if possible when we discuss SWs. 08:36:01 would you mind using the microphones as I am finding it impossible to hear 08:36:26 Vlad has joined #dpub 08:38:18 present+ 08:38:21 tzviya: other meetings include CSS (pagination, math). At the same time, APA (extended descriptions). Data recap, and action items will come out from there. 08:39:25 ... Permissions, Obligations, and Expressions WG (which is not DRM). Use cases doc FTW! 08:39:33 q? 08:41:16 *We are experiencing technical difficulties. Please stand by.* 08:47:08 if this computer stuff doesn’t work out - I think I have a new job doing phone support :) 08:47:20 08:48:00 Karen has joined #dpub 08:48:01 @marcos dial in, we're ready to start 08:48:05 oki 08:48:08 david_wood has joined #dpub 08:48:28 present+ david_wood 08:50:11 LHulse has joined #dpub 08:50:33 say hi 08:50:40 yay! Hello @marcosc 08:51:06 https://www.w3.org/dpub/IG/wiki/Detailed_TPAC_2016_Agenda#PWP-UCR_Fundamental_Issues 08:51:28 @marcosc we are using a microphone, but we're in a pretty big room 08:51:31 Scribenick: Karen 08:51:31 Tzviya: we had a detailed agenda 08:51:31 …Garth, can you start with a summary 08:51:31 Tzviya: we have a fundamental issues agenda 08:51:31 …I need to tell people when this meeting is starting 08:51:31 …Marcos, say hello 08:51:32 Marcos: Hello 08:51:32 Ivan: Do you hear us? 08:51:32 Tzviya: We ill use the microphones 08:51:32 Tzviya: as hopefully you are aware, we have more than 100 issues in a given repository 08:51:36 …Ivan and I tried to sort them into categories and we will try to work them to the best of our abilities 08:51:43 …The goal is not solve them, but to sort through them 08:51:49 …Heather is going to take notes in GitHub 08:51:57 …or by branching the repository 08:51:58 pkra has joined #dpub 08:52:04 …hoping to have a new draft 08:52:09 …First issue is 99 08:52:10 https://github.com/w3c/dpub-pwp-ucr/issues/99 08:52:29 Ivan: before getting into the deep end of the individual issues 08:52:36 …whether we can agree with Marcos being around 08:52:50 …what are the 3-4 very fundamental questions that are on the table, regardless of which issue they appear in 08:52:58 present+ dauwhe 08:52:58 …Some problems that spread over 2-3 issues in some sense 08:53:06 …We may decide to go one lever higher up 08:53:10 present+ Karen 08:53:17 …and how that translates into individual issues 08:53:25 Leonard: Looking at the fundamentals issue page 08:53:31 ..every one of the items on that page 08:53:39 …refers to the "P" term we are not talking about yet 08:54:02 …I am not sure how we handle we address until we handle the "P" problem; meaning package or portable 08:54:05 Ivan: That is one of them 08:54:11 …not sure which word to use 08:54:27 present+ glazou 08:54:33 Ivan: Regardless …how do we handle the online/offline 08:54:37 …one area where we want to be 08:54:46 …we started going in this direction in a general way 08:54:59 …it may be covered by service workers; special things; this is one big area 08:55:09 …There is an area of what kind of information do I have to make available 08:55:15 …for that type of action to work properly 08:55:22 ..whether there is any need at all or not 08:55:32 …issues about table of contents, info about available resources 08:55:36 …where the terminology gets messy 08:55:43 …the EPUB standard refers to those as a package 08:55:52 …which in the Web world is usually referred to as manifest 08:55:54 …that is one area 08:55:59 …Then there is the "P" word 08:56:04 …whether we want to provide a package 08:56:18 Garth: that thing we are fighting about is the container 08:56:23 Ivan: yes, the container as a facility or not 08:56:32 q+ 08:56:32 …these are the main areas that are the source of disagreement 08:56:41 …It think that is the main sticking point 08:56:51 …I would like to hear from Marcos 08:56:57 ack Bill_Kasdorf 08:57:04 Bill: Let me walk through the logi 08:57:06 c 08:57:19 …first, it can be as simple as single document or as complex as a collection 08:57:23 +1 to what Bill_Kasdorf just said 08:57:45 …whatever level of complexity comprises a publication must be distributed as a single unit; to be addressed by a single URI or identifier 08:57:47 …here is this thing 08:58:04 …and whether I fetch a zip file and unpack offline or simply access all components as service works, manifest 08:58:12 q+ 08:58:18 …it is not essential that it be packaged, but it is essential that it be identified 08:58:23 Tzviya: Marcos go ahead 08:58:37 Marcos: catching up what was just written 08:58:43 …i don't have any disagreement that was said 08:58:49 …Conceptually we are in agreement 08:59:03 …about what we are trying to achieve with use cases; it's how we get there 08:59:15 …maybe be premature to start writing solutions at this point 08:59:19 ack Daniel 08:59:25 q+ 08:59:32 ack gl 08:59:37 Tzviya: the mics are in the middle of the room 08:59:47 Glazou: I agree with your point 08:59:55 …another goal is to point to every resource inside documents 09:00:03 Bill: point that that thing gives you everything you need 09:00:13 Glazou: Web has to have URL from top to bottom 09:00:28 …if we don't do that we will have problems with scripts, with security, breaking 09:00:35 …we have to load whatever is in the publication 09:00:38 q? 09:00:44 ack Rebecca 09:00:57 q+ 09:01:08 Rebecca: Key problem from academic and scientific publishers is that the content must be completely refereable 09:01:20 …one way to get referable is to make a @ systems 09:01:31 q+ 09:01:42 ack Rebeca 09:01:45 …and to cite specific paragraph, in a specific page, in a specific edition of the book 09:01:54 [cites Don Quixote example] 09:02:02 …I don't care if it's an EPUB or PWP 09:02:08 …that's important for the publishers 09:02:12 …since ten years ago 09:02:26 …we should pay close attention to this approach 09:02:49 Tzviya: It's not just a matter of referencing; there needs to be a pattern to referencing the scientific record 09:03:00 …there needs to be the scientific record that says this is "the" thing 09:03:15 ack bo 09:03:16 …if article is edited or annotated or recalled, still needs to be a record of this 09:03:26 Boris: I am brand new to this group 09:03:29 …what is lacking I think 09:03:45 …we have overlapping, differing concepts and of how those are implemented 09:03:55 …if we are to get anywhere, we need to get harmonized 09:04:10 …but we are diving into details, but we have to agree on terminologies 09:04:11 ack boris_anthony 09:04:14 …maybe a formal exercise 09:04:25 Tzviya: you are right; may be good way to get us back to the issues 09:04:42 Marcos: another clause to Web in general. Would be great to know what other best practices or standards are 09:04:54 … Would be great to have some idea of how we are getting that in general 09:05:07 …how the scientific community deals with digital publishing and citations 09:05:15 hober has joined #dpub 09:05:19 q+ 09:05:24 q- 09:05:24 ack marcosc 09:05:24 Tzviya: Getting back to what Boris said, we need to be careful not to get into the weeds 09:05:30 present+ hober 09:05:35 …in Ivan's characterization, look at the higher issues 09:05:44 …in the document Ivan divided the issues into large categories 09:06:01 …The concept of publishing; relationships to service workers; the definition of online/offline, and offweb 09:06:08 …manifest and requirement and security issues 09:06:14 …and maybe talk about filtering 09:06:22 …cannot do that in the next 54 minutes 09:06:33 q+ to ask whether anyone is here from VIVO? "VIVO is member-supported, open source software and an ontology for representing scholarship." http://vivoweb.org/info/about-vivo 09:06:34 …Let's start with the concept of publication 09:06:38 …affects whole of PWP 09:06:39 Detailed agenda: https://www.w3.org/dpub/IG/wiki/Detailed_TPAC_2016_Agenda 09:06:43 …we need to discuss this 09:06:47 …As Leonard pointed out 09:06:54 …we had a lot of discussion 09:06:55 ack Ivan 09:06:56 ack iv 09:07:09 Ivan: I have the impression on the issue of this discussion that we are converging 09:07:14 …that when we talk of a publication 09:07:20 …and I'm talking about publication on the Web for now 09:07:32 …the fact that we need a concept that refers to a collection of documents 09:07:37 q+ 09:07:43 …I would make it a little bit larger and call it resources 09:07:55 …data sources are just as essential as an HTML file 09:08:00 …so a collection of resources 09:08:13 …we used term publication as the term for a collection of things 09:08:27 …it is the URL of the collection not the individual items 09:08:35 …we have to answer if I de-reference that URL 09:08:47 …there were discussions as to whether this was 09:08:52 …this concept is something of value 09:09:02 ..and it's a concept in this form does not exist on the Web right now 09:09:13 q+ 09:09:15 …is this a first point where we can have some sort of a consensus 09:09:17 q+ 09:09:33 ack da 09:09:33 david_wood, you wanted to ask whether anyone is here from VIVO? "VIVO is member-supported, open source software and an ontology for representing scholarship." 09:09:33 Leonard: I think you are right; it's where we started, it's a good definition 09:09:36 ... http://vivoweb.org/info/about-vivo 09:09:39 ack David_Woood 09:10:12 David: It seems to me that a lot of these problems have been addressed on the Web 09:10:27 …the library community has used consistent URLs to solve problems for 23 years 09:10:53 q+ 09:10:53 …we have W3C recommendations around annotations from SemWeb; ways to represent and describe a group of document, annotating these things 09:10:56 ack lr 09:10:57 …are we leveraging those? 09:10:57 q? 09:11:05 …and I wanted to say about the vivo community 09:11:18 …it's a community in academe addressing some similar problems in similar ways 09:11:23 …if you are not familiar 09:11:43 Leonard: We want to leverage existing standards wherever we can; looked a lot of these things 09:11:48 q+ 09:11:55 ack he 09:11:57 …David we would welcome more pointers to help us solve these problems 09:12:00 Publication: a collection of resources, each of which has its own URI. (? 09:12:03 ) 09:12:09 HeatherF: I want to clarify that I heard the definition correctly 09:12:22 …Publication is a collection of resources, each of whom has its own URI? 09:12:29 Leonard: He said it better before 09:12:32 ack ma 09:12:38 HeatherF: I'll go back and look in irc 09:12:44 q+ 09:12:44 Publication is a collection of resources, where there exists a single URL for the entire publication as well as a URL for each resources. 09:12:54 ack, thanks 09:12:55 Marcos: not unique to publications 09:12:58 q+ 09:13:01 …same problem in Webapplications 09:13:03 …a game 09:13:09 …there is a finite collection of resources 09:13:17 …that go into what we humans perceive as being a work 09:13:24 …that problem is not unique to publishing 09:13:35 …unique to any application on the Web; we can debate that later on 09:13:39 …more pragmatically 09:13:43 …I think it was David 09:13:50 …was mentioning the longevity of HTML 09:14:01 …and how we can string together the documents and the link relationships 09:14:04 …and in a more modern way 09:14:19 …the concept can define themselves what the relationships area 09:14:24 …the application, the book 09:14:33 …go to Ivan's point to resources and data 09:14:37 …these cannot be broken 09:14:40 q+ to say that this are publishing specific use cases that can be applied to other things, like apps and games 09:14:43 For example, a Dublin Core has a formal description of a "Bibliographic Resource", and a wealth of terms related to it: http://dublincore.org/documents/dcmi-terms/#terms-BibliographicResource 09:14:44 …having a declarative model around that 09:14:46 Suggestion: A publication is a resource or collection of resources with a persistent identity that enables interchange and reference. 09:14:48 …HTML support to do that 09:14:51 ack gl 09:14:52 …that is all I have to say on that 09:14:55 ack Daniel 09:15:13 Glazou: I heard something about all the specs we have in HTML, SemWeb 09:15:18 Dublin Core specifically addresses multiple formats, publications, etc. It was developed by the library community. 09:15:24 …that's great to hear, but it's almost useless 09:15:37 …only 10 percent is implemented by browser vendors or the rendering engines 09:15:45 …service workers do a lot of new stuff 09:15:49 @david_wood - that’s much too limited a definition 09:16:01 …some are completely useless; they don't exist from a market point of view 09:16:14 …reviewing the potential standards available in the world is one thing, but it is a waste of time 09:16:25 …we should focus on the rendering engines of browsers and reading systems that we have 09:16:27 …and focus on that 09:16:34 …otherwise we will end up in dead @ 09:16:34 ack bo 09:16:35 q+ to address implementation of Semantic Web features such as JSON-LD, available in every browser 09:16:42 http://w3c.github.io/dpub-pwp-ucr/#h-abstract 09:16:48 q? 09:17:00 Boris: In the PWP UCR use cases requirements doc we had put a definition of sort 09:17:03 …take out PWP 09:17:15 q+ to address the SemWeb stuff should be built with userland primitives 09:17:17 [Boris reads definition] 09:17:24 …fundamentally this is what we are talking about 09:17:33 …I can imagine a way to build this that can be loaded into a browser 09:17:38 q? 09:17:39 …we need HTML, and be loaded in 09:17:44 …very few things to be figured out 09:17:51 A Portable Web Publication (PWP) is 09:17:52 portable 09:17:53 bounded package of media 09:17:55 in web-standard formats 09:17:56 accessible by standard Web protocols 09:17:56 and consumable by standard Web tools. 09:17:59 ack iv 09:18:01 Tzviya: Dave and Jake built this a year ago; we have done the proof of concept 09:18:02 ack Ivan 09:18:08 Ivan: Two different things 09:18:11 …one answer to Marcos 09:18:15 q- 09:18:16 …to be precise about what I said 09:18:29 …I did not say that what we are talking about is unique to publications 09:18:39 …if there are other areas that have similar concerns, that is grea 09:18:40 t 09:18:47 …this issue is not properly solved 09:18:51 …Back to what David said 09:18:57 …what I know from my distant past 09:19:06 …there are certain issues that the SEmWeb community looked at 09:19:13 …and they are more sensitive on certain questions 09:19:17 …what is meaning of the URL 09:19:28 …and my question of what exactly you get when you de-reference the URL 09:19:37 …SemWeb community has been asking these questions for a long time 09:19:48 …if we are talking about web docs these are valid quesitons 09:19:54 …these are things we have to take into account 09:20:05 …they are more on the conceptual level than what is implemented in a browser 09:20:14 …it's a different question; a kind of answer to Glazou 09:20:23 …I am not talking about RDF rules that are out there 09:20:35 …there are long-standing discussions that are out there 09:20:39 ack bi 09:20:48 …To be honest, David, I'm not sure if there are any standards that we can use right away in this world 09:21:02 Bill_Kasdorf: To get back to consensus on fundamental terms and concepts 09:21:05 r12a has joined #dpub 09:21:13 …we need to understand what we mean by publication 09:21:17 …and if PWP is that definition 09:21:20 q? 09:21:24 chunming has joined #dpub 09:21:36 …a publication is collection of resources... 09:21:43 q? 09:21:48 [5:14 in minutes 09:22:04 …pointing out that a PWP is a particular type of publication, it's a web publication and it's portable 09:22:09 q+ 09:22:16 ack Tzviya 09:22:16 tzviya, you wanted to say that this are publishing specific use cases that can be applied to other things, like apps and games 09:22:17 ack tzviya 09:22:18 ack q 09:22:24 Tzviya: thank you, Bill 09:22:24 ack t 09:22:41 q+ 09:22:44 …this is not specific to publishing; if we can work on something that is usable for publishing and games and apps 09:22:51 q? 09:22:51 q- 09:22:55 ack m 09:22:55 marcosc, you wanted to address the SemWeb stuff should be built with userland primitives 09:22:59 …and a second doc that is specific to publishing then we will be in a good place 09:23:08 Marcosc: I wanted to say 09:23:12 q+ I'm curious about the use of offline for payment apps 09:23:15 Suggestion: A publication is a resource or collection of resources with a persistent identity that enables interchange and reference. A PWP is a web publication, and it's portable. 09:23:24 q+ 09:23:24 …it's all great and fine to explore deeper meanings of de-referencing URIs 09:23:26 of ffff 09:23:28 q- 09:23:30 …and this can be done in @ land 09:23:37 …but do we have enough stuff in the web platform to do that 09:23:38 dauwhe_ has joined #dpub 09:23:43 …to fetch API and so on 09:23:47 …is it in the DOM 09:23:53 …you can do 09:24:06 …is there enough in the browser; we'll need to experiment with these things 09:24:14 …had a hard time hearing the definition of publications 09:24:22 …i did like hearing about a resource 09:24:26 …interesting 09:24:29 @jakeA - we’re not talking about apps here, though…so not sure what you are thinking. 09:24:38 Tzviya: The definition that Bill proposed is a few lines up 09:24:45 lrosenth: I was thinking "ooops wrong window" 09:24:48 …others can review that also 09:24:53 [Tzviya rereads] 09:25:03 …We can come back to what portable means later 09:25:05 ack Garth 09:25:07 ack g 09:25:12 Garth: I think it was Boris who pasted in 09:25:17 …the abstract definition 09:25:21 …we are dancing a bit 09:25:28 …that definition is fine 09:25:33 …the exciting discussion 09:25:35 …on the issues 09:25:39 …I am going to repaste 09:25:47 …PWP definition 09:25:55 …I look at this 09:26:18 …we understand much of things; draw a line between top two and bottom three 09:26:24 Garth points to http://w3c.github.io/dpub-pwp-ucr/#h-abstract 09:26:27 q+ to say that I was not proposing the adoption of SemWeb standards per se; instead, I was suggesting that a PWP is a form of cache which could/should have a canonical URL (perhaps a 303 PURL to a publisher-controlled document described with Web Annotations in Dublin Core metadata). In other words, we can compose many existing standards and best practices to create a DPub-specific approach. 09:26:27 …after listening to Marcos' comments on the issues 09:26:38 …I think there is a contingent that wants to drop the first two of those 09:26:48 …i think Ivan or Tzviya raised that we are all in agreement in the bottom three 09:26:53 …that we expect browsers to do 09:27:04 …render this thing in its full print fidelity and it will be awesome 09:27:13 …and there is a community, probably coming from EPUB 09:27:17 …looking at market 09:27:20 …as it is today 09:27:22 q+ 09:27:30 …looking at a snapshot, selling to a vendor 09:27:34 …may or not be rendered 09:27:38 …so I could make an argument 09:27:45 Lhulse has joined #dpub 09:27:55 …that maybe those top two are clearly within the scope and are important 09:28:00 …invite publishers in room to chime in 09:28:11 …maybe the bounded and packaged media part is not meant to be implemented by brosers 09:28:16 …maybe its P,WP 09:28:18 +1 to @garth and his comments 09:28:21 …the support piece that we define 09:28:24 …it's a mission 09:28:31 …and then the WP and we define that as well 09:28:32 q+ 09:28:34 q+ then we need to show that EPUB and friends are not enough to the the "P" part. 09:28:37 …maybe if we an define that 09:28:42 Tzviya: I will jump the queue 09:28:48 …had a conversation with Dave last week 09:28:53 …perhaps this is the better perspective 09:28:59 q+, to discuss that EPUB and friends are not enough to the the "P" part. 09:29:02 …a lot of us working in publishing for a long time 09:29:11 q+ 09:29:12 …is where do we draw line between author and reading system requirements 09:29:28 …what is the magic that the user agent does and what we are writing that comes down to publisher requiremetns 09:29:45 …so are we talking about something that the publisher has to build into it, or is it the reading side 09:29:50 ack m 09:29:53 …that is fundamentally what we are arguing about 09:30:02 ack Marcos 09:30:13 q? 09:30:16 Marcos: you eventually end up why current formats are @ 09:30:26 …do all these things 09:30:32 ack d 09:30:32 david_wood, you wanted to say that I was not proposing the adoption of SemWeb standards per se; instead, I was suggesting that a PWP is a form of cache which could/should have a 09:30:36 ... canonical URL (perhaps a 303 PURL to a publisher-controlled document described with Web Annotations in Dublin Core metadata). In other words, we can compose many existing 09:30:36 ... standards and best practices to create a DPub-specific approach. 09:30:45 q? 09:30:45 ack Glazou 09:30:52 Glazou: I have two important concerns to express 09:31:01 …the first one is related to the proposal that Bill posted 09:31:05 [rereads] 09:31:14 …I am particularly surprised 09:31:19 …we don't even mention publishing 09:31:25 q+ 09:31:28 …a publication has to be edited and published 09:31:40 …making a resource and making it able to publish technically speaking 09:31:49 Bill: that is what I mean by interchange and reference 09:32:09 q+ 09:32:14 sam has joined #dpub 09:32:16 Glazou: we are still discussing the main word of the charter of this group 09:32:20 …it's important enough to be noted 09:32:27 …it seems that that work should be done before 09:32:32 …immediately before the publication itself 09:32:46 …we are still at the point of the WG and IG are not well defined 09:32:50 …we are not at that point 09:32:58 Ivan: just to answer Daniel 09:33:01 …we have to be precise 09:33:07 …this work was not chartered two years ago 09:33:15 …it was charted when we recharted a year ago 09:33:30 Glazou: the date on the charter is 31 August 2015 09:33:40 Ivan: The other point is to make very clear 09:33:47 …we did have a long discussion about the terminology 09:33:51 …we ended up with documents 09:33:54 q? 09:33:55 …for good or for worse 09:33:58 …this is the first time 09:34:08 …when the non-publisher community got interest in what we are doing 09:34:21 …and we began to have feedbacks and thank you Marcos 09:34:27 …we were having our internal discussions 09:34:35 …and now we are discussing because we have feedbacks 09:34:42 …I don't see that as a problem for an IG 09:34:46 David_Wood: To clarify 09:34:54 q? 09:34:57 …I put some notes in irc about the relation in my mind as a Web developer 09:35:02 …for a PWP 09:35:19 …hope you will look up those things up and speak with me and tell me where you think I'm wrong 09:35:20 q+ 09:35:21 ack bi 09:35:24 ack Bill_Kasdorf 09:35:30 Bill: Back to what Garth was pointing out 09:35:34 …which I very much appreciate 09:35:40 …one way to get closer to consensus 09:35:46 …is between the first two items and the last three 09:36:06 …if PWP must be able to be bounded and to be portable, distinct from it is bounded and it is portable 09:36:06 The five attributes of a PWP: http://w3c.github.io/dpub-pwp-ucr/#h-abstract 09:36:15 …the publication in the sense it's not a thing 09:36:17 Perhaps the first two are the "P" and the latter three are a "WP" 09:36:29 …that it's able to bounded and interchanged as a thing but cannot exist as a thing 09:36:33 @garth - I suggested that same thing in the github threads… (so +1) 09:36:38 …decades of history in publishing 09:36:49 …what we are srtuggling with here 09:37:03 …what is intellectual publication distinction 09:37:17 …what we are saying is that that intellectual publication, we want a PWP to identify that thing 09:37:29 ack bo 09:37:30 ack boris_anthony 09:37:37 Tzviya: We are not talking about what is a book and we are not branching into HPPT214 09:37:50 Bill: Reacting to able to be 09:38:06 s/HPPT214/HTTP-14/ 09:38:07 Boris: Some reps come in saying these are musts vs coulds or shoulds 09:38:19 …My question back to Garth's statement 09:38:24 laurentlemeur has joined #dpub 09:38:26 …we need to be clear what are the things we actually want 09:38:36 …to come back to separation of portable bounded 09:38:46 …I want to understand what we need browsers to do to be portable and bounded 09:38:49 q? 09:38:58 …URI, the constituent parts, and navigation of that content 09:39:08 …when I open URI, what does the browser do for me 09:39:18 …is it a feature they killed 15 years ago; index next and back 09:39:28 ack iv 09:39:30 …what is it we need to be portable and bounded; clarify that 09:39:37 HTTP Range-14 for those interested: https://www.w3.org/wiki/HttpRange14Webography ; short course at https://en.wikipedia.org/wiki/HTTPRange-14 09:39:37 Ivan: I want to get back to question of Marcos 09:39:43 …that you asked on one of issues as well 09:39:44 q? 09:39:49 …If you are talking about package 09:39:54 …why do we touch EPUB at all? 09:40:00 …which is a fair question 09:40:07 …what we do with Web publicaitons 09:40:20 …I think the main issue is that what we want to ensure is a smooth connection between the two 09:40:24 …a smooth transition 09:40:34 …if we unpackage; may be outdated in its structture 09:40:39 …maybe publishers will kill me 09:41:03 …but what I want to see is whatever the structure is, it makes it an easy interchange between what browsers can do on the web regardless of packaging 09:41:08 …that is where there is a disconnect 09:41:08 q+ the challenge is that things break when you change from one security model to another 09:41:16 …EPUB has been looked at from 09:41:21 q+ to the challenge is that things break when you change from one security model to another 09:41:27 …Looked at browser manifestation 09:41:31 …too many things would require change 09:41:36 …the issues that are there with EPUB 09:41:53 …if we definte a structure for publication about what browsers can do and they can do 90 percent of it 09:42:11 …and then we look at EPUB and deconstruct it and reconstruct it and make it compatable 09:42:18 …When I turned script into EPUB 09:42:35 …I had to do a long Python script to do that, to publish in EPUB because I had to adapt to what EPUB was requiring 09:42:41 …this should have been a smooth thing of two to three lines 09:42:48 Tzviya: We are supposed to break soon 09:42:56 q? 09:42:57 ack lr 09:43:03 …we have four people on the queue; you each have half a minute 09:43:28 Leonard; Part of my reason to join this group is to expand the definition beyond a curated definition 09:43:33 …no formal curation process 09:43:38 …that is one of limitations of EPUB today 09:43:55 …it is focused on the needs of professional publishers, which it was designed for 09:44:06 …but we should address the needs of any publisher on the web today 09:44:10 Rebecca; That's fine 09:44:13 ack g 09:44:19 ack re 09:44:24 Garth: I cannot help myself that you can do EPUB and Google docs 09:44:32 …thank Ivan for what he said 09:44:37 …that gets to the heart of the issue 09:44:50 …I thought I was on the precipice of what Marcos said 09:44:57 …EPUB is not solution for that and invent something new 09:45:06 …as we interate on the bottom three and what a publication is 09:45:16 …may run to @…doubt it would be .mobi 09:45:20 …maybe related to PDF 09:45:24 …round tripping 09:45:27 ack ma 09:45:27 marcosc, you wanted to the challenge is that things break when you change from one security model to another 09:45:30 …love if Marcos would say this makes sense 09:45:40 Marcos: challenge with going from one to the other 09:45:45 …from on web to packaged 09:45:50 …and need to change security model there 09:46:13 …those in HTTPS world it does affect how the APIs in web browsers work because they are tied to the same origin policy 09:46:15 I suggest a layered definition: What is a publication? What is a web publication? What is a portable web publication? 09:46:23 …down to origin that these things may break 09:46:35 …there is going to have to be some kind of tradeoff 09:46:39 …how dynamic to be 09:47:03 …I hope we can treat all of the web as publications and not have monolithic descriptions 09:47:06 q+ 09:47:11 …there will continue to be issues; some outlined in GitHub 09:47:24 Tzviya: Marcos, thank you very much for joining us 09:47:30 …we will address this again tomorrow 09:47:36 …we will take a break now 09:47:41 Must/Can - web users/browsers have always been ok with “breakage”… publishers and epub world … ready to accept that? 09:47:42 …and hope to dive into the actual issues tomorrow 09:47:48 …this has been a productive conversation 09:48:03 ack b 09:48:07 …as Boris reminds us, important not to get too far into the weeds as we are focused on use cases now 09:48:07 q? 09:48:14 …we will continue the discussion tomorrow 09:48:24 …we'll meet back here in 10 minutes to speak with WCAG WG 09:48:27 …they will come here 09:48:33 rrsagent, draft minutes 09:48:33 I have made the request to generate http://www.w3.org/2016/09/19-dpub-minutes.html Karen 10:00:42 rego has joined #dpub 10:01:34 rdeltour has joined #dpub 10:02:46 chu has joined #dpub 10:12:44 dauwhe has joined #dpub 10:14:57 laurentlemeur has joined #dpub 10:15:26 Lhulse has joined #dpub 10:15:26 tviaya: joint meeting of WCAG and DPUB…need to get to lunch so starting... 10:15:40 Kathy has joined #dpub 10:15:43 AWK has joined #dpub 10:15:47 david_wood has joined #dpub 10:15:48 skipping introductions - so we can get work done 10:15:48 JF has joined #dpub 10:15:57 present+ Kathy 10:15:59 mhakkinen has joined #dpub 10:16:00 Kepeng has joined #dpub 10:16:05 Andrew and Josh co-chair WCAG 10:16:10 alastairc has joined #dpub 10:16:11 no one on the phone 10:16:29 takeshi has joined #dpub 10:16:33 agenda: https://www.w3.org/dpub/IG/wiki/Detailed_TPAC_2016_Agenda#Meeting_with_WCAG 10:16:52 David_MacDonald has joined #dpub 10:16:54 Rachael has joined #dpub 10:16:59 brady gets to relax - no micrphones needed... 10:17:32 publishing has great interest in WCAG and @avneesh is leading the effort to on accessibility and DPUB 10:17:43 Topic: Joint meeting with WCAG WG 10:17:51 DPUB accessibility note: 10:17:52 acc checker discussions 10:17:52 https://w3c.github.io/dpub-accessibility/ 10:17:57 apologies but without the microphone I cant hear what is going on 10:18:00 David MacDonald here from WCAG 10:18:08 http://w3c.github.io/dpub-accessibility/index.html 10:18:20 Rebeca has joined #dpub 10:18:40 avneesh: George, Charles & Avnessh will lead the discussions 10:19:02 jeanne has joined #dpub 10:19:25 George: our people with one foot in PWP and one foot in EPUB 10:19:31 scribenick: lrosenth 10:19:40 from the beginning WCAG is fundemantal 10:19:58 to EPUB and publications to date 10:20:12 thanks 10:20:47 here’s Charles about the note on DPUB and WCAG, overlaps and deficiencies concerning publications 10:21:01 Joshue108 has joined #dpub 10:21:11 Charles: Acc TF charges with review of WCAG and what is missing... 10:21:23 s/Acc/A11y 10:21:24 …published note in May on what they found 10:21:33 bobbytung has joined #dpub 10:21:36 glazou has joined #dpub 10:21:52 …navigation of an ordered collection is a key item 10:22:11 …page markers and pagination is another area (aka locators?) 10:22:13 Paul_B has joined #dpub 10:22:17 Joshue108_ has joined #dpub 10:22:35 …but this may not equate to a printed version (but if there is, they should connected in some way, esp for students) 10:23:23 …phonetic spelling of proper names is important (as defined by author/publisher) 10:23:43 laurentlemeur has joined #dpub 10:24:06 q? 10:24:10 …discoverability of whether a given publication meets their A11y needs. (this info should be searchable and discoverable before any possible purchase) 10:24:35 …skippabiity and escapability. DAISY addresses these but not WCAG. 10:24:51 …for example, how to exit an equation and move to next item in reading order 10:25:12 …there may also be issues with Math and Annots - but early days there. 10:26:03 Avneesh: coming from EPUB, it uses OWP incl HTML and therefore leveraging WCAG. 10:26:18 …but it also has the same drawbacks of standard web pages 10:26:41 …so we need (in EPUB) a way to make A11y a first class citizen (requirement) 10:27:10 …but how to leverage WCAG and not create a new specification particular to EPUB? 10:27:30 for the record, the EPUB A11y spec 10:27:31 http://www.idpf.org/epub/a11y/accessibility.html 10:27:33 EPUB 3 A11y Docshttp://www.idpf.org/epub/a11y/accessibility.html 10:27:36 …So EPUB spec starts with WCAG and then adds stuff specific to EPUB 10:28:23 http://www.idpf.org/epub/a11y/techniques/techniques.html 10:28:36 …this is already in place and now look to move from EPUB to PWP, how can we move thse things to WCAG 10:28:58 …and what about certification? 10:28:59 https://www.w3.org/TR/wcag2ict/ 10:29:07 q? 10:29:25 DAISY is taken on certification as well as an A11y checker, that will be used for certification 10:29:44 …spec->best practices->A11y checker 10:31:07 …two great items: (1) collection of documents, currently in EPUB3, (2) discovery (metadata) 10:31:21 …discovery is collaboration with schema.org 10:31:36 https://www.w3.org/TR/wcag2ict/#keyterms_set-of-documents 10:31:56 ...other items: page markers and skipping that shoudl be incorporated into WCAG 10:32:27 …and let’s not forget media overlays and how they can be accessible 10:32:55 liam has joined #dpub 10:32:56 ..but the two items are the big ones we want to focus on 10:32:57 q+ to ask about certificication. 10:33:38 George: it has been difficult for professors to pick an A11y compliance title. having the metadata will enable this use case 10:33:57 …with info about what standards it complies to and perhaps a description 10:34:07 ack jo 10:34:07 Joshue108_, you wanted to ask about certificication. 10:34:15 Josh: thanks! 10:34:30 …questions about certifications esp about WCAG. 10:34:33 q+ to talk about where WCAG is and has been, and where it is heading 10:34:41 …what features, by whom and for what purpose 10:34:50 q+ 10:34:50 George: “conforms to” 10:35:04 see http://pending.schema.org/ 10:35:19 …would also include “who” is making the claim, and if there is any confirmation of claim 10:35:36 …publishers will build their own tooling 10:35:56 …but the process is important, since A11y involves both machine and human validation. 10:36:28 …for example, humans to check images 10:36:42 Josh: so do you require anything form WCAG for that? 10:36:47 rrsagent, draft minutes 10:36:47 I have made the request to generate http://www.w3.org/2016/09/19-dpub-minutes.html ivan 10:36:50 ack a 10:36:50 AWK, you wanted to talk about where WCAG is and has been, and where it is heading 10:37:10 Thanks George and Avneesh 10:37:15 AWK: might be helpful to talk about WCAG is at, where its been and where it is going… 10:37:30 q+, to talk about a11y checker tool 10:37:31 …but it looked like from the note that the gap analysis was more about the techniques 10:37:48 …but we know there are many things for which there are not technique (and this may always be the case) 10:38:07 …but if there missing sucess criteria for DPUB, that they get addressed 10:38:16 …WCAG since 2008 and large adoption 10:38:19 SONG has joined #DPUB 10:38:28 …it is a minimum bar, not a “serve everyone” 10:38:31 q+ to talk about a11y checker tool 10:38:32 q? 10:38:50 …there is AA and AAA, but there are still gaps. (for example, mobile) 10:39:12 …touch, DPUB, cognitive, low vision etc. 10:39:25 …WCAG chartered to work on extensions 10:39:45 …but there is a potential problem there with disconnnects between them 10:40:01 …what happens if you want to use a combination that are in conflict with each other 10:40:15 …one single standard for apps, pubs, etc. 10:40:34 …proposing to recharter towards WCAG 2.1 with all these various aspects included 10:40:47 …doing a dot release in the meantime 10:40:53 …but what do we do wiwth larger issues 10:41:18 …WCAG is currently focused on content, but things like escapability is more about the UA. 10:41:33 …so not sure what would make 2.1 or would come after that? 10:41:41 q? 10:41:55 …trying to increase speed of work, esp. with techniques (now eery 6 months) 10:42:01 …but moving to continual 10:42:09 hober has left #dpub 10:42:16 …so if that is all you needed, that ould be easy 10:42:18 ack d 10:42:58 David: Are you aware of the WCAG2ICT document? (links above) 10:43:13 …there is some material there about how WCAG applies to documents, so please look at it 10:43:17 https://www.w3.org/TR/wcag2ict/ 10:43:47 …also a link to “set of documents” above, so please reivew that 10:44:00 …glad to hear that human intervention is a key aspect of conformance 10:44:31 …in the web world, everybody says they comply with WCAG - but it’s not always true. 10:45:02 …most publishers will just “check the box”, so be aware 10:45:12 …what are you “success criteria” for this project? 10:45:26 q+ to respond to David that clients are already hiring accessibility consultancies to certify 10:45:27 …WCAG 2.1 is focused on such criteria and it would be good to align yours with ours 10:45:50 AWK: time for next version is mid-2018 (but not yet chartered) 10:45:55 VST-Rick has joined #dpub 10:46:04 q+ 10:46:13 …looking for those criterias by December to work from 10:46:30 …in terms of conformance claims, there is disc. in WCAG (but they are optional) 10:46:49 …we haven’t discussed if we want to change that for 2.1 10:47:11 …might be just as effective in a different context (eg. contract) 10:47:44 avneesh: such things currently being driven by DAISY, in concert with IDPF 10:48:06 ack rd 10:48:06 rdeltour, you wanted to talk about a11y checker tool 10:48:08 …DAISY OK stamp 10:48:29 rdeltour: A11y checker is for EPUB, but how relavent for this group? 10:48:32 …it’s not! 10:48:49 …it’s just an assistant to the process but coudl be done entirely by humans 10:49:20 …but what is important, is to join the ACT TF and contribute to the rules that go beyond “the web” towards DPUB/PWP 10:49:28 ack je 10:49:28 jeanne, you wanted to respond to David that clients are already hiring accessibility consultancies to certify 10:49:40 rdeltour has joined #dpub 10:49:45 Jeanne: work for A11y consulting firm and getting requests to certify ebooks. 10:49:54 ack r 10:50:03 Rick: clarification please. 10:50:04 jlee27 has joined #dpub 10:50:22 …in conversations with laywers, “prove you can do this”. 10:50:38 …fortunately WCAG is becoming a standard around the world, esp. the US 10:50:58 …but there is still some fuzzyness about “what has to be in/with the document” and what does the UA/RS do? 10:51:03 q+ 10:51:04 bobbytung has joined #dpub 10:51:11 ack vs 10:51:16 ack a 10:51:22 …but it is clear in the marketplace that talking about the file is more well defined, but the UA/RS not so much 10:51:25 q+ 10:51:29 q+ 10:51:48 AWK: the initial idea was that each of these thigns (as well as authoring tools) woudl be separate guidelines 10:52:02 …but that the others (such as UA/RS) havent moved forward 10:52:23 …as part of the claim, you have to include all the tools up the chain 10:52:46 …most folks don’t test against every platform, tool, reading system, etc. 10:53:07 …not going to change for 2.1 but for “next major version”, this could well be somethign important to incorporate 10:53:27 …as we look at the larger set of guidelines 10:53:39 …users just want to be able to “I did this, so I am OK" 10:53:58 …but that does indeed mean we need UA guidelines too... 10:54:13 Rick: interesting convergence of EPUB PWP etc. coming together 10:54:28 …and we also want folsk that want/need to test and verify these things 10:54:46 …customers want to be able to point to claims and understand how to validate 10:55:19 tviya: cutting off the queue in favor of next steps 10:55:39 ack av 10:55:49 avneesh: we would really like our things in the main doc and not extensions 10:55:56 q- 10:56:27 …will have to come up with those success criteria. 10:56:33 …is there a new TF to be formed is there is another way? 10:56:50 AWK: WCAG is not able to support another TF, even though we hve interest 10:57:30 avneesh: techniques first? would that be a place to start? 10:57:43 Josh: sure, that would be a good place to start 10:57:56 …people need to know how to do the work in their environments 10:58:10 …and fit into existing workflows 10:58:35 AWK: if youve got suggestions - post it and send us the link for review 10:58:41 techniques: http://www.idpf.org/epub/a11y/accessibility.html#refA11YTech 10:58:50 …this is a lightweight and straitforward process 10:59:28 correct link to techniques: http://www.idpf.org/epub/latest/accessibility/techniques 11:00:06 tzviya: let’s have a joint call since we have a document already 11:00:16 …will send this to the WCAG list 11:00:31 …this is specific to EPUB, not to DPUB or PWP 11:00:53 https://www.w3.org/WAI/GL/wiki/WCAG_2.1_Success_Criteria 11:01:12 jnurthen has joined #dpub 11:01:36 the link above is to what a Success Criteria is and what is required to propose a new Success Critera 11:01:40 rrsagent, make minutes 11:01:40 I have made the request to generate http://www.w3.org/2016/09/19-dpub-minutes.html jnurthen 11:02:02 lrosenth & tzviya: will work out whether it is EPUB or DPUB group that will be collaborating here 11:02:32 Theres also an SC template https://github.com/w3c/wcag21/issues/1 11:02:49 MichaelC has joined #dpub 11:02:52 will be meeting with CSS after lunch - 1 hour(!) 11:03:29 MichaelC has left #dpub 11:04:49 ivan has joined #dpub 11:04:50 rrsagent, draft minutes 11:04:50 I have made the request to generate http://www.w3.org/2016/09/19-dpub-minutes.html Karen 11:08:38 HeatherF has joined #dpub 11:12:19 jangkunblog_ has joined #dpub 11:19:25 pkra has joined #dpub 11:19:49 clapierre has joined #DPUB 11:20:04 clapierre1 has joined #DPUB 11:25:52 dauwhe has joined #dpub 11:41:59 sam has joined #dpub 11:42:16 rego has joined #dpub 11:44:56 dauwhe has joined #dpub 11:53:22 rdeltour has joined #dpub 11:56:41 dauwhe has joined #dpub 11:57:18 chaals has joined #dpub 11:58:19 clapierre has joined #DPUB 12:03:55 alastairc has joined #dpub 12:07:08 liam has joined #dpub 12:07:23 tzviya has joined #dpub 12:08:01 ivan has joined #dpub 12:08:53 glazou has joined #dpub 12:09:10 bobbytung has joined #dpub 12:09:14 david_wood has joined #dpub 12:09:18 duga has joined #dpub 12:09:21 Florian has joined #dpub 12:09:37 Karen has joined #dpub 12:10:49 Bill_Kasdorf has joined #dpub 12:11:02 takeshi has joined #dpub 12:11:17 Florian has joined #dpub 12:11:17 HeatherF has joined #dpub 12:11:54 lrosenth has joined #dpub 12:13:18 jnurthen has joined #dpub 12:17:31 jamesn has joined #dpub 12:19:07 pkra has joined #dpub 12:27:23 glazou has left #dpub 12:29:36 jeanne has joined #dpub 12:37:35 jeanne has left #dpub 12:46:50 boris_anthony has joined #dpub 12:47:40 bkardell_ has joined #dpub 12:54:11 laurentlemeur has joined #dpub 12:59:21 dkaplan3 has joined #dpub 13:15:36 sam has joined #dpub 13:20:08 laurentlemeur has joined #dpub 13:20:25 pkra has joined #dpub 13:21:23 laurentlemeur has left #dpub 13:22:46 Zakim has left #dpub 13:24:25 darobin has joined #dpub 13:28:15 Karen has joined #dpub 13:33:45 olivexu_ has joined #dpub 13:43:43 Bill_Kasdorf_ has joined #dpub 14:03:01 HeatherF has joined #dpub 14:12:58 HeatherF has joined #dpub 14:16:12 pkra has joined #dpub 14:18:29 jamesn has joined #dpub 14:19:24 boris_anthony has joined #dpub 14:23:11 bobbytung has joined #dpub 14:23:50 duga has joined #dpub 14:26:16 clapierre has joined #DPUB 14:27:13 rdeltour has joined #dpub 14:27:37 ivan has joined #dpub 14:28:01 trackbot, start telcon 14:28:03 RRSAgent, make logs public 14:28:03 Zakim has joined #dpub 14:28:05 Zakim, this will be dpub 14:28:05 ok, trackbot 14:28:06 Meeting: Digital Publishing Interest Group Teleconference 14:28:06 Date: 19 September 2016 14:28:40 VST-Rick has joined #dpub 14:28:42 rrsagent, draft minutes 14:28:42 I have made the request to generate http://www.w3.org/2016/09/19-dpub-minutes.html ivan 14:31:11 chair: garth 14:31:11 scribenick: duga 14:31:44 garth: agenda is recap and overflow. Overflow could take an hour. 14:32:10 ... wcag and regions discussion - any recap or questions? 14:32:14 david_wood has joined #dpub 14:32:30 present+ David_Wood 14:33:18 ... Recap from css: media queries, we got action and decision 14:33:39 HeatherF has joined #dpub 14:33:50 ivan: Media query for presence of mathml is accepted, but it is not clear when it will really appear in UAs 14:34:11 alastairc has joined #dpub 14:34:41 garth: Interesting thing was API for JS to tell UA that support really does exist (polyfill support) 14:35:16 ivan: Florian has an action to make a specific proposal for the spec 14:35:28 george: What does this mean for a publisher? 14:36:10 ivan: Publisher can put in an image element and mathml, then add css that say "if mathml is present, show the mathml, if it is not present then show the image" 14:37:46 : mathml is still in the dom, just not displayed (no css boxes). Would default to image. 14:38:36 tzviya: document is forthcoming, we will see the specifics when florian is done 14:39:14 pbelfanti has joined #dpub 14:39:29 george: In a11y spec, don't really know what to do with math now. We could just use this as the receommendation? 14:39:51 ivan: Depends. It still has a long path to implementation. 14:40:25 george: But the default is image, so we are fine, right? 14:40:50 q+ 14:40:55 Rebeca has joined #dpub 14:41:05 ivan: But it will drop the mathml for a current reading system, since it won't know about the media queries 14:41:27 george: summary from some meeting (apa?) 14:41:52 s/some meeting (apa?)/APA Meeting 14:41:57 https://github.com/w3c/html/issues/561 14:41:59 ... Want to make sure ARIA details are available for everyone 14:42:01 garth has joined #dpub 14:42:21 q+ 14:42:46 q? 14:43:12 ... Came up with media query to determine if nothing was shown, whether there was some indication of the ARIA details, and whether the details would be shown or not shown depending on the query 14:43:21 HeatherF has joined #dpub 14:44:09 ... the semantics with aria details is that there is an associated extended description 14:44:16 Florian has joined #dpub 14:44:30 s/aria details/aria-details 14:44:38 david_wood: What about implicit aria semantics? 14:44:55 https://www.w3.org/TR/2016/WD-wai-aria-1.1-20160317/#aria-details 14:45:21 george: if the role == presentation then it is not even in the a11y dom 14:45:42 q? 14:45:45 tzviya: aria-details is not a role, it is a property that is always explicit 14:46:08 ... can add an extended description to any element 14:46:38 q- 14:46:43 lrosenth has joined #dpub 14:47:13 tzviya: 2 questions - did Michael provide the requirements grid? 14:47:19 george: Yes 14:47:59 tzviya: This started with an issue on the css issue tracker, was there discussion about moving this out of css? 14:48:46 george: some time was spent on that, but they didn't get to a place where a browser could display anything 14:49:17 Bill_Kasdorf_: Is the description external? 14:49:25 george: only on the existing document 14:49:33 avneesh: could be external 14:49:49 george: Yes can internally point to an external thing 14:50:24 q+ 14:50:47 garth: How does it work? 14:51:04 george: aria-details="#abc" 14:51:20 ... somewhere there is an abc 14:51:31 ... abc could be a link. 14:51:46 tzviya: But may not be supported (external links) 14:51:56 lrosenth_ has joined #dpub 14:51:57 q- 14:51:59 ... need to work with html or css folks and making this work 14:52:24 ivan: Too close to long-desc, so we really have to get it working 14:52:34 ... from a political standpoint 14:52:51 david_wood: PWP could get difficult if not live on the web 14:53:12 garth: Back to external resources and packaging, general problem 14:53:36 Bill_Kasdorf_: could imagine pointing to external audio file 14:53:42 george: yes 14:54:19 ... made clear that publishing community does not see aria as only for disabilities. Anyone could see this if they want 14:54:38 hjlee has joined #dpub 14:54:43 ... example: webgl rotating heart, with a description for a 3d printer model for it 14:55:03 ... made very clear that everyone could find it. One complaint about long-desc 14:55:22 ... the other thing was in the diagrammer model there are many alt descriptions 14:55:45 ... [tactile, etc] 14:55:57 ... depending on settings, one or more of these might be selected 14:56:23 ... ETS example: low vision needed a description and needed simplified language 14:56:32 ... pick from the list and present it 14:57:09 ... there was vehement advocacy for the MQ to provide personalization in the type of resource that was available to provide 14:57:12 q+ 14:57:53 romain: Can just use a css selector to display the correct item 14:58:18 ivan: until the aria comes to agreement with css and html wgs, we can not really rely on it 14:58:21 s/diagrammer/diagrammar/ 14:58:25 http://diagramcenter.org/standards-and-practices/content-model.html 14:58:43 ... hope there is an action item on resolving with those groups 14:58:50 ... otherwise this feels unfinished 14:59:25 romain: talking about what "we need to do 14:59:37 ivan: Who is "we"? Very important question 15:00:06 romain: What to do with the description is not clear 15:00:39 q? 15:01:11 romain: Polyfill could look for the attribute, then display the icon and display the description when it is clicked/selected 15:01:26 ... maybe we could create the polyfill and see if ti solves the issues 15:02:00 lrosenth: Need to understand what the correct UX is for various groups and documents 15:02:00 q- 15:02:22 ... exploring is a good thing to do 15:02:42 george: Rich was saying MQs were at the OS level 15:02:58 garth: Not sure that is right 15:03:34 ivan: Not sure if what Rich was saying was facts or wishful thinking? We are getting contradicting reactions 15:03:50 george: Also heard about the MQ for mathml 15:04:04 Karen has joined #dpub 15:04:15 ivan: The mathml was easy, this sounds harder 15:04:42 tzviya: Needs fleshing out 15:05:09 ... need to get response of css wg first to understand what will happen here 15:05:32 romain: need customizable MQ 15:05:46 lrosenth: heard at css wg that worried about privacy 15:06:16 chaals has joined #dpub 15:06:40 avneesh: 2 uses of MQ - toggle and user customizability 15:06:56 garth: Is that all? 15:07:15 ... other 2 topics at css 15:07:41 ... hanging-punctuation discussion. Are used in Japan, but not by epub 15:07:58 ... may get deferred to level 4, leaving at-risk for now 15:08:14 ... long presentation of grid layout and regions 15:08:17 rego has joined #dpub 15:08:33 Publishers in the room started salivating over the idea of grid layout and regions. 15:08:37 ... Nice flow stuff, there was a proposal, but with some pushback from vendors 15:08:39 https://speakerdeck.com/jensimmons/proposal-to-csswg-sept-2016 15:09:03 ... long term, but of interest to people in this room 15:09:33 david_wood: coordination with html wg: if we think we are waiting on them, do they know? 15:09:53 ivan: There are open issues, but don't know what the priority is 15:10:06 tzviya: I am working on the behind the scenes side 15:10:21 ... they are really busy, so hard to talk to them 15:10:37 Florian_ has joined #dpub 15:10:51 lrosenth: Do you want a quick report about the image stuff in css? 15:10:54 garth: yes 15:11:14 lrosenth: Topic was HDR high dynamic range images as it relates to color 15:11:21 ... What are the problems? 15:11:46 ... css 4 color spec has everything you need, but going forward have to move from ICC4 to ICC max 15:12:40 iccMAX - http://www.color.org/iccmax-status.xalter 15:12:46 garth: Spoke to Mike Smith (sideshowbarker) 15:13:07 ... explained the 5 layers in pwp 15:13:18 ... some might be browser native, others not 15:13:22 Topic: UCR recap 15:13:25 ... did not get any pushback 15:13:41 Invited him to tomorrows discussion 15:14:07 ... We got somewhere this morning, do we want to reformulate 15:14:11 q+ 15:14:27 ivan: Reformulation brought forward some issues we can't avoid 15:15:10 ... need a section on the concept of multiple documents/resources 15:15:19 ... and need to address online/offline 15:15:35 ... which gets to manifest, etc 15:15:47 ... What exactly is the model for handling a PWP? 15:16:01 ... My model was as much as possible by the browser 15:16:17 ... but there might be some things (eg TOC) which is not of interest to the web as a whole 15:16:37 ... therefore, in my naive thinking there is something you can add to a browser to handle those things 15:17:04 ... I got some sort of pushback from Marcos, extensions are hacky and old 15:17:43 : talking, words words words 15:18:09 lrosenth: wanted to separate browser from browser engine 15:18:23 ivan: You are right and something we will have to do 15:18:56 ... Using my browser, I hit a PWP in my browser and read it (offline even) and not do anything (maybe via extension) 15:19:20 ... other approach is use the engine, but still need an app that is special 15:19:48 ... then there is a second part of the ucr document, we know how it works with the browser 15:20:04 ... for whatever reasons we want a packaged version of the doc, like epub 15:20:25 ... That thing is separate with it's own use cases. 15:20:35 ... That part is independent of the browser 15:20:57 ... Have impression that there is a pushback to get to packaged version from the browser 15:21:11 ... the UCR has to be cut in two along those lines 15:21:28 ... These two areas are subject of separate standards 15:22:00 ... That also gets to a number of technical issues we can put on the table 15:22:30 ... Views Marcos and Mike as canaries. They represent the web community 15:22:46 ... very happy about this feedback 15:23:44 lrosenth: In browser and want to see a PWP. Difference between seeing it with an extension or not 15:23:58 ... for example, Readium is an extension 15:24:10 ivan: No, it is an app, not an extension 15:24:22 billm: don't need to install anything 15:24:36 ivan: App takes over UI, etc 15:24:48 Next time, we really really need to stick with a queue, or do without notes! 15:24:54 ... And other extension don't work with it 15:25:04 lrosenth: Gave Readium too much credit 15:25:28 ... if you have to install anything it is no longer the browser, it is the browser engine 15:25:30 Karen has joined #dpub 15:25:45 ivan: Not what he thinks Marcos was saying 15:26:20 garth: Ivan, you were heading to a place of pro-active tunes to pwp 15:26:38 ivan: Let's not start editing the UCR doc yet 15:27:21 ... work in UCR is separated in two, we need to keep that in mind 15:27:34 garth: is dividing the stack ok as p,wp? 15:27:48 lrosenth: Yes, that is fine 15:28:06 boris_anthony: Presenting 15:28:13 Gus_ has joined #dpub 15:28:44 ... Need to understand the organization and terms 15:29:08 ... maybe we can discuss on Wednesday? 15:29:48 ... What do we think of as a minimum viable pwp? 15:30:11 ... Like minimum viable product from software side 15:31:00 ... we need to outline what these things mean 15:31:32 garth: Need to be careful about cutting back to uninteresting 15:31:43 ... don't want to ship a bad product 15:32:05 ivan: Don't want to reinvent basic web concepts 15:32:40 boris_anthony: Just want to understand how we, in the group, think about thi 15:32:44 ... s 15:33:20 ivan: For me, an example we need is an article in a scholarly journal 15:33:37 ... multiple files, is a publication, needs to be archived 15:33:51 ... might be a single html file, simple css, few images 15:34:03 ... not necessarily complex 15:34:46 boris_anthony: A lot of this comes close to progressive web applications 15:34:53 ... how is pwp different from pwa 15:35:41 ivan: What exactly is pwa 15:35:58 tzviya: we can invite someone at some points 15:36:39 bobbytung has joined #dpub 15:36:44 takeshi has joined #dpub 15:36:50 garth: tomorrow we reconvene at 9 with POE meeting 15:37:33 ... See if we can get Mike to join around 10 or 10:30 15:37:45 ... Chairs will figure it out 15:38:04 ... start with Ivan's hand waving 15:38:14 ... then maybe we can start slicing the UCR 15:38:30 ... then maybe some discussion of some tracker issues 15:39:09 david_wood: Asked if our goal was to produce a format or something beyond it? 15:39:27 ... seems like this is where we were years ago 15:39:50 ... Can't figure out the difference between a web archive and a pwp 15:40:05 ... very confused about what the group is trying to do 15:40:27 garth: our current definition is very close to a web archive 15:41:45 david_wood: Still in the situation of not understanding what the group is doing 15:42:05 ... maybe just myself, but worried that the group doesn't know 15:42:24 tzviya: Interesting perspective, and have called us out on an important point 15:42:54 ... you are hearing differing opinions in the group 15:43:31 david_wood: Was expecting to have consensus by now 15:43:52 tzviya: I have an opinion, but don't want to discuss it now 15:44:02 ivan: Need more time 15:44:16 david_wood: Is it a format or more than a format? 15:44:22 bobbytung has joined #dpub 15:44:22 garth: Is epub a format? 15:44:26 david_wood: Yes 15:44:35 ... ecosystem evolved to use the format 15:45:03 ... is a pwp a format in the hope it will adopted by industry or some is it broader than that? 15:45:12 ivan: I think it is a format 15:45:28 ... just a format bringing EPUB to general web browsing 15:45:46 david_wood: So it a collection of webby stuff 15:46:11 ... how is it different than a web archive? 15:46:29 garth: may well be web stuff packaged in an epub 15:46:42 ... other people might want a different sort of package 15:46:55 ... could be multiple package formats 15:47:38 tzviya: Document is really vague, so it is hard to understand 15:48:16 ivan: difference between pwp and web archive: the use is different 15:48:29 pbelfanti has left #dpub 15:48:39 ... archive is an archive. Publication needs the information the make it readable as a publication 15:48:52 ... things like a TOC for end user, etc 15:49:14 ... may well be the same as web archive spec (if such exists) 15:49:22 ... the user community is different 15:49:42 lrosenth: Other difference, web archive is fully self contained, there is no external comms 15:49:54 ... for pwp there are use cases to reach out for live things 15:50:23 Karen has joined #dpub 15:51:36 rrsagent, make minutes 15:51:36 I have made the request to generate http://www.w3.org/2016/09/19-dpub-minutes.html tzviya 15:57:58 pkra has joined #dpub 16:04:01 alastairc has joined #dpub 16:04:48 alastairc has joined #dpub 16:05:36 alastairc has joined #dpub 16:06:12 duga has joined #dpub 16:06:20 liam has joined #dpub 16:06:26 alastairc has joined #dpub 16:07:12 alastairc has joined #dpub 16:08:01 alastairc has joined #dpub 16:08:49 alastairc has joined #dpub 16:12:19 alastairc has joined #dpub 16:16:12 jamesn has joined #dpub 16:32:14 lrosenth has joined #dpub 16:39:24 lrosenth has left #dpub 16:39:40 rego has joined #dpub 16:52:09 ivan has joined #dpub 16:57:15 liam has joined #dpub 17:19:00 Florian has joined #dpub 17:23:24 Zakim has left #dpub 18:52:38 rdeltour has joined #dpub 19:49:28 ivan has joined #dpub 20:08:36 Florian has joined #dpub 20:25:48 cabanier has joined #dpub 20:27:08 duga has joined #dpub 21:33:24 dauwhe has joined #dpub 21:33:48 Karen has joined #dpub 21:37:43 Florian has joined #dpub 21:50:33 duga has joined #dpub 22:14:03 liam has joined #dpub 22:23:24 bobbytung has joined #dpub 22:32:49 alastairc has joined #dpub 22:48:09 darobin has joined #dpub 23:03:02 dauwhe has joined #dpub