"Preservation as a Service for Trust (PaaST)" – Draft ver. 0.8 (1 April 2016).
Existing Citations
capability : A capability is an action or a set of actions that can be or is performed in support of digital preservation. Capabilities respond to PaaST requirements and may be combined into composite services. Capabilities fall into four groups:
·&mnsp;Management capabilities establish and implement controls that govern preservation and related activities within a Preservation Environment, as well as enabling identification of problems related to objects, actions, or information in the Preservation Environment;
·&mnsp;Information processing capabilities generate, collect, maintain, manage and make available information about objects, actions, controls, and parties.
·&mnsp;Object processing capabilities operate on Preservation Objects, Preservation Object Sets, Submission Sets, and Data Objects;
·&mnsp;Preservation Processing capabilities execute the sequences of actions that accomplish digital preservation, including bringing Preservation Targets into and under the control of a Preservation Environment, ensuring Preservation Targets are stored in a way that guarantees their integrity and accessibility, implementing changes in Preservation Targets or in the technology needed to operate on and provide access to them, and providing copies of Preservation Targets and access to information about them to authorized parties.
¶ Capabilities may be grouped or orchestrated in different ways to suit the needs of different situations.
(†1881)
party : A Party is a person or organization that is directly or indirectly involved in the activities entailed by the PaaST requirements. A Party is defined by the activity performed and not by who performs the activity. Thus the same person or organization can fulfill the role of more than one Party. (†1875)
permanent feature : Permanent Feature Designation: Determines the essential requirements for preservation of a class, set, individual Preservation Target, or Preservation Data Object by identifying the features that must remain unchanged. Permanent Feature Designation qualifies a feature specified in Characterization.
(†1889)
Preservation as a Service for Trust (PaaST) : The Preservation as a Service for Trust (PaaST) project is an initiative in the InterPARES Trust that directly addresses the challenges of digital preservation in the Cloud. It sets out functional and data requirements that can be embodied in contracts for preservation with Cloud service providers; however, the potential benefits of using these requirements are not limited to the Cloud. They have been articulated to be applicable across as broad a variety of situations as possible, including
· heterogeneity in the types of information objects being preserved;
· variety in applicable directives, such as laws, regulations, standards, policies, business rules, and contractual agreements,
· including varying conditions of ownership, access, use, and exploitation;
· variation in institutional arrangements and relationships between the parties involved;
· across as wide a spectrum as possible from best practices to worst cases.
(†1861)
Preservation as a Service for Trust (PaaST) : The main differences between PaaST and OAIS are (1) the scope of PaaST is limited to digital information; (2) OAIS is predicated on the assumption that preservation will be carried out in a coherent system whereas PaaSt includes the possibility that different requirements for preservation are satisfied by different parties using different technologies; and (3) OAIS intentionally does not provide or constitute a guide to implementation, but PaaST is formulated to facilitate implementation in software. (†1862)
preservation director : Preservation Director: a Party that has either independent or contractual authority to direct the preservation of digital materials. (†1877)
preservation rule : Preservation Rules govern the execution of preservation activities. In effect, each PaaST requirement defines a rule, but these requirements indicate only what should be possible to do in a PaaST compliant Preservation Environment;, they do not specify what actually should be done. That should respond specifically to the objectives, policies and needs of the Preservation Director. An expression that specifies what should be done is a Preservation Rule. Preservation Rules make used of PaaST Capabilities. Preservation Rules also reflect the variety, scope and limitations of services offered by a Preservation Service Provider. (†1864)
preservation service provider : Preservation Service Provide: a Party that performs one or more preservation services. (†1878)
producer : Producer: a Party that created or is or was otherwise responsible for the existence of Preservation Targets. (†1876)
