Thibodeau, Kenneth. "Preservation as a Service for Trust (PaaST)," ver. 0.11 (InterPARES Trust, September 2016).
Existing Citations
access (p. 11): Access encompasses access to functionalities that implement PaaST requirements as well as to materials
being preserved and information about them. (†2469)
access (p. 23): Access is built on the realization of the DigitalComponent instances that include a ContentObject, the HTML file that holds the text of Great Expectations, a SoftwareObject, a HTML viewer such as a web browser, and an InstantiationObject, such as a cascading style sheet. (†2470)
access (p. 37): Access that involves only output of information or production of Instantiations for external clients would not change the state of any PreservationTarget. (†2471)
access (p. 49): In the PaaST requirements, Access is a capability that provides access to PreservationTargets, PreservationManagementInformation as well as to Capabilities available in the Preservation Environment. (†2472)
access (p. 49): In the Access Service, "access" refers not just to the ability to search for and receive access to PreservationTargets and related information, but more broadly to access to participation in PreservationActions and other actions in the Preservation Environment. (†2473)
access (p. 49): As with other Capabilities, Access capabilities do not extend to the full range of services generally included under the rubric of access to or dissemination of information, but focus on those that are a direct consequence of preservation. (†2474)
access (p. 49): In the PaaST requirements, Access is a capability that provides access to PreservationTargets, PreservationManagementInformation as well as to Capabilities available in the Preservation Environment. (†2477)
access data (p. 37): Access that involves only output of information or production of Instantiations for external clients would not change the state of any PreservationTarget. Details of what was output as a result of Access actions should be captured as AccessData. (†2476)
access service (p. 49): The Access Service manages access by all Actors to information resources and Capabilities. Thus, in the Access Service, "access" refers not just to the ability to search for and receive access to PreservationTargets and related information, but more broadly to access to participation in PreservationActions and other actions in the Preservation Environment. The Access Service includes three sequential sets of functions and the management of PreservationManagementData about Access. The first set of functions covers receiving requests for access to information, PreservationAction Capabilities, Information Management Capabilities or Preservation Management Capabilities. The second set determines if the requested Access is authorized and feasible. Authorization includes both conditions on access imposed on particular information resources and access rights and restrictions of individual Actors. The third comprises responding to requests. (†2478)
actor (p. 9): Role type: An enumeration that lists the possible roles an Actor may have in execution of a Preservation Action or PreservationRule. (†2479)
actor (p. 12): An Actor is a role played by an entity that interacts with a Preservation Environment using any capabilities defined in the PaaST requirements. An Actor will often be a person but could be an external system. A person acting in one or more of the capacities defined in section 3.1, may perform actions that would qualify them as Actors, but many actions entailed by these capabilities are external to the Preservation Environment. Such actions include defining, implementing, managing, overseeing and evaluating preservation, rather than carrying it out. In contrast, Actor is a class in the PaaST data model and is specifically referenced in the requirements.
(†2480)
actor (p. 12): There are four predefined ways an Actor may participate in activities that implement PaaST requirements. · Performer: an entity actively involved in executing one or more preservation capabilities, · Authorizer: an entity whose approval is needed for an action to be executed in specified circumstances. · Problem Resolver: an entity responsible for resolving a problem that occurs in preservation activities, and · Approver: an entity who determines if the outcome of an action, including resolution of any problems, is acceptable. Other roles might be defined to satisfy particular circumstances, in accordance with the AttributableClass
(†2481)
actor (p. 14): An Actor is a person or an external system that participates in one or more actions; however, a PreservationAction does not necessarily involve any Actor. Some actions may be executed automatically. Actor is associated with PreservationAction by the association class, Participation, which 17 specifies how the Actor participates in the action.
(†2482)
archival bond : Traditionally, the archival bond has been treated as equivalent to the arraingement of records in a filing system. With physical records, placement of records in file folders and series is probably the most effective way of expressing and perpetuating the archival bond. But other relationships can arise when information is used in activities and, in the digital realm, such relationships can be persistent and accessible independently of any actions to file records. For example, communication threads persist in the header fields of email and other Internet messages. The preservation of retrospective relationships other than record keeping classifications is one way that Archival Object and Archival Aggregate classes can be used to preserve Information Objects that do not satisfy the archival definition of record. (†1991)
feature : PaaST adopts the concept of Feature from UML [Unified Modeling Language], where a Feature is either an attribute or a behavior of an object. (†1974)
local preservation environment : A Preservation Environment is the highest level set of Preservation Targets that are preserved under the same Preservation Rules, together with the technological infrastructures and tools used in their preservation. The Preservation Environment may include separate, different and independently managed hardware and software used by different Preservation Service Providers. The capabilities offered by a single provider are called the Local Preservation Environment. (†1972)
Preservation as a Service for Trust (PaaST) (p. 3): The Preservation as a Service for Trust (PaaST) project is an initiative of the InterPARES Trust project that directly addresses the challenges of digital preservation in the Cloud. It sets out functional and data requirements that can be included 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 or among the parties involved;
· a wide spectrum of circumstances as possible from best practices to worst cases. (†1966)
Preservation as a Service for Trust (PaaST) : The PaaST requirements have been specifically crafted to enable those responsible for preserving digital information to entrust that information to Cloud service providers. The requirements extend the perception that digital preservation entails the use of different technologies over time and assert that different, independent technologies can be used for digital preservation both simultaneously and sequentially and, most importantly, reliably. (†1970)
preservation environment : Rather than speak of a preservation system, PaaST uses the concept of a Preservation Environment. A Preservation Environment is the highest level set of Preservation Targets that are preserved under the same Preservation Rules, together with the technological infrastructures and tools used in their preservation. The Preservation Environment may include separate, different and independently managed hardware and software used by different Preservation Service Providers. The capabilities offered by a single provider are called the Local Preservation Environment. (†1971)
preservation target : The class, Preservation Target, has two child classes: Preservation Object and Preservation Aggregate. (†1979)
record : A record is an Intellectual Object that was made or received in the course of an activity as an instrument or a by-product of such activity, and set aside for action or reference. Thus, a record has a determinate relationship to the activity of which it is a record, to the actor who kept it as a record and to other records of the same activity. This relationship, called the ‘archival bond,’ not only relates a record to a specific context of creation and use but also defines the Archival Aggregate in which it belongs. (†1988)
