-
Notifications
You must be signed in to change notification settings - Fork 13
/
index.html
1840 lines (1788 loc) · 107 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
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html>
<head>
<title>Web Publications Use Cases and Requirements</title>
<meta charset='utf-8'>
<script src='https://www.w3.org/Tools/respec/respec-w3c-common.js' class='remove' defer="defer"></script>
<script src="scripts/rcollect.js" class="remove"></script>
<script src="scripts/rdisplay.js" class="remove"></script>
<script src="https://w3c.github.io/wpub/common/js/biblio.js" class="remove"></script>
<link href="common/css/common.css" rel="stylesheet" type="text/css">
<link rel="stylesheet" href="extras.css">
<script class='remove'>
var respecConfig = {
preProcess : [rcollect, rdisplay, uccollect, ucdisplay],
postProcess : [rstore],
specStatus: "ED",
// publishDate: "2017-05-02",
shortName: "pwp-ucr",
editors: [
{
"name": "Franco Alvarado",
"company": "Macmillan Higher Education",
"companyURL": "http://macmillan.com/",
"w3cid": 105737
},
{
"name": "Joshua Pyle",
"company": "Wiley",
"companyURL": "https://www.wiley.com",
"w3cid": 102151
}
],
otherLinks: [{
key: "Editors of the previous version",
data: [{
value: "Heather Flanagan, Invited Expert",
href: "https://www.rfc-editor.org/"
}, {
value: "Ivan Herman, W3C",
href: "http://www.w3.org/People/Ivan/"
}, {
value: "Leonard Rosenthol, Adobe Systems",
href: "https://www.adobe.com"
}]
}],
previousMaturity: "WG-NOTE",
previousPublishDate: "2019-02-19",
processVersion: 2018,
includePermalinks: true,
permalinkEdge: true,
permalinkHide: false,
diffTool: "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
wg: "Publishing Working Group",
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/dpub-pwp-ucr/",
branch: "gh-pages"
},
localBiblio: {
"wpub": {
"title": "Web Publications",
"href": "https://www.w3.org/TR/wpub/",
"authors": [
"Matt Garrish",
"Ivan Herman"
]
}
},
// noRecTrack: "true"
};
</script>
<style media="screen">
ul.use-cases::before {
content: "Usage examples:";
font-weight: bold;
font-style: italic;
text-decoration: underline;
}
ul.requirements::before {
content: "Requirements:";
font-weight: bold;
font-style: italic;
text-decoration: underline;
}
</style>
</head>
<body>
<section id='abstract'>
<p>
Publications, from corporate memos to newsletters to electronic books to scholarly journal articles, must be
considered first-class content on the Web, equal to the more common forms of Web pages available today. This
document describes the various use cases highlighting the problems users and publishers face when these
publications are to be used in a digital, Web environment. The requirements that come from those use cases
provide the basis for the technical considerations in a companion document, currently entitled “Web
Publications” [[wpub]].
</p>
</section>
<section id='sotd'>
<!-- <p>
This is work in progress. The final version of this document is planned to be published as a Working Group Note.
</p> -->
<p>
A previous version of this document was published by the <a href="https://www.w3.org/dpub/IG">Digital Publishing
Interest Group</a> as an <a href="https://www.w3.org/TR/2017/NOTE-pwp-ucr-20170502/">Interest Group Note</a>.
After the closure of that Interest Group the <a href="https://www.w3.org/publishing/groups/publ-wg/">Publishing
Working Group</a> took it over for further work.
</p>
</section>
<section id="introduction">
<h2>Introduction</h2>
<p>
The Web emerged in 1994, based on a model of individual pages loosely joined by hyperlinks. Clustering within
domains and with explicit navigation elements built into them, webpages evolved into websites. Despite the
Web's strong connections to print media (e.g. web resources are “pages” and the in-memory model for Web
applications is the “Document Object Model”), this document argues that the web platform may still not be
meeting certain requirements from print media that users desire.
</p>
<p>
Over centuries, “books” have assumed many forms: journals, magazines, pamphlets of long-form articles and
essays, newspapers, atlases, comics, notebooks, albums of all sorts. We can define these different
manifestations as “publications”: bound editions of meaningful media, made public.
</p>
<p>
Another form of publication that also has a long history in both the printed as well as the digital world are
documents. These are publications that are written and distributed in a more ad-hoc manner, such as legal
briefs, corporate memos, and even the definitions of standards, such as this content currently being read.
</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 (OWP). New models of
economic sustainability and innovative experiences of knowledge depend on this.
</p>
<p>
It is the task of the W3C <a href="https://www.w3.org/dpub/IG/">Digital Publishing Interest Group</a> to
explore the uniqueness, desirability, and feasibility of bringing these two great models of publishing
together. This document explores requirements based on examples of real world use cases and scenarios.
Requirements for publications on the Web are explored first, without referring to any packaging aspect that
would correspond to current practices like EPUB. This is followed by requirements of those packaging aspects,
as a structure on top of a purely Web-based distribution. The complete list of requirements is also collected
in <a href="#reqtable">a separate table</a> in an appendix.
</p>
<section>
<h3>Terminology</h3>
<ul class="terms">
<li>
This document uses the term <dfn>user agent</dfn>, as used by the Web community; see, for example, the
<a href="https://www.w3.org/WAI/UA/work/wiki/Definition_of_User_Agent">WAI glossary entry</a>. The
publishing community often uses the term “reading system” for roughly the same notion; while there may be
subtle differences, it is better to stick to a single term for the purposes of this document.
</li>
<li>
A <dfn>Web Publication</dfn> (WP) is a collection of one or more constituent resources, organized together
in a uniquely identifiable grouping, and presented using standard Open Web Platform technologies.
</li>
<li>
A <dfn>Packaged Web Publication</dfn> (PWP) is a <a>Web Publication</a> whose constituent resources are
combined into a single distributable file, using some standard packaging format.
</li>
<li>
In this document, <dfn>manifest</dfn> refers to an abstract means to contain information necessary to the
proper management, rendering, and so on, of a publication. This is opposed to metadata that contains
information on the content of the publication like author, publication date, and so on. The precise format
of how such a manifest is stored is not considered in this document.
</li>
</ul>
</section>
</section>
<section id="web-standards">
<h2>Web Standards</h2>
<section id="owp">
<h3>Open Web Platform</h3>
<p id="r_owp" class="req-set cc-minimal">
Web Publications should be able to make use of all features offered by the Open Web Platform (OWP).
</p>
<p>
There is a remarkable development of tools and frameworks built on top of OWP that make it possible to
develop powerful interactive layers on top of OWP. These include, for example, data visualization systems
(e.g., d3, built on top of SVG), possibilities to access external services like Wolfram Alpha, or tools to
create and store (possibly as part of the publication) annotations. These tools have been traditionally
developed around browsers and provide possibilities that publications should also benefit from. That
requires that <a data-lt="Web Publication">Web Publications</a> become first class citizens on the Web
platform.
</p>
<ul class="use-cases">
<li id="uc_owp_tools">
A large, multidisciplinary, Web-based journal relies on traditional Web technologies like HTML and CSS for
its content. The journal, responding to the evolving expectations of its audience, is increasingly using
additional media such as video, audio, animated graphics, and very large images; the trend is to consider
these as integral parts of the scientific output. The journal as a result needs access to the latest
visualization and other data management tools that the OWP-based tools can offer.
</li>
<li id="uc_owp_lms">
Educational publications are increasingly making use of OWP features. In addition to video, audio, and
animations, they may also include interactive exams (possibly linked to online evaluation facilities),
visualization of data or of algorithms, and built-in interpreters for various languages (e.g., for courses
on programming). In many respects, the borderline between these publications and Web applications is
becoming fuzzy.
</li>
<li id="uc_owp_in_house">
A large technology company with extensive “in-house” documentation to support technical and administrative
processes and user documentation for their various products, develops all this material in digital-only
formats. The quantity of documentation makes it impractical to produce these documents in print. Instead,
the company publishes them on the company intranet, and/or provides them to their employees and contractors
via specialized mobile applications. These documents, as a type of publication, require accessibility,
portability of annotations, and the possible inclusion of complex media.
</li>
<li id="uc_owp_news">
News outlets often rely on video, audio, large images, and interactive elements to enhance their content.
Web Publications would allow news outlets to provide this content in a unique, identifiable format that can
facilitate archiving and offline access.
</li>
<li id="uc_owp_comics">
Image-based narrative content like comics, manga, and graphic novels relies heavily on support for large
images. This type of content may also experiment with interactivity and unique forms of navigation.
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#scope">Scope</a></li>
</ul>
</section>
<section id="horizdep">
<h3>Horizontal Dependencies</h3>
<p id="r_horizdep" class="req-set cc-minimal">
A Web Publication should conform to the requirements of all horizontal dependencies: accessibility,
internationalization, device independence, security, and privacy.
</p>
<p>
Web content has to be consumed under different circumstances: it must be available to the largest possible
audience in a secure manner, providing the necessary protection of the reader’s privacy. Publication content
must be able to answer to a number of principles like accessibility, internationalization, device
independence, security, and privacy. (These are usually referred to, in the W3C context, as “horizontal”
dependencies.) These principles are, in general terms:
</p>
<dl>
<dt>Accessibility:</dt>
<dd>
People with disabilities should be able to access the content of a publication. They should be able to
perceive, understand, navigate, and interact with it, as well as contribute to it. Accessibility
encompasses all disabilities that affect access to the content, including visual, auditory, physical,
speech, cognitive, and neurological disabilities.
</dd>
<dt>Internationalization:</dt>
<dd>
Publications should be well adapted to any language, writing systems, region, or culture. This includes
the usage, when appropriate, of left-to-right, right-to-left, horizontal or vertical writing; item
numbering, or interactive forms specific to local cultures; usage of the right character sets and of
local typographic conventions.
</dd>
<dt>Device Independence:</dt>
<dd>
The content in a publication should be usable on a large number of devices with very different device
characteristics: different screen types and sizes, various input modalities, varying level of processing
power, etc. These different affordances should be automatic with no, or very little, user intervention.
</dd>
<dt>Security:</dt>
<dd>
Publications should be presented by a User Agent using a security model that is at least (if not more)
secure than the standard <a href="https://www.w3.org/TR/runtime/">Web security model</a>. Doing this will
prevent publications that contain malicious attacks, data theft, and other security incidents from
impacting users by jeopardizing the integrity of the underlying data or machine operations.
</dd>
<dt>Privacy:</dt>
<dd>
The content in a publication should maintain and support user privacy, in spite of the fact that the
evolution of online technologies has increased the possibility for the collection and processing of personal,
and possibly sensitive, data. However, since a publication may use <a href="#r_owp">any part of the OWP</a>,
it may choose to use functionality such as the ability to track a user's activity within the publication.
</dd>
</dl>
<p>
These principles correspond to technical requirements on the underlying technologies (i.e., OWP, and its
possible extension to Web Publications) insofar as the technologies must empower the authors (writers,
editors, publishers, etc.) to produce content that follow them. Whether authors use the possibilities of
these technologies or not is not addressed in this document.
</p>
<p>
All these constraints are formalized in the context of the usage on the Web and by extension Web
Publications. This means that they are valid for publications in general. In some cases, for example due to
legislative reasons, the demands on publications may be more stringent than for generic Web sites. The use
cases below provide some examples for the publication-specific situations. Note also that some aspect of
horizontal dependencies (e.g., accessibility or security), are also the subject of further use cases and
requirements elsewhere in this document.
</p>
<ul class="use-cases">
<li id="uc_horizdep_wcag" class="uc-accessibility">
<span class="uc-categories">(On Accessibility)</span> Legal Publishing Ltd. publishes all the official texts
as issued by the government of its country. Per local legislation, the publication must be accessible,
following W3C’s WCAG Level AA requirements, to serve as official references in courts.
</li>
<li id="uc_horizdep_lms" class="uc-accessibility uc-privacy">
<span class="uc-categories">(On Privacy, Accessibility)</span> EducationPublishing Ltd. publishes digital
textbooks to cover BigUniversity’s curriculae. These (digital) educational publications also include access
to interactive tests via specialized services on the Web that regularly access the student’s progress. The
privacy and the integrity of the student’s test data must be preserved. This, and the fact that digital
textbooks must also abide to WCAG Level AA requirement in terms of accessibility, are such that
EducationPublishing may be liable in case they are not fulfilled.
</li>
<li id="uc_horizdep_i18n" class="uc-i18n">
<span class="uc-categories">(On Internationalization)</span> PublicationInternational SA. publishes literary
work all over the world and in many languages. In order to continue its business in different countries, it
must be able to produce digital publications acceptable by local customers. Vertical, right-to-left, and
bidirectional writing, among other typesetting traditions, must be supported by the reading systems and
possible to enable in the Web Publications. Additionally, the reading system should allow for varied
interaction with the content, such as right-to-left page navigation for content in languages like Japanese
and Arabic.
</li>
<li id="uc_horizdep_anonymity" class="uc-privacy">
<span class="uc-categories">(On Privacy)</span> Thomas has written a pamphlet advocating a government
overthrow. The government has decreed that the author of the pamphlet as well as the readers of the pamphlet
shall be jailed. Thomas needs to distribute the pamphlet in ways that preserve his anonymity and allow the
public to read without fear of the government cyber-police.
</li>
<li id="uc_horizdep_devind" class="uc-device-independence">
<span class="uc-categories">(On Device Independence)</span> Yoshio usually reads a book on his tablet when
he is at home, but he does not carry his tablet around while commuting on the train. Instead, he prefers to
use his phone to continue reading. Publications must be able to adapt to the consumption environment, so as
to provide a good reading experience regardless of the device.
</li>
<li id="uc_horizdep_security" class="uc-security">
<span class="uc-categories">(On Security)</span> LocalLibrary receives publications from a variety of
sources that they then make available to their members. It is imperative that none of these publications can
cause any damage to their own systems or those of their members.
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#accessibility">Accessibility</a></li>
<li><a data-cite="!wpub/#language-and-dir">Language and Base Direction</a></li>
<li><a data-cite="!wpub/#manifest-specific-language-and-dir">Item-specific Language</a></li>
<li><a data-cite="!wpub/#reading-progression-direction">Reading Progression Direction</a></li>
<li><a data-cite="!wpub/#accessibility-report">Accessibility Report</a></li>
<li><a data-cite="!wpub/#privacy-policy">Privacy Policy</a></li>
</ul>
</section>
<section id="escalating-trust">
<h3>Escalating Trust</h3>
<p id="r_escalating-trust" class="req-set">
User agents may provide a method for escalating trust for a specific publication.
</p>
<p>
Some publications may require additional capabilities (for example, access to camera or geolocation) that a
user agent might normally not enable. Today, some platform and UA vendors offer methods for otherwise
untrusted local scripts to become trusted and regain API privileges, a similar ability needs to exist for
publications as well.
</p>
<ul class="use-cases">
<li id="uc_escalating-trust_geolocation" class="uc-privacy">
Rebecca has assigned an exercise from a WP textbook. The exercise requires the use of geolocation to measure
distances from the user’s location to a target. The UA detects that the WP came from a trusted source (the
textbook publisher), and therefore allows the WP to use the full capabilities of the UA.
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#privacy-policy">Privacy Policy</a></li>
</ul>
</section>
</section>
<section id="document-composition">
<h2>Document Composition</h2>
<section id="identification">
<h3>Identification</h3>
<p id="r_uid" class="req-set cc-minimal">
A Web Publication, as a collection of resources, must be identified by either a
single URL or a unique <a href="http://www.handle.net/">handle</a> that can resolve to a single URL.
</p>
<p>
The unique identification of a specific Web Publication is essential. If not expressed as a URL, there should
be a way to map this unique identification onto a Web Address. The Web Publication must be
identifiable as a single logical resource
with its own URL beyond the references to its constituent
resources.
</p>
<ul class="use-cases">
<li id="uc_uid_scholarly-references">
Scholarly references demand a unique identification of the publication and, possibly, its internal structure.
That unique identification must be available as a Web link, to make it possible for other publications and
other sites (e.g., the authors’ institutional sites) to unambiguously link to the publication. These
features are essential in the scholarly community to make, for example, the assessment of individual
researchers possible.
</li>
<li id="uc_uid_textbook-editions">
Textbook editions should be clearly distinct from one another using unique identifiers. Links should be
accurate in order to avoid confusion in classes, especially since each class is not necessarily using the
latest edition.
</li>
<li id="uc_uid_single-search">
Marwin wants to search for a term on the publication. As a reader, he does not know the internal structure
of the book, i.e., whether the content is one or several HTML files; he wants to search to be executed on
the whole (logical) content, regardless of its internal representation.
</li>
<li id="uc_uid_single-p13n">
Svetlana sets her preferences in terms of font selection and size, background color, etc, for her WP textbook.
She wants those to be in effect on all chapters of the book automatically.
</li>
<li id="uc_uid_single-enumeration">
User agents that support value counters (page counters, section numbering, footnotes, endnotes), should do
so across the entire Web Publication (as opposed to individual components being numbered separately)
</li>
<li id="uc_uid_single-assistive-technology" class="uc-accessibility">
Assistive Technology such as screen readers or voice dictation control needs to have the Web Publication
presented to it as if it was a single unit.
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#wp-bounds">Web Publication Bounds</a></li>
<li><a data-cite="!wpub/#wp-resources">Resources</a></li>
<li><a data-cite="!wpub/#primary-entry-page">Primary Entry Page</a></li>
<li><a data-cite="!wpub/#address">Address</a></li>
<li><a data-cite="!wpub/#canonical-identifier">Canonical Identifier</a></li>
<li><a data-cite="!wpub/#extensibility-linked-records">Linked Records</a></li>
<li><a data-cite="!wpub/#wp-obtaining-manifest">Obtaining a Manifest</a></li>
<li><a data-cite="!wpub/#publication-types">Publication Types</a></li>
</ul>
<p id="r_identify-const-resources" class="req-set">
All constituent resources, and their contents, should be identified by either a URL or a unique handle that can resolve to a URL.
</p>
<p>
The requirement that a Web Publication be uniquely identifiable can be easily extended to the constituents
of a Web Publication, as well as the fragments, parts, sections, etc, of those resources. Those
idenfications should be stable and resilient to changes and new iterations of the publication.
</p>
<ul class="use-cases">
<li id="uc_identify-const-resources_theorem">
Markus refers to a specific mathematical theorem in a publication. That reference must be unique, stable and
retrievable on the Web, and it should not depend on whether the publisher issues a new iteration of the
target publication (thereby possibly change the section numbering).
</li>
<li id="uc_identify-const-resources_sections">
Tanya and Kelly are collaborating on curriculum for the upcoming school year. They are able to reference the
same Web Publication in their shared documents and rely on stable, retrievable links to sections within the
WP.
</li>
<li id="uc_identify-const-resources_annotation">
Judit uses an annotation tool to comment on a publication authored by Pablo. She puts an annotation against
a sentence in a particular paragraph, anchoring that annotation to the sentence using a reliable way of
identifying it. That identification should not be invalidated by a subsequent change of the document by
Pablo (unless he, e.g., removes that sentence).
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#manifest-embed">Embedding a Manifest</a></li>
<li><a data-cite="!wpub/#manifest-link">Linking to a Manifest</a></li>
<li><a data-cite="!wpub/#pagelist">Page List</a></li>
<li><a data-cite="!wpub/#address">Address</a></li>
<li><a data-cite="!wpub/#resource-categorization-properties">Resource Categorization Properties</a></li>
<li><a data-cite="!wpub/#resource-list">Resource List</a></li>
<li><a data-cite="!wpub/#cover">Cover</a></li>
<li><a data-cite="!wpub/#table-of-contents">Table of Contents</a></li>
</ul>
</section>
<section id="manifest-metadata">
<h3>Metadata</h3>
<p id="r_manifest-metadata" class="req-set cc-minimal">
Web Publications should include technical metadata and descriptive metadata, including accessibility metadata,
as well as any additional characteristics of the <a href="#constituent-resources">constituent resources.</a>
</p>
<p>
A user agent may require information about the publication and its components in order to process it. For
example, performance and memory requirements may prevent a user agent from parsing a large number of content
documents in order to discover the necessary components and their relationships. A user agent may need to
make some decisions about how to present content before displaying it.
</p>
<p>
A Web Publication should be able to include additional information that the user agent can use, such as:
</p>
<ul>
<li>
the rights of various components identified in the package;
</li>
<li>
captions belonging to multimedia resources within the publication;
</li>
<li>
whether there is a need for additional processing, such as with MathML;
</li>
<li>
the title, author(s), cover image, etc., to display the publication on a shelf without downloading all its
content;
</li>
</ul>
<ul class="use-cases">
<li id="uc_manifest-metadata_ownership_rights">
Marla is writing an art book and wishes to include the rights relevant to the image of the Mona Lisa owned
by the Louvre, so that a user agent will know whether it is permissible to download the image for offline
use.
</li>
<li id="uc_manifest-metadata_chapter_name_displayed">
While listening to a chapter in an audiobook via a user agent with a display, Clarence would like to see the
current chapter name displayed.
</li>
<li id="uc_manifest-metadata_chapter_name_spoken">
While listening to a chapter in an audiobook via a user agent with no display, Zara wants to see what
chapter she is in by saying, “Hey [Digital Assistant], what’s this chapter called?” and then hear the name
of the chapter before resuming reading.
</li>
<li id="uc_manifest-metadata_detailed_descriptions" class="uc-accessibility">
Ferdous wants to buy a book about a museum exhibit, but before he does that, he wants to guarantee that the
images and videos about the exhibits have detailed descriptions to ensure that he will be able to read it
with a screen reader or refreshable Braille display. This can be done because the publisher provided that
information as part of the metadata assigned to the Web Publication.
</li>
<li id="uc_manifest-metadata_wcag" class="uc-accessibility">
A university professor is developing a course and the professor knows that he is required by the
university's policy to use digital materials that conform to WCAG 2.0 level AA. The professor searches to
determine which titles are accessible and therefore suitable for his use. This can be done because the
publishers have added <a href="https://www.w3.org/wiki/WebSchemas/Accessibility">Schema.org Accessibility Metadata</a>
to the Web Publication, describing the accessibility characteristics for each constituent resource.
</li>
<li id="uc_manifest-metadata_digital_assistant">
When Bella is listening to an audiobook or browsing her digital bookshelf, she wants to ask questions like, “Hey
[Digital Assistant], who’s the narrator?” or “How long is that book?” and hear the corresponding metadata
read to her by text-to-speech before resuming listening to content or browsing.
</li>
<li id="uc_manifest-metadata_ainu">
Marco is an Ainu audiobook listener, and the book he is reading has a table of contents consisting of images
because the Ainu language has no script. While listening, he asks for the chapter name, and the reading
system plays the audio for the title of the current table of contents item, and then resumes playback from
the last position in the content.
</li>
<li id="uc_manifest-metadata_library_promotion">
A library wants to promote a particular type of publication depending on different categories available in a
publication’s metadata (age suitability, genre, author, etc.)
</li>
<li id="uc_manifest-metadata_anthology">
An online literary magazine wishes to compile an anthology of short stories authored by a specific writer.
The magazine should be able to identify the stories within the manifests by author and bring those chapters
together into a new Web Publication.
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#manifest-link">Linking to a Manifest</a></li>
<li><a data-cite="!wpub/#accessibility">Accessibility</a></li>
<li><a data-cite="!wpub/#creators">Creators </a></li>
<li><a data-cite="!wpub/#language-and-dir">Language and Base Direction</a></li>
<li><a data-cite="!wpub/#manifest-specific-language-and-dir">Item-specific Language</a></li>
<li><a data-cite="!wpub/#wp-title">Title</a></li>
<li><a data-cite="!wpub/#links">Links</a></li>
<li><a data-cite="!wpub/#accessibility-report">Accessibility Report</a></li>
<li><a data-cite="!wpub/#privacy-policy">Privacy Policy</a></li>
<li><a data-cite="!wpub/#cover">Cover</a></li>
<li><a data-cite="!wpub/#table-of-contents">Table of Contents</a></li>
<li><a data-cite="!wpub/#extensibility-linked-records">Linked records</a></li>
<!--<li><a data-cite="!wpub/#feature-publication-mode">Switch to Publication Mode</a></li>-->
<li><a data-cite="!wpub/#wp-obtaining-manifest">Obtaining a manifest</a></li>
</ul>
</section>
<section id="constituent-resources">
<h3>Resources</h3>
<p id="r_const-res" class="req-set">
The information regarding the constituent resources of a Web Publication must be easily discovered and there
should be a way to differentiate between essential and non-essential resources.
</p>
<p>
A Web Publication will likely be composed of multiple Web documents and their resources. A more complicated
Web Publication may have many resources, some of which are essential and some of which are not. Because of
this complexity, extracting in advance all the references to some or all constituent resources may be
prohibitive. It is therefore necessary for the user agent to have an easy access to the list of constituent
resources and some of their characteristics, such as media type, size, and whether they are essential.
</p>
<p>
In a publication, some content is essential to the user being able to consume it while other content could
be either absent or have a provided fallback for situations such as limited connectivity or storage. This
information, provided by the author or publisher of the Web Publication, would enable a user agent to provide
a better experience to the user. For example, the user agent can ensure that essential resources are made
available when offline (see <a href="#offline"></a>).
</p>
<ul class="use-cases">
<li id="uc_const-res_fallback">
Nick is reading a long-form narrative on a device with limited storage: a publication filled with text,
images, audio, and multimedia files. Nick also rides the subway where he loses Internet connectivity
frequently and without warning for long stretches of time. During offline or low-storage situations, there
are still critical parts of the publication that are consumable, mainly the text (and possibly images).
Having a reasonable fallback for video, such as a poster image or placeholder image, would allow Nick to
read the content while offline or on a device with limited storage.
</li>
<li id="uc_const-res_video_descriptions" class="uc-accessibility">
Henry creates a Web Publication and includes the accessibility metadata indicating that the publication has
descriptions for videos. He marks the accessible descriptions as essential and marks videos as non-essential
while providing images as fall-back. This enables the print-disabled readers to access the accessible
descriptions and video when there is good internet connectivity, and fall-back images along with accessible
descriptions when internet connectivity is not optimum.
</li>
<li id="uc_const-res_essential_font">
Gösta is reading a treatise on the theory of functions. A mathematical font is essential for the proper
display of the mathematical formula in this publication, so the author has marked the font as essential so
it is made available offline.
</li>
<li id="uc_const-res_datasets">
While reading an article on a new spam analysis algorithm, Lars is primarily interested in the findings of
the research. Since the research was funded by a government agency, the dataset, consisting of millions of
anonymized log files, is also available. Because of its size, the researchers have marked the dataset as
non-essential for conveying the results of the paper and therefore indicates it can be skipped when reading
the publication offline.
</li>
<li id="uc_const-res_stock_values">
Sarah is reading a publication about the stock exchange. The current value of the stock is fetched (from a
remote resource) when she opens the publication. However, when she is on the train (without a connection)
one week later and opens the stock exchange publication, she will continue to see the value of the stock as
it was the last time she opened the publication. It should be possible for either the content itself or the
user agent to provide some user experience that notifies her that the currently presented data is a week old.
</li>
<li id="uc_const-res_database_access">
Risha publishes an article which includes an interactive component that accesses a database, exposed to the
Web via a RESTful API. The interactive component is implemented as a JavaScript library. Such data cannot be
included in a packaged publication and the interactive module is of no use without such data. Risha
therefore marks the Web Publication component relative to the interactive module as not essential when
offline.
</li>
<li id="uc_const-res_non-essential">
Chiara is listening to an audiobook on Roman history. The description when she bought it mentioned that the
maps and images referred to the book were available as supplemental content in the file. At the end of the
audiobook, she is able to view the content, which helps her understand the audiobook better, but it is
marked as non-essential if the audiobook is taken offline.
</li>
<li id="uc_const-res_lms_submission">
Stephanie, a student, is answering questions in an assessment embedded in a Web Publication. Her internet
connection is unreliable at home. She should be able to save
those responses in the Web Publication. The assessment allows her to submit responses to a database. A notification within the Web Publication should inform her whether the data has been successfully submitted.
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#manifest-embed">Embedding a Manifest</a></li>
<li><a data-cite="!wpub/#manifest-link">Linking to a Manifest</a></li>
<li><a data-cite="!wpub/#address">Address</a></li>
<li><a data-cite="!wpub/#resource-categorization-properties">Resource Categorization Properties</a></li>
<li><a data-cite="!wpub/#links">Links</a></li>
<li><a data-cite="!wpub/#cover">Cover</a></li>
<li><a data-cite="!wpub/#table-of-contents">Table of Contents</a></li>
</ul>
</section>
<section id="reading-order">
<h3>Default Reading Order</h3>
<p id="r_reading-order" class="req-set cc-minimal">
There should be a means to indicate the author’s preferred navigation structure among the resources of a Web
Publication, and User Agents should provide an accessible way of navigating the same.
</p>
<!-- <p>
A user agent needs to know the sequence in which to present components of a Web Publication to the user,
including the starting point, and should also provide an accessible way of navigating the same.
</p> -->
<ul class="use-cases">
<li id="uc_reading-order_sequential">
Moby Dick contains 136 chapters. Each chapter is a separate HTML document, with a logical order for reading
them. It should be possible for the publication to inform the user agent that the proper order for
consumption of the HTML documents is sequentially, starting by the first chapter.
</li>
<li id="uc_reading-order_alphabetical">
The Encyclopedia of Stuff includes 1348 articles, each one in a unique HTML document. The publication must
be able to indicate to the user agent that the standard way to consume the articles is alphabetical order,
by title.
</li>
<li id="uc_reading-order_subheadings">
The third edition of the Writing Handbook has 10 chapters with 5-10 subsections apiece and 4-8 readings.
Each subsection and reading starts its own HTML page. The Web Publication should be able to inform the user
agent that the proper order for consumption of the HTML documents is sequentially, starting with the first
chapter. Moreover, in the navigation structure, the user agent should be able to indicate to the user which
subheadings and readings belong to which chapter, and that those subheadings and readings are navigated
sequentially, starting with the first subheading in the parent chapter.
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#pagelist">Page List</a></li>
<li><a data-cite="!wpub/#default-reading-order">Default Reading Order</a></li>
<li><a data-cite="!wpub/#table-of-contents">Table of Contents</a></li>
</ul>
</section>
<section id='tableofcontents'>
<h3>Navigation</h3>
<p id="r_toc" class="req-set cc-minimal">
A user agent should be able to reveal the navigable structure of a Web Publication as a table of contents that
is accessible to users, including those with disabilities.
</p>
<p>
The table of contents must include a link to at least one resource, and all links should refer to resources
within the publication bounds. The user agent presents an accessible table of contents, which allows the user to
access the links without navigating away from the current resource.
</p>
<ul class="use-cases">
<li id="uc_toc_answers">
Chandrasekhar has been assigned a set of exercises in his math Web Publication textbook. To double check his work, he
wants to easily navigate to the answers in the back of the Web Publication. Using the table of contents exposable by his
user agent, he is able to navigate to the answers and return to the exercise with ease.
</li>
<li id="uc_toc_skipping_around">
Penelope has opened her Web Publication to its preface. She would like to skip the preface and go to chapter
one. She is able to reveal the table of contents built into her Web Publication via a function in her user
agent and view a link to chapter one. She changes her mind and decides to read the preface. Since she is
still on the preface and has not navigated away, she only needs to close out of the table of contents to
continue reading the preface.
</li>
<li id="uc_toc_anthology">
Matilda is reading an anthology but would like to read her favorite author's short stories first. She is
able to reveal the navigation built into her Web Publication via a function in her user agent and access the
relevant stories.
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#table-of-contents">Table of Contents</a></li>
</ul>
<p id="r_player-nav" class="req-set">
For content that requires a player interface for time-based media,
the Web Publication should provide the User Agent a way to navigate
to a specific position in the content.
</p>
<ul class="use-cases">
<li id="uc_player-nav_skip_to_story">
Belinda would like to skip directly to a specific short story in a collected edition. The Web Publication provides the user agent
with metadata to access the short story.
</li>
<li id="uc_player-nav_skip_to_minute">
Mr. Sterling asks his students to skip directly to the 23rd minute of an audiobook.
</li>
<li id="uc_player-nav_skip_to_chapter">
Ken was assigned part of a non-fiction book for a class. He wants to open the audiobook but only needs to
listen to chapter 19. The Web Publication provides the
user agent with metadata to access the chapter.
</li>
</ul>
<ul class="wpub-xref">
<li><a href="https://www.w3.org/TR/audiobooks/">Audiobook</a></li>
<li><a data-cite="!wpub/#table-of-contents">Table of Contents</a></li>
<!--<li><a data-cite="!wpub/#affordances">Table of Contents > Affordances</a></li>-->
</ul>
</section>
<section id="random-access">
<h3>Random Access to Content</h3>
<p id="r_random-access" class="req-set">
Authors of a Web Publication should be able to provide the user agent with information to access random
parts of the publication.
</p>
<p>
It should be possible for the author to convey several potential <a href="#reading-order">reading orders</a>
that may go beyond the “default” for the content of the publication. This alternative reading order may only
include specific parts of the publication rather than the full content of the publication.
</p>
<p>
A user agent should be able to access the resources of the publication in whatever order it chooses—beyond
the order provided by the publication itself.
</p>
<ul class="use-cases">
<li id="uc_random-access_list_of_abstracts">
EsteemedJournalPublisher would like to offer the users of the EsteemedJournal of Chemistry App the
opportunity to read only the abstracts of the journals in the app. The publication would therefore provide
the user a list (table of contents) of abstracts (disjointed objects in the package with semantic
information or metadata informing the package of the nature of the object).
</li>
<li id="uc_random-access_teasers">
A publisher wants to provide “teasers” for a book by providing a series of extracts that are meant to give
an overview of the book without the need to read the whole publication. This can be typically used by
a reseller allowing for a prospective client to access part of the publication free of charge.
</li>
<li id="uc_random-access_dro_beginner_vs_advanced">
EducationalPublisher publishes a complex textbook. The textbook is created is such a way that it could be
used both for beginner and advanced levels. The default reading order corresponds to beginners, but the
goal is that advanced students can follow a different path through the material, corresponding to their
level of knowledge. EducationalPublisher therefore adds alternative reading orders to the publication that
advanced users can follow.
</li>
<li id="uc_random-access_dro_a-z_vs_categorized">
Acme Publishing has published a book on wines that can be read from A-Z, or personalized to only read about
red wines or wines from a specific region.
</li>
<li id="uc_random-access_alt-text" class="uc-accessibility">
A specialized user agent wishes to find all images in a publication that do not already have alternative
text and automatically provide it using an image identification service such as
<a href="http://labelme.csail.mit.edu/">LabelMe</a>.
</li>
<li id="uc_random-access_alternate_glossary">
EducationalPublisher publishes a history textbook in English. The textbook contains two glossaries, one in
English and one in Spanish for Spanish-speaking students learning English as their target language to
facilitate their ability to understand key terms in the text. A specialized user agent should be able to
reveal and suppress the Spanish glossary based on what the student requires.
</li>
<li id="uc_random-access_study_guides">
A foreign language textbook Web Publication allows for a specialized user agent to filter and display content identified as vocabulary and conjugation charts. This is done in order to
facilitate the teacher creating study guides.
</li>
<li id="uc_random-access_labels">
CookbookPublisher wants to create a cookbook that either a function within the publication itself or a
feature in a user agent can filter to only show recipes with certain labels.
</li>
<li id="uc_random-access_dro_alternatives">
The publisher of an experimental novel would like to publish the book as a Web
Publication. The author wishes the reader to have the option to read chapters in a variety of different sequences, all of which are offered as
alternative reading orders in the Web Publication.
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#default-reading-order">Default Reading Order</a></li>
<li><a data-cite="!wpub/#table-of-contents">Table of Contents</a></li>
</ul>
<p id="r_print-page" class="req-set">
If there is a physical book version of the Web Publication, the user must have the ability to quickly browse
to a corresponding pointer as identified in the physical book.
</p>
<ul class="use-cases">
<li id="uc_print-page_skip_to_page" class="uc-accessibility">
Beatrix is visually impaired and uses accessible Web Publications in her class, while her sighted classmates
use physical books. When the teacher asks the class to open page 71 and read the second paragraph, Beatrix
should be able to navigate to exactly the same position in her version as her sighted classmates.
</li>
<li id="uc_print-page_bookmark">
Zoya borrowed a book from her library but must return it. She has decided to buy a WP version of the same
text and would like to continue reading where she left off.
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#table-of-contents">Table of Contents</a></li>
<li><a data-cite="!wpub/#page-list">Page List</a></li>
</ul>
</section>
<section id="alternative-modalities">
<h3>Alternative Modalities</h3>
<p id="r_alt-mods" class="req-set">
A Web Publication should encompass publications such as audiobooks, graphic books, mixed media, and
interactive media.
</p>
<p>
All concepts and structures related to a Web Publication should enable the creation and/or production of
alternative renderings for visual and auditory content.
</p>
<ul class ="use-cases">
<li id="uc_alt-mods_hands-free" class="uc-accessibility">
Sree wants to access audiobooks while commuting, jogging, doing dishes, or otherwise not able to use his
eyes or hands.
</li>
<li id="uc_alt-mods_audio_version">
Daniel wants to complete his assigned class readings during his commute to work. His textbook Web Publication allows him
to access an audio version of the each of the readings.
</li>
<li id="uc_alt-mods_wider_audience">
Khoudia, a librarian focusing on the children's section of her local library, is looking exclusively for
material rich in audio and video components so as to reach a wider age bracket.
</li>
<li id="uc_alt-mods_braille_music" class="uc-accessibility">
James, a musician, requires that the musical score within a publication come preformatted in braille music
notation in order to read it, as he uses freely available assistive technology which does not have braille
music translations built in.
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#publication-types">Publication Types</a></li>
<li><a data-cite="!wpub/#wp-bounds">Web Publication Bounds</a></li>
<li><a data-cite="!wpub/#links">Links</a></li>
</ul>
</section>
<section id="synch-time-based-media">
<h3>Synchronized Time-based Media</h3>
<p id="r_time" class="req-set">
A Web Publication needs to support synchronization between text and time-based media.
</p>
<p>
A Web Publication needs to support time-based media, such as synchronized video, audio, captions or
transcript, or sign language interpretation. A Web Publication must also be able to enable a synchronized
media experience while navigating through the publication, with sufficient level of granularity.
</p>
<ul class="use-cases">
<li id="r_time_assistive_audio_and_text" class="uc-accessibility">
Illyés has a cognitive disability and uses accommodated texts in the classroom to help learn the content
while improving his reading. His assistive technology uses combined audio and highlighted text, which it
obtains from the UA through the information provided in the Web Publication, to turn the page for him
while reading along in sync with the page currently open.
</li>
<li id="r_time_read-aloud">
Marco is learning German as a second language. In order to improve his understanding and pronunciation
while reading a German text, he uses a read-aloud function available through his user agent and made
accessible by the information provided in the Web Publication.
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#links">Links</a></li>
<li><a data-cite="!wpub/#resource-list">Resource List</a></li>
</ul>
</section>
<section id="data">
<h3>Data</h3>
<p id="r_extdata" class="req-set cc-minimal">
Web Publications should be able to include data as <a href="#constituent-resources">resources</a>, just as
it does with text, images, etc.
</p>
<ul class="use-cases">
<li id="uc_extdata_csv">
Rosa has submitted an article to EsteemedJournal and provided her research data in CSV format. She and
EsteemedJournal provide users access to the CSVs when accessing her article in any situation by including
the CSV data, as well as the Javascript library to display the content in human friendly form, as part of
the Web Publication.
</li>
<li id="uc_extdata_graphs">
A news organization wishes to run a series of articles containing graphs based on a set of raw data. Those
graphs are generated dynamically in each article depending on what the topic is. The data is also available
to the user for transparency.
</li>
<li id="uc_extdata_dynamic">
An exercise in an educational Web Publication requires the student to push data to a CSV and analyze the
subsequent graphs that are dynamically created with each datapoint that the student enters.
</li>
<!-- <li>
Risha publishes an article which includes an interactive component that accesses a database, exposed to
the web via a RESTful API. The interactive component is implemented as a JavaScript library. Such data
cannot be included in a packaged publication and the interactive module is of no use without such data.
Risha therefore marks the web publication component relative to the interactive module as not relevant
when offline.
</li>
<li>
InteractiveCompany publishes a Web Publication containing an interactive component implemented as a
JavaScript library, but this library requires several other JavaScript libraries. Therefore
InteractiveCompany makes it sure that all JavaScript libraries required to get the interactive component
running offline.
</li> -->
</ul>
<ul class="wpub-xref">
<!--<li><a data-cite="!wpub/#example-65">Single-Document Publication > Example 65</a></li>-->
<li><a data-cite="!wpub/#resource-list">Resource List</a></li>
</ul>
</section>
<section id="protection">
<h3>Protection</h3>
<p id="r_protection" class="req-set">
A Web Publication should allow for application of access control and write protections of the publication.
</p>
<ul class="use-cases">
<li id="uc_protection_ill">
A library may loan the publication for two weeks or a university may make a textbook available for its
students for the course of the year. A Web Publication should provide a means to inform user agents about
the availability period to enable the UA to control access accordingly.
</li>
<li id="uc_protection_assistive_technology" class="uc-accessibility">
Alice is working on potentially Nobel prize winning research and has drafted her paper describing her
discoveries. She asks her print disabled friend Bob to review the paper, but needs to make sure that the Web
Publication retains specific protections on what Bob is able to do with the publication
without restricting Bob's assistive technology from accessing the content.
</li>
</ul>
<ul class="wpub-xref">
<li><a data-cite="!wpub/#privacy-policy">Privacy Policy</a></li>
<!--<li><a data-cite="!wpub/#feature-publication-mode">Switch to Publication Mode</a></li>-->
</ul>
</section>
<section id="document-packaging-doc">
<h3>Packaging</h3>
<p id="r_pwp" class="req-set">
It should be possible to create and distribute a Web Publication as a single unit over different protocols or
physical media.
</p>
<p>
This can be done through the usage of <a data-lt="Packaged Web Publication">Packaged Web Publications</a>.
</p>
<ul class="use-cases">
<li id="uc_pwp_secure_email">
HA, Ltd, a publisher of legal briefs, needs to distribute content in a consumable format to its clients via
secure email.
</li>
<li id="uc_pwp_device_transfer" class="uc-device-independence">
Dalia, a patent lawyer, wants to consume content on a multitude of devices, some of which may not always have
connectivity. In order to meet her expectations, it is necessary to have all required content grouped in a
logical structure that can be easily transferred between devices.
</li>
<li id="uc_pwp_single_unit">
Andreas is working on his first collaborative research paper with a fellow student. He wants to share a
relevant publication that includes content, diagrams, and datasets with his writing partner. He does not have
time to learn how to share each component so that his partner can access it all without much effort; he
expects to be able to share this material as a single unit via the chatting system that they use to
collaborate.
</li>
<li id="uc_pwp_offline_lending">
Dave is reading Moby Dick on his tablet (at home with network connectivity). He then jumps on a plane with his
good friend Tzviya. After having finished reading the book, he wants to lend it to Tzviya, so that she can
start reading on her own tablet. They are both offline, but can exchange data with SD cards or Bluetooth.
</li>
<li id="uc_pwp_simple_distribution">
Giselle is an independent author who has produced the audio version of her latest novel. She wants to
distribute it directly to a few beta readers before launch without worrying about sending a list of files
with no structure.
</li>