-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
275 lines (231 loc) · 13.6 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
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<meta charset="utf-8" />
<title>Web Publications</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove" async></script>
<script src="common/js/biblio.js" class="remove"></script>
<link href="common/css/common.css" rel="stylesheet" type="text/css" />
<script class="remove">
var respecConfig = {
wg: "Publishing Working Group",
specStatus: "ED",
shortName: "wpub",
// edDraftURI: "https://w3c.github.io/wpub/",
editors: [
{
name: "Matt Garrish",
url: 'http://www.daisy.org',
company: "DAISY Consortium",
companyURI: "http://www.daisy.org",
w3cid: 51655
}
],
processVersion: 2017,
includePermalinks: true,
permalinkEdge: true,
permalinkHide: false,
diffTool: "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
wgURI: "https://www.w3.org/publishing/groups/publ-wg/",
wgPublicList: "public-publ-wg",
wgPatentURI: "https://www.w3.org/2004/01/pp-impl/100074/status",
github: {
repoURL: "https://github.com/w3c/wpub",
branch: "master"
},
// otherLinks: [
// {
// key: "Repository",
// data: [{
// value: "Github Repository",
// href: "https://github.com/w3c/wpub"
// }]
// },
// {
// key: "Changes",
// data: [
// // {
// // value: "Diff to previous version",
// // href: "diff.html"
// // },
// {
// value: "Commit history",
// href: "https://github.com/w3c/wpub/commits/master"
// }]
// }
// ],
localBiblio: biblio
};
</script>
</head>
<body>
<section id="abstract">
<p>This specification defines digital publishing based on a fully native representation of publications within
the Open Web Platform.</p>
</section>
<section id="sotd">
<p>This first public working draft provides a preliminary outline of a Web Publication. Many details are under
active consideration within the Publishing Working Group and are subject to change. The most prominent known
issues have been identified in this document and links provided to comment on them.</p>
<p>In particular, the Working Group seeks feedback on the following issues:</p>
<ul>
<li>...</li>
</ul>
</section>
<section id="intro" class="informative">
<h2>Introduction</h2>
<section>
<h3>Background</h3>
<p>For millenia now, the written word has been the primary means of encoding and sharing ideas and
information. The publication as a bounded edition, made public, has been used to carry intellectual and
artistic works of innumerable form: novels, plays, poetry, journals, magazines, newspapers, articles,
laws, treatises, pamphlets, atlases, comics, manga, notebooks, memos, manuals, and albums of all
sorts.</p>
<p>More recently, with the advent of the information age, print has been ceding ground to digital, and the
Web has become a major forum for the public dissemination of ideas. But the Web is unbounded: information
and resources are only loosely connected through hyperlinks. While this model has helped the Web thrive
in many areas, it has proven problematic for traditional information publishing—users often cannot access
works in their entirety, especially when offline, and have not been able to easily access, compile and
download content for curation and personal use. That, in turn, has fed the continuing development of
non-Web document formats to redress these problems, and made it necessary to create both Web-ready
content and alternative offline renditions to ensure publications are fully available.</p>
<p>This specification aims to reduce these barriers and reinvigorate publishing by combining the best aspects
of both models—the persistent availability and portability of bounded publications with the pervasive
accessibility, addressability, and interconnectedness of the Open Web Platform.</p>
</section>
<section id="scope">
<h3>Scope</h3>
<p>This specification only defines requirements for the production and rendering of valid <a>Web
Publications</a>. As much as possible, it leverages existing Open Web Platform technologies to
achieve its goal—that being to allow for a measure of boundedness on the Web without changing the way
that the Web itself operates.</p>
<p>Moreover, the specification is designed to adapt automatically to updates to Open Web Platform
technologies in order to ensure that Web Publications continue to interoperate seamlessly as the Web
evolves (e.g., by referencing the latest published versions instead of specific versions).</p>
<p>Further, this specification does not attempt to constrain the nature of a Web Publication: any type of
work that can be represented on the Web constitutes a potential Web Publication.</p>
</section>
<!-- <section id="nature">
<h3>Web Publications</h3>
<p>The act of publishing involves obtaining resources, organizing them into a publication and making that
publication available on a Web server. In doing so, the publisher establishes the interconnectedness that
binds the resources into a single work. This process also provides an origin for the Web Publication and
a URL that uniquely identifies it, giving provenance to the work.</p>
<p>The establishment of this discoverable and identifiable collection is what enables users to access their
content without concern for whether they are online or offline. The user agent can cache the resources
ensuring that the Web Publication is available and functional while offline, providing the user, as much
as possible, a seamless experience interacting with a Web Publication regardless of their network
connection.</p>
<p>The Web Publication introduces the concept of a manifest, which serves to carry information about the
constituent resources of the publication. The manifest includes metadata that describes the publication
as a whole, as it has an identity and nature beyond its constituent resources. The metadata and manifest
also incorporate information about the sequence and presentation of the content.</p>
<p>A Web Publication also provides a default ordering of its primary constituent resources, although that
order may be changed by user interaction or scripting. The user is able to access any primary resource
directly via navigation provided by the publication itself or via the user agent.</p>
</section> -->
<section id="terminology">
<h3>Terminology</h3>
<dl>
<dt><dfn>Default Reading Order</dfn></dt>
<dd><p>The default reading order is a specific progression through the <a>primary resources</a> defined in
the <a>manifest</a> by the creator of a <a>Web Publication</a>.</p>
<p>A user might follow alternative pathways through the content, but in the absence of such interaction
the default reading order defines the expected progression from one primary resource to the
next.</p></dd>
<dt><dfn data-lt="IRI">IRI</dfn></dt>
<dd><p>An IRI, or Internationalized Resource Identifier, is an extension to the URI specification to allow
characters from Unicode. There is a mapping algorithm for translating between IRIs and the equivalent
encoded URI form. IRIs are defined by [[!rfc3987]].</p></dd>
<dt><dfn data-lt="Manifests">Manifest</dfn></dt>
<dd><p>A manifest represents structured information about a <a>Web Publication</a>, such as informative
metadata, a list of all <a data-lt="primary resource">primary</a> and <a>secondary resources</a>, and
the <a>default reading order</a>.</p></dd>
<dt><dfn data-lt="Primary Resources">Primary Resource</dfn></dt>
<dd><p>A primary resource is one that is listed in the <a>default reading order</a> of a <a>Web
Publication</a>.</p></dd>
<dt><dfn data-lt="Secondary Resources">Secondary Resource</dfn></dt>
<dd><p>A secondary resource is one that is required for the processing or rendering of a <a>primary
resource</a>.</p></dd>
<dt><dfn data-lt="Web Publications">Web Publication</dfn></dt>
<dd><p>A Web Publication is a collection of one or more <a>primary resources</a>, organized together through
a <a>manifest</a> into a single logical work with a <a>default reading order</a>. The Web Publication
is uniquely identifiable and presentable using Open Web Platform technologies.</p></dd>
<dt><dfn data-lt="Web Publication Canonical Identifier">Web Publication Canonical Identifier</dfn></dt>
<dd><p>A Web Publication canonical identifier is assigned to a Web Publication by the publisher.
It SHOULD be a dereferenceable IRI and the Web Publication Address. If not, it MUST be possible to
make a 1-to-1 mapping to the Web Publication Address. If a dereferenceable IRI it MAY be used as the
value of the href attribute of a canonical link element (i.e., a link element with a
rel='canonical' attribute).</p></dd>
<dt><dfn data-lt="Web Publication Identifier">Web Publication Identifier</dfn></dt>
<dd><p>A Web Publication identifier is metadata that is intended to be used to refer to a Web Publication
in a persistent and unambiguous manner. IRIs, URIs, DOIs, ISBNs, PURLs are all examples of
identifiers frequently used in publishing.</p></dd>
<dt><dfn data-lt="Web Publication Address">Web Publication Address</dfn></dt>
<dd><p>A Web Publication Address is a URL or other dereferenceable IRI which refers to the location of a
Web Publication and enables the retrieval of a representation of the manifest of the Web
Publication.</p></dd>
</dl>
</section>
</section>
<section id="conformance">
<section>
<h2>Conformance Classes</h2>
<p>This specification defines two conformance classes: one for <a>Web Publications</a> and one for user agents that process them.</p>
<p id="wp-conformance">A Web Publication is conformant to this specification if it meets the following criteria:</p>
<ul>
<li>It MUST have at least one <a>primary resource</a>.</li>
<li>It MUST have a <a>manifest</a> that conforms to all normative requirements defined in <a href="#manifest">Manifest</a>.</li>
</ul>
<p id="ua-conformance">A user agent is conformant to this specification if it meets the following criteria:</p>
<ul>
<li>It MUST be capable of processing and interpreting the manifest, as defined in <a href="#manifest">Manifest</a>.</li>
</ul>
</section>
</section>
<section id="manifest">
<h2>Manifest</h2>
<section id="manifest-intro" class="informative">
<h3>Introduction</h3>
<div class="ednote"> Placeholder for introduction to manifests. </div>
</section>
<section id="manifest-metadata">
<h3>Metadata</h3>
<div class="ednote"> Placeholder for explanation of metadata requirements for publications. </div>
<section>
<h4>Identifier Metadata</h4>
<p>When published, a Web Publication SHOULD be assigned a canonical identifier. This canonical identifier MUST be unique
to the Web Publication and, if assigned, MUST be included in the Web Publication manifest. The Identifying IRI
(i.e., the canonical identifier if it is an IRI or the locator mapped from the canonical identifier) MUST enable
the retrieval of a representation of the manifest of the Web Publication. The Identifying IRI does not preclude
the creation and use of other identifiers and / or locators to retrieve a representation of a Web Publication
in whole or part.</p>
<div class="note">The Identifying IRI can also be used as value for an identifier link relation
[[https://tools.ietf.org/html/draft-vandesompel-identifier-00#section-3.1]].</div>
<div class="ednote"> Placeholder for further explanation of additional publication identifier metadata,
e.g., identifier and locator metadata associated with secondary (and primary?) resources. </div>
</section>
</section>
<section id="manifest-resources">
<h3>Resources</h3>
<div class="ednote"> Placeholder for explanation of enumerating the resources in a publication. </div>
</section>
<section id="manifest-reading-order">
<h3>Reading Order</h3>
<div class="ednote"> Placeholder for explanation of listing the default reading order of a publication.
</div>
</section>
<section id="manifest-nav-doc">
<h3>Navigation Document</h3>
<div class="ednote"> Placeholder for explanation of requirements of navigation (table of contents, landmarks,
etc.). </div>
</section>
</section>
<section id="pub-identification">
<h2>Publication Identification</h2>
<div class="ednote"> Placeholder for how a document identifies it is or belongs to a publication.
May need to revise title of this section....</div>
</section>
<section id="ack" data-include="common/html/acknowledgements.html" data-include-replace="true"></section>
</body>
</html>