2015/beijing-2015/index.html

<!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 content="text/html; charset=utf-8" http-equiv="content-type">
    <title property="dc:title">The Future of W3C Digital Publishing</title>
    <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/style.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: 60px 0 0 !important;
        height: 150px ;
        background: url(figures/W3C_ribbon.png) no-repeat ;
      }
      .titlepage p.copyright {
        left: 10em;
      }
      .shout h3 {
        padding-right: 0em;
        padding-left: 0em;       
      }
    </style>
  </head>

  <body class="list" 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">The Future of W3C Digital Publishing</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 property="dc:date">2015-11</h3>
      <p class="copyright">
        <a href="http://creativecommons.org/licenses/by-nd/3.0/"><img class="plain" alt="Creative Commons License" src="figures/80x15.png"></a>&nbsp;
        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 class="copyright">Copyright <sup>©</sup>2015 W3C<sup>®</sup> (MIT, ERCIM, Keio, Beihang)</p>
    </header>


    <section class="slide titlepage"><div>
      <h2>The Future of W3C Digital Publishing</h2>
      <h3>Ivan Herman, W3C </h3>
      <h4>2015-11</h4>

      <p class="copyright">This work is licensed under a <a target="_blank" href="http://creativecommons.org/licenses/by-nd/3.0/">Creative Commons Attribution 3.0 License</a>, with attribution to <a target="_blank" href="http://www.w3.org">W3C</a>.<br />
        Copyright <sup>©</sup>2015&nbsp;W3C<sup>®</sup> (MIT, ERCIM, Keio, Beihang)</p>
    </div></section>

    <section class="slide"><div>
      <h2>These Slides are Available on the Web </h2>
      <p>See: <br>
        <span style="font-size:90%"><a href="http://w3c.github.io/dpub/beijing-2015/index.html"><code>http://w3c.github.io/dpub/beijing-2015/index.html/</code></a></span></p>
      <p>(Slides are in HTML)</p>
    </div></section>

    <section class="slide"><div>
      <h2>About W3C: “Leading the Web to its Full Potential”</h2>
      <figure class="right">
        <img src="figures/timbl.jpg" width="80%" alt="Photo of Tim Berners-Lee"/>
        <figcaption class="credit">LeFevre communications, 2001</figcaption>
      </figure>
      <ul>
        <li>Founded in 1994, and directed by Tim Berners-Lee, the Inventor of the Web</li>
        <li>Member organization with over 400 members</li>
        <li>Cca. 80 staff bound to “hosts” in the USA (MIT), China (Beihang University), Japan (Keio University), and France (ERCIM)</li>
        <li>Focuses on Web ecosystem: users, developers, browsers, as well as specific industry requirements brought by industry segments</li>
      </ul>
    </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 this 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,&nbsp;…</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 many other standard bodies) hardly know about the requirements that this 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 target="_blank"  href="https://www.w3.org/dpub/IG/">Digital Publishing Interest Group</a> was formally created in May 2013</li>
        <li>DPUB IG has weekly teleconferences and bi-annual face to face meetings</li>
      </ul>
    </div></section>

    <section class="slide"><div>
      <h2> DPUB IG Mission</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>Goal is to raise issues to W3C working groups who can update or develop specs based on the needs of the publishing community.</li>
        <li>Work on a future vision of Digital Publishing called “Portable Web Publications (PWP)”</li>
      </ul>
      <p>See our <a target="_blank" href="https://www.w3.org/dpub/IG/wiki/Main_Page">website</a> for more detail.</p>
    </div></section>

    <section class="slide"><div>
      <h2>IDPF and W3C</h2>
      <table class="comparison striped">
        <tr>
          <th>IDPF</th>
          <th>W3C</th>
        </tr>
        <tr>
          <td>Standards for the Electronic Publishing and Content Consumption (EPUB)</td>
          <td>Standards for the General Web Technologies</td>
        </tr>
        <tr>
          <td>Builds on lower level Web (e.g., W3C) Standards</td>
          <td>Builds on lower level Internet (e.g., IETF, ECMA) Standards</td>
        </tr>
        <tr>
          <td>Does <em>not</em> develop standards beyond publishing</td>
          <td>Does <em>not</em> develop industry specific standards if there is another home for those</td>
        </tr>
      </table>
      <p>The key is <em>collaboration</em>.</p>
    </div></section>

    <section class="slide"><div>
      <h2>Relationships to some other organizations</h2>

      <ul>      
        <li><strong>BISG</strong>: represented in the Interest Group; joint discussions in the areas of metadata and accessibility.</li>
        <li><strong>EDItEUR</strong>: represented in the Interest Group.</li>
        <li><strong>IPTC</strong>: not a member of W3C yet, but there are some new activites on right expressions at W3C where they may participate.</li>
        <li><strong>Daisy Consortium</strong>: one of the most active members of the W3C Accessibility work.</li>
      </ul>    
    </div></section>

    <section class="slide shout cover" id="results"><div>
      <img src="figures/achievements.png">
      <h3>Some results of the past two years</h3>
      <style type="text/css">
        #results h3 {
          color: red;
          margin-top: 2.4em;
        }
      </style>
    </div></section>

    <section class="slide"><div>
      <h2>Layout and Styling</h2>
      <figure class="right">
        <img src="figures/latinreq.png" alt="Screen dump of the latinreq document" width="88%">
      </figure>
      <ul>
        <li>An evolving document: <a href="http://w3c.github.io/dpub-pagination/">“Requirements for Latin Text Layout and Pagination”</a></li>
        <li>Describes issues like hyphenation, spreads and bleeds, drop caps, pagination, etc.</li>
        <li>Has greatly influenced some current CSS Work, e.g. <a href="http://www.w3.org/TR/css-inline-3/">“CSS Inline Layout Module Level 3”</a> (handling initial letters, dropcaps), or <a href="http://www.w3.org/TR/css-gcpm-3/">“CSS Generated Content for Paged Media Module”</a> (handling running heads and footers)</li>
      </ul>
    </div></section>

    <section class="slide"><div>
      <h2>Priorities for CSS</h2>
      <figure class="right">
        <img src="figures/css_priorities.png" class="noborder" alt="Screen dumps of the CSS Priorities' document" width="100%">
      </figure>
      <ul>
        <li>Another evolving document: <a href="http://w3c.github.io/dpub-pagination/">“Priorities for CSS from the DPUB IG”</a>
          <ul><li>major emphasis on pagination-related features</li></ul>
        </li>
        <li>Provides a list of the top CSS priorities, and their current availability </li>
        <li>Also influences the work of the CSS Working Group</li>
      </ul>
    </div></section>
 
    <section class="slide"><div>
      <h2>Content and Markup</h2>
      <ul>
        <li>Goal: identify the semantics of the HTML elements
          <ul><li>“abstract”, “indexed term”, “footnote”, "chapter", …</li></ul>
        </li>
        <li>Express structural information (“where can that element be used”)</li>
        <li>Do it in a forward looking way in terms of W3C standards.
          <ul>
            <li>i.e., move away from <code>epub:type</code> used in EPUB&nbsp;3</li>
            <li>the resulting HTML should be valid</li>
          </ul>
        </li>
        <li>These terms may be useful for the Web at large!
      </ul>
    </div></section>

    <section class="slide"><div>
      <h2>Content and Markup: Approach Chosen</h2>
      <ul>
        <li>Use <a href="http://www.w3.org/TR/wai-aria/">“Accessible Rich Internet Applications (WAI-ARIA)”</a> as a basic mechanism:
          <ul>
            <li>use specific attributes in HTML</li>
            <li>attribute values convey a specific semantics</li>
            <li>values mapped on Assistive Technologies interfaces</li>
          </ul>
        </li>
      </ul> 
    </div></section>

    <section class="slide"><div>
      <h2>Content and Markup: DPUB ARIA module</h2>
      <figure class="right"> 
        <img src="figures/dpub-aria.png" alt="Screen dump of the DPUB ARIA document" width="98%"> 
      </figure>
      <ul>
        <li>A Digital Publishing ARIA module is in development</li>
        <li>Publishing terms become part of ARIA</li>
      </ul>
      <pre>&lt;section <mark>role="doc-appendix"</mark>&gt;
  &lt;h1>Appendix A. Historical Timeline&lt;/h1&gt;
   …
&lt;/section&gt;</pre>  
    </div></section>

    
    <!-- ========================================================================= -->

    <section class="slide shout cover"><div id="major">
      <img src="covers/future.jpg">
      <h3>Major work coming up: Portable Web Publications (PWP)</h3>
       <style type="text/css">
        #major h3 {
          color: yellow;
        }
        </style>
    </div></section>

    <section class="slide shout"><div>
        <h3>The main message:</h3>
    </div></section>

    <section class="slide shout cover"><div id="webpubl">
      <img src="covers/blackboard.jpg">
      <h2>Web = Publishing!</h2>
      <style type="text/css">
      #webpubl h2 {
        color: snow;
        font-style: italic;
      }
      </style>
    </div></section>

    <section class="slide shout"><div>
        <h3>put it another way…</h3>
    </div></section>

    <section class="slide shout cover"><div id="publweb">
      <img src="covers/blackboard.jpg">
      <h2>Publishing = Web!</h2>
      <style type="text/css">
      #publweb h2 {
        color: snow;
        font-style: italic;
      }
      </style>
    </div></section>

    <section class="slide"><div>
      <h2>What does this mean?</h2>
      <figure class="right">
        <img src="figures/pwp.svg" width="100%" alt="Portable Web Publication at a glance"/>
      </figure>
      <ul>
        <li>Separation between publishing “online”, as Web sites, and offline/packaged 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>contents are mostly authored regardless of where they are used </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>What does this mean?</h2>
      <figure>
        <img src="figures/pwp.svg" alt="Portable Web Publication at a glance" width="100%">
      </figure>
    </div></section>

    <section class="slide shout cover"><div>
      <img src="covers/why.jpg">
      <!-- <h3>Why Bother?</h3> -->
      <p class="credit">ibta arabia</p>
    </div></section>

    <section class="slide"><div>
      <h2>For Example: Book in a Browser</h2>
      <figure class="right"> 
        <img src="figures/joseph-web.png" alt="Joseph Reagle's book as a web page" width="98%"> 
        <figcaption class="credit">Extract of Joseph Reagle’s Book as ePUB</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 “into” a page in a book</li>
            <li>use useful plugins and tools that my browser may have</li>
            <li>create annotations</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" alt="Joseph Reagle's book as an ebook in reader" width="80%">
        <figcaption class="credit"><a target="_blank" href="http://reagle.org/joseph/2010/gfc/chapter-4.html">Extract of Joseph Reagle’s Book</a> as ePUB</figcaption>
      </figure>
      <ul>
        <li>But:</li>
        <ul>
          <li>sometimes I may need the computing power of my desk-top for, e.g., interactive 3D content</li>
          <li>at other times I may also want to use a small dedicated reader device to read the book on the beach…</li>
        </ul>
        <li>All these on <em>the same</em> book (not conversions from one format to the other)!</li>
      </ul>
    </div></section>

    <section class="slide"><div>
      <h2>For Example: I May Not Be Online…</h2>
      <figure class="right"> 
        <img src="figures/commute.jpg" alt="Person sitting in a station with a mobile in hand" width="98%"> 
        <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>
          <li>Note: some browsers have an “archiving” possibility, but they are not interoperable
            <ul>
              <li>the content can definitely not be read on a dedicated reader</li>
            </ul>
          </li>
        </ul>
      </ul>
    </div></section>

    <section class="slide"><div>
      <h2>For Example: Scholarly Publishing</h2>
      <figure class="right"> 
        <img src="figures/f1000.png" alt="Screen dump of an article on F1000" width="98%"> 
        <figcaption class="credit">Screen dump of an article <a target="_blank" href="http://bit.ly/1wFcfWC">“Sub-strains of Drosophila Canton-S…”</a> on F1000</figcaption> 
      </figure>
      <ul>
        <li>My paper is published, primarily, on-line, but people may want to download it for offline use</li>
        <li>The format of the paper should be adaptable to my reading environment
          <ul><li>do not want a two column, fixed layout file that I cannot handle on my iPad…</li></ul>
        </li>
        <li>My “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"><div>
      <h2>For Example: Educational Materials</h2>
      <figure class="right"> 
        <img src="figures/auditorium.jpg" alt="University hall with students, most of them with a tablet" width="98%"> 
        <figcaption class="credit"><a target="_blank" href="http://j.mp/1t7Gpie">Merrill College of Journalism</a>, Flickr</figcaption> 
      </figure>
      <ul>
        <li>What is an educational publication?</li>
        <ul>
          <li><em>a book</em> that requires offline access?</li>
          <li><em>a packaged application</em> with built-in interactive tests, animated examples?</li>
          <li><em>a Web client</em> reaching out to Web services for assessing test results, to encyclopedia,&nbsp;…?</li>
          <li><em>an interactive data container</em> storing various data for, e.g., demonstrations?</li>
        </ul>
        <li>The borderline between a “book” and a “(Web) Application” are becoming blurred!</li>
      </ul>
    </div></section>

    <section class="slide shout cover" id="synergy"><div>
      <img src="covers/synergy.jpg">
      <h3>Synergy effects of convergence</h3>
      <style type="text/css">
      #synergy h3 {
        margin-top: 3.4em;
        background-color: hsla(181, 9%, 78%, 0.5);
        padding-right: 0em;
        padding-left: 0em;
      }
      </style>
    </div></section>

    <section class="slide"><div>
      <h2>Advantage for Publishers‘ Community </h2>
      <figure class="right"> 
        <img src="figures/javascript.jpg" alt="Photo of two javascript books" width="98%"> 
        <figcaption class="credit"><a target="_blank" href="http://j.mp/1CP4M41">Nathan Smith</a>, Flickr</figcaption> 
      </figure>
      <ul style="width: 57%">
        <li>Publishers want to concentrate on what <em>they</em> know better: how to produce, edit, curate, etc, great content</li>
        <li>Publishers are <em>not</em> technology companies, nor do they intend to be; they want instead to rely on the vibrant Web community!</li>
      </ul>
    </div></section>

    <section class="slide">
      <div>
        <h2>Advantage for Publishers‘ Community (cont.)</h2>
        <ul>
          <li>OWP is more than “just” HTML, CSS, MathML, etc.</li>
          <li>It also defines a large number of facilities that provide access to, e.g., system resources or utilities
            <ul><li>index database, Web storage, battery status API, real-time communication, geolocation,…</li></ul>
          </li>
          <li>Aligning more on OWP means that publishing oriented devices, software, services, etc, can rely on those
            <ul><li>instead of possibly re-inventing the wheel…</li></ul>
          </li>
        </ul>
      </div>  
    </section>

    <section class="slide"><div>
      <h2>Advantage for the Web Community</h2>
      <figure class="right"> 
        <img src="figures/manuscript.jpg" alt="image of a medieval manuscript" width="80%"> 
      </figure>
      <ul>
        <li>Publishers have a long experience in ergonomics, typography, paging,&nbsp;…</li>
        <li>Publishing long texts, with the right aesthetics, readability, structure, etc., is an expertise the Web community can profit from</li>
        <li>Experience of publishers in the complete workflow for producing content may become important for Web design</li>
      </ul>
    </div></section>

    <section class="slide shout cover" id="road_tech"><div>
      <img src="covers/road.jpg">
      <h3> How do we get there? (Technically)</h3>
      <style type="text/css">
        #road_tech h3 {
          color:red;
          background-color: hsla(181, 9%, 78%, 0.5);
          padding-bottom: 0.1em;
        }
      </style>
    </div></section>
    
    <section class="slide"><div>
      <ul class="notitle">
        <li>A strong cooperation between the different communities should be ensured</li>
        <li>Technical challenges must be identified
          <ul><li>note that some of the challenges are not PWP specific, but Digital Publishing in general (e.g., pagination control)</li></ul>
        </li>
        <li>Some examples follow…</li>
      </ul>
    </div>
    </section>

    <section class="slide shout cover" id="warning"><div>
      <img src="covers/warning.jpg">
      <h3>Warning: everything I say is subject to change!</h3>
      <style type="text/css">
      #warning h3 {
        margin-top: 0.8em;
        color: hsla(0,100%,60%,1.0);
      }
      </style>
      <p class="credit">Catherine Kolodziej, Flickr</p>
    </div></section>

    <section class="slide shout cover" id="arch"><div>
      <img src="covers/architecture.jpg">
      <h3>Technical Challenge: Overall Architecture</h3>
      <style type="text/css">
        #arch h3 { 
          color: #E9FB23;
          font-size: 2.2em;
          background-color: hsla(181, 9%, 78%, 0.5);
          padding-right: 0em;
          padding-left: 0em;
        }
      </style>
    </div></section>

    <section class="slide"><div>
      <h2>Advances in modern browsers: Web and Service Workers</h2>
      <ul>
        <li>A browser has a hidden, <i>truly parallel</i> engine attached to it</li>
        <li>That engine “catches” all calls out to the Web, and:
          <ul>
            <li>either lets it through and the original request happens;</li>
            <li>or performs local processing (e.g., gets content from a cache) and returns that content instead</li>
          </ul>
        </li>
        <li>The “main” rendering engine is unaware of the underlying proxy process
        <ul><li>it operates as if it was connected to the Web in a traditional way</li></ul>
        </li>
      </ul>
    </div></section>

    <section class="slide"><div>
      <h2>Advances in modern browsers: Web and Service Workers</h2>
      <ul>
        <li>A browser has a hidden, <i>truly parallel</i> engine attached to it</li>
        <li>That engine “catches” all calls out to the Web, and:
          <ul>
            <li>either lets it through and the original request happens;</li>
            <li>or performs local processing (e.g., gets content from a cache) and returns that content instead</li>
          </ul>
        </li>
        <li>The “main” rendering engine is unaware of the underlying proxy process
        <ul><li>it operates as if it was connected to the Web in a traditional way</li></ul>
        </li>
      </ul>
      <p class="stamp small" >Work in progress</p>
    </div></section>

    <section class="slide"><div>
      <h2>Envisioned Architecture: <br/>unpacked state</h2>
      <figure> 
        <img class="plain" src="figures/Workers-basic.svg" alt="Document consumed through the Web in a traditional way" width="99%">
      </figure>
    </div></section>

    <section class="slide"><div>
      <h2>Envisioned Architecture: <br/>cached state</h2>
      <figure> 
        <img class="plain" src="figures/Workers-cache.svg" alt="Document consumed through a Service Worker, possibly cached" width="99%">
      </figure>
    </div></section>

    <section class="slide"><div>
      <h2>Envisioned Architecture: <br/>packed state</h2>
      <figure> 
        <img class="plain" src="figures/Workers-package.svg" alt="Document consumed through a Service Worker, possibly unpacked" width="99%">
      </figure>
    </div></section>

    <section class="slide"><div>
      <h2>Envisioned Architecture: <br/>packed state</h2>
      <figure> 
        <img class="plain" src="figures/Workers-package.svg" alt="Document consumed through a Service Worker, possibly unpacked" width="99%">
      </figure>
      <p class="stamp" style="left:20%">Draft…</p>
    </div></section>

    <section class="slide shout cover" id="pack"><div>
      <img src="covers/package.jpg">
      <h3>Technical Challenge: Archival Format </h3>
      <style type="text/css">
      #pack h3 {
        color: snow;
        font-size: 2.3em;
        margin-top: 1em;
        background-color: hsla(181, 9%, 78%, 0.5);
        padding-right: 0em;
        padding-left: 0em;
      }
      </style>
    </div></section>

    <section class="slide"><div>
      <h2>Rough structure of an EPUB3 file</h2>
      <figure> 
        <img class="plain" src="figures/EPUB3-Package-Structure.svg" alt="EPUB Packaging structure diagram" width="99%">
      </figure>
    </div></section>

    <section class="slide"><div>
      <h2>Archival Format </h2>
      <ul>
        <li>There is a growing interest at W3C for a Web friendly packaging format:
          <ul>
            <li>should be streamable</li>
            <li>should rely, as much as possible, on existing Web technologies (e.g., HTTP)</li>
          </ul>
        </li>
        <li>Use cases include:
          <ul>
            <li>retrieve an HTML file with related CSS files, images</li>
            <li>access Web Applications (“Widgets”) with all libraries involved</li>
            <li><em>Portable Web Publications are a clear use case</em></li>
          </ul>
        </li>
        <li>But: current Web Packaging proposal is <em>not</em> OPF based
          <ul><li>this may lead to a different packaging in future for Digital Publishing</li></ul>
        </li>
        
      </ul>
    </div></section>

    <section class="slide"><div>
      <h2>PWP packaging structure</h2>
      <figure> 
        <img class="plain" src="figures/PWP-Package-Structure-2.svg" alt="PWP Packaging structure diagram with admin file in JSON" width="99%">
      </figure>
    </div></section>

    <section class="slide shout cover" id="presentation"><div>
      <img src="covers/choice.jpg">
      <h3>Technical Challenge: Presentation Control </h3>
      <style type="text/css">
        #presentation h3 {
          color: yellow;
          font-size: 2.4em;
          background-color: hsla(181, 9%, 78%, 0.5);
          padding-right: 0em;
          padding-left: 0em;
        }
      </style>
    </div></section>

    <section class="slide"><div>
      <ul class="notitle">
        <li>What is the level of user control of the presentation? </li>
        <li>The Web and eBook traditions are vastly different:
          <ul>
            <li>in a browser, the Web designer is in full control
              <ul>
                <li>CSS alternate style sheets are hardly in use</li>
                <li>some user interface aspects can be controlled but only for the browser as a whole</li>
              </ul>
            </li>
            <li>in an eBook reader, there is more user control
              <ul>
                <li>foreground/background color</li>
                <li>choice of fonts</li>
              </ul>
            </li>
          </ul>
        </li>
        <li>There is a need to reconcile these traditions</li>
      </ul>
    </div></section>

    <section class="slide shout cover" id="road_pract"><div>
      <img src="covers/road.jpg">
      <h3> How do we get there? (Practically)</h3>
      <style type="text/css">
        #road_pract h3 {
          color:red;
          background-color: hsla(181, 9%, 78%, 0.5);
          padding-bottom: 0.1em;
        }
      </style>
    </div></section>

    <section class="slide"><div>
      <h2>DPUB IG and Portable Web Publications</h2>
      <ul>
        <li>“Portable Web Publications” was, originally, a separate “vision” document (under the name “EPUB+WEB”)</li>
        <li>Was adopted, formally, as part of the group’s work in September 2015, and is now published as an IG document</li>
        <li>The group will contribute to the formulation of the PWP technical challenges, to a better understanding of the requirements</li>
        <li><i>PWP is the guiding principle for the group’s further work</i></li>
      </ul>
    </div></section>

    <section class="slide"><div>
      <h2>IDPF, W3C, and others</h2>
      <ul>
        <li>On long term, some PWP related standard-track specification work may have to be done
          <ul><li>this requires a consensus and agreement of different communities</li></ul>
        </li>
        <li>IDPF and W3C (and maybe others?) may create the necessary groups, eventually</li>
      </ul>
    </div></section>

    <section class="slide"><div>
      <h2>However…</h2>
      <ul>
        <li>PWP does <em>not</em> replace EPUB&nbsp;3 (and upcoming EPUB&nbsp;3.1) at this moment</li>
        <li>Many of the new features may also be part of EPUB&nbsp;3.1 (e.g., structural semantics)</li>
        <li>The vision is a convergence of the EPUB&nbsp;3.* specifications and PWP, eventually</li>
      </ul>
    </div></section>

    <section class="slide"><div>
      <h2>Conclusion</h2>
      <ul>
        <li>There is a great potential in a convergence between the Open Web Platform and Portable Web Publications</li>
        <li>It will require a common effort and cooperation of both communities</li>
        <li>But it is an exciting prospect!</li>
      </ul>
      <figure style="text-align:center"> <img src="figures/contents.jpg" width="65%"> </figure>
    </div></section>

   <section class="slide"><div>
      <h2>Some references</h2>
      <dl>
        <dt>DPUB IG Wiki</dt>
          <dd><a target="_blank" href="https://www.w3.org/dpub/IG/wiki/Main_Page"><code>https://www.w3.org/dpub/IG/wiki/Main_Page</code></a></dd>
        <dt>Latest PWP Draft:</dt>
          <dd><a target="_blank" href="http://www.w3.org/TR/pwp/"><code>http://www.w3.org/TR/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>
        <dt>This presentation:</dt>
          <dd><a target="_blank" href="http://w3c.github.io/dpub/beijing-2015/index.html"><code>http://w3c.github.io/dpub/beijing-2015/index.html</code></a> (<a href="http://w3c.github.io/dpub/beijing-2015/slides.pdf">PDF</a> is also available for download)</dd>
        <dt>Direct contact</dt>
          <dd><a href="mailto:ivan@w3.org">ivan@w3.org</a></dd>
      </dl>
    </div></section>


    <section class="slide shout"><div>
      <h3>Thank you for your attention!</h3>
    </div></section>

    <!-- ===================================== -->
    <div class="progress"><div></div> </div>
    <script src="shower/shower.min.js"></script>
    
  </body>
</html>