This repository has been archived by the owner on Jan 25, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
/
Copy pathindex.html
executable file
·748 lines (652 loc) · 49.3 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
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta content="text/html; charset=utf-8" http-equiv="content-type">
<title>Publishing WG Charter</title>
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2005/10/w3cdoc.css" media="screen">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/Guide/pubrules-style.css">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css">
<style type="text/css">
ul#navbar {
font-size: small;
}
ul li{
margin-bottom: 0.2em;
}
dt.spec {
font-weight: bold;
}
figcaption {
text-align: center;
}
dt.spec new {
background-color: yellow;
background-image: none;
background-repeat: repeat;
background-attachment: scroll;
background-position: 0% 0%;
}
.issue {
background-color: cornsilk;
background-image: none;
background-repeat: repeat;
background-attachment: scroll;
background-position: 0% 0%;
font-style: italic;
}
.todo {
color: rgb(153, 0, 0);
font-style: italic;
}
footer {
font-size: small;
}
.warning {
box-shadow: 10px 5px 3px 0px gray;
border-top-width: thin;
border-right-width: thin;
border-bottom-width: thin;
border-left-width: thin;
border-top-style: solid;
border-right-style: solid;
border-bottom-style: solid;
border-left-style: solid;
border-radius: 3px;
width: 80%;
padding-top: 0.5em;
padding-right: 0.5em;
padding-bottom: 0.5em;
padding-left: 0.5em;
}
.warning h1 {
font-size: 130%;
font-style: italic;
font-weight: bold;
text-align: center;
}
.warning p {
font-size: 110%;
}
section section {
margin-left: 2em;
}
h3 {
counter-reset: h4
}
h4:before {
content: counter(h2) "." counter(h3) "." counter(h4) " ";
display: inline;
}
h4 {
counter-increment: h4;
counter-reset: h5;
}
h5:before {
content: counter(h2) "." counter(h3) "." counter(h4) "." counter(h5) " ";
display: inline;
}
h5 {
counter-increment: h5;
}
h4, h5, h6 {
font-size: 100%;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li><a href="#goals">Goals</a></li>
<li><a href="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</a></li>
<li><a href="#coordination">Coordination</a></li>
<li><a href="#participation">Participation</a></li>
<li><a href="#communication">Communication</a></li>
<li><a href="#decisions">Decision Policy</a></li>
<li><a href="#patentpolicy">Patent Policy</a></li>
<li><a href="#licensing">Licensing</a></li>
<li><a href="#about">About this Charter</a></li>
</ul>
</aside>
<p>
<a href="https://www.w3.org/"><img alt="W3C" src="https://www.w3.org/Icons/w3c_home" height="48" width="72"></a>
</p>
</header>
<main>
<h1 id="title">Publishing Working Group Charter</h1>
<p class="mission">
The <strong>mission</strong> of the <a href="https://www.w3.org/publishing/groups/publ-wg/">Publishing Working Group</a> is to enable all Web Publications (see below) — with all their specificities and traditions — to become first-class entities on the Web.
The WG will provide the necessary technologies on the Open Web Platform to make the combination of traditional publishing and the Web complete in terms of accessibility, usability, portability, distribution, archiving, offline access, and reliable cross referencing.
</p>
<div class="noprint">
<p class="join">
<a href="https://www.w3.org/2004/01/pp-impl/100074/join">Join the Publishing Working Group.</a>
</p>
</div>
<section id="details">
<table class="summary-table">
<tbody>
<tr id="Start">
<th>Start date </th>
<td>12 June, 2017</td>
</tr>
<tr id="End">
<th>End date </th>
<td>1 July, 2020</td>
</tr>
<tr>
<th>Chairs </th>
<td>Garth Conboy (Google) and Tzviya Siegman (John Wiley & Sons., Inc.) </td>
</tr>
<tr>
<th>Team Contacts </th>
<td><a href="https://www.w3.org/People/Ivan/">Ivan Herman</a> (0.4 <abbr title="Full-Time Equivalent">FTE</abbr>)</td>
</tr>
<tr>
<th> Meeting Schedule </th>
<td> <strong>Teleconferences:</strong> 1-hour calls will be held weekly. <br> <strong>Face-to-face:</strong> We will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year. <br>
(See also the <a href="#communication">section on communications</a> for further details.)
</td>
</tr>
</tbody>
</table>
</section>
<section id="goals" class="goals">
<h2>Goals</h2>
<p>
Publications, from magazine articles to product documentation, from electronic books to scholarly journal articles, are increasingly present on the Web.
While following the traditions of the publishing world in terms of typesetting, layout, ergonomics, and usage patterns, the Web brings a new level of pervasive accessibility, internationalization, addressability, and interconnectedness to these publications.
However, the combination of traditional publishing and the Web is not yet perfect: the <a href="https://www.w3.org/TR/pwp-ucr/">“Web Publications Use Cases and Requirements”</a> document, published by the <a href="https://www.w3.org/dpub/IG/">Digital Publishing Interest Group</a>, lists a number of use cases and requirements for publications on the Web.
</p>
<p>
It is the goal of the Publishing Working Group to provide, in concert with other W3C Groups as outlined in <a href="#w3c-coordination">Section 4.1</a>, the necessary technologies on the Open Web Platform to make the combination of traditional publishing and the Web complete in terms of the readers’ needs, portability, distribution, archiving, offline access, or reliable cross referencing.
In short, <em>all publications—with all their specificities and traditions—should become first-class entities on the Web</em>, as Web Publications.
</p>
<p>
A <strong>Web Publication (WP)</strong> is a collection of one or more constituent resources, organized together in a uniquely identifiable grouping that may be presented using standard Open Web Platform technologies.
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 <a href="https://tools.ietf.org/html/rfc6454">origin</a> for the WP, and a URL that can uniquely identify that <a href="https://archive.ifla.org/VII/s13/frbr/frbr1.htm#3.2">(<abbr title="Functional Requirements for Bibliographic Records">FRBR</abbr>)</a> manifestation.
The detailed requirements have already been <a href="https://www.w3.org/TR/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 it may be hosted at some other origin.
</li>
<li>
A Web Publication may be packaged by having all its constituent resources combined into a single file.
A Web Publication’s origin is essential information if it is to become portable.
The act of packaging must be reversible; one must be able to recover the original structure and organization.
</li>
<li>
It must be possible to make Web Publications accessible to a broad range of readers with different needs and capabilities.
</li>
<li>
A Web Publication must be available and functional while the user is offline.
</li>
<li>
A Web Publication, having an identity and nature beyond its constituent resources, will have metadata that describes the publication as a whole.
</li>
<li>A Web Publication must provide access to a range meta-information including (but not restricted to):
<ul style="margin-top:0.2em">
<li>table of contents, default or alternate reading order;</li>
<li>security and authentication data;</li>
<li>metadata such as author(s), title, and unique identification.</li>
</ul>
</li>
</ul>
<p>
<strong><a href="https://www.w3.org/Submission/2017/SUBM-epub31-20170125/">EPUB</a></strong> has become one of the fundamental technologies for the global publishing ecosystem (see the <a href="https://w3c.github.io/publ-bg/docs/EPUB4_business_case.html">separate document</a>, published by the <a href="https://www.w3.org/community/publishingbg/">W3C Publishing Business Group</a>, for more details and background).
It is the preferred format for a broad range of types of publications, not only for distribution but increasingly also for authoring and production workflows.
As part of the work on Web Publications, described in this charter, it is essential that a next generation of EPUB, currently referred to as EPUB 4, retain the specificity, portability, predictability, accessibility, and internationalization required by the publishing ecosystem while benefitting from the improved features and functionalities offered by Packaged Web Publications.
EPUB 4 should not be in conflict with Web Publications; it should be a type of Web Publication that provides the predictability and interoperability that this ecosystem has come to rely on.
</p>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>
The WG will specify Web Publications and identify what they need the underlying Web platform to provide.
It will build upon existing platform technologies specified by other groups, where available, seeking to fill gaps by assuring that the unique requirements of Web Publications are addressed by features (including optional features) or extension points in those specifications.
</p>
<p>
In particular, the WG will make normative Recommendations for Web Publications; Packaged Web Publications; EPUB 4; and DPUB-ARIA 2.0, as described in <a href="#deliverables">Deliverables</a> below.
</p>
<p>
Recommendation-track deliverables will contain mechanisms to make Web Publications accessible to a broad range of readers with different needs and capabilities.
This includes general Web Content Accessibility Guidelines (WCAG) and Web Accessiblity Initiative (WAI) requirements of the W3C as well as requirements for international readers using different scripts and document formats.
Profiles of Web Publications may be defined with more stringent accessibility requirements.
</p>
<section>
<h3 id="out-of-scope">Out of Scope</h3>
<p>
The following features are out of scope, and will not be addressed by this Working group.
</p>
<ul class="out-of-scope">
<li>
Digital Rights Management (DRM) features for Web Publications.
</li>
<li>
New metadata vocabularies.
</li>
<li>
New document identification schemes (i.e., alternatives to DOI or ISBN).
</li>
<li>
Maintenance of EPUB 3 (and previous versions of EPUB) (done in the separate <a href="https://www.w3.org/community/epub3/">EPUB 3 Community Group</a>).
</li>
</ul>
</section>
<section>
<h3>Success Criteria</h3>
<p>
In order to advance to <a href="https://www.w3.org/2017/Process-20170301/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each specification is expected to have <a href="https://www.w3.org/2017/Process-20170301/#implementation-experience">at least two independent implementations</a> of each of feature defined in the specification.
</p>
<p>
Each specification should contain a section detailing any known security or privacy implications for implementers, Web authors, and end users.
</p>
<p>
Each specification should contain a section describing: known impacts on accessibility for users with disabilities; ways the specification features address those impacts; and recommendations for minimizing accessibility problems in implementation.
</p>
<p>
Testing plans for each specification should be provided, starting from the earliest drafts.
</p>
</section>
</section>
<section id="deliverables">
<h2> Deliverables </h2>
<p>
More detailed milestones and updated publication schedules are available on the <a href="https://www.w3.org/publishing/groups/publ-wg/PublStatus">group publication status page</a>.
</p>
<p>
To facilitate timely progress on the Recommendation track and for the sake of maintainability the Working Group may, based on consensus in the Working Group, split or merge its deliverables.
</p>
<section id="normative">
<h3>Recommendation-track Deliverables</h3>
<p>
The Working Group will deliver the following W3C normative specifications (titles of the documents are provisional; some documents listed below may be grouped into one document or split into several, constituent documents):
</p>
<dl>
<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, organized together in a uniquely identifiable grouping that may be 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>
<dt class="spec" id="pwp">Packaged Web Publications</dt>
<dd>
<p>
This specification defines a way to combine the resources of a Web Publication into a distributable file using a packaging format.
Note that if the <a href="https://w3ctag.github.io/packaging-on-the-web/">Packaging on the Web</a> work leads to a W3C Recommendation and fulfills all the requirements for Packaged Web Publications, publishing this deliverable <i>may</i> become unnecessary.
</p>
</dd>
<dt class="spec" id="epub4">EPUB 4</dt>
<dd>
<p>
This specification defines a functional <em>profile</em> of the general idea of Packaged Web Publications that may deliver a higher degree of comprehensive accessibility capabilities and reliability.
This specification should generally be a functional superset of EPUB 3.1.
Functional round-tripping to/from EPUB 3.1 considered highly desirable.
</p>
</dd>
<dt class="spec" id="structural-semantics">DPUB-ARIA Module 2.0</dt>
<dd>
<p>
This specification extends the <a href="https://www.w3.org/TR/dpub-aria-1.0/">DPUB-ARIA Module 1.0</a> specification, adding terms for a more complete coverage of publication-related terms.
Its primary input is the full set of terms defined by the <a href="https://idpf.github.io/epub-vocabs/structure/">EPUB 3 Structural Semantics Vocabulary</a> but other, similar vocabularies will also be considered.
</p>
</dd>
</dl>
</section>
<section id="ig-other-deliverables">
<h3> Other Deliverables </h3>
<dl>
<dt class="spec">Requirements for Latin Text Layout and Pagination (Working Group Note)</dt>
<dd>
<p>
This document will describe the requirements for pagination and layout of publications that use the Latin script, based on the tradition of print book design and composition.
These principles can inform the pagination of digital content as well, and serve as a reference for the CSS Working Group and other interested parties.
</p>
<p>
This deliverable draws upon a <a href="http://w3c.github.io/dpub-pagination/">previous version of this document</a>, published by the <a href="https://www.w3.org/dpub/IG/">Digital Publishing Interest Group</a>.
</p>
</dd>
</dl>
<p>Other non-normative documents may also be created such as: </p>
<ul>
<li>Use case and requirement documents.</li>
<li>Test suites and implementation reports for the specification.</li>
<li>Primers or Best Practice documents to support content authors and application developers.</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">
<h3>Milestones</h3>
<p>
The group’s <a href="https://www.w3.org/publishing/groups/publ-wg/PublStatus">Publication Status</a> document provides current data about all of the group’s specifications.
Although the group expects all of its active deliverables to progress during this charter period, the charter does not include detailed milestone data for each specification because such data is speculative and easily becomes out of date.
The Working Group does expect the following to occur:
</p>
<ul id="milestone_list">
<li>Face-to-face meeting, June 22-23, 2017, New York City, NY, USA.</li>
<li>Face-to-face meeting at the W3C TPAC meeting, week of November 6, Burlingame, CA, USA.</li>
<li>WP:
<ul>
<li>First Public Working Draft (FPWD): Q4 2017.</li>
<li>Candidate Recommendation (CR): Q1 2019.</li>
<li>Recommendation (REC): Q2 2020.</li>
</ul>
</li>
<li>PWP:
<ul>
<li>First Public Working Draft (FPWD): Q4 2017.</li>
<li>Candidate Recommendation (CR): Q1 2019.</li>
<li>Recommendation (REC): Q2 2020.</li>
</ul>
</li>
<li>EPUB 4:
<ul>
<li>First Public Working Draft (FPWD): Q1 2018.</li>
<li>Candidate Recommendation (CR): Q1 2019.</li>
<li>Recommendation (REC): Q2 2020.</li>
</ul>
</li>
<li>DPUB-ARIA:
<ul>
<li>First Public Working Draft (FPWD): Q1 2018.</li>
<li>Candidate Recommendation (CR): Q4 2018.</li>
<li>Recommendation (REC): Q4 2019.</li>
</ul>
</li>
</ul>
<figure aria-describedby="#milestone_list">
<img src="figures/timeline.svg" style="width:90%" alt="The timeline of the deliverables">
<figcaption>
Major milestones (figure also available as a <a href="figures/timeline.png">PNG image</a>)
</figcaption>
</figure>
</section>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>
For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/Charter.html#horizontal-review">horizontal review</a> for accessibility (via the <a href="http://www.w3.org/WAI/APA/">Accessible Platform Architectures WG</a>), internationalization (via the <a href="https://www.w3.org/International/core/Overview">Internationalization WG</a>), performance (via the <a href="https://www.w3.org/webperf/">Web Performance WG</a>), privacy (via the <a href="http://www.w3.org/Privacy/">Privacy IG</a>), security (via the <a href="http://www.w3.org/Security/IG/">Web Security IG</a>), and with the <a href="https://www.w3.org/2001/tag/">Technical Architecture Group (TAG)</a>.
Invitation for review must be issued during each major standards-track document transition, including <a href="https://www.w3.org/2017/Process-20170301/#RecsWD" title="First Public Working Draft">FPWD</a> and at least 3 months before <a href="https://www.w3.org/2017/Process-20170301/#RecsCR" title="Candidate Recommendation">CR</a>, and should be issued when major changes occur in a specification.
</p>
<p>
Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/2017/Process-20170301/#WGCharter">W3C Process Document</a>:
</p>
<section>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/WebPlatform/WG/">Web Platform Working Group</a></dt>
<dd>
<p>
This group develops and/or maintains a number of specifications that may be fundamental for the specification and/or the implementation of Web Publications. Examples are:
</p>
<ul style="margin-bottom:1em">
<li><em>Web App Manifests</em>, that may be the basis for specifying table of content, metadata, etc., provided by a Web Publication.</li>
<li><em>Service Workers</em>, that may become the fundamental building block for the implementation and testing of Web Applications.</li>
<li><em>Packaging on the Web</em> (jointly developed with the <a href="http://www.w3.org/2001/tag/">Technical Architecture Group</a>) may provide a way of packaging for the purpose of Packaged Web Publications.</li>
</ul>
</dd>
<dt><a href="http://www.w3.org/Style/CSS/members">CSS Working Group</a></dt>
<dd>
<p>
New CSS features may be needed to support web publications. Such features would be specified in the CSS Working Group, with the Publishing Working Group providing use cases, requirements, and examples.
The Publishing Working Group would also help the CSS WG with the development and testing of new and existing CSS functionality that is of interest to the publishing community.
The group will designate liaisons to work with the CSS WG on issues as needed. Liaisons will ideally be part of both groups.
</p>
</dd>
<dt><a href="http://www.w3.org/2011/webappsec/">Web Application Security Working Group</a></dt>
<dd>
<p>
Porting a Web Publication, hosting the publication at some other origin, may raise security issues.
The Publishing Working Group will have to work closely with the Web Application Security WG to ensure that the approaches developed by that Working Group are adopted by Web Publication, and any additional work done by the Publication Working Group are in line with general Web Application Security.
</p>
</dd>
<dt><a href="http://www.w3.org/WAI/ARIA/">Accessible Rich Internet Applications WG</a></dt>
<dd>
<p>
This Working Group is responsible for the development of ARIA; the development of DPUB-ARIA Module 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/">Accessibility Guidelines Working Group</a></dt>
<dd>
<p>
The Publishing Working Group will work with the AG Working Group to address digital publishing use cases in accessibility guidelines, and develop techniques to implement accessibility features in web publications.
The group will designate liaisons to work with the AG on issues as needed.
Liaisons will ideally be members of both groups.
</p>
</dd>
<dt><a href="https://www.w3.org/community/epub3/">EPUB 3 Community Group</a></dt>
<dd>
<p>
While working on EPUB 3-related projects, the EPUB 3 Community Group may surface technical concerns, requirements, and issues that are also relevant to the work of the Publishing Working Group.
The two groups will coordinate to ensure that such issues are taken into account by the Publishing Working Group.
</p>
</dd>
<dt><a href="https://www.w3.org/community/publishingbg/">Publishing Business Group</a></dt>
<dd>
<p>
The mission of the Publishing Business Group is to foster ongoing participation by members of the publishing industry and overall ecosystem in the development of the Web for publishing, and to serve as a conduit for feedback between the publishing ecosystem and W3C.
In doing so, technical or business requirements may come up that are also relevant to the work of the Publishing Working Group.
The two groups will formally cooperate to ensure that such issues are taken into account by the Publishing Working Group.
</p>
</dd>
</dl>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a href="bisg.org">Book Industry Study Group (BISG)</dt>
<dd>
<p>
This group currently maintains the <a href="http://epubtest.org/">EPUB 3 Support Grid</a>, which provides information and reading-system support for EPUB 3.
This tool may be extended to track support for WP in general and EPUB 4 in particular.
</p>
</dd>
<dt><a href="https://edrlab.org/edrlab/">EDRLab</a></dt>
<dd>
<p>
EDRLab, acting as the European headquarter of the <a href="http://readium.org/">Readium Foundation</a>, is actively working on the ReadiumJS, Readium SDK and Readium-2 projects.
The latter is especially interesting as a future reference implementation of PWP and EPUB 4.
</p>
</dd>
</dl>
</section>
<section id="input-documents">
<h3>Input Documents</h3>
<p>
The following documents will be considered by the Working Group as inputs to the specifications to be developed.
The Working Group will identify requirements that are not yet fully covered by the current environments based on the Open Web Platform, that therefore need further work, while re-using existing technologies developed by other Working Groups to the extent possible.
The Working Group should not reinvent technologies that have been, or are being developed elsewhere in W3C Working Groups, and should seek instead further cooperation with the relevant groups.
</p>
<ul>
<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.
(Note that Web App Manifests are <em>distinct</em> from the now-defunct effort on Cache Manifests.)
</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.
In particular, Service Workers offer facilities for an offline access to documents published on the Web.
</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="http://www.w3.org/TR/dpub-aria-1.0/">Digital Publishing WAI-ARIA Module 1.0</a>.
The planned DPUB ARIA Module 2.0 is planned to be an extension to this specification.
</li>
<li>
<a href="https://idpf.github.io/epub-vocabs/structure/">EPUB 3 Structural Semantics</a>.
This document will form the basis for the work on DPUB-ARIA Module 2.0.
</li>
<li>
The WG expects to rely on other relevant Recommendations including <a href="https://www.w3.org/TR/html/">HTML</a>, <a href="https://www.w3.org/TR/SVG/">SVG 1.1</a>, <a href="https://www.w3.org/TR/CSS/">CSS</a>, <a href="https://www.w3.org/TR/wai-aria-1.1/">Accessible Rich Internet Applications (WAI-ARIA) 1.1</a>, <a href="https://www.w3.org/TR/odrl-model/">ODRL Information Model</a>, and <a href="https://www.w3.org/TR/odrl-vocab/">ODRL Vocabulary & Expression</a>.
</li>
</ul>
<p>
The following documents provide inputs for non-normative work:
</p>
<ul>
<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 has collected a number of accessibility features that are relevant for the publishing community and not (yet) part of the W3C Web Content Accessibility Guidelines.
This document provides a basis for the working aiming at the extension of future versions of WCAG regarding publishing.
</li>
<li>
<a href="http://w3c.github.io/dpub-pagination/">Requirements for Latin Text Layout and Pagination</a>.
This document has been worked on by the <a href="https://www.w3.org/dpub/IG/">Digital Publishing Interest Group</a> (whose charter expires in October 2017).
The Working Group will continue this work and plans to publish a Working Group Note.
</li>
</ul>
<p> References: </p>
<ul>
<li>
<a href="https://www.w3.org/TR/pwp/">Web Publications for the Open Web Platform: Vision And Technical Challenges</a>.
This document summarizes the technical deliberations on the subject by the DPUB Interest Group.
</li>
<li>
<a href="https://www.w3.org/TR/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/Submission/2017/SUBM-epub31-20170125/">EPUB 3.1</a>.
The Member Submission of EPUB 3 will be an important input into Web Publications, Portable Web Publications, and EPUB 4.
Compatibility with EPUB 3 will be a consideration in the development of all three specifications.
(Note that this reference is to an “umbrella” document for a <a href="https://www.w3.org/Submission/2017/SUBM-epub31-20170125/#sec-epub-specs">suite of six specifications</a>.)
</li>
<li>
<a href="https://github.com/readium/webpub-manifest">Readium Web Publication Manifest</a>.
First draft of a Web Publication manifest format, provided by the <a href="http://readium.org/">Readium Consortium</a>.
</li>
<li>
<a href="http://www.idpf.org/epub/profiles/edu/spec/">EPUB for Education</a>.
This profile of EPUB 3 gives a good example for the type of profiles that the publishing community uses.
</li>
</ul>
</section>
</section>
<section class="participation">
<h2 id="participation">Participation</h2>
<p>
To be successful, this Working Group is expected to have 6 or more active participants for its duration, including representatives from key implementers and users (e.g., publishers, authors) of this specification, and active Editors and Test Leads for each specification.
The Chairs, specification Editors, and Test Leads are expected to contribute 4 hours per week towards the Working Group.
There is no minimum requirement for other Participants.
</p>
<p>
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href="#communication">Communication</a>.
</p>
<p>
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a>.
Chairs and Team contacts may also contact these contributors to encourage them to join the Working Group to make their licensing commitment easier.
</p>
</section>
<section id="communication">
<h2> Communication </h2>
<p id="public">
Technical discussions for this Working Group are conducted in <a href="https://www.w3.org/2017/Process-20170301/#confidentiality-levels">public</a>: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public.
Working Drafts and Editor’s Drafts of specifications will be developed on a public repository, and the drafts may permit direct public contribution requests.
The meetings themselves are not open to public participation, however.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="https://www.w3.org/publishing/groups/publ-wg/">Publishing Working Group home page.</a>
</p>
<p>
Most Publishing Working Group teleconferences will focus on discussion of particular specifications.
The calls will be conducted on a weekly basis.
</p>
<p>
This group primarily conducts its technical work on the public mailing list <a id="public-email" href="mailto:public-publ-wg@w3.org">public-publ-wg@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/public-publ-wg/">archive</a>), and through GitHub repositories and issues.
These, but also tools like IRC channels and possibly other communication technologies should make asynchronous work possible.
The <a href='#decisions'>decision policy</a> adopted by the group is defined to allow this.
</p>
<p>
The public is invited to review, discuss and contribute to this work.
</p>
<p>
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
</p>
</section>
<section id="decisions">
<h2> Decision Policy </h2>
<p>
This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/2017/Process-20170301/#Consensus"> W3C Process Document (section 3.3</a>).
Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers. Consensus emerges with little formal voting being required.
</p>
<p>
However, if a decision is necessary for timely progress, but consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote, recording a decision along with any objections.
</p>
<!-- <p>
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional until 5 working days after the publication of the resolution in draft minutes sent to the group's mailing list.
Depending on the chairs’ evaluation of the group consensus on an issue a call for consensus (CfC) may be also issued as an addition to, or as a replacement for, a meeting resolution (for example, via email and/or web-based survey), with a response period from 5 to 10 working days.
If no objections are raised on the mailing list by the end of the response period, the resolution will be considered to have obtained consensus as a resolution of the Working Group.
</p> -->
<p>
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional.
A call for consensus (CfC) will be issued for all resolutions (for example, via email and/or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue.
If no objections are raised on the mailing list by the end of the response period, the resolution will be considered to have obtained consensus as a resolution of the Working Group.
</p>
<p>
All decisions made by the group should be considered resolved unless and until new information becomes available, or unless reopened at the discretion of the Chairs or the Director.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/policies#Votes">W3C Process Document (Section 3.4, Votes)</a>. It includes no voting procedures beyond what the Process Document requires.
</p>
</section>
<section id="patentpolicy">
<h2> Patent Policy </h2>
<p>
This Working Group operates under the <a href="http://w3.org/Consortium/Patent-Policy-20040205/">W3C Patent Policy</a> (5 February 2004 Version).
To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the <a href="https://www.w3.org/2004/01/pp-impl/">W3C Patent Policy Implementation</a>.
</p>
</section>
<section id="licensing">
<h2>Licensing</h2>
<p>
This Working Group will use the <a href="https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document">W3C Software and Document license</a> for all its deliverables.
</p>
</section>
<section id="about">
<h2> About this Charter </h2>
<p>
This charter has been created according to <a href="https://www.w3.org/Consortium/Process/groups#GAGeneral">section 5.2</a> of the <a href="https://www.w3.org/Consortium/Process">Process Document</a>.
In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
</p>
<!-- <section id="history">
<h3>Charter History</h3>
<p>
The following table lists details of all changes from the initial charter, per the <a href="https://www.w3.org/2017/Process-20170301/#CharterReview">W3C Process Document (section 5.2.3)</a>:
</p>
<table class="history">
<tbody>
<tr>
<th>Charter Period</th>
<th>Start Date</th>
<th>End Date</th>
<th>Changes</th>
</tr>
<tr>
<th>Initial Charter</th>
<td>12 June 2017</td>
<td>1 July 2020</i></td>
<td>–</td>
</tr>
</tbody>
</table>
</section> -->
</section>
</main>
<hr>
<footer>
<address><a href="https://www.w3.org/publishing/groups/publ-bg/">Publishing BG</a> & <a href="https://www.w3.org/dpub/IG/">DPUB IG</a>; ed: <a href="mailto:ivan@w3.org">Ivan Herman</a></address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2017 <a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> ( <a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="https://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a> ), All Rights Reserved. <abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
<p>$Id: index.html,v 1.7 2017/06/07 14:09:07 ivan Exp $</p>
</footer>
</body>
</html>