The preservation idetnfier helps to identify file formats or software alternatives for process implementation based on a context model of the process. This approach identifies software replacements for a specific software application at risk. Such a risk might be a lack of future support, incompatibility with other components of the process, or that the license the software is published under is prohibitive for the future use or preservation of the system. Using the knowledge base obtained from Freebase and PRONOM, we are able to retrieve migration path information in a structured way. We can e.g. propose the migration of a proprietary word processor file format to a more standard format. Depending on whether we need just read access or also write access to the artefact, different conversions will be available – in general, there will be more support for reading a specific format, thus if this is the only requirement, we will be able to identify more potential alternatives.
Supported process models need to be in the format of the context model. Examples can be found in http://timbus.teco.edu/ontologies/examples/. An exemplaric request could specify the Internet Explorer as tool at risk, and would be presented with alternative ontologies where the Internet Explorer is replaced with alternative tools. This example is shown below, other alternatives can be determined using the web UI of the PI http://kronos.ifs.tuwien.ac.at:8080/kbserver/.
Input (tool at risk):
Output (alternative tools):
* Firefox supports: action_read_HTML-File-Format_Firefox action_write_OpenDocument_Firefox action_read_CSS-File-Format_Firefox * Safari supports: action_read_CSS-File-Format_Safari action_read_HTML-File-Format_Safari * Opera supports: action_read_CSS-File-Format_Opera action_read_HTML-File-Format_Opera action_read_Adr_Opera action_write_Adr_Opera * Google-Chrome supports: action_read_CSS-File-Format_Google-Chrome action_read_HTML-File-Format_Google-Chrome
Copyright (c) 2013/2014 Verein zur Foerderung der IT-Sicherheit in Oesterreich (SBA). The work has been developed in the TIMBUS Project and the above-mentioned are Members of the TIMBUS Consortium. TIMBUS is supported by the European Union under the 7th Framework Programme for research and technological development and demonstration activities (FP7/2007-2013) under grant agreement no. 269940. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at: http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTIBITLY, or FITNESS FOR A PARTICULAR PURPOSE. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law or agreed to in writing, shall any Contributor be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work. See the License for the specific language governing permissions and limitation under the License.
This project is hosted at opensourceprojects. You can clone the project using following command:
git clone https://opensourceprojects.eu/git/p/timbus/dpes/preservation-identifier/parent; git submodule init; git submodule update
The service is hosted at http://kronos.ifs.tuwien.ac.at:8080/pi/preservationIdentifier.
The knowledgebase that backens the PI can be accessed at http://kronos.ifs.tuwien.ac.at:8080/kbserver/. It shows, which tools and formats are available, and which replacements will be performed.
The PI service is hosted at http://kronos.ifs.tuwien.ac.at:8080/pi/preservationIdentifier, can execute on TIMBUS compliant context models, as can be found in http://timbus.teco.edu/ontologies/examples/. The tools and formats that are replaced are specified in a risks XML file. An exemplary risk file is shown in the following:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <businessProcess> <id>businessProcessID</id> <risks> <risk> <id>risk1</id> <name>Imagemagick</name> <likelihood>69</likelihood> <potentialLoss>6.9</potentialLoss> <strategicImpact>None</strategicImpact> <customerImpact>None</customerImpact> <legalImpact>None</legalImpact> <maxRecoveryTime>0.0</maxRecoveryTime> <minRecoveryTime>0.0</minRecoveryTime> <occurInResource>resource1</occurInResource> <occurInBusinessActivity>businessActivity1</occurInBusinessActivity> <riskCategory></riskCategory> </risk> <risk> <id>risk2</id> <name>Oracle Java 6</name> <likelihood>69</likelihood> <potentialLoss>6.9</potentialLoss> <strategicImpact>None</strategicImpact> <customerImpact>None</customerImpact> <legalImpact>None</legalImpact> <maxRecoveryTime>0.0</maxRecoveryTime> <minRecoveryTime>0.0</minRecoveryTime> <occurInResource>resource2</occurInResource> <occurInBusinessActivity>businessActivity1</occurInBusinessActivity> <riskCategory></riskCategory> </risk> </risks> <resources> <resource> <id>resource1</id> <name>imagemagick</name> <type></type> <contextModelURI>http://timbus.teco.edu/ontologies/examples/WP7-OSWF-Migration/wp7-oswf-migration.owl#ieaf928d4</contextModelURI> </resource> <resource> <id>resource2</id> <name>java6-installer</name> <type></type> <contextModelURI>http://timbus.teco.edu/ontologies/examples/WP7-OSWF-Migration/wp7-oswf-migration.owl#idda7d620</contextModelURI> </resource> </resources> <businessActivities> <businessActivity> <id>businessActivity1</id> <name>Search Process</name> <requireResource>resource1</requireResource> </businessActivity> </businessActivities> </businessProcess>