Common use of Information Model Clause in Contracts

Information Model. Core Elements‌ In this Section, we provide some preliminary ideas for the definition of an information model as part of the PoF Reference Model, following the approach used in OAIS. The information model again focuses on the needs of bridging the gap between the Active System and the DPS. In order to meet the requirements of a variety of systems on the site of the Active System as well as on the site of the DPS, the information model has been kept quite generic in this reference model. The core elements of the information model are represented by the UML diagram de- picted in Figure 10, where we included the main types used to represent the objects of preservation. The core element of the information model is an Archival Object (see Figure 10), which is made up of a Content Object and a Context Object. Content Object and Context Object are linked to each other by a gives context link. Both Content Object and Context Object are of type Archival Resource, which is described by a Metadata type and is represented by an Information Object type. An Information Object can be a Single Object such as a photo, a file, or a concept or it can be a Complex Object. An important type of Complex Object is a Collec- tion of objects that are to be archived together. A second type of Complex Object is an Object Graph of interlinked Information Object types. Context is represented by either a Local Context or a World Context type. The Local Context has to be stored in the PDS, because it can, in future, not be easily found elsewhere. World Context is context information that is expected that also in future can be found somewhere else and, thus, it might be sufficient to store only some references to keep this context information. See deliverable D6.1 [ForgetIT, 2013c] for a more detailed discussion of this issue. The information model drafted here will be further refined and described with all details in the next version of the PoF Reference Model, in deliverable D8.5 [ForgetIT, 2016].

Information Model. Core Elements‌ In this Section, we provide some preliminary ideas for the definition of an information model as part of the PoF Reference Model, following the approach used in OAIS. The information model again focuses on the needs of bridging the gap between the Active System and the DPS. In order to meet the requirements of a variety of systems on the site of the Active System as well as on the site of the DPS, the information model has been kept quite generic in this reference model. The core elements of the information model are represented by the UML diagram de- picted in Figure 10, where we included the main types used to represent the objects of preservation. The core element of the information model is an Archival Object (see Figure 10), which is made up of a Content Object and a Context Object. Content Object and Context Object are linked to each other by a gives context link. Both Content Object and Context Object are of type Archival Resource, which is described by a Metadata type and is represented by an Information Object type. An Information Object can be a Single Object such as a photo, a file, or a concept or it can be a Complex Object. An important type of Complex Object is a Collec- tion of objects that are to be archived together. A second type of Complex Object is an Object Graph of interlinked Information Object types. Context is represented by either a Local Context or a World Context type. The Local Context has to be stored in the PDS, because it can, in future, not be easily found elsewhere. World Context is context information that is expected that also in future can be found somewhere else and, thus, it might be sufficient to store only some references to keep this context information. See deliverable D6.1 [ForgetIT, 2013c?] for a more detailed discussion of this issue. The information model drafted here will be further refined and described with all details in the next version of the PoF Reference Model, in deliverable D8.5 [ForgetIT, 2016ForgetIT(2016)].