forked from w3c/dpub-pwp-arch
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathArchival-UCR.html
185 lines (174 loc) · 9.65 KB
/
Archival-UCR.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
<!DOCTYPE html>
<html>
<head>
<title>Digital Publishing: Archival Use Cases and Requirements</title>
<meta charset='utf-8'>
<script src='https://www.w3.org/Tools/respec/respec-w3c-common'
async class='remove'></script>
<script class='remove'>
var respecConfig = {
specStatus: "base",
shortName: "dpub-pwp-arch-Archival-UCR",
editors: [
{ name: "Tim Cole",
url: "http://www.library.illinois.edu/people/bios/t-cole3/",
company: "University of Illinois at UC",
companyURL: "http://illinois.edu/",
mailto: "[email protected]" },
{ name: "Ayla Stein",
company: "University of Illinois at UC",
companyURL: "http://illinois.edu/",
mailto: "[email protected]" }
],
previousMaturity: "",
previousPublishDate: "",
wg: "Digital Publishing Interest Group",
wgURI: "http://www.w3.org/dpub/IG/",
wgPublicList: "public-digipub-ig",
wgPatentURI: "",
noRecTrack : "true",
otherLinks: [
{
key: "Repository",
data: [{
value: "Github Repository",
href: "https://github.com/w3c/dpub-pwp-arch"
}]
},
{
key: "Issues tracker",
data: [{
value: "Github Issue Tracker",
href: "https://github.com/w3c/dpub-pwp-arch/issues"
}]
}
],
edDraftURI: "http://w3c.github.io/dpub-pwp-arch/Archival-UCR.html",
};
</script>
</head>
<body>
<section id='abstract'>
<p>
It is anticipated that Portable Web Publications (PWP) for the Open Web Platform will need to be archived.
[<cite><a class="bibref" href="#bib-pwp-archival-services">pwp-archival-services</a></cite>] This document describes
archival use cases and requirements of potential interest to those developing the vision and requirements for PWPs.
</p>
</section>
<section id='sotd'>
<p>
This document was created by a Task Force of the <a href="http://www.w3.org/dpub/IG/">Digital Publishing Interest Group</a>.
If you wish to make comments regarding this document, please send them to
<a href="mailto:[email protected]">[email protected]</a>
(<a href="mailto:[email protected]?subject=subscribe">subscribe</a>,
<a href="http://lists.w3.org/Archives/Public/public-digipub-ig/">archives</a>).
All comments are welcome. Prefix your subject line with "[dpub-arch]".
</p>
</section>
<section>
<h2>Introduction</h2>
<p>There are multiple definitions of "digital preservation," but among the more useful starting point definitions are the
[<cite><a class="bibref" href="#bib-definitions-of-digital-preservation">definitions-of-digital-preservation</a></cite>]
posted several years ago by the American Library Association's Association for Library Collections and Technical
Services. These include: "Digital preservation combines policies, strategies and actions to ensure access to reformatted and
born digital content regardless of the challenges of media failure and technological change. The goal of digital preservation
is the accurate rendering of authenticated content over time." Various workflows and approaches (i.e., use cases) have
been developed over time to create services that strive to meet this definition of digital preservation.</p>
<p>Captured here are some of these use cases and parts of use cases that provide context and articulate the requirements and expectations
typical of archival services that are likely to archive PWPs. To add a use case, please copy and populate the template
and insert as next new section below. The use cases are for now unordered. The template provided is adapted from the IG's Use Case Template.
[<cite><a class="bibref" href="#bib-dpub-use-case-template">dpub-use-case-template</a></cite>]
</p>
</section>
<section>
<h2>Use Cases</h2>
<section id="template">
<h2>
Use Case Template: [put here the title of the use case]
</h2>
<dl>
<dt>Description</dt>
<dd>Plain english scenario which specifies relevant actors and intended/desired flow of events.</dd>
<dt>Requirement(s)</dt>
<dd>List of requirements drawn from the above Description.</dd>
<dt>Stakeholder(s)</dt>
<dd>Always use a consistent and preferably predefined value: ARCHIVING-SERVICES, LIBRARIES, PUBLISHERS-ALL, PUBLISHERS-STEM, USERS-ALL, USERS-A11Y, RETAILERS, IMPLEMENTERS.
New values can be added to this space as they are needed. </dd>
<dt>Relations/dependencies</dt>
<dd>Optional, links to other use cases. </dd>
<dt>Relevant W3C group(s)/specification(s)</dt>
<dd>Where the target WG/spec is obvious, specify it.</dd>
<dt>External relevant group(s)/specification(s)</dt>
<dd>Where there are external groups/specifications that address on this problem in whole or part.</dd>
<dt>Comments</dt>
<dd>Any additional info (clarifications, etc.).</dd>
<dt>Created By</dt>
<dd>name of first (original) author of the use case.</dd>
<dt>Status</dt>
<dd>Always uses one of the values NEW | REJECTED | ACCEPTED. </dd>
</dl>
</section>
<section id="LOCKSS">
<h2> Preservation by caching, format migration on access -- a use case based on LOCKSS </h2>
<dl>
<dt>Description</dt>
<dd>Digital preservation is challenging because digital content must be rendered by software
agents that evolve and change over time. In the case of the Open Web platform, Web
browsers, HTML standards, CSS specs and rendering agents evolve. Accordingly document formats
evolve as well to ensure that the presentation of content is as intended. For this reason
content that has been captured in the past needs to be reformatted, i.e. have its formatting
refreshed to continue to be viable in new Web browsers. This process is called format
migration. LOCKSS uses a caching approach to update files preserved and
postpones archive-based format migration until a user actually requests the preserved content.
LOCKSS crawls publisher Websites to retrieve the content it preserves and then disseminates
this content by acting as a proxy cache for subsequent requests from Web Browsers, updating cached files
as necessary for as long as a publisher copy remains available.
LOCKSS recognizes the need for format migration based on mismatches between the Accept: header
provided by a Web Browser when requesting content and the MIME type of the preserved content.
A digitized registry of converters is then used to find and invoke an appropriate converter.
If no converter is found a 406 (Not Acceptable) response is generated. </dd>
<dt>Requirement(s)</dt>
<dd>Ability for Archiving Service to cache PWP documents; Reliance on HTTP Accept: Headers</dd>
<dt>Stakeholder(s)</dt>
<dd>ARCHIVING-SERVICES, LIBRARIES,
PUBLISHERS-ALL, USERS-ALL. </dd>
<dt>Relations/dependencies</dt>
<dd>Optional, links to other use cases. </dd>
<dt>Relevant W3C group(s)/specification(s)</dt>
<dd>HTTP.</dd>
<dt>External relevant group(s)/specification(s)</dt>
<dd>Where there are external groups/specifications that address on this problem in whole or
part.</dd>
<dt>Comments</dt>
<dd>Are there implications here for PWP reliance on Service Workers acting as caches, e.g., as described in sections Sections 5.1 & 5.2 of PWD draft?</dd>
<dt>Created By</dt>
<dd>Tim Cole</dd>
<dt>Status</dt>
<dd>NEW (in Progress)</dd>
</dl>
</section>
</section>
<section id="references" class="appendix">
<h2>References</h2>
<section>
<h3>Informative references</h3>
<dl class="bibliography">
<dt id="bib-pwp-archival-services">[pwp-archival-services]</dt>
<dd>Markus Gylling; Ivan Herman; Tzviya Siegman. <a href="http://w3c.github.io/dpub-pwp/#libraries-and-archival-services"
><cite>Portable Web Publications for the Open Web Platform</cite></a>. 4 February 2016. W3C Editor's Draft.
URL:<a href='http://w3c.github.io/dpub-pwp/#libraries-and-archival-services'>
http://w3c.github.io/dpub-pwp/#libraries-and-archival-services</a>.</dd>
<dt id="bib-dpub-use-case-template">[dpub-use-case-tempalte]</dt>
<dd>Digital Publishing Interest Group. <a href="https://www.w3.org/dpub/IG/wiki/UseCase_Template"
><cite>Use Case Template</cite></a>. 8 June 2015.
URL: <a href="https://www.w3.org/dpub/IG/wiki/UseCase_Template">https://www.w3.org/dpub/IG/wiki/UseCase_Template</a>. </dd>
<dt id="bib-definitions-of-digital-preservation">[bib-definitions-of-digital-preservation]</dt>
<dd>Association for Library Collections and Technical Services, American Library Association.
<a href="http://www.ala.org/alcts/resources/preserv/defdigpres0408"><cite>Definitions of Digital Preservation</cite></a>.
24 June 2007. URL: <a href="http://www.ala.org/alcts/resources/preserv/defdigpres0408"
>http://www.ala.org/alcts/resources/preserv/defdigpres0408</a>.</dd>
</dl>
</section>
</section>
</body>
</html>