This repository has been archived by the owner on Jan 17, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
/
Copy pathindex.html
658 lines (590 loc) · 29.9 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
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
<!DOCTYPE html>
<html prefix="talk: http://w3c.github.io/dpub/idpf-digital-book-2015/index.html ore: http://www.openarchives.org/ore/terms/" lang="en">
<head about="talk:">
<meta charset="utf-8">
<title property="dc:title">(Packaged) Web Publications</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<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 http-equiv="x-ua-compatible" content="ie=edge">
<script src="js/hyphenate.js" type="text/javascript"></script>
<link rel="stylesheet" href="css/styles/style.min.css">
<!-- <link rel="stylesheet" href="css/styles/style.min.css"> -->
<!-- These styles should be adapted to the details on where and what ribbon should be used, and how large the copyright is -->
<style type="text/css">
/*.slide::after {
padding: 50px 0 0 !important;
height: 130px ;
background: url(css/images/ribbon_w3c.svg) no-repeat ;
}*/
</style>
</head>
<body class="shower list hyphenate" about="talk:#talk" prefix="bibo: http://purl.org/ontology/bibo/ event: http://purl.org/NET/c4dm/event.owl#" typeof="cc:Work bibo:Slideshow">
<header class="caption">
<h1 property="dc:title" rel="dc:subject" resource="http://id.loc.gov/authorities/subjects/sh85042368#concept">(Packaged) Web Publications (PWP)</h1>
<h2>
<span rel="bibo:authorList" inlist="">
<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://orcid.org/0000-0003-0782-2704">W3C</span></span>
</span>
</h2>
<h3 rel="bibo:presentedAt">
<span typeof="event:Event bibo:Conference">
<span property="dc:title">EU Interinstitutional Digital Publishing Committee Plenary Meeting</span>, <span property="event:place">Brussels, Belgium</span>
</span>
</h3>
<h3 property="dc:date">2016-10-11</h3>
<p class="copyright">
<a href="http://creativecommons.org/licenses/by-nd/4.0/"><img class="plain" alt="Creative Commons License" src="figures/80x15.png"></a>
This work is licensed under a <a rel="cc:license" href="http://creativecommons.org/licenses/by-nd/4.0/">Creative Commons Attribution 4.0 License</a>,
with attribution to <a rel="cc:attributionURL" href="http://www.w3.org" property="cc:attributionName">W3C</a></p>
<p class="copyright">Copyright <sup>©</sup> 2016 W3C<sup>®</sup> (MIT, ERCIM, Keio, Beihang)</p>
</header>
<section class="slide titlepage">
<h2 class="donthyphenate">(Packaged) Web Publications</h2>
<h3>Ivan Herman, W3C </h3>
<h4>EU Interinstitutional Digital Publishing Committee Plenary Meeting, Brussels, Belgium</h4>
<h4>2016-10-11</h4>
<p class="copyright">This work is licensed under a <a target="_blank" href="http://creativecommons.org/licenses/by-nd/4.0/">Creative Commons Attribution 4.0 License</a>, with attribution to <a target="_blank" href="http://www.w3.org">W3C</a>.<br />
Copyright <sup>©</sup>2016 W3C<sup>®</sup> (MIT, ERCIM, Keio, Beihang)</p>
</section>
<section class="slide">
<h2>These Slides are Available on the Web </h2>
<p>See: <br>
<span style="font-size:90%"><a href="http://w3c.github.io/dpub/2016/IDPC/index.html"><code>http://w3c.github.io/dpub/2016/IDPC/index.html</code></a></span></p>
<p>(Slides are in HTML)</p>
</section>
<section class="slide shout cover">
<img src="covers/epub_cover.jpg">
<h3 style="color:red">A format to represent digital publications: EPUB 3</h3>
<p class="credit">Cloned Milkmen, Flickr</p>
</section>
<section class="slide">
<h2 class="donthyphenate">EPUB 3 is a very mature specification</h2>
<ul>
<li>Widely used format for digital publication</li>
<li>A truly portable and non-proprietary format</li>
<li>The standard format for digital books…</li>
<li>…but can be also be used for magazines, journal articles, documentation, etc.</li>
</ul>
</section>
<section class="slide shout cover" id="bookshelf"><div>
<img src="covers/bookshelf.jpg">
<h3 class="donthyphenate">A wide variety of books have been created</h3>
</section>
<section class="slide">
<h2>Books with of illustrations…</h2>
<figure class="left larger">
<img src="figures/petit_prince_1.png" alt="An extract of the 'Petit Prince' with a typical drawing" />
<figcaption class="credit">Antoine de Sain-Exupéry: “Le Petit Prince”, Ebooks libres et gratuits</figcaption>
</figure>
<figure class="right larger">
<img src="figures/winnie_the_pooh.png" alt="An extract of Winnie the Pooh with a typical drawing" />
<figcaption class="credit">A.A. Milne: “Winnie-the-Pooh”, Egmont UK Ltd.</figcaption>
</figure>
</section>
<section class="slide">
<h2>Art books</h2>
<figure class="middle">
<img src="figures/dutch_painting.png" alt="Page with an annotated high quality reproduction of a Dutch painting" />
<figcaption class="credit">Ingrid Koenen: “Dutch Golden Age”</figcaption>
</figure>
</section>
<section class="slide">
<h2>Mangas</h2>
<figure class="middle">
<img src="figures/manga.png" alt="Page of a typical Japanese manga" />
<figcaption class="credit">“ハルコさんの彼氏”, IDPF EPUB3 Sample</figcaption>
</figure>
</section>
<section class="slide">
<h2>Technical books</h2>
<figure class="left larger">
<img src="figures/css.png" alt="Extract of a CSS book, with codes and figures" />
<figcaption class="credit">Lea Verou: “CSS Secrets”, O'Reilly</figcaption>
</figure>
<figure class="right larger">
<img src="figures/func_js.png" alt="Extract of a Javascript book with figure and code" />
<figcaption class="credit">Michael Fogus: “Functional Programming”, O'Reilly</figcaption>
</figure>
</section>
<section class="slide">
<h2 class="donthyphenate">Books with different character sets and writing directions</h2>
<figure class="left larger">
<img src="figures/arabic.png" alt="An extract of a text in arabic" />
<figcaption class="credit">“Régime Anti-Cancer Arabic”, IDPF EPUB3 Sample</figcaption>
</figure>
<figure class="right larger">
<img src="figures/japanese.jpg" alt="An extract a text in Japanese, written in vertical" />
<figcaption class="credit">Murasaki Shikibu: “The tale of the Genji”, Aozora Bunko</figcaption>
</figure>
</section>
<section class="slide shout">
<h3>It is not only for books! It can be…</h3>
</section>
<section class="slide">
<h2 class="donthyphenate">…journals or magazines (articles)</h2>
<figure class="left larger">
<img src="figures/jep.png" alt="Cover of the JEP journal" />
</figure>
<figure class="right larger">
<img src="figures/jep1.png" alt="Table of content of the JEP journal" />
</figure>
</section>
<section class="slide">
<h2>…official reports of all kinds</h2>
<figure class="left larger">
<img src="figures/EU-en.png" alt="EU brochure in English" />
<figcaption class="credit">European Commission — General Report 2015</figcaption>
</figure>
<figure class="right larger">
<img src="figures/EU-bg.png" alt="EU brochure in Bulgarian" />
<figcaption class="credit">European Commission — General Report 2015</figcaption>
</figure>
</section>
<section class="slide">
<h2 class="donthyphenate">In fact, just about anything!</h2>
<figure class="left larger" style="margin-top:1.5em">
<img src="figures/gdrive.png" alt="Screendump of gdrive saving a document as EPUB" />
</figure>
<figure class="right larger">
<img src="figures/pages.png" alt="Screendump of Apple Pages saving a document as EPUB" />
</figure>
</section>
<!-- ===================================== -->
<section class="slide shout cover">
<img src="covers/secret.jpg">
<h3>What is the secret?</h3>
<p class="credit">James Arboghast, flickr</p>
</section>
<section class="slide">
<h2 class="donthyphenate">Well, at least one of the secrets…</h2>
<ul>
<li>EPUB is based on Web Technologies like HTML, CSS, SVG, JS, etc.
<ul>
<li>collectively referred to as “Open Web Platform” (OWP)</li>
</ul>
</li>
<li>I.e., no separate rendering, formatting, etc., specification had to be defined</li>
<li>Instead, EPUB relies on specifications defined by W3C and deployed in browsers</li>
</ul>
</section>
<section class="slide">
<h2 class="donthyphenate">Rough structure of an EPUB file</h2>
<figure>
<img class="plain" src="figures/EPUB3-Package-Structure.svg" alt="EPUB Packaging structure diagram" width="99%">
</figure>
</section>
<section class="slide">
<h2 class="donthyphenate">A good example</h2>
<figure class="right larger">
<img src="figures/photo_css.png" alt="Figure with a complex image processing done, in fact, in CSS" />
<figcaption class="credit">Lea Verou: “CSS Secrets”, O'Reilly</figcaption>
</figure>
<ul>
<li>The image on the right is displayed through that translucent “screen”</li>
<li>This is <em>not</em> done through some separate image processing step</li>
<li>Instead, it is based on some complex CSS features (implemented in browsers but also in EPUB readers)</li>
</ul>
</section>
<section class="slide shout">
<h3 class="donthyphenate">Bottom line: relationships of EPUB with OWP is fundamental</h3>
</section>
<section class="slide">
<h2 class="donthyphenate">Are we all done? <br/>I.e., are OWP and EPUB a perfect match?</h2>
<p>
There are two major areas that need work:
</p>
<ol>
<li>bring OWP and Digital Publishing closer</li>
<li>bring the <em>Web</em> and Digital Publishing closer</li>
</ol>
</section>
<section class="slide shout cover" id="owp_dpub">
<img src="covers/bring_owp_dpub.jpg"/>
<h3>Bring OWP and Digital Publishing closer</h3>
</section>
<section class="slide">
<h2 class="donthyphenate">Missing OWP features</h2>
<ul>
<li>Some features, needed by publishing, are missing from OWP; examples:
<ul>
<li>pagination, page controls for headings, page numbers</li>
<li>graphics transition effects (needed in, e.g., mangas, cartoons, children books)</li>
<li>dynamic numbering of pages, index references, etc., over <i>several</i> (HTML) files</li>
</ul>
</li>
<li>Bring extra Web facilities, libraries, services, etc., closer to publishing</li>
<li>W3C has a <a href="https://www.w3.org/dpub/IG/">Digital Publishing Interest Group</a> to look into these issues and cooperate with the relevant W3C groups</li>
</ul>
</section>
<section class="slide shout cover" id="web_dpub">
<img src="covers/bring_web_dpub.jpg"/>
<h3>Bring the <em>Web</em> and Digital Publishing closer</h3>
</section>
<section class="slide">
<h2>What is, in fact, a (digital) book?</h2>
<ul>
<li>It is a mean to transmit ideas to readers in various formats</li>
<li>It is independent of format: the same “book” should be available in different format and media
<ul>
<li>printed book, digital books, Web page(s)…</li>
</ul>
</li>
<li>Today, a Digital Book is different than a Web page (conceptually and practically)</li>
<li><em>This should not be the case!</em></li>
</ul>
</section>
<section class="slide">
<h2 class="donthyphenate"><em>“This should not be the case!”</em><br>what does this mean?</h2>
<figure>
<img src="figures/pwp.svg" alt="Portable Web Publication at a glance">
</figure>
</section>
<section class="slide shout cover">
<img src="covers/why.jpg">
<!-- <h3>Why Bother?</h3> -->
<p class="credit">ibta arabia</p>
</section>
<section class="slide">
<h2 class="donthyphenate">For example: book in a browser</h2>
<div class="flexright">
<figure>
<img src="figures/joseph-web.png" alt="Joseph Reagle's book as a web page">
<figcaption class="credit">Joseph Reagle: <a target="_blank" href="http://reagle.org/joseph/2010/gfc/chapter-4.html">“Good Faith Collaboration”</a>, PhD Thesis, MIT Press</figcaption>
</figure>
<ul>
<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 to “within” a page in a book</li>
<li>use useful plugins and tools that my browser may have</li>
<li>create annotations</li>
<li>sometimes I may need the computing power of my desk-top for, e.g., powerful text analysis</li>
</ul>
</li>
</ul>
</div>
</section>
<section class="slide">
<h2 class="donthyphenate">For example: book in a browser</h2>
<div class="flexleft">
<figure>
<img src="figures/joseph-bluefire.png" alt="Joseph Reagle's book as an ebook in reader">
<figcaption class="credit">Joseph Reagle: <a target="_blank" href="http://reagle.org/joseph/2010/gfc/chapter-4.html">“Good Faith Collaboration”</a>, PhD Thesis, MIT Press</figcaption>
</figure>
<ul>
<li>But, at other times, I may also want to use a small dedicated reader device to read the book on the beach…</li>
<li>All these on <i>the same</i> book (not conversions from one format to the other)!</li>
</ul>
</div>
</section>
<section class="slide">
<h2 class="donthyphenate">For example: I may not be online…</h2>
<div class="flexright">
<figure class="larger">
<img src="figures/commute.jpg" alt="Person sitting in a station with a mobile in hand">
<figcaption class="credit"><a target="_blank" href="http://j.mp/1t7BxJN">Bryan Ong</a>, Flickr</figcaption>
</figure>
<ul>
<li>I may find an article on the Web that I want to review, annotate, etc., while commuting home on a train</li>
<li>I want the results of the annotations to be back online, when I am back on the Internet</li>
</ul>
</div>
</section>
<section class="slide">
<h2 class="donthyphenate">For example: scholarly publishing</h2>
<div class="flexleft">
<figure>
<img src="figures/f1000.png" alt="Screen dump of an article on F1000">
<figcaption class="credit">Jullien Colomb et. al: <a href="http://f1000research.com/articles/3-176/v2">“Sub-strains of Drosophila Canton-S…”</a>, F1000Research</figcaption>
</figure>
<ul>
<li>Paper may be published on-line, but people may want to download it for offline use</li>
<li>The format of the paper should be adaptable to reading environment
<ul><li>no two column, fixed layout file that cannot be handled on an my tablet…</li></ul>
</li>
<li>The “paper” may also contain video, audio, data, programs…
<ul><li>scholarly publishing is not text only any more!</li></ul>
</li>
</ul>
</div>
</section>
<section class="slide">
<h2 class="donthyphenate">For example: in-house publishing</h2>
<figure class="right">
<img src="figures/manuals.jpg" alt="Bookshelf full of documentation">
<figcaption class="credit"><a target="_blank" href="http://j.mp/1t7B4HH">Peliro Agüera</a>, Flickr</figcaption>
</figure>
<ul class="smaller">
<li>Major companies (IBM, Intel, Boeing, FAO, Renault,…) are specialized “publishers” publishing a huge amount of documentation</li>
<li>Delivering it on paper may not be an option any more</li>
<li>Fast refresh time is needed</li>
<li>The <i>same</i> document should be available offline (e.g., in the cockpit) or online (e.g., on the work floor): there should be no difference between the two</li>
</ul>
</section>
<section class="slide shout cover" id="road_tech">
<img src="covers/road.jpg">
<h3 class="donthyphenate"> How do we get there? (Technically)</h3>
<style type="text/css">
#road_tech h3 {
color:red;
}
</style>
<p class="credit">Moyan Brenn, Flickr</p>
</section>
<section class="shout slide">
<h3>Let us concentrate on the Web only for now<br>(forget about “traditional” e-books)</h3>
</section>
<section class="slide">
<h2 class="donthyphenate">Need for the concept of a “publication” of many resources</h2>
<ul>
<li>A publication may consist of many resources (text, images, videos, etc)</li>
<li>On the Web, these are linked together, but they keep their complete “independence”</li>
<li>For publishing the abstract “work” should be a <em>single, conceptual unit on the Web</em>: a <strong>Web Publication (WP)</strong></li>
</ul>
</section>
<section class="slide">
<h2 class="donthyphenate">What does that mean technically?</h2>
<div class="flexright">
<figure class="large">
<img src="figures/WP-manyURL.svg" alt="a collection of resources with different URL pointer">
</figure>
<ul>
<li>The current Web builds on the notion of a single resource:
<ul>
<li>HTML source, metadata, CSS style sheet, etc.
</li>
<li>each has its own URL</li>
</ul>
</li>
<li>Rendering is based on the interoperation of many such resources</li>
</ul>
</div>
</section>
<section class="slide">
<h2 class="donthyphenate">What does that mean technically?</h2>
<div class="flexright">
<figure class="large">
<img src="figures/WP-oneURL.svg" alt="a collection of resources in a 'blob' with one URL pointer">
</figure>
<ul>
<li>A WP is <em>collection of Web resources considered as one unit</em>
<ul>
<li>this means there is a unique Web address for the <i>collection</i> (as opposed to a single constituent)</li>
<li>the <i>same</i> WP can be offline or online with the same address</li>
</ul>
</li>
<li>WP-s are <em>part of the Web</em>!</li>
</ul>
</div>
</section>
<section class="slide">
<h2 class="donthyphenate">Why do we need the WP concept?</h2>
<ul>
<li>The whole book should be archived in a national library</li>
<li>The publication has to be checked for integrity <em>as a whole</em> (e.g., in a legal publication)</li>
<li>Sharing a publication with a friend requires the concept of the publication <em>as a whole</em> </li>
<li>Publishing and library business models are based on the concept of “works”</li>
</ul>
</section>
<section class="slide">
<h2 class="donthyphenate">Why do we need the WP concept?</h2>
<ul>
<li>Value counters (counters, section numbering, footnotes, endnotes, etc.) should be consistent across the publication</li>
<li>Any search, text analysis, etc., facility for a book should have access to the full publication</li>
<li>User preferences should apply to the “work” rather than to a single Web page</li>
</ul>
</section>
<section class="slide">
<h2>(Some) technical challenges</h2>
<ul>
<li>How to ensure a unique identification of a WP?</li>
<li>How to represent, programatically, the concept of a WP?</li>
<li>How to assign metadata, additional information, etc., to a WP (rather than just a Web page)?</li>
<li>How to control user interface preferences for a full WP?</li>
<li>How to ensure security for the full publication (even if it is copied)?</li>
</ul>
</section>
<section class="slide">
<h2>The “online” vs. “offline” issue</h2>
<ul>
<li>In fact, that will become solved in the future, due to the evolution of browser technology
<ul>
<li>modern browsers will have possibilities of offline vs. online built in</li>
</ul>
</li>
<li>But some adjustments are necessary to get it working with a Web Publications</p>
</ul>
</section>
<section class="slide">
<h2 class="donthyphenate">What kinds of documents are we talking about?</h2>
<ul>
<li>A journal or magazine article, including the relevant CSS files and images</li>
<li>An educational article, including the JavaScript to do interactive exercises</li>
<li>A novel or a poem on the Web, including the necessary fonts, CSS files, etc., to provide the required aesthetics</li>
</ul>
</section>
<section class="slide">
<h2 class="donthyphenate">What kinds of documents are we <i>not</i> talking about?</h2>
<ul>
<li>A Web mail application</li>
<li>A social Web site like Facebook, VK, Renren, or Twitter</li>
<li>A stock exchange page</li>
</ul>
</section>
<!-- =================================================================================== --->
<section class="slide">
<h2><em>Packaged</em> Web Publications (PWP)</h2>
<ul>
<li>For a large number of use cases Web Publications (essentially, online/offline reading) is all they really need
<ul>
<li>e.g., scholarly journals, online magazines, brochures</li>
</ul>
</li>
<li>But a number of use cases rely on an extra step: to “pack” the content of a WP into a single file
<ul>
<li>archival, library distributions,…</li>
<li>extension of the current business model of trade publishers (built on EPUB)</li>
</ul>
</li>
</ul>
</section>
<section class="slide">
<h2>A layer “on top” of WP-s</h2>
<div class="flexright">
<figure class="large">
<img src="figures/PWP-oneURL.svg" alt="a collection of resources in a 'blob' in a rectangle with one URL pointer">
</figure>
<ul>
<li>Packaging means collecting all the content of a WP into a single file</li>
<li>Some additional issues to be handled:
<ul>
<li>special entries to the manifest</li>
<li>archival format(s)</li>
<li>etc.</li>
</ul>
</li>
<li>A specific “profile” for WP may have to be defined for a PWP</li>
</ul>
</div>
</section>
<section class="slide shout cover" id="what_about_epub">
<img src="covers/sea_marseille.jpg">
<h3 class="donthyphenate" style="color:red">But what about<br/> EPUB???</h3>
</section>
<section class="slide">
<h2 class="donthyphenate">PWP vs. EPUB3.1</h2>
<ul>
<li>PWP does <em>not</em> replace EPUB 3 today</li>
<li>It is, instead, part of a future evolution, or a vision, for the years to come</li>
</ul>
</section>
<section class="slide">
<h2 class="donthyphenate">Most things are the same!</h2>
<ul>
<li>Important to note that the <em>content</em> of a PWP and EPUB 3 are identical
<ul>
<li>usage of HTML, CSS, SVG, etc.</li>
</ul>
</li>
<li>The main change is the “administrative” aspect of the publication (locators, manifest, etc)</li>
</ul>
</section>
<section class="slide shout cover" id="synergy">
<img src="covers/synergy.jpg">
<h3 class="donthyphenate">Other synergy effects of convergence</h3>
<style type="text/css">
#synergy h3 {
color: hsla(240,50%,30%,1);
}
</style>
</section>
<section class="slide">
<h2 class="donthyphenate">Advantage for the publishers‘ community</h2>
<div class="flexleft ">
<figure class="large">
<img src="figures/zeldman.jpg" alt="Photo of a bookshelf with lots of technical books">
<figcaption class="credit"><a target="_blank" href="https://www.flickr.com/photos/zeldman/">Jeffrey Zeldman</a>, Flickr</figcaption>
</figure>
<ul class="smaller">
<li>The main interest of publishers is to produce, edit, curate, etc., <em>content</em></li>
<li>Publishers would have an easier access to a large audience</li>
<li>Publishers have invested heavily into technology developments, but the Web developers’ community can complement that with a wider reach and perspective</li>
</ul>
</div>
</section>
<section class="slide">
<h2 class="donthyphenate">Advantage for the publishers‘ community</h2>
<div class="flexleft">
<figure class="large">
<img src="figures/zeldman.jpg" alt="Photo of a bookshelf with lots of technical books">
<figcaption class="credit"><a target="_blank" href="https://www.flickr.com/photos/zeldman/">Jeffrey Zeldman</a>, Flickr</figcaption>
</figure>
<ul class="smaller" style="font-size:90%">
<li>Working closely with Web developers avoids re-inventing wheels
<ul>
<li>e.g., API-s to access system resources or utilities, like index database, battery status API, real-time communication, geolocation,…</li>
</ul>
</li>
<li>Aligning more on OWP means that specialized readers or Web sites, software, services, etc, can rely on it
</li>
</ul>
</div>
</section>
<section class="slide">
<h2 class="donthyphenate">Advantage for the Web community</h2>
<div class="flexright">
<figure>
<img src="figures/euclid.png" alt="image of a medieval manuscript">
<figcaption class="credit"><a href="http://www.math.ubc.ca/~cass/Euclid/byrne.html">Oliver Byrne's edition of Euclid</a>, University of British Columbia</figcaption>
</figure>
<ul>
<li>Publishers have experience in:
<ul>
<li>ergonomics, typography, aesthetics…</li>
<li>publishing long texts, with the right readability and structure</li>
</ul>
</li>
<li>Workflow for producing complex content</li>
<li>In some sense, a new type of content comes to the fore</li>
</ul>
</div>
</section>
<section class="slide">
<h2 class="donthyphenate">Some references</h2>
<dl>
<dt>Latest PWP Use Cases and Requirements draft:</dt>
<dd><a target="_blank" href="https://w3c.github.io/dpub-pwp-ucr/"><code>https://w3c.github.io/dpub-pwp-ucr/</code></a></dd>
<dt>Latest PWP Editors’ draft:</dt>
<dd><a target="_blank" href="https://w3c.github.io/dpub-pwp/"><code>https://w3c.github.io/dpub-pwp/</code></a></dd>
<dt>PWP Issue list:</dt>
<dd><a target="_blank" href="https://github.com/w3c/dpub-pwp/issues"><code>https://github.com/w3c/dpub-pwp/issues</code></a></dd>
</dl>
</section>
<section class="slide stamped">
<h2 class="donthyphenate">Some references</h2>
<dl>
<dt>Latest PWP Use Cases and Requirements draft:</dt>
<dd><a target="_blank" href="https://w3c.github.io/dpub-pwp-ucr/"><code>https://w3c.github.io/dpub-pwp-ucr/</code></a></dd>
<dt>Latest PWP Editors’ draft:</dt>
<dd><a target="_blank" href="https://w3c.github.io/dpub-pwp/"><code>https://w3c.github.io/dpub-pwp/</code></a></dd>
<dt>PWP Issue list:</dt>
<dd><a target="_blank" href="https://github.com/w3c/dpub-pwp/issues"><code>https://github.com/w3c/dpub-pwp/issues</code></a></dd>
</dl>
<p class="stamp small" class="donthyphenate" style="font-size:2em;">Constantly evolving…</p>
</section>
<section class="slide">
<h2>Thank you for your attention!</h2>
<dl>
<dt>This presentation:</dt>
<dd><a target="_blank" href="http://w3c.github.io/dpub/2016/IDPC/index.html"><code>http://w3c.github.io/dpub/2016/IDPC/index.html</code></a> <br>(<a href="http://www.w3.org/2016/Talks/EU-Brussels-IH/slides.pdf">PDF</a> is also available for download)</dd>
<dt>My contact:</dt>
<dd>ivan@w3.org</dd>
</dl>
</section>
<!-- ===================================== -->
<div class="progress"></div>
<script src="js/shower.min.js"></script>
</body>
</html>