Skip to content
This repository has been archived by the owner on Jan 25, 2019. It is now read-only.

Made some changes on the document, namely: #5

Merged
merged 1 commit into from Jan 20, 2017
Merged

Made some changes on the document, namely: #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
114 changes: 94 additions & 20 deletions index.html
View file
Open in desktop
Expand Up @@ -22,6 +22,9 @@
ul#navbar {
font-size: small;
}
ul li{
margin-bottom: 0.2em;
}
dt.spec {
font-weight: bold;
}
Expand Down Expand Up @@ -107,7 +110,7 @@
<div class="warning">
<h1>Very Early Draft</h1>

<p>This very early draft is expected to be an input to the chartering process of a DPUB Working Group, envisioned as part of the combination of IDPF and W3C whose plans have been <a href="https://www.w3.org/2016/05/digpub.html.en">announced in May 2016</a> and which should come to fruition in early 2017. The development of this charter is owned by the W3C Staff but will be driven by a Publishing Business Group, which is intended to be created early in the combination of the two organizations. The early draft charter draws on the work of the <a href="https://www.w3.org/dpub/IG/">Digital Publishing Interest Group</a>, and that group will continue to contribute to the technical aspects of the charter (particularly to sections <a href="#scope">1: “Scope”</a> and <a href="#deliverables">2: “Deliverables”</a>).</p>
<p>This very early draft is expected to be an input to the chartering process of a DPUB Working Group, envisioned as part of the combination of IDPF and W3C whose plans have been <a href="https://www.w3.org/2016/05/digpub.html.en">announced in May 2016</a> and which should come to fruition in early 2017. The development of this charter is owned by the W3C Staff but will be driven by a Publishing Business Group, which is intended to be created early in the combination of the two organizations. The early draft charter draws on the work of the <a href="https://www.w3.org/dpub/IG/">Digital Publishing Interest Group</a>, and that group will continue to contribute to the technical aspects of the charter (<a href="#scope">2: “Scope”</a>, and <a href="#deliverables">3: “Deliverables”</a>).</p>

<p>Issues and comments from the public at large, but especially from the representatives of IDPF and W3C members, are encouraged and highly welcome. Comments should be submitted by raising <a href="https://github.com/w3c/dpubwg-charter/issues">issues on this (public) repository</a>. (In the case of a problems, comments can also be sent to the editor of this document, Ivan Herman, <a href="mailto:ivan@w3.org">ivan@w3.org</a>, who will submit the comment to the issue list in the commenter’s name.)</p>

Expand Down Expand Up @@ -155,12 +158,61 @@ <h1 id="title">Digital Publishing Working Group Charter</h1>

<section id="goals" class="goals">
<h2>Goals</h2>
<p>
The Web emerged in 1994, based on a model of individually-authored documents loosely tied together by hyperlinks. Since then, those Web “pages” have evolved into Web sites and Web Apps, with smaller and smaller bits of content, generated by more and more users or databases, with increasing amounts of interactivity. The Web has become a swarm of small content, changing very quickly. Although we still talk about pages, this model has little to do with that much older, yet still very powerful, paged-based media we call books or, using a more general term, “publications”.
</p>

<p>
Over centuries, “publications” have assumed many forms: traditional books, journals and individual journal articles, magazines, pamphlets, newspapers, business reports, atlases, comics, manga, notebooks, albums of all sorts. We can define these different manifestations as “publications”: bounded editions of meaningful media, made public.
</p>

<p>
We believe there is great value in combining this older tradition—of portable, bounded publications—with the pervasive accessibility, addressability, and interconnectedness of the Open Web Platform. New models of economic sustainability, innovative experiences of knowledge and invigorated socio-cultural engagement depend on this. The flourishing e-book market, largely based on the EPUB standard, has already changed the face of traditional publishing; this evolution can be fostered further by completely reconciling both traditions. (For further backgrounds, see also the <a href="https://w3c.github.io/dpub-pwp-ucr/">“Web Publications Use Case and Requirements”</a> document, collected by the W3C Digital Publishing Interest Group.)
</p>

<p>
<em>In short, “publications”—with all their specificities and traditions—should become first class entities on the Web</em>. It is the goal of the Digital Publishing Working Group to provide the technical underpinning of this evolution.
</p>



</section>

<section id="scope" class="scope">
<h2>Scope</h2>
<p><i class="todo">Brief background of landscape, technology, and relationship to the Web, users, developers, implementers, and industry.</i></p>

<p>
For the purpose of this document, a <a>Web Publication</a> (WP) is a bounded collection of Web resources, envisioned and created as a whole, that can be presented using Open Web Platform technologies. A <a>Web Publication</a> is not just a collection of links—the act of publishing involves obtaining resources and organizing them into a publication, which must be “manifested” by having files on a Web server. Thus the publisher provides an origin for the WP, and a URL that can uniquely identify that manifestation. A <a>Web Publication</a> must provide a number of features whose detailed specification is in the scope of this Working Group. While some of the detailed requirements have already been <a href="https://w3c.github.io/dpub-pwp-ucr/"> documented elsewhere</a>, the most important and high level characteristics, that must be translated into specifications are:
</p>
<ul>
<li>
A Web Publication may be portable, and be hosted at some other origin. However, it must preserve information about its original origin and identity, so that references to a portable copy can be reconciled with the original publication, and so that the other origin can make informed choices about how much trust to grant to the publication.
</li>

<li>
A Web Publication may be packaged by having all its constituent resources combined into a single file. The package must include the unique identifier of the manifestation—a Web Publication’s origin is essential information if it is to becomes portable. The act of packaging must be reversible; one must be able to recover the original structure and organization.
</li>

<li>
A Web Publication must be accessible to the broadest possible range of readers. In addition to WCAG and WAI requirements, accessibility requirements specific to Web Publications are to be developed.
</li>

<li>
A Web Publication must be available and functional while the user is offline. A user should, as much as possible, have a seamless experience of interacting with a Web Publication regardless of their network connection. We make no distinction between online and offline when defining web publications.
</li>

<li>
A Web Publication, having an identity and nature beyond its constituent resources, will have metadata that describes the publication as a whole. We also introduce the abstract concept of a manifest, which serves to carry information about the constituent resources of the publication, their sequence, and presentation.
</li>

<li>A Web Publication must provide access to a range metainformation including (but not restricted to):
<ul style="margin-top:0.2em">
<li>table of content, default or alternate reading order</li>
<li>security and authentication data</li>
<li>metadata like author(s), title, unique identification</li>
</ul>
</li>
</ul>

<section id="input-documents">
<h3>Input Documents</h3>
Expand All @@ -172,19 +224,31 @@ <h3>Input Documents</h3>
<h5>W3C documents</h5>
<ul>
<li><a href="http://w3c.github.io/dpub-pwp/">Web Publications for the Open Web Platform</a>. This document summarizes the technical deliberations on the subject by the DPUB Interest Group and provides possible technical avenues for the final specifications.</li>

<li><a href="https://w3c.github.io/dpub-pwp-ucr/">Web Publications Use Case and Requirements</a>. This is a collection of use cases collected by the DPUB Interest Group showing the requirements for Web Publications and Packaged Web Publications.</li>

<li><a href="https://www.w3.org/TR/appmanifest/">Web App Manifest</a>. The definition of Web Publications may rely on the introduction of a manifest and, if so, a compatibility with, and/or linkage to, Web App Manifests should be considered.</li>

<li><a href="https://w3c.github.io/ServiceWorker/">Service Workers</a>. Service Workers may provide an implementation vehicle for some aspects of Web Publications in a browser context.</li>

<li><a href="https://w3ctag.github.io/packaging-on-the-web/">Packaging on the Web</a>. The definition of packaging for Packaged Web Publications should consider this format as (one of) its standard format(s).</li>

<li><a href="https://www.w3.org/TR/wai-aria-1.1/">Accessible Rich Internet Applications (WAI-ARIA) 1.1</a>. ARIA&nbsp;1.1 provides the basis for the work on DPUB ARIA Module&amp;2.0</li>

<li><a href="http://www.w3.org/TR/dpub-aria-1.0/">Digital Publishing WAI-ARIA Module 1.0</a>. The planned DPUB ARIA Module&nbsp;2.0 is planned to be an extension to this specification.</li>

<li><a href="https://www.w3.org/TR/2016/NOTE-dpub-accessibility-20160503/">Digital Publishing and Accessibility in W3C Documents</a>. This Interest Group Note collects a number of accessibility features that are relevant for the publishing community and not (yet) part of the W3C Web Content Accessibility Guidelines. These document provides a basis for the working aiming at the extension of future versions of WCAG regarding publishing.</li>
</ul>

<h5>Non-W3C documents</h5>
<ul>
<li><a href="http://www.idpf.org/epub3/latest">EPUB 3</a>. EPUB&nbsp;3 will be an important input into Web Publications, Portable Web Publications, and EPUB&nbsp;4. Compatibility with EPUB&nbsp;3 will be a consideration in development of all three specifications. (Note that this reference is to an “umbrella” document for a <a href="http://www.idpf.org/epub3/latest#sec-epub-specs">suite of six specifications</a>.) <span class="todo">[If EPUB 3 moves to W3C as a member submission, this entry should be moved into the "W3C documents" section with an updated reference.]</span></li>

<li><a href="http://www.idpf.org/epub/profiles/edu/spec/">EPUB for Education</a>. This profile of EPUB&nbsp;3 gives a good example for the type of profiles that the publishing community uses. <span class="todo">[Depending ont he details of the new W3C/IDPF setup this document may have to be moved into the "W3C documents" section, too.]</span></li>

<li><span class="todo">[Documents, coming from the EPUB 3.1 WG, on BFF should be added once a stable reference is provided]</span></li>

<li><span class="todo">[Documents, coming from the Readium consortium, on the experiences of using browser friendly structures for EPUB3, should be added once a stable reference is provided]</span></li>
</ul>

</section>
Expand All @@ -196,10 +260,21 @@ <h3 id="out-of-scope">Out of Scope</h3>
</p>

<ul class="out-of-scope">
<li>Digital Right Management features for Web Publications (however, the Working Group shouldn’t make any design decision that would make such features impossible)</li>
<li>New metadata vocabularies</li>
<li>New document identification schemes (i.e., alternatives to DOI or ISBN)</li>
<li>Maintenance of EPUB3 (to be done in a separate Community Group)</li>
<li>
Digital Right Management features for Web Publications (however, the Working Group shouldn’t make any design decision that would make such features impossible)
</li>

<li>
New metadata vocabularies
</li>

<li>
New document identification schemes (i.e., alternatives to DOI or ISBN)
</li>

<li>
Maintenance of EPUB3 (to be done in a separate Community Group)
</li>
</ul>
</section>

Expand All @@ -218,7 +293,7 @@ <h3>Success Criteria</h3>
</p>

<p>
Testing plans for each specification, starting from the earlierst drafts.
Testing plans for each specification should be provided, starting from the earlierst drafts.
</p>
</section>
</section>
Expand All @@ -237,15 +312,7 @@ <h3>Recommendation-track Deliverables</h3>
<dt id="wp" class="spec">Web Publications</dt>
<dd>
<p>
This specification defines a Web Resource representing a collection of one or more constituent Web Resources, and presented using standard Open Web Platform technologies. A Web Publication may represent a journal or magazine article, an in-house documentation, or a digital book. It provides a standard to access information pertinent for the collection as a whole and that may be usable for the proper presentation of the publication; examples for such information are:
</p>
<ul>
<li>table of content, default or alternate reading order</li>
<li>security and authentication data</li>
<li>metadata like author(s), title, unique identification</li>
</ul>
<p>
The separate <a href="https://www.w3.org/TR/pwp-ucr/">Use Case and Requirement</a> document provides guidelines of the features a Web Publication should fulfill.
This specification defines a Web Resource representing a collection of one or more constituent Web Resources, and presented using standard Open Web Platform technologies. A Web Publication may represent a journal or magazine article, an in-house documentation, or a digital book. It provides a standard to access information pertinent for the collection as a whole and that may be usable for the proper presentation of the publication.
</p>
</dd>

Expand All @@ -254,15 +321,12 @@ <h3>Recommendation-track Deliverables</h3>
<p>
This specification defines a way to combine the resources of a Web Publication into a distributable file using a a packaging format.
</p>
<p>
<i class="todo">Something explicit about locator related issues?</i>
</p>
</dd>

<dt class="spec" id="epub4">EPUB 4</dt>
<dd>
<p>
This specification defines a <em>profile</em> of Packaged Web Publications that delivers a higher degree of comprehensive accessibility capabilities and of reliability. This specification should be as close as possible to a strict functional superset of EPUB&nbsp;3, with incompatibilities minimized.
This specification defines a <em>profile</em> of Packaged Web Publications that delivers a higher degree of comprehensive accessibility capabilities and of reliability. This specification should be as close as possible to a strict functional superset of EPUB&nbsp;3.1, with incompatibilities minimized.
</p>
</dd>

Expand All @@ -280,6 +344,7 @@ <h3>Potential Recommendation-track Deliverables</h3>
<p>
The following deliverables may be developed as Recommendation track documents, if there is consensus in the Working Group that incubation suggests success:
</p>

<dl>
<dt class="spec" id="dci">Document Collection API</dt>
<dd>
Expand Down Expand Up @@ -307,6 +372,8 @@ <h3> Other Deliverables </h3>
<li>Test suites and implementation reports for the specification</li>
<li>Primer or Best Practice documents to support web developers when designing applications</li>
</ul>

<p>The group should also contribute to the ongoing work to newer releases of WCAG to ensure the inclusion of publication specific features.</p>
</section>

<section id="timeline">
Expand Down Expand Up @@ -367,6 +434,13 @@ <h3 id="w3c-coordination">W3C Groups</h3>
This Working Group is responsible for the development of ARIA; the development of DPUB-ARIA Module&nbsp;2.0 should be done in close cooperation with the further development of ARIA in general
</p>
</dd>

<dt><a href="http://www.w3.org/WAI/GL/">Web Content Accessibility Guidelines Working Group</a></dt>
<dd>
<p>
This Working is responsible for the development of WCAG; the Digital Publishing Working Group shold work together with that Working Group to ensure the inclusion of publication specific features.
</p>
</dd>
</dl>

<h3 id="external-coordination">External Organizations</h3>
Expand Down