Structure of the Deliverable. The rest of this deliverable is structured as described in the following. In Section 2, we discuss the foundations of the PoF Reference Model, covering the characteristics of the model as well as the requirements, which did influence its development. In Sec- tion 3, we present the PoF Reference Model for an integrated information and preser- vation management system, which considers this combination as a joint ecosystem. In more detail, we describe a functional model and an information model. In Section 4, we relate the PoF Reference Model to the reference architecture of the PoF Framework. This architecture, which is based on the system architecture presented in deliverables D8.1 [ForgetIT, 2014c] and D8.3[ForgetIT, 2014d], maps the joint ecosystem of building blocks from the reference model on an architecture with three main parts: the Active Sys- tem, the Digital Preservation System (DPS) and the PoF Middleware. In the second part of the deliverable, we relate the PoF Reference Model to existing models and approaches, in order to ease adoption. This includes a discussion of the extensions required in an information system for becoming part of an information and preservation management ecosystem (Section 5) and a discussion on how to map the relevant parts of the model on an OAIS based DPS as well as suggested extensions to such a system (Section 6). We conclude the deliverable with a summary of the main insights, with ideas for future work and an assessment of the results compared to success indicators reported in the project proposal.
Structure of the Deliverable. In Section 2, we discuss the foundations of the PoF Reference Model, covering the char- acteristics of the model as well as the requirements, which influenced its development. We also describe the model in the context of an integrated information and preservation management system, combined as a joint ecosystem. The PoF Reference Model itself is described in two subsequent sections: the functional part in Section 3 and the information part in Section 4, respectively. In Section 5, we relate the PoF Reference Model to the reference architecture of the PoF Framework, mapping the joint ecosystem of building blocks from the reference model to an architecture with three layers (Active System, DPS, PoF Middleware) [Xxxxx et al., 2016]. In the second part of the deliverable, we relate the PoF Reference Model to existing models and approaches, in order to ease adoption. This includes a discussion on how to map the relevant parts of the model to an OAIS based DPS and to other relevant digital preservation standards (Section 6. Furthermore, we required extensions to the Active System for becoming part of an information and preservation management ecosystem (Section 7). Finally, we provide a summary of the main insights, with ideas for future work and an assessment of the results compared to the success indicators in the project proposal.
Structure of the Deliverable. This deliverable consists of four main parts: condensing the ComfDemo message (1), dissemination (2), communication (3) and exploitation (4).
Structure of the Deliverable. The rest of this report is structured as follows: section 2 describes the methodology of the roadmapping effort. Section 3 presents the analysis of the projects in connection with the exploration of disruptive technologies as previously identified in WP1 (Task 1.1). For each technology at first a short introduction is provided (subsection 1), the relevant projects on the European level are described and systematized (subsection 2). The research and the training needs from the projects are extracted and described. In section 4, thirteen possible future scenarios depict potential usages of disruptive technologies in different areas of digital government. Section 4.2 details the research and training needs collected with the help of the scenario analysis. Section 5 contains research and training roadmaps, where specific actions are described in detail. Section 6 outlines recommendations for the implementations of the roadmap actions for different stakeholders. Finally, section 7 concludes the report by briefly summarising the findings and explaining how the findings of this work package can be used in the subsequent work packages of Gov 3.0 project.
Structure of the Deliverable. The current deliverable will be based on two fundamental aspects of communication: • External Communication • Internal communication The external communication of the project will be conducted based on a well-‐structured dissemination strategy by all WP6 partners targeting various audiences (key stakeholders – identified in following section) in order to achieve the objectives and mission of COMRADES. Internal communication among the partners is evenly important for project’s succession and cannot be disregarded, as the smooth development of the project needs to be ensured. The main sections of the document are delineated below: • Introduction • External Communication o Stakeholder Identification -‐ Target groups that are anticipated to be interested in the project and are regarded as key to the project will be identified and listed.
Structure of the Deliverable. The remainder deliverable is structured as follows •
Structure of the Deliverable. The deliverable includes spreadsheet documentation for each of the messages, XSD XML schemas for each pair (request/response) of messages and HMTL documentation/visualisation of the message structures. The XSD and HTML elements can be found in the zipped file attached to this Deliverable 3.4.1., whose contents are as follows: ✓ ARROW Reference Schema v0.1; ✓ Seven individual schema files for message pairs M1 – M7; ✓ One schema file for all code lists (enumerated types); ✓ One schema file containing structures common to all message pairs; ✓ One schema file containing structures not common to all message pairs, but common to message pairs M2 and M4 in the The European Library domain; ✓ Eight HTML files containing schema documentation for each of the above eight schemas; ✓ Various HTML and CSS files supporting display of the documentation; ✓ An ‘img’ folder containing the image file diagrams for the documentation
Structure of the Deliverable. This deliverable reports on the outcome of testing content re-ingestion as part of testing iteration 3 XXX prototype. The deliverable is structured in the following way: • An overview of the preparation before testing the iteration 3 XXX prototype • The results of testing the iteration 3 XXX prototype – content re-ingestion • Conclusions and next steps • APPENDIX I: Preparing testing iteration 3 XXX – content re-ingestion: informing content partners. • APPENDIX II: Content providers survey – iteration 3 on content re-ingestion.
Structure of the Deliverable. This deliverable describes the final version of the TULIPP Reference Platform (TRP), and consists of four parts: •
Structure of the Deliverable. The DREAMS application and platform meta-model has been structured into four main viewpoints that provide meta-models for the description of different aspects of DREAMS systems. In the following, these viewpoints that are defined in Chapter 2 will be summarized: The group of Architecture Viewpoints clusters meta-models used to describe structural aspects of the system. It includes a Logical Viewpoint that provides meta-model for the platform-independent description of applications, a Technical Viewpoint capturing the structure of instances of the DREAMS platform, and a Deployment Viewpoint for the description of mappings between the model elements of the logical and the technical viewpoint. The Temporal Viewpoint provides meta-models that can be used to express timing requirements and temporal properties of applications. The Extra-Functional Viewpoint groups meta-models for the description of application requirements and platform properties related to safety, security and power consumption. The Variability Viewpoint provides a meta-model that can be used to create separate specifications of variation points of a given (product) model.
