18:35:29 RRSAgent has joined #ebooks 18:35:29 logging to http://www.w3.org/2013/02/11-ebooks-irc 18:35:39 who's scribing 18:35:42 RRSAgent, make logs public 18:35:57 ScribeNick: glazou 18:36:14 thierry: (introducing workshop committee) 18:36:28 … thanks to Marcus and Angela for all hard work and organization 18:36:30 JJ has joined #ebooks 18:36:40 … we have also 19 experts in program committee 18:36:49 … thanks for their hard work reviewing all papers 18:36:53 Meeting: W3C ebook Workshop in NYC 18:36:57 … finally thanks W3C colleagues 18:37:20 … for experience, advice ; Karen for all logistics aspects and Maria at the registration/admin 18:37:27 … a few words about submissions 18:37:38 … we got 43 submission papers that covered many topics 18:37:45 … presentation, metadata, DRM, etc 18:37:48 … we reviewed all 18:37:51 gcapiel has joined #ebooks 18:37:54 … and we built agenda from there 18:38:04 … unable to accomodate everyone because too many papers submitted 18:38:23 … great interest in all the papers but need to have a subset to fit the 1.5 day schedule 18:38:34 plh-ebook has joined #ebooks 18:38:36 … we have 90 attendees representing all sectors of ebook industry 18:38:55 … readers, publishers, SW, distributors, libraries, search engines, A11Y, etc. 18:38:56 JJ has left #ebooks 18:39:10 … participation is also a success because all ey players are here 18:39:19 … (shows companies attending on screen) 18:39:25 Jaejeung has joined #ebooks 18:39:34 … particpation is also international, 13 countries, 4 continents 18:39:49 … will allow to address int'l issues related to ebooks 18:39:53 … About highlights 18:40:10 … the event is divided in 5 sessions, 1 session per topic domain 18:40:19 … (lists all sessions, see agenda) 18:40:23 TomDN has joined #ebooks 18:40:30 … Also a couple of keynotes 18:40:32 gluejar has joined #ebooks 18:40:50 … we want this wkshp interactive so please participate 18:41:00 … we have then scheduled a lot of slots for discussions and feedback 18:41:08 … and also a wrap-up session 18:41:08 using #w3cebook on twitter 18:41:24 … "lead the ebook publishing to its full potential"' 18:41:31 … share info and expertise 18:41:46 … unlikely we'll solve all tech issues but at least we can discuss them 18:41:53 … create new work items specific to ebooks 18:42:17 … where and when to adress the tasks we will discuss: standard bodies or new WGs or or or 18:42:39 TAC_NISO has joined #ebooks 18:42:41 … Karen gave you wifi thingies, use IRC, the slides will be available on W3C site 18:42:53 … there will be bkfst tomorrow, break today is 4-4:30 18:43:00 … lunch not provided tomorrow by W3C 18:43:05 azaroth42 has joined #ebooks 18:43:12 jdovey has joined #ebooks 18:43:17 … all invited tomorrow evening to O'Reilly reception 18:43:35 … thanks to all sponsors of the event: Pearson, Adobe, Google, Microsoft and O'Reilly 18:43:56 … (my slides linked from agenda), thank you 18:44:06 Topic: Keynote - Extending W3C current work, collaboration with IDPF 18:44:08 Karen: introducing Jeff Jaffe, W3C CEO 18:44:24 … we have conti'd to grow under Jeff's leadership 18:44:31 Eric_A has joined #Ebooks 18:44:42 s/Topic: Keynote - Extending W3C current work, collaboration with IDPF /Thierry's slides http://www.w3.org/2012/08/electronic-books/slides/S0-welcome/ 18:44:54 jeff: Thanks Karen and Thierry 18:45:03 … let me be the 2nd to thank everyone 18:45:16 … in particular the host, collaborators and and and 18:45:25 … was asked to do 3 things 18:45:37 … since we're diverse community, first I'll provide an intro about w3c 18:45:45 … second, brief update on recent activities 18:46:03 … for you W3C members, that's not news 18:46:08 … but others need it 18:46:26 … third, some thoughts about why w3c thinks it is important for us 18:46:33 … w3c founded by TBL inventor of web 18:46:38 … still director of w3c 18:46:48 … simple and powerful mission, lead the web to full potential 18:46:55 … good job done but more to do 18:46:56 Valerie has joined #ebooks 18:47:01 … member-based organization 18:47:12 … companies, research, academic, other standards bodies 18:47:21 erikmannens has joined #ebooks 18:47:26 … financial model comes from the largest companies called full members 18:47:33 … all the big names you know 18:47:41 … discussing with the whole ecosystem of the wbe 18:47:48 tmichel has joined #ebooks 18:48:06 … professional staff to support tbl and the dialog with the industry, 70 on staff in 4 locations, latest host in China 18:48:31 … our major goal is to define tech standards 18:48:35 ArtB has joined #ebooks 18:48:46 … tbl did not want companies to innovate alone and create wall gardens 18:48:51 … we then all work together 18:48:58 … contribute innovations and keep it open 18:49:05 … standards available to everybody 18:49:29 … 4 tech domains in W3C: interaction, Ubiweb, a11y, tech and society 18:49:32 … 45 WGs 18:49:44 alexz has joined #ebooks 18:49:48 … html 450 people in the WG, some other WG are much smaller 18:49:55 … liaison with ?? other orgs 18:50:09 With 80 orgs 18:50:11 … royalty-free patent policy is our marjor cornerstone 18:50:37 … we ask members to make royalty)free commitments 18:50:51 … it's more an int'l forum 18:51:02 tzviya has joined #ebooks 18:51:08 … we have relationship with de jure standards bodies too 18:51:21 … lately, we've been working on a collection of standards: open web platform 18:51:24 … many different techs 18:51:26 … html5 18:51:42 … but also css, webapps for apis, fonts, device APIs, etc. 18:51:59 … large contrast with what we had 15 years ago 18:52:03 … rich interactivity 18:52:05 … multimedia 18:52:08 … graphics 18:52:09 duga_ has joined #ebooks 18:52:17 … verye exciting capabilities 18:52:29 … interesting number of different devices 18:52:38 … was difficult to browse the web from a phone 18:52:54 … at CES everyone had a HTML5 set-top box 18:53:03 … the web is now ubiquitous 18:53:19 … making it work everywhere is a feature of the open web platform 18:53:31 … core supporting role for the trends of the industry and society 18:53:51 Sparrowhawk has joined #ebooks 18:53:55 … survey dopne over a year ago, how many developers using html5 18:54:00 s/dopne/done 18:54:04 … now 150% :-) 18:54:24 … how many browsers will html5 in 2016: 2.1 billion 18:54:37 … gartner surveyed tech 18:54:49 … number 2 was mobile apps 18:54:50 How do they know 2.1B? Ran out their 32 bits ;) 18:55:09 … only the beginning 18:55:21 … as we move to next step, impact on businesses is amazing 18:55:31 … we talk to many people in indsutries 18:55:37 … next-gen technology 18:55:49 … business impact : opportunity for dialogs and business change 18:55:55 … should not surprise us 18:56:04 eric has joined #ebooks 18:56:12 opporunity for businesses to change 18:56:13 … looking back, the basic idea of the web transformed sharing of info and al 18:56:39 jeff: what about publishing and the web? 18:56:42 … not strangers 18:56:49 … we publish web sites 18:56:58 … the web is a really nice tool 18:57:05 … introduced a new form of publishing 18:57:13 … able to reach more people in some more open ways 18:57:33 … when publishers needed add'l tools orgs created enhancements of what we're doing 18:57:41 Takeshi has joined #ebooks 18:57:43 … the web has democratized publishing 18:57:50 mgylling has joined #ebooks 18:57:51 … every person is now a publiusher 18:58:13 Jeff_Bell has joined #ebooks 18:58:17 … we reached conclusion we need a more complete robust dialog with publishing community 18:58:29 … if we have a better dialog, we can make thinbgs happen better 18:58:38 s/publiusher/publisher/ 18:58:51 … let's be at the front-line of publishing and web technology 18:59:05 … I'll talk about it at TOC on wednesday 18:59:15 … I'm going to listen and learn today and tomorrow 18:59:23 … and will be your spokesperson at TOC 18:59:39 … will just mention a few high-level thoughts 18:59:42 … 4 categories for better dialog 18:59:48 … first, styling on the web 18:59:57 … nothing compared to classical publishing 19:00:01 … we need to learn from that 19:00:27 … second, more publishing will leverage the web 19:00:32 thrid, distribution 19:00:43 s/thrid/... third 19:00:51 … fourth, the web is consumed differently 19:00:52 RRSAgent, make minutes 19:00:52 I have made the request to generate http://www.w3.org/2013/02/11-ebooks-minutes.html ArtB 19:01:01 … that will change everything 19:01:22 jeff: that's all I had to say 19:01:33 … at the end of day, we discuss transforming businesses 19:01:42 … remember this is just the 1st meeting of that kind 19:01:46 … lots more conversation 19:01:49 … thank you 19:02:20 karen: introducing Bill McCoy, CEO IDPF 19:02:22 Topic: Keynote - Extending W3C current work, collaboration with IDPF 19:02:22 abole has joined #ebooks 19:02:42 bill: thank you Karen and Jeff 19:02:57 … thank you all very much 19:03:06 … a priviledge to be here and make this happen 19:03:15 … w3c process for wkshops is pretty selective 19:03:24 … so thanks all of you 19:03:43 … many of us here may realize a hashtag is a subchannel of IRC 19:04:07 … #w3cebook is the hastag 19:04:13 s/hastag/hashtag 19:04:26 bill: warm-up presentation 19:04:34 … I'll be little controversial 19:04:48 davidwood has joined #ebooks 19:05:02 bill: a word about IDPF 19:05:11 … 2/3rds of you are IDPF members 19:05:14 … 350 members 19:05:19 … all parts of the value chain 19:05:28 … (lists) 19:05:47 … mission is to foster an open ecosystem for digital publishing 19:05:51 … develop epub format 19:05:55 … dozen years 19:06:03 … one piece only of the big picture 19:06:08 … epub widely adopted for ebooks 19:06:24 … many ebook retailers distribute epub to consumers 19:06:35 … interchange format too 19:06:46 … conversion from epub to local format 19:06:51 … also database format 19:06:57 smyles has joined #ebooks 19:06:59 s/database/delivery 19:07:01 NickRuffilo has joined #ebooks 19:07:10 jeff: needs to extend html to the future 19:07:26 … 2 years ago, kickoff meeting of epub3 in NYC 19:07:50 … (digression about Marriott Marquis lobby) 19:07:54 … charter for epub3 19:08:00 … two distinct paths 19:08:09 … xml schema 19:08:15 … or build on the web 19:08:23 … at that time html5 support was minority 19:08:23 s/Marriott Marquis/Random House 19:08:44 … adopting all of html5 would mean browser was required 19:08:50 … consensus reached eventually 19:09:06 … even Norman Walsch agreed 19:09:15 … 3 years later, still dealing with consequences 19:09:19 s/Walsch/Walsh/ 19:09:21 … was a brain transplant 19:09:28 … still parts difficult to deal with 19:09:39 … the publishing industry does not exist ina vacuum 19:09:46 … one click away from the web 19:09:56 … we cannot reinvent the wheel 19:10:00 @glazou, will the IRC channel logs be openly available? 19:10:04 … building on the web was a no-brainer 19:10:21 … if you look at the last 20+ years, 3 ways to deliver digital contents 19:10:47 … download files or apps ? 19:10:53 … not a topic for the next two days 19:10:59 … all valid ways to distribute contents 19:11:05 … depends on what consumer need 19:11:13 … sometimes one, sometimes the other 19:11:20 … we reinventing what we call books and magazines 19:11:34 … no need to argue about files#apps#... 19:11:34 s/jeff:/bill:/ 19:11:38 thanks plh-ebook 19:11:50 bill: browser interface is what users see 19:11:55 … we're at the very beginning 19:12:17 … consumers are spending more time in apps and less in files 19:12:24 … controversial perhaps 19:12:32 … but not aguing against the open web platform 19:12:45 … web technologies are becoming common place 19:12:52 … so we're on the verge of success 19:13:04 … reusing tools and components across all modes of creation and distirbution 19:13:09 … a universal platform 19:13:13 … the web platform 19:13:16 … not done yet 19:13:29 … we're also near failure 19:13:57 … not surprising 19:14:07 … the big risk is fragmentation 19:14:17 … look at webapps, many systems 19:14:26 … fragmentation already there in webapps 19:14:42 … in publishing we have our own suspects 19:14:46 … all html5-based 19:14:51 … but non interoperable 19:15:03 … many will support epub3 but no every feature 19:15:09 … so browser wars still alive and well 19:15:18 … of course, all propose proprietary extensions 19:15:35 … (digression about Adobe stealing from Xerox :-) ) 19:15:46 … extract all the value from open standards 19:15:53 … taking advantage of it 19:16:06 … bootstrap your own proprietary platform 19:16:23 … shame on us as an open community if we let that happen 19:16:35 … even worse is monopoly control by a single vendor 19:16:42 … let's face it, we're almost here 19:16:58 … what can we do about fragmentation? 19:17:09 … 100 specs are used by us ! 19:17:20 … we don't even have an exact count of them 19:17:40 … the open web platform is perceived as unrelated blocks of legos (shown on screen) 19:17:48 … we need a better architecture 19:17:56 … no enough vision 19:18:08 … what specs comprise the platform? too many WGs ? 19:18:14 … some WGs seems competitors 19:18:23 … html5 did sucessfully kill Flash 19:18:34 … but the open platform is not able to catch up yet 19:18:50 … the browser market share is today better than it used to be because no monopoly 19:18:57 … interoperable standards are here 19:19:04 … lots of issues to work out still 19:19:14 … 2 things we need to do, really: 19:19:21 … first, collaborate much better 19:19:39 … we're the bazaar not the cathedral 19:19:54 … we cannot remain in isolation 19:20:14 … browser vendors must NOT be the only ones dealing with the open web platform 19:20:28 … minimizing religious disagreements about secondary details 19:20:48 … (digression about Monty Python) 19:21:25 … not pointing fingers at W3C, same thing about IPDF 19:21:40 bill: we have responsability and we're not there yet 19:22:00 … second, eliminit assumption that browsers are only to display web contents 19:22:11 … the OWP has to make documents and apps first-class 19:22:20 … everything can be served from the cloud 19:22:32 … we don't really know what the future experience will be 19:22:43 … we can also take a position here 19:23:03 … we simply have to do it to create momentum 19:23:10 … let's raise the bar of the OWP 19:23:17 … the browser wars have shown 19:23:27 … I'd like to see excellence 19:23:43 miketaylr has joined #ebooks 19:23:48 … question if the OWP should bother with requirements from commercial platforms 19:23:52 RRSAgent, make minutes 19:23:52 I have made the request to generate http://www.w3.org/2013/02/11-ebooks-minutes.html Mike5 19:24:11 … does it matter if OWP is adopted by publishing and digital platforms? 19:24:33 … still doubt if W3C membership has embraced the notion of publishing industry+web 19:24:44 … going to be a win-win and we need to realize it 19:24:58 … full adoption is going to be large across various industries 19:25:03 Can http://www.webplatform.org/ play a role? Documentation of both the vision and how the components should fit together seems a possible direction to discourage fragmentation. 19:25:09 … high-design content needed 19:25:26 bill: interactivity and rich media 19:25:38 … w3c does not speak of semantic web any more 19:25:46 BUT THEY SHOULD 19:25:46 … learning material for education? 19:25:48 :) 19:26:05 … semantic structure 19:26:09 … files, apps, websites 19:26:15 … multiple channels, interop 19:26:25 … int'l, global languages 19:26:38 … writing modes in CSS 19:26:55 … publishers need to represent content on various shapes and sizes of screens 19:27:03 … a11y is a critical focus 19:27:16 … print disabled people must have access 19:27:22 … we need user-friendly tools 19:27:35 … democratizing the web cannot only for coders 19:27:41 … (applause) 19:28:00 … benefits of the focusing on OWP are both ways 19:28:15 … it's not about publishing to raise the web, but vice-versa too 19:28:22 … I'm optimistic we can succeed 19:28:31 karl has joined #ebooks 19:28:32 … universal OWP for publishing and web sites 19:28:34 Structured semantics are legitimately important (IMO) for publishers because the alternatives include fragmented individual solutions, unstructured semantics like tags and disconnected semantics like microformats. 19:28:40 … future of the web is up to all of you 19:28:45 … let's make next two days count 19:29:14 alexz has joined #ebooks 19:29:34 http://www.w3.org/2012/08/electronic-books/agenda.html#Session-1 19:29:55 Topic: 14:30-16:00 Session 1: Presentation (CSS, Fonts, etc.) 19:31:28 eric has joined #ebooks 19:31:46 ivan has left #ebooks 19:31:56 maria has joined #ebooks 19:32:07 ivan has joined #ebooks 19:32:10 What we really need to minute is the discussions sessions. 19:32:26 where are the minutes? 19:32:34 For the talk we will publish the slides 19:32:46 karen has joined #ebooks 19:32:51 fjh has left #ebooks 19:32:56 But everyone is welcome to scribe during the presentation of course ;-) 19:32:58 HL: multicolor is CSS module 19:33:06 ...resizing this, you can reset width 19:33:14 ...number of columns changes dynamically 19:33:23 ...basically say my ideal wideth is 14m 19:33:26 ...one line of code 19:33:31 ...we have this nasty scroll bar 19:33:39 ...to read full article, you have to scroll up and down 19:33:42 ...not idea 19:33:46 ...so we added overflow page 19:33:56 ...if I were on a tablet, I would use my finger 19:34:03 ...this is one idea 19:34:09 ...the Romans changed the world of publishing 19:34:15 ...putting things on scrolls 19:34:27 ...another magic things that happens when I combine floats 19:34:30 ...with multicolumns 19:34:37 ...why image is on the right 19:34:43 ...also span two paragraphs 19:34:51 ...moving from 4-3 columns, something gives 19:34:54 rrsagent, draft minutes 19:34:54 I have made the request to generate http://www.w3.org/2013/02/11-ebooks-minutes.html ivan 19:34:56 ...image moves to next page 19:35:02 ...don't have to write in detail, it happens normally 19:35:12 ...We want more pictures and flow things to bottom, top, corners 19:35:19 ...make elements span across all columns 19:35:25 ...you see where I am aiming with this layout 19:35:29 ...I replace those cats 19:35:36 ...replaced them with sheep 19:35:47 ...We don't know what The Guardian designer would have done 19:35:54 ...this is all being done dynamically in front of you 19:35:58 ...See the byline, second colunn 19:36:02 ...It was hard to do 19:36:08 ...pushed things aside a bit 19:36:12 ...That's newspaper example 19:36:18 ...this can also be done for magazines 19:36:26 ...we can combine this with what we have in CSS 19:36:35 ...the rotation, text shadows...still page layout 19:36:39 ...and only ten lines of code 19:36:47 ...Another interesting example is dictionaries 19:36:53 ...many have text and images intertwined 19:36:57 ...As I resize this 19:37:01 ...the images make up white areas 19:37:06 ...this image of Cato 19:37:11 ...white space 19:37:20 ...so find a solution...such as all pages on top 19:37:23 ...but that doesn't work 19:37:33 ...still use float and multicolumn layout 19:37:36 ...but also use snap 19:37:46 ...so it moves to its natural position in the layout 19:37:57 ...this is very useful, especially in scientific publications 19:38:03 ...I end with an academic paper 19:38:10 ...This is a boring looking document 19:38:15 ...but it has an important byline 19:38:20 ...has been impossible to do on the web 19:38:28 ...as I reformat for different screens, it changes 19:38:34 ...I want it to be on bottom and in page mode 19:38:36 ...There we are 19:38:41 ...let me summarize briefly 19:38:44 ...In ten lines of code 19:38:53 ...I can replicate 90 percent of publications 19:39:00 ...clean HTML, responsive design 19:39:06 ...number of columns changes from tablet to mobile 19:39:09 ...this works out the box 19:39:17 ...Think we should have run-arounds 19:39:21 ...and synchronization with baselines 19:39:23 ...don't have those 19:39:30 ...and select independent colors and pages 19:40:14 s/colors/columns/ 19:40:15 Alan: Next speaker is Vlad Levantovsky, Monotype 19:40:39 Vlad: Monotype is a big organization everyone knows 19:40:56 ...I found it to be useful to start with newspapers similar to Hokum 19:41:04 ...see type 19:41:15 ...two and a half inches in size with eight different type faces 19:41:20 ...doesn't really help to convey information 19:41:25 ...Nothing really changes when you look at the web 19:41:33 ...as much type 19:41:41 ...Jeff mentioned in his keynote, everyone is a publisher 19:41:43 ...which is scarey 19:41:50 ...So I'm going to talk about professional publishers 19:41:57 ...not just what we say, but how we say 19:42:19 ...I'm sure you'd like 'Harvey Davidson' in swirley font 19:42:28 ...[a few other examples] 19:42:36 ...Type face gives your message trust and integrity 19:42:42 ...you can make it whisper or screan 19:42:49 [GoodYear example] 19:42:57 ...all these tricks can be accomplished today 19:43:03 ...Do we have web fonts? yes 19:43:09 ...Embedded fonts? yes 19:43:14 ...life is good; are we done? 19:43:17 ...Not really 19:43:38 ...Jan Tschhichold said, "Everything that counts in typography is...." 19:43:48 ...Screen typography is very different from paper 19:43:56 ...why it's different 19:44:06 ...Here is how I want my type to be seen on the screen page 19:44:24 ...when glyph outlines convert into pixels, it is blurry 19:44:31 ...apologize for highly visual nature 19:44:36 ...Quality of rendoring is big factor 19:44:40 ...that is not easy to control 19:44:44 ...those tyings are type features 19:44:49 ...when you look at print publications 19:45:01 ...today, most publishers use ligatures, numbering styles 19:45:14 ...tools that publishers get accustomed to using 19:45:24 ...Everything from the printing press will look identical 19:45:29 ...to their true, original design 19:45:36 ...with onscreen typography 19:45:47 ...publishers need to understand the underlying screen limitations 19:45:57 ...something that works well in print will not work on screen 19:46:04 ...Here is an example of incorrect type faces 19:46:11 [Mad Men example] 19:46:35 ...At Monotype we have been going through effort of converting popular book faces into ebook formats 19:46:47 ...shows changes of width, proportion, limitations of print display 19:47:02 ...We have been developing completely new breeds of type faces for onscreen and ebook display 19:47:08 ...Malabar is one such example 19:47:18 ...see this onscreen in the Nook reader from Barnes & Noble 19:47:22 ...gives crisp design 19:47:27 ...and is popular with ebook readers 19:47:32 ...That concludes my presentation 19:47:44 ...I wanted to outline the problems, mostly in the professional publishing world 19:47:52 ...We'll see more of them 19:47:55 ...We need to communicate 19:48:07 ...Publishers need to understand limitations of screen typopgraphy 19:48:16 ...and web needs to understand their needs 19:48:21 ...so we can accomplish both 19:48:30 rrsagent, draft minutes 19:48:30 I have made the request to generate http://www.w3.org/2013/02/11-ebooks-minutes.html tmichel 19:48:46 Jaejung Kim, KAIST 19:48:57 Enrichment of eBook User Interfaces: A Skeuomorphic Approach, Jaejeung Kim (Kaist) 19:49:00 s/Jaejeung 19:50:20 rrsagent, draft minutes 19:50:20 I have made the request to generate http://www.w3.org/2013/02/11-ebooks-minutes.html kaz 19:50:46 TomDN has joined #ebooks 19:50:50 ScribeNIck: karen 19:51:20 s/Jaejung/Jaejeung/ 19:51:46 rrsagent, make minutes 19:51:46 I have made the request to generate http://www.w3.org/2013/02/11-ebooks-minutes.html karen 19:51:57 i/What we really need to minute is the discussions sessions/scribenick: karen/ 19:51:59 rrsagent, draft minutes 19:51:59 I have made the request to generate http://www.w3.org/2013/02/11-ebooks-minutes.html kaz 19:52:41 JK: I am a user experience researcher at KAIST 19:52:50 ...presentation is enrichment of user interfaces 19:52:58 ...Reading a book requires a good presentation 19:53:04 ...content layouts, font alignment 19:53:11 ...another perspective is well manipulation of pages 19:53:17 ...which requires a good user interface 19:53:28 ...how the content changes depending upon user input 19:53:33 ...Novels are mainly composed of text 19:53:39 ...we read line by line in sequential order 19:53:43 TomDN has joined #ebooks 19:53:43 ...this is formal reading 19:53:47 ebook prototype UI by KAIST http://www.youtube.com/watch?v=rVyBwz1-AiE 19:53:58 ...Text books are composed of text, graphics...but not always in a sequence 19:54:03 ...jump to references 19:54:13 ...Newspapers and magazines are composed of all sorts of content 19:54:16 ...we read without order 19:54:22 ...so it's informal or casual reading 19:54:30 ...eBook content are more than just text 19:54:35 ...they are evolving to more interactive 19:54:40 ...this is what ePub is aiming for 19:54:51 ...it requires a more dynamic way of navigating through the content 19:54:58 ...We conducted research to search for answer 19:55:04 ...I will show you our design approach 19:55:17 ...focus was not just eye candy or photo realism 19:55:29 ...but to functionally contribute to the users' reading experience 19:55:40 ...to bring print reading functional to touch-screen device 19:55:47 ...Let me introduce you to two missing features 19:55:51 ...thumbing through pages 19:55:55 ...and temporal 19:55:59 @ 19:56:12 ...our prototype is not based on any web technology 19:56:14 s/temporal/temporal bookmarking/ 19:56:19 ...Thumbing through is a four edge 19:56:26 ...highlight area is called the four edge 19:56:29 ...to thumb through 19:56:43 ...you are able to perceive overall structure and content in a few seconds 19:56:49 ...cannot use search 19:56:59 ...have to go through pages to find a picture without explicit data 19:57:11 ...use of this thumbing through was high in formal documents 19:57:17 ...four edge UI is rendered on side 19:57:20 ...touch dragging outward 19:57:28 ...flips pages very quickly, in a few seconds 19:57:36 minhyungko has joined #ebooks 19:57:36 ...and user is freely able to turn pages in a book holding position 19:57:55 ...addtional role of this four edge gives a tactile cue of page location, amount of pages left...plays a huge role 19:58:03 ...also used to tag for location; a sort of bookmark 19:58:09 ...we applied this in the ebook in the four edge area 19:58:22 ...another feature was temporal bookmarking 19:58:28 ...frequently done in book reading tests 19:58:33 ...make a comparison among pages 19:58:49 ...or stay on current page and get content from going back/forth to other pages 19:58:53 ...use dragging gesture 19:59:01 ...on release either return or stay the remote page 19:59:05 ...Give you a demo 19:59:26 ...This is thumbing through; second is temporal bookmarking 19:59:34 ...compare pages and instantly return 19:59:48 ...This video has had more than 500K views on YouTube 19:59:59 ...Issues and requirements from Web perspective 20:00:02 ...If it goes to web 20:00:07 ...it requires a layout of the interface 20:00:14 ...and rendering of page stack behind the current view page 20:00:18 ...this cannot replace 20:00:20 ...the slider bar 20:00:25 ...to jump from page to page 20:00:33 ...requires an HTML5 cache control to load pages 20:00:44 ...also an API for placing additional features on four edge area 20:00:47 ...like bookmarking 20:00:59 ...and also flexible division of separate content on same page 20:01:12 ...I have my device and you are welcome to try it hands-on later on 20:01:41 ScribeNick: glazou 20:01:57 stearns: introduces himself 20:02:07 … "Web versus eBooks" 20:02:14 … relatively new to both domains 20:02:21 … been working on CSS standards last two years 20:02:27 … epub features in CSS 20:02:33 … what epub needed for adaptive layout 20:02:47 … will detail my impressions 20:02:50 eric has joined #ebooks 20:02:58 … great thing to see epub3 based on html5 20:03:00 … and the OWP 20:03:12 … the web ecosystem is so much larger than the one we have for ebooks 20:03:25 … it's going thru the transition now 20:03:40 … more widespread authoring skills 20:03:49 … Web+EPUB is then a good shift 20:04:03 … but what I would like to see is the two techs working better together 20:04:12 edas has joined #ebooks 20:04:20 stearns: where interests converge, we should find a single solution 20:04:34 … where EPUB leads, improve the Web based on it 20:04:47 … for instance the EPUB content document 20:05:04 … we should work on it in the CSS WG looking at those requirements 20:05:20 … where interests diverge, make the web extensible and use polyfills 20:05:44 … the IDPF should create those polyfills 20:05:52 … packaging is a convergence 20:05:59 … offline apps and documents share a lot of things 20:06:06 … would be an awful thing to see them diverge 20:06:24 … we should work at converging them into a single baseline 20:06:47 … the Content document for EPUB was leading the W3C standards and used prefixed CSS properties to do that 20:07:06 … some people complained about WIP in CSS but I think it was fine 20:07:20 … showing what they actually need 20:07:33 s/WIP/using prefixed properties from specs in progress/ 20:07:38 … once you have prefixed properties, you have to push ; IDPF has to push 20:07:50 … to make W3C specs move along the REC track 20:08:05 stearns: we should prioritize based on that 20:08:12 … CSS TExt are crucial to EPUB 20:08:17 … needed also for the OWP 20:08:24 … still a Working Draft until last week 20:08:45 stearns: CSS WG meeting last week about it 20:08:55 … I'm guilty about keeping things late 20:09:06 … Want to push EPUB things need 20:09:10 … CSS 3 Speech 20:09:17 … there epub properties about this 20:09:29 … in CSS WG this ended up at the end of list of priorities 20:09:41 … only the editor has been pushing this 20:09:45 … so we need more participation from IDPF about this 20:09:59 … it needs to go to LC and needs Test Suite 20:10:13 … this particular lags because of lack of interest 20:10:23 stearns: that's one point of collaboration we can do 20:10:28 … CSS specs needs test suites 20:10:34 … and love more generally 20:10:42 … IDPF could contribute producing them 20:10:56 … naive understanding is that IDPF has not done that testing 20:11:02 … there could be more 20:12:02 … if there are EPUB tests we can go to, are this or that property available in EPUB readers? 20:12:13 … each viewer is not required to support everything 20:12:22 stearns: so different capabilities across readers 20:12:30 … now, polyfills... 20:12:48 … there are some things that could be added ontop of OWP to support EPUB features 20:12:53 … for instance in JS 20:13:11 … would help viewer development 20:13:28 stearns: adaptive layout for instance, Adobe had a large JS library 20:13:37 … not really the way you want to do a polyfill 20:13:48 … smaller minimal chunks per feature 20:14:01 … not a comprehensive, too large library 20:14:11 … not everything can be polyfilled 20:14:21 … things from håkon's demo for instance 20:14:57 … some things should be prioritized in the OWP or made so they can be polyfilled 20:15:00 eric has joined #ebooks 20:15:27 stearns: the CSS WG appears to me to come up with 80% solutions that are not extensible 20:15:35 … hence dead ends 20:15:40 … and then JS is needed 20:16:00 … we should have extensibility points so an ecosystem like eBooks can build upon our stack 20:16:05 … paginated views for instance 20:16:16 … would be a terrible failure if we come up with different solutions 20:16:31 … a bit about my own specs, Regions, Exclusions & Shapes, Page Templates 20:16:39 .. all things about adaptive layout 20:16:48 … find a good isolated feature for each piece 20:17:00 … CSS features EPUB can build upon 20:17:24 … I would like to see more collaboration and feedback about this 20:17:48 … CSS Regions in particular has diverged from original intent, from what you see in EPUB 20:18:03 … so complaining a bit : we need more collaboration 20:18:30 … when I brought proposal to IDPF, I got silence and splitism 20:18:37 … that attitude needs to change 20:18:48 … there will always be changes in a standards process 20:18:54 gluejar has joined #ebooks 20:18:55 … you just have to accept it and live with it 20:19:03 … I'm not going to take more time 20:19:10 … I want Q&A now 20:19:24 … I want to raise the OWP to ebook standards 20:19:41 … (applause) 20:20:11 plh breaks the ice :-) 20:20:38 karlpro: how many people know about polyfills and caniuse in the room? raise hands ! 20:20:39 Karl Dubost 20:20:53 people raise hands 20:20:55 Plyfill about 30 % 20:21:10 stearns: polyfill 1/2, caniuse a bit less 20:21:18 s/Plyfill/Polyfill/ 20:21:20 stearns explains what they are 20:21:40 stearns explains Polyfill 20:22:38 stearns explains caniuse 20:22:52 and also explains caniuse 20:22:55 http://caniuse.com/ 20:23:06 Ambica Desaraju (CourseSmart): 3 questions 20:23:15 … could bindings be an example of polyfills ? 20:23:27 … epub lists bindings as fallbacks for widgets the browser does not support 20:23:31 … for example slideshow 20:23:49 … bindings pulled out at run time 20:23:57 stearns: you choose different JS ? 20:24:03 stearns: then yes 20:24:13 ambica: future of html5 appcache? 20:24:17 all laugh 20:24:26 plh: working on it 20:24:34 … the appcache meachnism is broken right now 20:24:40 … implemented but broken 20:24:55 … meeting last week in london to find a new proposal 20:24:58 … work being done 20:25:04 … trying to find asolution 20:25:13 ambica: are mobile devices considered too? 20:25:14 plh: yes 20:25:49 rrsagent, draft minutes 20:25:49 I have made the request to generate http://www.w3.org/2013/02/11-ebooks-minutes.html tmichel 20:25:53 stearns: documents and apps are all the same thing ; example of PhoneGap and polyfill model 20:26:19 … whenever we build somthg into PhoneGap, we want that to become obsolete and polyfills the way to go 20:26:34 ambica: howcome, you listed ten lines of coce 20:26:51 … what about responsive design for mobile devices, CSS Media Queries for many devices 20:26:58 howcome: there were no MQ in my examples 20:27:01 … only multicol 20:27:25 … when you hit the limit, you need the MQ but that's a last resort solution 20:27:32 … we have a range here 20:27:46 plh: Philippe Le Hégaret, W3C 20:27:53 … thanks for bringing testing 20:28:01 … had a meeting in SF about that 20:28:09 … reps from mobile and non-mobile industry 20:28:17 … all had a their own profile of OWP 20:28:25 … they realized they share 90% 20:28:32 … lots of common interest 20:28:47 … if we're going to look at epub's profile, lots of common interest too 20:28:57 … so contributing to testing to OWP 20:29:12 Kim Marriott 20:29:15 Kim Marriott : CSS has come a long way 20:29:23 … one of the things we miss in CSS 20:29:41 … will it do everything for EPUB? 20:29:57 howcome: yeah, people always ask me for boustrophedon 20:30:17 stearns: I have a longer list than howcome 20:30:33 howcome: I think we should not stop before Guthenberg's bible 20:30:44 Marky Gylling IDPF 20:30:48 Marcus Gylling, IDPF: we have few efforts on testing 20:30:52 … support grid 20:30:57 … similar to caniuse 20:31:11 … test suite on github 20:31:25 ACTION mgylling post URL here 20:31:41 mgylling: we should find ways to share testing platform 20:31:49 stearns: we just had meeting 2 weeks ago about that 20:31:52 … we can coordinate 20:31:57 This BISG EPUB 3 Support Grid is set to be updated later this month...then again in April 2013... http://www.bisg.org/what-we-do-16-152-epub-3-support-grid.php 20:32:01 … about TTWF 20:32:11 … will help to hear from IDPF and vice-versa 20:32:32 stearns: Tobbie Langel, Facebook and now W3C fellow is now your contact 20:32:55 Peter Krautzberger (Mathjax): polyfills are very interesting and we call for more collab 20:33:09 … what can we do with mathml since we see no interest from browser vendors 20:33:21 stearns: not familiar with MathML 20:33:28 … what is the alternative? 20:33:31 … images ? 20:33:40 peter: we produce both and SVG output 20:33:59 … we can do that only if you have mathml support 20:34:06 … webkit has not a single developer about it 20:34:13 … so how can you push a standards ? 20:34:37 stearns: mathml is more complex than the example I have : balancing text 20:35:02 … adobe developed a polyfill for it 20:35:37 Glazou: If I can comment 20:35:42 ...we have an example in the market 20:35:52 ...about a large difference between WebKit 20:35:55 pagelab has joined #ebooks 20:36:03 ...on Asian languages 20:36:11 ...only way to improve mark-up is to change it all 20:36:41 ...Gekko... 20:37:02 Kaz: Thank you for your great presentations 20:37:13 ...I was interested in Alan's presentation 20:37:17 ...ebooks services and devices 20:37:24 ...Opera had speech 20:37:26 s/Gekko/Gecko/ 20:37:33 glazou: just use whatever rendering engine is available, that's going to introduce a shift in the market and other engines will respond 20:37:37 ...and speech API is implemented 20:37:43 ...W3C is working on speech capability 20:37:46 ...for web apps 20:37:51 scribenick: karen 20:37:52 duga has joined #ebooks 20:37:55 ...ePub3 includes SML capability 20:38:06 ...wondering about what type of extensibility should be for eBooks? 20:38:14 ...is there anything specified; other options? 20:38:24 danielweck has joined #ebooks 20:38:27 HL: You want to find common solutions to problems without pollyfils 20:38:34 ...sometimes will fail when moving to other devices 20:38:41 ...want to identify the core problems 20:38:48 ...certainly speech and audio are high on the list 20:38:54 ...we did implement this with IBM 20:39:02 ...we found we had a crash bug in the code 20:39:11 ...and people had not noticed 20:39:22 Kaz: Do you have suggestions for speech interface, Alan? 20:39:33 Alan: I don't have enough experience to provide an informed opinion 20:39:42 ...anyone else who has experience in the audience 20:40:03 Gerard Capio, Benetech 20:40:14 GC: we use Chrome speech to text capability 20:40:19 ...which requires an extension 20:40:24 ...they have been working on working group 20:40:31 ...to put forward a speech API 20:40:42 ...expect they will implement a speech synthesis piece 20:40:50 ...may be available in Chrome without extensions 20:41:11 ...And seeing other browsers like Firefox using it; will try to show a demo tomorrow in my presentation 20:41:22 Mark Hakkinnen: Another part of speech is haptics 20:41:30 ...we have been experiment with this 20:41:36 ...help students be more accessible 20:41:41 ...and more engaged 20:41:45 ...We are testing this 20:41:49 kawabata has joined #ebooks 20:41:49 ...would like to see how this works 20:41:59 ...other technologies coming out such as haptics in CSS 20:42:02 ...any others? 20:42:05 RRSAgent, draft minutes 20:42:05 I have made the request to generate http://www.w3.org/2013/02/11-ebooks-minutes.html glazou 20:42:09 Gerrard: I'll try to do a demo 20:42:12 Ivan Herman, W3C 20:42:21 IH: There is an underlying issue 20:42:26 ...not going into technical details 20:42:32 ...that comes up with all the discussions 20:42:46 ...that every decision is make on whether another browser is using something 20:42:55 ...W3C, like IDPF is a member organization 20:43:01 ...we work the members we get; those who are there 20:43:17 ...in that WG, if only the big browsers are present, then they will take the decision 20:43:20 ...that is the way it works 20:43:25 ...The only way to change that 20:43:33 ...is to have people who represent the users of OWP 20:43:35 ...like eBooks 20:43:40 ...not sure how we work that out 20:43:44 ...there is an underlying thing 20:43:46 philm has joined #ebooks 20:43:53 ...and I can imagine same for IDPF 20:44:03 ...we need the active presence and participation of the publishers 20:44:08 s/Mark Hakkinnen/Markku Hakkinen/ 20:44:08 ...to help turn the direction 20:44:13 ...might be a fight 20:44:16 ...with the browser vendors 20:44:25 ...What triggered me was something said about WebKit 20:44:26 s/Gerard Capio/Gerardo Capio/ 20:44:30 ...not having MathML 20:44:36 ...WebKit is a place to put code in 20:44:49 ...if there are communities that want MathML in WebKit, they need to add it 20:44:59 @@: @ has been doing the work for years 20:45:10 Ivan: Only an example 20:45:17 ...underlying issue is the same...be present please 20:45:24 ...have to work together on how to accomplish this 20:45:30 ...we have to find the mechanics for this 20:45:48 Alan: YOu can talk about being present in the room, or you can cast it as engagement [laughter] 20:46:00 @@: Work on accessibility with subtitles 20:46:11 ...some publishers want rich media 20:46:15 ...in multiple languages 20:46:21 ...without having their assets multiplied 20:46:32 ...I had my catch-all answer 20:46:35 ...We have to "engage" 20:46:40 ...maybe there is more information to give 20:46:57 Alan: I do know that there is a fight for the soul of sub-titling going on in W3C 20:46:58 s/@@: @/Murray Malroney/ @/ 20:47:03 ...VTT vs TTML 20:47:12 ...there may be a tipping point you can influence by joining now 20:47:20 Glazou: a point about collaboration 20:47:35 ...CSS Working Group designs specs but we are not the users 20:47:39 ...We had a big divergence 20:47:53 ...sometimes big arguments with the web designers 20:48:02 ...Brad @ is helping us do the right thing in CSS 20:48:07 ...for example if the grammar is bad 20:48:15 ...or not the best one for designers 20:48:19 ...you should do that, too 20:48:26 ...Your presence is absolutely needed 20:48:41 ...We all forget that most ePub viewers are based on two rendering engines 20:48:49 ...Another way to help is to contribute code 20:48:57 ...higher a developer, it's not that expensive 20:49:05 ...compared to the publishing industry 20:49:11 ...higher a developer 20:49:19 ...W3C develops software...like the Validator 20:49:24 ...it took years, do it 20:49:28 Alan: MathML is in WebKit 20:49:36 ...decision of Safari and Chrome whether to release it 20:49:39 Glazou: fork it 20:49:54 @ Design Science: I want to ask Vlad about fonts 20:50:03 ...what are we doing about making math fonts beautiful for the web 20:50:14 ...and make sure there are all the technical symbols and math symbols 20:50:19 Vlad: We are not doing enough 20:50:22 ...we should do more 20:50:32 ...One of the messages I wanted to get across 20:50:40 ...is to ask people what they need so we can work on them 20:50:46 ...So this question is important to us 20:50:54 ...not sure I can answer right now 20:51:18 @: MathML Drop by Chrome...was disservice to math and engineering communities 20:51:25 s/@ Design/Neil Soiffer Design/ 20:51:25 ...Safari put it in even with security issues 20:51:32 ...issue is not evil and they hate math 20:51:39 ...but more that nobody cared 20:51:43 ...I believe as a community 20:51:44 s/@:/ Neil Soiffer:/ 20:51:56 ...publishing community needs to step up and say this is important 20:52:00 ...and make it a priority 20:52:05 ...someone needs to take responsibility 20:52:15 ...no one wants to step up and make sure it's there 20:52:20 ...It's really a disservice 20:52:31 ...hope anyone in this group can help with that 20:52:44 HL: A colleague has identified a subset of MathML 20:52:49 ...and then attach a style sheet 20:52:54 ...I have not tried it 20:53:06 Neil: I was in original MathML but it's not there yet 20:53:16 ...@ takes huges advantage of CSS 20:53:21 ...maybe redo some of those 20:53:26 ...not looking at take this small thing 20:53:31 ...giant Javascript library 20:53:40 ...have to download all sorts of fonts 20:53:55 Murray Maloney: I have been aware of the math problem since the mid-90s 20:54:06 ...multiple math societies complainted 20:54:18 ...Many people in community have recognized this problem and have put effort into it 20:54:24 ...@ Did the work on his own 20:54:25 larsw has joined #ebooks 20:54:27 ...no compensation 20:54:35 ...he wants one language as the one true language 20:54:42 ...as the only one that is not supported properly on the web 20:54:51 ...any time he went to somebody to get this code activity 20:54:58 ...Seems there is always somebody smarter than you 20:55:06 ...they think about it and it never gets done 20:55:09 ...MathML work is done 20:55:22 ...publishers should feel confident in their ability to publish math but they cannot 20:55:27 ...reminds me of problem with HTML5 20:55:40 ...when HTML5 WG would not recognize things that were not out on the web 20:55:52 ...so the fact that publishers were using something within their walled gardens 20:55:55 ...that did not count 20:56:01 ...in all the years I have worked in standards 20:56:05 ...is that publishers never step up 20:56:11 ...you need to get somebody in the room 20:56:19 ...and you need to start putting more content out on the web 20:56:26 ...so the people who develop these tools 20:56:35 ...can see that publishers use the b and the itag 20:56:43 ...people who work with you say it's the right thing to do 20:56:48 ...but browsers don't help 20:56:57 ...get a membership in W3C and start screaming bloody murder 20:57:10 ...if you don't, it's going to be programmers who don't know anything about publishing 20:57:13 [applause] 20:57:21 Liam: I have to follow Murray 20:57:25 ...a quick comment 20:57:33 ...This discussion of how we change things 20:57:37 ...that is what this workshop is for 20:57:42 ...it's to figure out how to change things 20:57:49 ...ask everyone to hold in your hearts 20:57:56 ...to notice all these things that need to be changed and why 20:58:02 ...and think about how we can make changes 20:58:07 ...to some of the things we have heard 20:58:17 maria has joined #ebooks 20:58:17 ...getting MathML into Chrome; where are the test cases 20:58:24 ...how do we get test cases to rec 20:58:29 ...not one asnwer to everything 20:58:33 ...more use cases, more examples 20:58:45 ...Keep in mind please, how can we change the future [applause] 20:58:48 Alan: Last question 20:58:51 ...before the break 20:59:02 Thierry: break for 30 minutes at back of room 20:59:12 ...I would like to thank Daniel and Karen for scribing 20:59:24 ...please see me or Karen and volunteer for the next session 20:59:29 ...Also, if you want to do demos 20:59:34 ...we have round tables during the break 20:59:36 danielweck has joined #ebooks 20:59:39 ...so feel free to use them 20:59:44 ...We will reconvene at 4:30pm 20:59:49 rrsagent, make minutes 20:59:49 I have made the request to generate http://www.w3.org/2013/02/11-ebooks-minutes.html karen 21:03:53 glazou has joined #ebooks 21:04:39 lukis has joined #ebooks 21:05:16 danielweck has joined #ebooks 21:17:10 abarsto has joined #ebooks 21:17:27 abarsto has joined #ebooks 21:18:19 tmichel has joined #ebooks 21:18:30 danielweck has joined #ebooks 21:26:32 philm has joined #ebooks 21:30:42 jeff has joined #ebooks 21:31:57 eric has joined #ebooks 21:34:30 scribenick: Karl Dubost 21:34:37 Topic: 16:30-18:00 Session 2: OWP and EPUB/eBooks 21:34:47 scribenick: karl 21:35:13 glazou: (introduction of the good and bad of ePub) 21:35:46 ... I implemented epub2 and epub3. 21:35:49 Takeshi has joined #ebooks 21:36:13 ... I'm not pointing fingers, just talking about issues *we* have to solve. 21:37:20 ... (going through bgee requirements) 21:38:53 ... epub3 specs are based on several dialects. There are too many to deal with for being able to implement it. 21:39:11 ... we could decrease that number 21:39:34 ... There are also important changes between epub2 and epub3 21:40:09 ... Some drafts are considered as Recs, that's an issue. There was no unitary tests for epub. 21:40:18 s/was/were/ 21:41:03 davidwood has joined #ebooks 21:41:14 ... There are a lot of inconsistencies, unspecified parts, which need to be solved. 21:41:35 ... All implementers, authors, tutorials writers understand the spec and its meaning. 21:41:56 Jaejeung has joined #ebooks 21:41:59 ... (normative references tables which are not normative.) 21:43:14 ... Some of the documents can evolve a lot, and so the references will not be valid anymore. 21:43:31 ... It makes it difficult to base your work on moving implementations. 21:43:44 ... Some ebooks will become irrelevant in a few months. 21:44:31 ... The very first thing you hit in an epub is a Manifest… but zip already contains a Manifest. 21:44:41 danielweck has joined #ebooks 21:45:20 ... Is it useful to know the relationships between the files? 21:45:49 ... many things are already given from by the viewers engine and their api already. 21:46:35 ... Too many TOCs 21:46:41 ... We just need one. 21:47:26 ... Metadata in epu3 were a nightmare to implement. 21:47:41 ... the relationships in between the metadata are scary. 21:48:52 ... id/idref are too complex. It should not happened. It's very bad for UI. People do not understand them. 21:49:20 Takeshi has joined #ebooks 21:49:45 ... Heavy usage of namespaces make the documents bloated. 21:50:50 ... 1000 pages are opened in a few seconds. It's not needed to have namespaces. 21:51:31 ... URI management in epub is a proof of the devil 21:51:50 ... complex management of property vocabularies. 21:52:12 ... "We may remove the prefix in the future" 21:52:30 ... but it's not specified what you should do once the prefix is removed. 21:52:31 eric has joined #ebooks 21:53:18 ... Compatibility between epub versions is a myth. 21:53:51 ... content documents: no default rendering. 21:54:11 maria has joined #ebooks 21:54:15 ... epub3 refers to html5 which is still in work in progress. 21:54:27 ... extra schema for html5 that editing tools don't use. 21:54:50 ... is epub:trigger needed? There's an implementation cost with it. 21:55:42 ... AltStyleTags meaningful link classes. No notifications to the CSS WG. It reduces the space of class. 21:56:13 ... CSS profile based on WDs which are not stable. 21:56:31 ... epub should be only a packaging format with Web standards only. 21:57:19 ... Should use only html5, allow both serializations? 21:57:51 danielweck has joined #ebooks 21:59:17 ... Some decisions in the spec lead to bad UI requirements. 22:00:24 ... We have in the W3C to listen the publishing platform, but we need to do a few things before HTML5 Rec, CSS regions, Archive API for zips, etc. 22:00:54 ... BUT we need the participation of the publishing industry. 22:01:25 ... Get rid of proprietary XML dialects, and Epub core model and tests, tests, tests, … 22:02:05 fjh has joined #ebooks 22:02:41 Soochoi: Soo Choi, epub production department at Harpers Collins 22:02:41 jdovey has joined #ebooks 22:02:56 mgylling has joined #ebooks 22:03:00 ... Reaching the same screen in the digital landscape. 22:03:25 ... Retailers specific formats are coming back. 22:03:36 ... "Enhanced ebook" 22:04:11 ... (in house workflows for the print graph) 22:05:20 ... Print files are converted to ebooks 22:06:23 ... ISBN assignment are part of the issue. Every file format requires a unique format. 22:07:11 ... It has been very difficult to support the different devices. 22:07:33 ... sometimes the retailers are having their own features and they do not tell in advance what will they support. 22:08:23 ... There should be an enforcement of epub3 by govs, or organizations. 22:09:05 ... (Proposal for a limited subset of specs) 22:10:07 ... We need a consistent and positive experience between the author and the reader 22:11:10 Dave Cramer, Hachette 22:11:31 cramer: we want more robust ebooks. 22:11:46 ... case study L.A. Noire 22:11:50 danielweck has joined #ebooks 22:12:01 ... some viewers render things very differently even the simpler thing 22:12:52 ... some fonts are used very specifically for the mood of the book. Monospaced font was not possible to use on ibooks until we found a hack. 22:13:11 ... We want users to have the option to see it as designed. 22:13:50 ... We do not know which reading system our books is on. 22:14:02 ... web developers use UA string. 22:14:17 ... mediaqueries are useful if it was not crashing 22:14:40 ... @support would be useful if it was implemented. 22:15:09 ... For interactivity the spec is quite light. 22:15:41 ... epub2 was defined for things working in theory but not in practice. 22:16:21 ... epubpreflight for checking what is supported. 22:18:10 marriott: from Monash University 22:18:41 ... standards should not be only static. We are designing for the future too. 22:19:18 ... What are the opportunities for the future? 22:19:42 Judy has joined #ebooks 22:21:02 ... we want to have interactive and dynamic contents. 22:21:14 ... we want things to be immersive to be able to live the contents. 22:21:24 ... we want to be able to customize the content. 22:21:44 ... including collaborative and continuous authoring. 22:22:03 ... Multiple devices and accessibility. 22:24:19 ... (summary of the automatic document layout discussed at ACM on document engineering) 22:25:21 ... There are things which are already available in CSS, but not everything. 22:25:51 ... (mentioning things like pdftex, indesign, tex, vdp, etc.) 22:28:17 ... accessible graphic, haptic feedback. We need content and a standard for it. 22:28:36 ... When making standards, we need to think about the future. 22:28:39 danielweck has joined #ebooks 22:29:09 danielweck has left #ebooks 22:31:16 glushko: Robert J. Glushko, Berkeley - Bridging the Gap between ebook readers and browsers 22:32:26 ... collaborative teaching with a multidisciplinary textbook 22:32:31 danielweck has joined #ebooks 22:33:03 ... We can imagine a networked discoverable books with transcluded content. 22:33:14 ... It requires to think about books differently 22:33:39 ... a book can not be only on the Web, they should be of the Web. 22:33:53 ... We want books are native Web fabrics. 22:34:11 ... We want to be able to have Web books which are Web things. 22:35:17 ... Ebooks should be a first class Web citizen. 22:35:23 ... It should be linkable. 22:36:15 ... It should not be publisher centric. 22:36:56 ... How do we store content is an issue. There should be a browser agnostic system, where we can identify things with URI. 22:38:17 ... we want to be able to cache the content, manipulate it, modify it and have sync from the client to the server and so on. 22:38:36 ... There should be a browser export/import format. 22:39:27 QUESTIONS 22:39:35 Murray Maloney 22:39:49 murray: I was surprised by your comment on id/idrefs 22:40:09 ... first class links, How do we point things? 22:40:25 glazou: we need linking mechanism and counting mechanism. 22:40:43 ... things right now are working inside one document, not across documents. 22:40:59 ... How do we do it? And how do we make it happen right now? 22:41:18 danielweck has joined #ebooks 22:41:20 rrsagent, make minutes 22:41:20 I have made the request to generate http://www.w3.org/2013/02/11-ebooks-minutes.html erikmannens 22:41:26 Mia Amato, Skyhorse Publishing 22:41:56 mia: How do we plan to handle QA in between retailers and different devices? 22:42:16 maria has joined #ebooks 22:42:25 soochoi: There are multiple rounds of QA involved on different devices. There is technical QA. 22:42:33 mia: editorial are involved? 22:42:37 soochoi: yes 22:43:35 nick AAAAA: we talk about advanced features, but even on the basic features there are a lot of issues. 22:43:56 ... without the kindle, we are not making money. So we need to be compatible with them. 22:44:00 Nick @ Rufolo 22:44:08 ... How do we put pressure on them? 22:44:22 s/AAAAA/@ Rufolo/ 22:44:44 cramer: I'm very pessimistic about Amazon changing things. 22:44:57 ... It's sad. 22:45:33 Frederick Hirsch, Nokia 22:45:41 glushko: textbooks are not likely to go to kindle more than other things. 22:46:40 mccoy (hirsch too): What is the roadmap 22:46:52 mccoy: It's why we are here today. 22:47:29 … The full power of the Web platform has to be in books. We do not know yet how to monetize it. 22:47:53 BBBB: We heard about content cache, appcache 22:47:58 Anderson, Los Alamos National Labs 22:48:17 s/Anderson/Robert Sanderson 22:48:19 ... Could you share how annotations should be carried on in books. 22:48:35 s/s/BBBB/Robert Sanderson/ 22:49:11 s/BBBB/Robert Sanderson/ 22:49:12 glushko: My books are designed to evolve. Publishers think in release once and for all. 22:49:45 ... The system don't work this way. It's sad. We can't do continuous annotation. 22:50:14 David Cramer, Hachette 22:50:46 Scribenick: karen 22:50:56 ...it's complicated thing, I don't have a good answer 22:51:09 Robert Sanderson: Daniel, can you weigh in on this 22:51:17 ...helping the reader or publisher or somehwere in between 22:51:21 ...to add content to the ebook 22:51:27 ...and how that might work with an extended API 22:51:31 Glazou: content is not a problem 22:51:37 ...content and distributing it is a problem 22:51:48 ...all the repository owners of documents have applications 22:51:56 ...they know how to distribute a new version of an app 22:52:04 ...should know how to distribute a document 22:52:12 ...it's not server side, it's on client side 22:52:17 ...book, you need a dif 22:52:22 my question was (a) given the concerns with ePub is deployment happening and is there a roadmap to fix issues 22:52:23 ...this is something a bit @ 22:52:36 ...on annotations, likely need a linking mechanism between packages 22:52:42 and (b) what is the deployment situation for education and textbooks (given need for interactivity etc) 22:52:44 ...if you download one package, you need a link 22:52:48 ...whether it's free or not 22:52:57 ...renderer gets data from two different channels 22:53:01 ...that is likely the right way to do it 22:53:08 Neil, design science 22:53:18 ...No representatives from Apple or Amazon 22:53:26 ...a challenge, where are the publishers 22:53:35 ...and where are the implementers to do the standards 22:53:40 ...I know this has been a problem 22:53:46 ...this is a pretty critical situation 22:53:49 tmichel has joined #ebooks 22:53:59 David C: Apple has participated to some extent in the ePub work 22:54:09 ...expect they are under interesting contraints from their management 22:54:13 ...I have no idea what goes on 22:54:23 rrsagent, make minutes 22:54:23 I have made the request to generate http://www.w3.org/2013/02/11-ebooks-minutes.html tmichel 22:54:30 ...Amazon has had no participation as far as I know 22:54:36 ...feel that they don't need to talk to us 22:54:41 ...'If you build it they will come' 22:54:59 Karen: we had a non-response from Amazon outreach for this workshop 22:55:11 Glazou: we met last week in Tuscon for CSS F2F 22:55:15 ...and Apple was there 22:55:25 ...but some of their own features we would like them to submit, we did not see 22:55:32 ...Apple has a way of doing things that belongs to Apple 22:55:38 ...and they don't have the right to speak at conferences 22:55:51 ...unless they are allowed on the conference basis 22:55:54 ...what can I say? 22:56:02 Markus: In terms of bashing companies not present 22:56:14 ...Apple has been one of the earliest implementers of ePub3 22:56:23 ...they are certainly a good citizen in the ecosystem 22:56:27 ...everything is relative 22:56:32 David: I would agree with that statement 22:56:41 Karl Dubost: We talked about a lot of issues for publishers 22:56:45 ...but also issues for readerse 22:56:48 ...I am a big reader 22:56:58 ...I can put an image, notes, annotation into my books 22:57:03 ...I may put two books side by side 22:57:10 ...these are things missing in the ebooks ecosytems 22:57:18 ...cannot make notes between two books 22:57:26 ...I'd like to have a wiki book approach 22:57:30 ...and edit content inside the book 22:57:35 ...plenty of things we cannot do right now 22:57:44 ...where it's a failure to the print platform 22:57:53 RobertG: any book with a URI can do this 22:58:02 Glazou: if a book has no URI, not fragments 22:58:05 scribenick: Karl 22:58:26 ccc: in terms of annotations, there will be more talk about it tomorrow 22:58:37 glazou: nevermind, my bad 22:58:59 http://www.w3.org/community/openannotation/ 22:59:02 ccc: we want to speed up the process. 22:59:16 ddd, Google: I just want to clarify something. 22:59:43 ... It was not just a liaison. It was a recommendation of the css wg. 22:59:50 glazou: no 23:00:14 ddd: Maybe there was misunderstanding, but there was discussion made at the css wg. 23:00:27 ... search for alternate stylesheets. 23:00:53 Peter Krautzberger 23:00:56 eee: One of the key issues seems to be to get the reading systems out of the way 23:00:59 danielweck has joined #ebooks 23:01:51 krautzberger: It should not be only implemented but also overrided. 23:02:17 cramer: Something it depends on the constraints that devs have seen in the wild. 23:04:00 glazou: you can't really. The issue is that there are competitive advantage in between readers. 23:04:32 cramer: It's a battle in between two paradigms. 23:04:52 glazou: the vendor can infer many things about your reading habits. 23:05:01 ... these data are sold. 23:05:27 ... all vendors want to keep readers to have access to these data. 23:06:13 Topic: Conclusion for today. 23:06:29 tmichel: we reconvene tomorrow at 8:30 23:06:57 rrsagent, make minutes 23:06:57 I have made the request to generate http://www.w3.org/2013/02/11-ebooks-minutes.html karen 23:06:58 kaz has left #ebooks 23:08:47 eric has joined #ebooks 23:12:40 plh-ebook has joined #ebooks 23:13:14 philm has joined #ebooks 23:16:37 plh2 has joined #ebooks 23:26:10 gcapiel has joined #ebooks 23:39:34 jeff has joined #ebooks