forked from w3c/epubweb
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
538 lines (492 loc) · 26.4 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
<!DOCTYPE html>
<html lang="en" prefix="talk: http://w3c.github.io/epubweb/presentation/index.html?full#1 ore: http://www.openarchives.org/ore/terms/">
<head about="talk:">
<meta content="text/html; charset=utf-8" http-equiv="content-type">
<title property="dc:title">
Advancing Portable Documents for the Open Web Platform: EPUB-WEB
</title>
<meta name="description" content="W3C Information and Knowledge Domain">
<meta name="apple-mobile-web-app-capable" content="yes">
<link rel="ore:describes" resource="talk:#talk">
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
<meta name="viewport" content="width=792, user-scalable=no">
<meta http-equiv="x-ua-compatible" content="ie=edge">
<link rel="stylesheet" href="shower/themes/w3c/styles/screen.css">
<link rel="stylesheet" href="shower/themes/w3c/styles/w3c-shower.css">
<style type="text/css">
.slide:after {
padding: 60px 0 0 !important;
height: 150px ;
background: url(figures/W3C_ribbon.png) no-repeat ;
}
li.c2 {list-style: none; display: inline}
p.c1 {font-size:70%}
figure.right {
float: right;
margin-left: 1em;
width: 40%;
}
img {
border: 1px solid #CCC;
border-radius: 10px;
box-shadow: 7px 7px 5px #888;
}
figcaption {
font-size:25%;
position:relative;
top:-15px;
left: 15px;
}
</style>
</head>
<body class="list" about="talk:#talk" prefix="bibo: http://purl.org/ontology/bibo/" typeof="cc:Work bibo:Slideshow">
<header class="caption">
<h1 property="dc:title" rel="dc:subject" resource="http://id.loc.gov/authorities/subjects/sh85042368#concept">
W3C Digital Publishing Interest Group
</h1>
<h3>2015-01-05</h3>
<h2>
<span rel="bibo:authorList" inlist="">
<span resource="https://www.linkedin.com/pub/markus-gylling/6/127/b10" typeof="foaf:Person">
<span property="foaf:name">Markus Gylling</span>, IDPF and DAISY,</span>
<span resource="https://www.linkedin.com/in/tzviya" typeof="foaf:Person">
<span property="foaf:name">Tzviya Siegman</span>, Wiley,</span>
<span resource="http://www.ivan-herman.net/foaf#me" typeof="foaf:Person"> <span property="foaf:name">Ivan Herman</span>,
<span property="rdfs:seeAlso" resource="http://www.ivan-herman.net/foaf">W3C</span></span>
</span>
</h2>
<p class="c1"><a href="http://creativecommons.org/licenses/by-nd/3.0/"><img alt="Creative Commons License"
style="border-width:0" src="http://i.creativecommons.org/l/by-nd/3.0/80x15.png"></a>
This work is licensed under a <a rel="cc:license" href="http://creativecommons.org/licenses/by-nd/3.0/">Creative
Commons Attribution 3.0 License</a>, with attribution to <a rel="cc:attributionURL"
href="http://www.w3.org" property="cc:attributionName">W3C</a></p>
<p>
Copyright <sup>©</sup>2015 IDPF® and ©2015 W3C® (MIT, ERCIM, Keio, Beihang)
</p>
</header>
<section class="slide titlepage">
<div>
<h2>
W3C Digital Publishing Interest Group Update
</h2>
<h3>
<span rel="bibo:authorList" inlist="">
<span resource="https://www.linkedin.com/pub/markus-gylling/6/127/b10" typeof="foaf:Person">
<span property="foaf:name">Markus Gylling</span>, IDPF and DAISY,</span>
<span resource="https://www.linkedin.com/in/tzviya" typeof="foaf:Person">
<span property="foaf:name">Tzviya Siegman</span>, Wiley, and</span>
<span resource="http://www.ivan-herman.net/foaf#me" typeof="foaf:Person"> <span property="foaf:name">Ivan Herman</span>,
<span property="rdfs:seeAlso" resource="http://www.ivan-herman.net/foaf">W3C</span></span>
</span>
</h3>
<h3>2015-01-06</h3>
<p style="margin-top:10em;"><a href="http://creativecommons.org/licenses/by-nd/3.0/"><img alt="Creative Commons License"
style="border-width:0; box-shadow:none; border:none; border-radius: 0" src="http://i.creativecommons.org/l/by-nd/3.0/80x15.png"></a>
This work is licensed under a <a rel="cc:license" href="http://creativecommons.org/licenses/by-nd/3.0/">Creative
Commons Attribution 3.0 License</a>, with attribution to <a rel="cc:attributionURL"
href="http://www.w3.org" property="cc:attributionName">W3C and IDPF</a><br/>
Copyright <sup>©</sup>2015 IDPF<sup>®</sup> and <sup>©</sup>2015 W3C<sup>®</sup> (MIT, ERCIM, Keio, Beihang)
</p>
</div>
</section>
<section class="slide">
<div>
<h2>
DPUB IG Origins
</h2>
<ul>
<li>The publishing industry is, probably, the most important user of W3C’s Web technologies after (traditional) browsers:
<ul>
<li>Almost <em>all</em> journals, magazines, etc, have an online version these days</li>
<li>Scholarly publishing cannot exist without the Web any more</li>
<li>EPUB is, essentially, a frozen and packaged Web site</li>
</ul>
</li>
<li>The quality requirements of the publishing industry are very high:
<ul>
<li>High quality typesetting, graphics, etc.</li>
<li>New forms of publishing will be based on high level of interactions, rich media,…</li>
<li>Common document and data publishing comes to the fore</li>
</ul>
</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>
DPUB IG Origins (cont.)
</h2>
<ul>
<li>But… the publishing industry had been in an entirely “passive” mode v.a.v. Web technologies
<ul>
<li>No participation in the development of fundamental Web technologies</li>
<li>W3C (and other standard bodies) hardly know about the requirements that industry may have</li>
<li>The potential synergy between Web developers and publishers is missed out</li>
</ul>
</li>
<li>Consequence: Working Groups at W3C set their priorities without knowing about, and considering, the publishing industry</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>
DPUB IG Origins (cont.)
</h2>
<ul>
<li>W3C and IDPF organized a series of exploratory workshops in 2012 to create a missing synergy among communities</li>
<li>The W3C <a href = "http://www.w3.org/dpub/">Digital Publishing Activity</a> and the <a href="https://www.w3.org/dpub/IG/">Digital Publishing Interest Group</a> was formally <a href="http://www.w3.org/2013/02/digpubig.html">chartered</a> in May 2013</li>
<li>DPUB IG has weekly teleconferences and annual face to face meetings</li>
<ul>
<li>New in 2015 - semi annual F2F: Join us in NY for the spring F2F on 26 May</li>
</ul>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>
DPUB IG Mission
</h2>
<blockquote>The mission of the Digital Publishing Interest Group (DPUB IG) […] a forum for experts in the digital publishing ecosystem […] for technical discussions, gathering use cases and requirements to align the existing formats and technologies (e.g., for electronic books) with those used by the Open Web Platform […] </blockquote>
</div>
</section>
<section class="slide">
<div>
<h2>
DPUB IG Mission Explained
</h2>
<ul>
<li>Experts familiar with the ins and outs of digital publishing and its associated industry groups identify issues that are not addressed by the Open Web Platform</li>
<li>Our goal is to raise issues to W3C working groups who can update (or develop) specs based on our information. We often lend members to the WGs as well</li>
<li>DPUB IG has task forces with leads to focus attention on specific issues and collaborate with other WGs</li>
</ul>
<p>See our <a href="https://www.w3.org/dpub/IG/wiki/Main_Page">website</a> for more detail.</p>
</div>
</section>
<section class="slide shout">
<div>
<h2>
So, who does the work?
</h2>
</div>
</section>
<section class="slide">
<div>
<h2>
Everybody does the work!
</h2>
<ul>
<li>IDPF has been writing specs for digital publishing for 15+ years, using W3C standards as a basis</li>
<li>DPUB IG highlights issues in OWP (W3C) that do not support the needs of digital publishing and learns from the W3C</li>
<li>W3C WGs update specs as needed to reflect needs of digital publishing and the broader web community</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>
DPUB IG Task Forces
</h2>
<ul>
<li>Annotations: Rob Sanderson</li>
<li>Layout and Styling (aka Pagination): Dave Cramer</li>
<li>Metadata: Bill Kasdorf and Madi Solomon</li>
<li>Content and Markup: Tzviya Siegman</li>
<li>Accessibility: Deborah Kaplan and Charles LaPierre</li>
<li>STEM: Peter Krautzberger</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>Annotations</h2>
<ul>
<li>Published <a href ="http://w3c.github.io/dpub-annotation/">Annotation Use Cases</a></li>
<li>Activity and work has shifted to the <a href="http://www.w3.org/annotation/">Web Annotations Working Group</a>, the first WG born of DPUB work
<ul>
<li>The work aims at annotation <em>for all forms of Web Documents</em>, whether in a browser or an eBook</li>
<li>The first Working Group at W3C joining forces of both browser and publishing industries from the start.</li>
</ul>
</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>Pagination and Layout</h2>
<ul>
<li>Published <a href ="http://www.w3.org/TR/dpub-latinreq/">Requirements for Latin Text Layout and Pagination</a></li>
<ul>
<li>Requirements for print and digital publishing from HTML and CSS using the Latin alphabet</li>
<li>Not a static document, new releases will come</li>
</ul>
<li>Work with CSS WG to publish the <a href ="http://www.w3.org/TR/2014/WD-css-inline-3-20141218/">CSS Inline Layout Module Level 3</a>, a working draft that enables drop caps and stick-up caps in CSS</li>
<li>Participation in the CSS WG’s new work on making pagination control implementable in a standard way (as opposed to the current, wildly differring solution used by the industry), also gathering <a href="https://www.w3.org/dpub/IG/wiki/Pagination_Requirements">requirements</a>.</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>Metadata</h2>
<ul>
<li>Interviewed publishing experts in metadata</li>
<li>Published <a href ="http://w3c.github.io/dpub-metadata/">DPUB IG Metadata Task Force Report</a></li>
<ul>
<li>Note summarizing findings in interviews</li>
<li>Discovered that OWP has the tools that publishers seek, but many in publishing are not familiar with tools</li>
<li>This group can aid the publishing industry in using OWP tools to implement existing vocabularies </li>
</ul>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>Content and Markup</h2>
<ul>
<li>Goal is to provide a standard way to add a logical structure on top of (but staying compatible with) HTML
<ul>
<li>E.g., identification of various types of sections, index terms, glossaries, etc.</li>
</ul>
</li>
<li>Working with a W3C Working Group that develops such extensions (through standard attribute terms) for accessibility purposes (called ARIA)</li>
<li>Proposed preliminary list of terms to introduce as a digital publishing module of ARIA
<ul>
<li>Terms provide native HTML elements with specific semantic meaning appropriate to digital publishing</li>
<li>Working in the context of ARIA provides increased accessibility</li>
</ul>
</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>Accessiblity</h2>
<ul>
<li>Drafted use cases related to accessibility and personalization in digital publishing</li>
<li>Reviewing W3C accessibility documentation (UAAG, WCAG, and ATAG) to assess whether the documents reflect the needs of digital publishing and whether publishers are using the documents</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>STEM</h2>
<ul>
<li>Conducted initial interviews with STEM experts to get an idea of major pain points in digital publishing</li>
<li>Preparing pointed survey to refine information gathered in interviews</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>What's Next?</h2>
<ul>
<li>Bring some guests to DPUB. Exposing our group to some experts of the web world will be mutually beneficial</li>
<li>Continue our task forces with targeted deadlines and deliverables</li>
<li>Involve DPUB members in the planning and development of <a href= "http://w3c.github.io/epubweb/">EPUB-WEB</a></li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>What's Next? EPUB-WEB</h2>
<ul>
<li>IDPF and W3C published joint vision of future of digital publishing in a white paper entitled "Advancing Portable Documents for the Open Web Platform: EPUB-WEB"
<ul>
<li>White Paper is available at <a href="http://w3c.github.io/epubweb/">http://w3c.github.io/epubweb/</a></li>
<li>Provide feedback at <a href="https://github.com/w3c/epubweb/issues">https://github.com/w3c/epubweb/issues</a></li>
</ul>
</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>The EPUB-WEB Vision</h2>
<ul>
<li>Portable documents are fully native citizen of the Open Web Platform</li>
<li>Separation between online (i.e., the “Web”) and portable (i.e., “EPUB”) is diminished to zero</li>
<li>This means:
<ul>
<li>Content authored for primarily offline use can be used online by loading it into a browser</li>
<li>Content authored for primarily online use can be easily saved as a portable document for offline use</li>
<li>These should be doable smoothly, solely based on the user’s interaction</li>
</ul>
</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>
The vision
</h2>
<ul>
<li>Publishers can choose to utilize either or both of these publishing modes</li>
<li>Users can choose either or both of these consumption modes</li>
<li>Essential features flow seamlessly between on-line and off-line modes, like
<ul>
<li>Cross-references, user annotations, access to on-line databases</li>
<li>Licensing and rights management</li>
<li>etc.</li>
</ul>
</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>
For example: book in a browser
</h2>
<figure class="right">
<img src="figures/joseph-web.png" width="100%" alt="Joseph Reagle's book as a web page"/>
<figcaption><a href="http://reagle.org/joseph/2010/gfc/chapter-4.html">Extract of Joseph Reaggle’s PhD</a> on the Web</figcaption>
</figure>
<ul style="57%">
<li>On a desktop I may want to read a book just like a Web page:
<ul>
<li>easily follow a link “out” of the book</li>
<li>create bookmarks “into” a page in a book</li>
<li>use useful plugins and tools that my browser may have</li>
</ul>
</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>
For example: book in a browser (cont.)
</h2>
<figure class="right">
<img src="figures/joseph-book.png" width="100%" alt="Joseph Reagle's book as an ebook in a browser"/>
<figcaption><a href="http://reagle.org/joseph/2010/gfc/chapter-4.html">Extract of Joseph Reaggle’s PhD</a> as ePUB</figcaption>
</figure>
<ul>
<li>But:</li>
<ul>
<li>my book may be 2000 pages long</li>
<li>conventional Web browsing may not be the right way to view content, a paginated view may be better</li>
<li>I may also want to use a small dedicated reader device to read the book on the beach…</li>
</ul>
<li>All this should happen using <em>the same</em> book, and not a conversion from one format to the other!</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>
Other Use Cases
</h2>
<ul>
<li>Online <em>and</em> Offline support</li>
<li>Scholarly publishing, including data sets, audio, video, programs, etc.</li>
<li>In-house publishing. Companies (IBM, Boeing, Renault, etc.) publish digitally and require fast refresh time and same information in cockpit (offline) and office (online)</li>
<li>Archiving and preservation of complete Web documents </li>
<li>Education materials including “book” content, interactive assessments, animations, a Web client for assessing test results, data for demos, and more</li>
</ul>
</div>
</section>
<section class="slide shout">
<div>
<h2>
How do we get there? (Technically)
</h2>
</div>
</section>
<section class="slide">
<div>
<h2>How do we get to EPUB-WEB?</h2>
<ul>
<li>A strong cooperation between the different communities should be ensured</li>
<li>Technical challenges must be identified</li>
<li>A new generation of EPUB (“EPUB-WEB”) has to be specified</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2><em>Some</em> technical challenges</h2>
<ul>
<li>Packaging Format better adapted to Web needs (e.g., streaming), see <a href="http://w3ctag.github.io/packaging-on-the-web/">Packaging on the Web</a> draft</li>
<li>Document Structure: the current EPUB3 structure (“spine”, etc) may have to be adapted to Web browsers, with possible defaults and possibility for user interactions</li>
<li>Identification:
<ul>
<li>General structures for unique ID-s so that documents Web citizens</li>
<li>IDs for fragments so that it is possible to link <em>into</em> documents</li>
</ul>
</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2><em>Some</em> technical challenges (cont.)</h2>
<ul>
<li>Metadata: use of webby methods to identify products, provide means for rich metadata carried with the EPUB-WEB document</li>
<li>Further improvements on styling and pagination</li>
<li>Security and privacy</li>
<li>Presentation control: reconcile the different traditions of user control (e.g., font size) for documents</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>DPUB IG and EPUB-WEB</h2>
<ul>
<li>DPUB IG already has task forces dedicated to working on many of the EPUB-WEB issues</li>
<li>The group should contribute to the formulation of the EPUB-WEB technical challenges, better understanding of the requirements</li>
<li>The detailed technical specification for EPUB-WEB will be done in separate W3C Working Groups</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>Upcoming events</h2>
<ul>
<li>26 May, 2015: DPUB Face to Face @ Hachette Book Group, New York, NY</li>
<li>27 - 28 May, 2015: IDPF Digital Book 2015</li>
</ul>
</div>
</section>
<section class="slide">
<div>
<h2>Some references</h2>
<dl>
<dt>DPUB IG Wiki</dt>
<dd><a href="https://www.w3.org/dpub/IG/wiki/Main_Page"><code>https://www.w3.org/dpub/IG/wiki/Main_Page</code></a></dd>
<dt>EPUB-WEB White paper:</dt>
<dd><a href="http://w3c.github.io/epubweb/"><code>http://w3c.github.io/epubweb/</code></a></dd>
<dt>EPUB-WEB Issue list:</dt>
<dd><a href="https://github.com/w3c/epubweb/issues"><code>https://github.com/w3c/epubweb/issues</code></a></dd>
<dt>This presentation:</dt>
<dd><a href="http://tzviyasiegman.github.io/epubweb/presentation/"><code>http://tzviyasiegman.github.io/epubweb/presentation/</code></a></dd>
</dl>
</div>
</section>
<section class="slide">
<div>
<h2>Direct Contacts</h2>
<dl class="plain">
<dt>Markus Gylling, IDPF</dt>
<dt>Ivan Herman, W3C</dt>
<dt>Tzviya Siegman, Wiley</dt>
</dl>
</div>
</section>
<section class="slide shout">
<div>
<h2>
Thank you
</h2>
</div>
</section>
<div class="progress"><div></div></div>
<script src="shower/shower.min.js"></script>
</body>
</html>