Common use of Evolution Layer Clause in Contracts

Evolution Layer. ‌ The Evolution Layer contains three new workflows: the Situation Change workflow is responsible for monitoring semantic changes in the Active System and to propagate them into the DPS, in order to keep the preserved content understandable; the Setting Change workflow deals with changes in practices, formats and technology in the environment of the preservation (setting); finally, the System Change workflow is responsible for situa- tions, where one of the involved systems changes. The first two workflows are described in more detail below, whereas the last workflow is left to the revised version of the PoF Ref- erence Model which will be reported in deliverable D8.5 [ForgetIT(2016)]. In support of the aforementioned workflows, the Evolution Layer includes additional functionalities: Evolu- tion Monitoring, Context Evolution Management, Content Value Re-assessment and Context-aware Preservation Management. The Situation Change workflow consists of four steps (as depicted in Figure 8): (1) change monitoring, (2) change assessment (assessment of detected changes), (3) change notification (notification of involved components as well as the DPS on rele- vant changes) and (4) change propagation, which performs different types of actions depending on the observed change and the chosen change propagation strategy. For monitoring, assessing the changes and deciding about the consequences, in support to the Situation Change workflow, the functionalities Evolution Monitoring (mainly part of Active System), Context Evolution Management and Content Value Re-assessment have been introduced in the Evolution Layer: The Setting Change workflow consists of four different phases with two different starting points (as depicted in Figure 9): the activity monitoring which (1.1) logs the bi-directional communication between the Active System and DPS and (1.2) receives a change request from a DPS, (2) the change assessment that detects and triggers change requests, (3) the change estimation of suitable change recommendations based on content value, purpose of use, and use statistics, (4) the change recommendation, namely the notifi- cation of recommended actions to DPS, which could be of different types, such as change of content or change of physical and logical content structure.

Evolution Layer. ‌ The Evolution Layer contains three new workflows: the Situation Change workflow is responsible for monitoring semantic changes in the Active System and to propagate them into the DPS, in order to keep the preserved content understandable; the Setting Change workflow deals with changes in practices, formats and technology in the environment of the preservation (setting); finally, the System Change workflow is responsible for situa- tions, where one of the involved systems changes. The first two workflows are described in more detail below, whereas the last workflow is left to the revised version of the PoF Ref- erence Model which will be reported in deliverable D8.5 [ForgetIT(2016)ForgetIT, 2016]. In support of the aforementioned workflows, the Evolution Layer includes additional functionalities: Evolu- tion Monitoring, Context Evolution Management, Content Value Re-assessment and Context-aware Preservation Management. The Situation Change workflow consists of four steps (as depicted in Figure 8): (1) change monitoring, (2) change assessment (assessment of detected changes), (3) change notification (notification of involved components as well as the DPS on rele- vant changes) and (4) change propagation, which performs different types of actions depending on the observed change and the chosen change propagation strategy. For monitoring, assessing the changes and deciding about the consequences, in support to the Situation Change workflow, the functionalities Evolution Monitoring (mainly part of Active System), Context Evolution Management and Content Value Re-assessment have been introduced in the Evolution Layer: The Setting Change workflow consists of four different phases with two different starting points (as depicted in Figure 9): the activity monitoring which (1.1) logs the bi-directional communication between the Active System and DPS and (1.2) receives a change request from a DPS, (2) the change assessment that detects and triggers change requests, (3) the change estimation of suitable change recommendations based on content value, purpose of use, and use statistics, (4) the change recommendation, namely the notifi- cation of recommended actions to DPS, which could be of different types, such as change of content or change of physical and logical content structure.