RSS feed: articles by this authorhttp://www.ariadne.ac.uk/author/profile/887/articles
RSS feed: articles related to specified authorenA Foundation for Automatic Digital Preservationhttp://www.ariadne.ac.uk/issue48/ferreira-et-al
<div class="field field-name-field-teaser-article field-type-text-long field-label-hidden"><div class="field-items"><div class="field-item even"><p><a href="/issue48/ferreira-et-al#author1">Miguel Ferreira</a>, <a href="/issue48/ferreira-et-al#author2">Ana Alice Baptista</a> and <a href="/issue48/ferreira-et-al#author3">Jose Carlos Ramalho</a> propose a Service-Oriented Architecture to help cultural heritage institutions to accomplish automatic digital preservation.</p>
</div></div></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>Efforts to archive a large amount of digital material are being developed by many cultural heritage institutions. We have evidence of this in the numerous initiatives aiming to harvest the Web [<a href="#1">1-5</a>] together with the impressive burgeoning of institutional repositories [<a href="#6">6</a>]. However, getting the material inside the archive is just the beginning for any initiative concerned with the long-term preservation of digital materials. <span class="read-more"><a href="/issue48/ferreira-et-al" title="A Foundation for Automatic Digital Preservation" rel="nofollow"><strong>Read more<span class="element-invisible"> about A Foundation for Automatic Digital Preservation</span></strong></a></span></p></div></div></div><div class="field field-name-field-original-article-html field-type-text-long field-label-hidden"><div class="field-items"><div class="field-item even"><p>Efforts to archive a large amount of digital material are being developed by many cultural heritage institutions. We have evidence of this in the numerous initiatives aiming to harvest the Web [<a href="#1">1-5</a>] together with the impressive burgeoning of institutional repositories [<a href="#6">6</a>]. However, getting the material inside the archive is just the beginning for any initiative concerned with the long-term preservation of digital materials. Digital preservation can best be described as the activity or set of activities that enable digital information to be intelligible for long periods of time. In general, digital information kept in an archival environment is expected to be readable and interpretable for periods of time much longer than the expected lifetime of the individual hardware and software components that comprise the repository system, as well as the formats in which the items of information are encoded [<a href="#7">7</a>][<a href="#8">8</a>]. Over the past decade, a vast number of preservation strategies have emerged from the various preservation projects developed, literally, all over the world [<a href="#9">9-12</a>]. Nonetheless, the most cited and applied preservation strategy continues to be migration [<a href="#13">13</a>][<a href="#14">14</a>], especially in contexts where non-interactive digital objects, such as images, databases or text documents, are the focus of preservation. Migration can be described as a '( - ) set of organized tasks designed to achieve the periodic transfer of digital materials from one hardware/software configuration to another or from one generation of computer technology to a subsequent generation.' [<a href="#15">15</a>]. The major drawback in this approach is that whenever an object is converted to a new format, some of its original properties may not be adequately transferred to the target format. This may occur due to incompatibilities between the source and target formats or because the application used to do the conversion is not capable of carrying out its tasks correctly. Understanding Migration Every preservation intervention involves choices. Resources are finite, often scarce. As a result, decisions have to be taken to ensure that the best possible preservation strategy is selected from the wide range of options available. These decisions depend upon a multiplicity of factors such as: technical expertise, users' expectations, institutional budget, existing equipment and available time [<a href="#16">16</a>]. In this respect migration-based strategies are no different. In order to better understand all the steps involved in a migration process, one should consider the following sequence of activities: Selection of a Migration Strategy Two decisions have to be made prior to any object migration: which format should be used to accommodate the properties of the original object; and which application should be used to carry out that migration. This decision-making activity constitutes the first stage of any migration process. It is in the best interests of the preserving institution to aim for the optimal combination of target format and conversion software, i.e. one that preserves the maximum number of properties of the original object at the minimum cost. Cost should be regarded as a multi-dimensional variable. Factors such as throughput, application charges, format openness or prevalence should be considered collectively during this decision-making activity. Objective tools or frameworks especially designed to help institutions in the selection of appropriate options would greatly simplify this exceptionally complicated task. The Conversion The conversion work consists of the reorganisation of the information elements that comprise the digital object into the logical structures as defined by a different format [<a href="#17">17</a>]. From the preserver's point-of-view, carrying out a conversion usually consists in setting up a conversion application and executing it against a collection of digital objects. Some scripts may have to be developed in order to automate the whole procedure. Evaluation of Results After the conversion process, the resultant objects should be evaluated in order to determine the amount of data loss incurred during migration. This is accomplished by comparing the properties that comprise the source object (also known as significant properties [<a href="#18">18</a>][<a href="#19">19</a>]) with the properties of its converted counterparts. If the evaluation results are below expectations, i.e. the object's properties have degraded to an unacceptable level, a different migration alternative should be selected and the whole process reinitiated. In most cases, the evaluation process still requires a considerable amount of manual labour. Certain subjective properties such as the disposition of graphic elements in a text document or the presence of compression artifacts in an image file are generally inspected by human experts, rendering this activity both onerous and time-consuming [<a href="#20">20</a>]. A Service-Oriented Architecture for Automatic Migration At the University of Minho research is being undertaken to devise new pathways to carry out the three outlined activities in an automated fashion (i.e. selection of migration options, conversion and evaluation). Current activities are focused on the development of a Service-Oriented Architecture (SOA) [<a href="#21">21</a>][<a href="#22">22</a>] that, by combining input from different distributed applications, enables client institutions to preserve collections of digital material automatically. It is assumed that client institutions already possess a digital repository system capable of storing, managing and providing access to the digital objects they hold. The repository system will act as the client application that benefits from the services provided by the SOA. In order better to understand all the functions provided by the SOA one might consider the following scenario: The National Archives of Portugal [<a href="#23">23</a>] are currently engaged in the development of a digital repository system capable of preserving authentic digital objects produced by affiliated public administration institutions (Project RODA [<a href="#24">24</a>]). Alongside the development of the repository software comes the creation of ingest and preservation policies that will aid producers in the preparation of their material before it is submitted to the repository. This notwithstanding, the repository will expect to be confronted by objects in formats previously unencountered and which will need to undergo a process of normalisation before being deposited. In the presence of an unrecognised format, the repository system could invoke a format identification service provided by the SOA in order to obtain information about the object's format, in addition to checking its integrity. After this operation, the repository could interrogate the SOA to obtain a list of formats to which the object could be converted. Simultaneously, the repository would inform the SOA of its preservation preferences and requirements, i.e. a list of preservation-oriented requirements derived from the policies created by the senior management of the archive. A few examples of such requirements are as follows:
</p><ul><li>Preservation interventions should be affordable and swift;</li>
<li>Interventions should preserve the maximum number of significant properties of the original object;</li>
<li>The interventions should not resort to formats that are dependent on the payment of royalties.</li>
</ul><p> The SOA would then address all of these criteria with information previously acquired about the behaviour and quality of all accessible conversion applications and would then produce a ranked list of optimal migration options. The repository system could then select the most suitable one from this list and request the SOA to carry out the corresponding migration. After the conversion process, the repository system would receive a new digital object (better yet, a new digital representation of the source digital object) and a migration report stating the amount of data lost in that migration. This report could then be merged with the preservation metadata already maintained by the repository in order to document the preservation intervention and sustain the object's authenticity. On a regular basis, the repository would consult with a notification service to determine if any of the formats it holds are at risk of becoming obsolete. When a format falls into that condition, a new migration process is triggered. A close examination of the outlined scenario enables us to identify the following services:
</p><ul><li>A format identification service that also checks the integrity of digital objects;</li>
<li>A service that produces recommendations of optimal migration options (selection of a migration option);</li>
<li>A service to carry out format migrations (the conversion);</li>
<li>A service to determine the amount of data loss resulting from a migration (evaluation of results);</li>
<li>A service that provides information about the formats that are at risk of becoming obsolete.</li>
</ul><p> The general architecture of the proposed SOA is depicted in Figure 1. This design does not intend to be prescriptive or limiting in any way. The goal is to provide a framework for discussion by pointing out the fundamental elements that should be present in such a system. Several interesting and competing research projects are presented as promising candidates to implement some of these elements. We recognise of course that many other initiatives and solutions might also exist outside the scope of our work or this article. Figure 1: General architecture for a SOA capable of delivering automatic digital preservation. The figure is divided into two major sections: the client and the server-side. The client-side depicts a few examples of applications that may use the services provided by the SOA. Among these are: digital repository systems like DSpace [<a href="#25">25</a>], Fedora [<a href="#26">26</a>] or Eprints [<a href="#27">27</a>], and custom applications developed by individual users. It is important to point out that any application capable of invoking a Web service may make use of the proposed SOA. On the server-side are depicted the chief components comprising this framework. Each of these components is actually an independent application with distinctive roles and responsibilities that co-operate with each other by exchanging messages. This approach makes it possible for each component to be governed by a different organisation and facilitates the distribution of workload. Obsolescence Notifier The first of these components is the Obsolescence Notifier, a service responsible for raising awareness among client institutions of the file formats that are at risk of becoming obsolete. This service should to be consulted regularly by client institutions in order to determine if the objects in their custody are close to becoming unreadable to their designated community. Several resources are available that could be used to support such a service. A few examples are as follows:
</p><ul><li>The report 'Risk Management of Digital Information: A File Format Investigation' by Lawrence, et al [<a href="#17">17</a>], is a study on the impact of migration on file integrity and can provide some guidance in assessing the risk involved in keeping certain file formats.</li>
<li>The INFORM Methodology [<a href="#28">28</a>] is an approach for measuring the durability of digital formats.</li>
<li>The service could also be supported by a group of human experts responsible for monitoring consumer trends and emerging technologies. Several institutions already perform this type of work, although in a more generalised fashion, e.g. DigiCULT with its annual Technology Watch Reports [<a href="#29">29</a>] and the Digital Preservation Coalition with its monthly themed Technology Watch Reports [<a href="#30">30</a>].</li>
</ul><p> Format Detector The Format Detector, as the name suggests, is a service capable of identifying the underlying encoding of a digital object. The client institution should be able to monitor, migrate and validate the integrity of digital objects without human intervention and this service is indispensable in accomplishing that goal. Furthermore, it enables digital formats to be identified according to the naming scheme used by other components that comprise the proposed SOA (e.g. the Migration Broker). The following applications are potential candidates for supporting such a service:
</p><ul><li>JHOVE, jointly developed by JSTOR and the Harvard University Library, is an application specifically designed to identify and characterise digital formats. In fact, JHOVE is more of a technical metadata extractor than a simple format identifier. At the moment, JHOVE is capable of supporting 11 different file formats [<a href="#31">31</a>].</li>
<li>Droid, on the other hand, was developed exclusively to identify digital formats. It was developed by the National Archives of the United Kingdom, the creators of the PRONOM format registry [<a href="#32">32</a>][<a href="#33">33</a>], and currently supports hundreds of different file formats [<a href="#34">34</a>].</li>
</ul><p> Some institutions and initiatives have been developing services capable of carrying out format migrations [<a href="#35">35-40</a>]. Such initiatives rely on a common set of communication protocols to support the discovery and invocation of conversion procedures. Any conventional application may also be used as a service if an appropriate application wrapper is developed [<a href="#22">22</a>], i.e. a small piece of software that acts as the intermediary between the application and communication protocol. In this type of approach, a client application is used to send out a digital object to a remote procedure that, after unpackaging the received message, converts the embedded object and returns the result back to the client. Standard protocols, such as the ones that accompany Web services technology [<a href="#41">41</a>], may play an important role in this domain due to their open-standard and platform-independent characteristics. A distributed approach to migration introduces some appealing properties:
</p><ul><li>the use of Web services hides the complexity of the conversion software that is being used under the hood and promotes interoperability by cloaking the peculiarities of the supporting hardware and operating system;</li>
<li>combining conversion services enables new migrations to be performed and makes this solution capable of coping with the gradual disappearance of converters [<a href="#22">22</a>];</li>
<li>the development of redundant services ensures that the migration network remains functional during situations of partial breakdown.</li>
<li>this approach is compatible with several variants of migration, such as normalisation [<a href="#13">13</a>][<a href="#42">42-47</a>] and migration on-request [<a href="#10">10</a>].</li>
</ul><p> However, requiring the presence of a computer network to carry out format migrations hardly seems reasonable in a preservation context. This type of reliance on technology is generally very undesirable. However, digital preservation is a global problem. A distributed approach may very well prove to be an effective way to handle the intricacies of preservation as it allows institutions worldwide to share their solutions and co-operate in the network of services. Service Registry The Service Registry component is responsible for managing information about existing conversion services. It stores metadata about its producer/developer (e.g. name, description and contact), about the service itself (e.g. name, description, the source/target formats that it is capable of handling, cost of invocation, etc.) and information on how the service should be invoked by a client application (i.e. its access point). It is important that the Service Registry is populated with rich metadata. Much of the information delivered to end-users after a conversion will be obtained from this data source. This information can be used to document the preservation intervention as it outlines all the components that took part in the migration process and describes the outcome of the event in terms of data loss and object degradation (see <a href="#ObjectEvaluator">Object Evaluator</a>). This migration report constitutes what PREMIS refers to as an Event Entity [<a href="#48">48</a>]. One of the major advantages of using Web services in this context is in the capacity to combine tens or hundreds of conversion services to create new migration operations. However to accomplish this, each conversion service should respect a well-defined interface that establishes the arguments that each conversion service should be capable of handling. Although this interface is essential to produce service compositions, it is not sufficient on its own. Each conversion service must be described with source and target format metadata elements whose values are obtained from a controlled vocabulary. This is fundamental to enable the computation of the migration network (i.e. all possible migration paths between two given formats). Several initiatives are considered suitable candidates to provide that controlled vocabulary:
</p><ol><li>The PRONOM registry, an initiative from the National Archives of the UK aims at building a registry of information about every existing file format [<a href="#32">32</a>][<a href="#33">33</a>];</li>
<li>The Digital Formats Web site, created by the Library of Congress aims at providing information about digital content formats [<a href="#49">49</a>][<a href="#50">50</a>];</li>
<li>The Global Digital Format Registry intends to provide sustainable distributed services to store, discover and deliver representation information about digital formats [<a href="#51">51</a>][<a href="#52">52</a>];</li>
<li>Representation Information Registry/Repository is an OAIS representation information registry for digital data and is currently being developed by the Digital Curation Centre [<a href="#53">53</a>].</li>
</ol><p> Migration Broker The Migration Broker is responsible for carrying out object migrations. In practice, this component is responsible for making sure that composite conversions are performed atomically from the point of view of the client application and the rest of the SOA components. Additionally, this component is responsible for recording the performance of each migration service. The results of these measurements are stored in the Evaluations Repository, a knowledge base that supports the recommendation system (see <a href="#MigrationAdvisor">Migration Advisor</a>). A prototype of the proposed SOA is currently being devised at the University of Minho and is presently capable of measuring the following process-related criteria:
</p><ul><li>Availability, i.e. the probability of a service being operational at the time of invocation.</li>
<li>Stability, i.e. the capacity of a service to carry out what it purports to do.</li>
<li>Throughput, i.e. the amount of work that the service is capable of doing per time unit. The workload is determined by the size of the object to be converted.</li>
<li>Cost, i.e. the amount that a client will have to pay to use the service on one occasion. The cost of a composite migration is the sum of each individual cost.</li>
<li>Outcome size, i.e. the size in bytes of the resulting object when compared with the original.</li>
<li>Outcome file count, i.e. the number of files in the resulting representation.</li>
</ul><p> Format Evaluator The Format Evaluator provides information about the current status of file formats. This information enables the Migration Advisor to determine which formats are better suited to accommodate the properties of source objects by looking at the characteristics of each pair of formats. This service is supported by a data store containing facts about formats (i.e. Format Knowledge Base), but could also exploit external sources of information such as the PRONOM registry or Google Trends [<a href="#54">54</a>], to determine automatically a format's prevalence and usage. The current prototype is capable of determining the potential gain (in terms of preservation) that one might obtain in converting an object from its original format to a new one by considering the following set of criteria:
</p><ul><li>Market share, i.e. whether the format is widely accepted or simply a niche format. Market share is also known as 'adoption'. Adoption refers to the degree to which the format is already used by the primary creators, disseminators, or users of information resources;</li>
<li>Support level, i.e. whether the creator of the format provides good technical support on the format;</li>
<li>Is standard, i.e. whether the format has been published by a standards organisation;</li>
<li>Open specification, i.e. whether specification can be independently inspected.</li>
<li>Supports compression, i.e. whether the format supports any type of compression.</li>
<li>Lossy compression only, i.e. whether the format only supports a lossy type of compression.</li>
<li>Supports transparency, i.e. whether the format supports transparency features.</li>
<li>Embedded metadata, i.e. whether the format may contain embedded metadata.</li>
<li>Royalty-free, i.e. whether royalties or licence fees are payable.</li>
<li>Open source, i.e. whether there are decoders whose source can be independently inspected.</li>
<li>Backwardly compatible, i.e. whether revisions have support for previous versions.</li>
<li>Documentation level, i.e. whether the format specification is well documented.</li>
<li>Competing formats available, i.e. whether competing or similar formats exist.</li>
<li>DRM support, i.e. whether DRM (Digital Rights Management), encryption or digital signatures can be used.</li>
<li>Update frequency, i.e. whether revisions happen so fast that the archive cannot keep up with demand.</li>
<li>Supports custom extensions, i.e. whether extensions, such as executable sections or narrowly supported features, can be added to the format.</li>
<li>Life time, i.e. how many years have passed since the format has been officially released.</li>
<li>Transparent decoding, i.e. the degree to which the digital representation is open to direct analysis with basic tools, including human readability using a text-only editor.</li>
<li>Reader single producer, i.e. whether the reader/viewer is produced by a single entity.</li>
<li>Single reader, i.e. whether the format can only be read by one piece of software.</li>
<li>Open source reader, i.e. whether the source-code of the reader software can be independently inspected.</li>
<li>Multiplatform reader, i.e. whether the reader software can be run on various platforms (e.g. operating systems or hardware).</li>
</ul><p> All of these criteria are being considered by the Migration Advisor to rank all the available migration options. This component is capable of measuring the preservation gain of performing a certain transformation. For example, if the target format is royalty-free while the source format is not, there is a preservation gain associated with that transformation. On the other hand, if the target format only supports a lossy type of compression, while the source format is not compressed at all, there is a potential risk of losing important information in the process. The criteria present in this evaluation taxonomy were assembled from various bibliographic sources such as [<a href="#28">28</a>][<a href="#49">49</a>][<a href="#55">55</a>]. Groups of format experts and digital curators may also contribute with additional criteria to enrich the evaluation taxonomy. <a name="ObjectEvaluator" id="ObjectEvaluator"></a>Object Evaluator The Object Evaluator is in charge of judging the quality of the migration outcome. It accomplishes this by comparing objects submitted for migration with their converted counterparts. Again, these evaluations will be performed according to a range of criteria. These criteria, known in this context as significant properties, constitute the set of attributes of an object that should be kept intact during a preservation intervention [<a href="#19">19</a>]. They constitute the array of attributes that characterise an object as a unique intellectual entity, independently of the encoding used to represent it. The Bible for example, may exist in many different formats and media, e.g. ASCII text, Portable Document Format, written on paper or carved on stone, and still be regarded as the Holy Bible. Considering text documents as an example, some significant properties could be: the number of characters, the order of those characters, the page size, the number of pages, the graphical layout, the font type and size. <a name="MigrationAdvisor" id="MigrationAdvisor"></a>Migration Advisor The Migration Advisor is responsible for producing suggestions of migration alternatives. In reality this component acts as a decision support centre for client institutions and is capable of determining the best possible choice within a wide range of options. It accomplishes this by confronting the preservation requirements outlined by client institutions with the accumulated knowledge about the behaviour of each accessible migration path. The behaviour of each migration path is determined by taking into consideration the sets of criteria previously described: conversion performance, status of the formats involved and data loss (handled respectively by the Migration Broker, Format Evaluator and Object Evaluator). Evaluations Repository In order to generate an appropriate recommendation, the Migration Advisor resorts to the Evaluations Repository, a database containing all the measurements taken by the Object Evaluator, the Format Evaluator and the Migration Broker. Averaging these readings provides a general idea about the behaviour of each migration path. Different institutions will have distinct preservation needs. They will be able to state their individual requirements by weighting the importance of each criteria handled by the system. This enables the system to rank all the alternatives according to their level of aptness to resolve the preservation problem of the client institution. In order to rank all possible options, the Evaluations Repository must be populated with data. This is generally called training and basically consists in requesting the SOA to convert a large set of digital objects in different forms and sizes using all possible migration paths. This operation forces all the evaluators to produce reports that will be used by the Migration Advisor to compute an appropriate recommendation. The Migration Advisor uses the same principles as the evaluation framework described by Rauch and Rauber [<a href="#16">16</a>][<a href="#20">20</a>][<a href="#55">55-57</a>]. The process within the SOA is orchestrated as follows:
</p><ol><li>For each migration path, a standard or average behaviour is determined for all of the evaluation criteria. This task is performed by the Migration Advisor whenever a suggestion is requested. It is assumed that the Evaluations Repository has already been populated with data (Figure 2, step 1);</li>
<li>The average behaviour per criterion of a given migration path is then normalised into a comparable scale of 0 to 1 (Figure 2, step 2). The highest measurements assume the value of 1 whilst the lowest are normalised to a 0. All other values are spread between these two figures. It is important to point out that evaluations always produce positive preservation results, i.e. high values correspond to a better preservation performance. The cost criterion, for example, must be inverted before the normalisation step, as higher values of cost correspond to lower preservation performances.</li>
<li>The client institution is then asked to assign weights to each evaluation criteria according to its perception of importance. These weights are then multiplied by the normalised values calculated in the previous step (Figure 2, step 3);</li>
<li>The overall score of a migration path is obtained by summing up all the ensuing values. The most appropriate migration option is the one that attains the highest score (Figure 2, step 4).</li>
</ol><p> Figure 2: Steps involved in the ranking migration alternatives. MP1 and MP2 represent two different migration paths to convert text documents. (This table is displayed in an <a name="table" id="table"></a><a href="table2.html">alternative format</a>.) Evaluation A prototype implementing the concepts described in this paper is currently being devised at the University of Minho and is expected to be fully operational by the end of 2006 [<a href="#22">22</a>][<a href="#58">58</a>]. The purpose of this prototype is to evaluate the suitability of the proposed architecture and the precision of the recommendation system. Precision will be assessed using cross-validation techniques. Still images are generally represented by simple structures and, for that reason, are being used to guide the development of the prototype. More complex objects, like text documents produced by word-processing software, will be considered afterwards in order to assess their effectiveness in handling more subjective criteria, such as appearance or text layout. The current prototype fully implements the following components:
</p><ul><li>a Service Registry, being supported by an UDDI server.</li>
<li>a Migration Network with 91 registered converters.</li>
<li>a Migration Broker, fully capable of combining migration services and recording their performance;</li>
<li>a Format Detector, being supported by Droid [<a href="#34">34</a>];</li>
<li>a Format Evaluator, capable of comparing several file formats according to the criteria outlined in the previous section;</li>
<li>a Migration Advisor, fully capable of computing recommendations based on the information collected in the Evaluations Repository.</li>
</ul><p> Adding new evaluation criteria to the prototype is as easy as updating a configuration file. The real complexity relies on creation of new criterion evaluators. Once developed, these evaluators can be placed in the servers file system (to be loaded during system's bootstrap) or remotely invoked. New conversion services can be attached to the system by simply adding them to the Service Registry. Training the Migration Advisor to recognise new conversion services is, of course, essential. Throughout this article, Web services have been presented as a promising technology to support the proposed SOA. However, many other protocols exist which could be used to implement these ideas. Different technologies could even be utilised together by means of gateways or proxies. For example, a gateway is currently being developed to enable converters provided by the TOM Conversion Service [<a href="#35">35</a>][<a href="#59">59</a>], a technology that uses a non-standard communication protocol, to be used by our prototype. Conclusions and Future Work This article describes the set of components that are necessary to build a Service- Oriented Architecture (SOA) to enable cultural heritage institutions to carry out digital preservation with minimum human intervention. The proposed SOA enables institutions to co-operate in the establishment of a global advisory service that, among other things, will be capable of producing recommendations of optimal migration options, perform format migrations and thoroughly document preservation interventions by generating appropriate preservation metadata. The proposed SOA could also be used as an objective tool for comparing file formats and conversion software. It could be used to provide an on-demand migration service, i.e. a service capable of converting objects from their archival configurations to formats more suitable for dissemination; as well as a normalisation procedure for ingest work. Although a prototype for this SOA is still under development, some conclusions can already be drawn. The set of digital objects used to train the recommendation system should be as heterogeneous as possible in terms of shape and size, and should contain at least a couple of thousand objects. Small or homogeneous object sets generate very imprecise recommendations due to overfitting in the learning process [<a href="#60">60</a>]. Further research could be conducted to detect patterns in the user-assigned weights. Such patterns would represent user profiles and would enable the recommendation process to be automated one step further. The proposed SOA could also contribute to fostering new lines of research such as the improvement, or the development, of comparison algorithms for different classes of objects, e.g. image, text, audio, video or datasets. Comparators such as these are necessary to develop a general purpose Object Evaluator. Further work should also be conducted to devise a general evaluation taxonomy for several classes of digital objects. Acknowledgments The work reported in this article has been funded by the FCT (Fundação para a Ciência e a Tecnologia, Portugal) under the grant SFRH/BD/17334/2004. References
</p><ol><li><a name="1" id="1"></a>PANDORA - Australia's Web Archive <a href="http://pandora.nla.gov.au/">http://pandora.nla.gov.au/</a></li>
<li><a name="2" id="2"></a>UK Web Archiving Consortium <a href="http://www.webarchive.org.uk/">http://www.webarchive.org.uk/</a></li>
<li><a name="3" id="3"></a>The Wayback Machine <a href="http://www.archive.org/">http://www.archive.org/</a></li>
<li><a name="4" id="4"></a>Austrian On-Line Archive <a href="http://www.ifs.tuwien.ac.at/~aola/">http://www.ifs.tuwien.ac.at/~aola/</a></li>
<li><a name="5" id="5"></a>Kulturarw3 - Long time preservation of electronic documents <a href="http://www.kb.se/kw3/ENG/">http://www.kb.se/kw3/ENG/</a></li>
<li><a name="6" id="6"></a>Growth of Institutional Archives over Time <a href="http://archives.eprints.org/index.php?action=analysis">http://archives.eprints.org/index.php?action=analysis</a></li>
<li><a name="7" id="7"></a>D. S. H. Rosenthal, T. Robertson, T. Lipkis, V. Reich, and S. Morabito, "Requirements for Digital Preservation Systems", <em>D-Lib Magazine</em> 11 (11), 2005 <a href="http://www.dlib.org/dlib/november05/rosenthal/11rosenthal.html">http://www.dlib.org/dlib/november05/rosenthal/11rosenthal.html</a></li>
<li><a name="8" id="8"></a>L. S. Lin, C. K. Ramaiah, and P. K. Wal, "Problems in the preservation of electronic records", Library Review 52 (3), pp. 117-125, 2003.</li>
<li><a name="9" id="9"></a>A. R. Heminger and S. B. Robertson, "Digital Rosetta Stone: A Conceptual Model for Maintaining Long-Term Access to Digital Documents", presented at 6th DELOS Workshop, Tomar, Portugal, 1998.</li>
<li><a name="10" id="10"></a>P. Mellor, P. Wheatley, and D. M. Sergeant, "Migration on Request, a Practical Technique for Preservation", presented at ECDL '02: 6th European Conference on Research and Advanced Technology for Digital Libraries, London, UK, 2002.</li>
<li><a name="11" id="11"></a>S. Granger, "Emulation as a Digital Preservation Strategy", <em>D-Lib Magazine</em> 6 (10), 2000 <a href="http://www.dlib.org/dlib/october00/granger/10granger.html">http://www.dlib.org/dlib/october00/granger/10granger.html</a></li>
<li><a name="12" id="12"></a>R. A. Lorie, "A Methodology and System for Preserving Digital Data", presented at Second ACM/IEEE-CS Joint Conference on Digital Libraries (JCDL'02), Portland, Oregon, 2002.</li>
<li><a name="13" id="13"></a>K.-H. Lee, O. Slattery, R. Lu, X. Tang, and V. McCrary, "The State of the Art and Practice in Digital Preservation", Journal of Research of the National Institute of Standards and Technology 107 (1), pp. 93-106, 2002.</li>
<li><a name="14" id="14"></a>P. Wheatley, "Migration: a Camileon discussion paper", <em>Ariadne</em> issue 29, September 2001 <a href="../../issue29/camileon/">http://www.ariadne.ac.uk/issue29/camileon/</a></li>
<li><a name="15" id="15"></a>Task Force on Archiving of Digital Information, Commission on Preservation and Access, and Research Libraries Group, Preserving digital information: report of the Task Force on Archiving of Digital Information. Washington, D.C.: Commission on Preservation and Access, 1996.</li>
<li><a name="16" id="16"></a>C. Rauch and A. Rauber, "Preserving Digital Media: Towards a Preservation Solution Evaluation Metric", presented at International Conference on Asian Digital Libraries, Shanghai, China, 2004.</li>
<li><a name="17" id="17"></a>G. W. Lawrence, W. R. Kehoe, O. Y. Rieger, W. H. Walters, and A. R. Kenney, "Risk Management of Digital Information: A file format investigation", Council on Library and Information Resources, Washington, DC 2000.</li>
<li><a name="18" id="18"></a>H. Hofman, "Can Bits and Bytes be Authentic? Preserving the Authenticity of Digital Objects", presented at International Federation of Library Associations Conference, Glasgow, 2002.</li>
<li><a name="19" id="19"></a>A. Rusbridge, "Migration on Request", University of Edinburgh - Division of Informatics, 4th Year Project Report 2003.</li>
<li><a name="20" id="20"></a>C. Rauch, F. Pavuza, S. Strodl, and A. Rauber, "Evaluating preservation strategies for audio and video files", presented at DELOS Digital Repositories Workshop, Heraklion, Crete, 2005.</li>
<li><a name="21" id="21"></a>OASIS SOA Reference Model TC, "OASIS Reference Model for Service Oriented Architectures (Working Draft 10)", OASIS 2005.</li>
<li><a name="22" id="22"></a>M. Ferreira, A. A. Baptista, and J. C. Ramalho, "CRiB: A service oriented architecture for digital preservation outsourcing", presented at XATA - XML: Aplicações e Tecnologias Associadas, Portalegre, Portugal, 2006.</li>
<li><a name="23" id="23"></a>Instituto dos Arquivos Nacionais/Torre do Tombo Web site <a href="http://www.iantt.pt/">http://www.iantt.pt/</a></li>
<li><a name="24" id="24"></a>RODA (Repositório de Objectos Digitais Autênticos) Web site <a href="http://roda.iantt.pt/">http://roda.iantt.pt/</a></li>
<li><a name="25" id="25"></a>DSpace Web site <a href="http://www.dspace.org">http://www.dspace.org/</a></li>
<li><a name="26" id="26"></a>Fedora Web site <a href="http://www.fedora.info/">http://www.fedora.info/</a></li>
<li><a name="27" id="27"></a>EPrints Web site <a href="http://www.eprints.org/">http://www.eprints.org/</a></li>
<li><a name="28" id="28"></a>A. Stanescu, "Assessing the Durability of Formats in a Digital Preservation Environment", <em>D-Lib Magazine</em> 10 (11), 2004.</li>
<li><a name="29" id="29"></a>Technology Watch Reports <a href="http://www.digicult.info/">http://www.digicult.info/</a> </li>
<li><a name="30" id="30"></a>Technology Watch Reports <a href="http://www.dpconline.org/graphics/reports/">http://www.dpconline.org/graphics/reports/</a></li>
<li><a name="31" id="31"></a>JHove - JSTOR/Harvard Object Validation Environment <a href="http://hul.harvard.edu/jhove/">http://hul.harvard.edu/jhove/</a></li>
<li><a name="32" id="32"></a>J. Darlington, "PRONOM - A Practical Online Compendium of File Formats", RLG DigiNews 7 (5), 2003.</li>
<li><a name="33" id="33"></a>PRONOM - The file format registry <a href="http://www.nationalarchives.gov.uk/pronom/">http://www.nationalarchives.gov.uk/pronom/</a></li>
<li><a name="34" id="34"></a>UK National Archives, "Droid: Digital Record Object Identification," 1.0 ed. Surrey: UK National Archives, 2005.</li>
<li><a name="35" id="35"></a>J. M. Ockerbloom, "Mediating Among Diverse Data Formats," in School of Computer Science. Pittsburg: Carnegie Mellon University, 1998, pp. 164.</li>
<li><a name="36" id="36"></a>F. L. Walker and G. R. Thoma, "A Web-Based Paradigm for File Migration", presented at IS&amp;T's 2004 Archiving Conference, San Antonio, Texas, USA, 2004.</li>
<li><a name="37" id="37"></a>J. Hunter and S. Choudhury, "A Semi-Automated Digital Preservation System based on Semantic Web Services", presented at Joint ACM/IEEE Conference on Digital Libraries (JCDL'04), 2004.</li>
<li><a name="38" id="38"></a>Preservation webservices Architecture for Newmedia and Interactive Collections (PANIC) <a href="http://metadata.net/panic/">http://metadata.net/panic/</a></li>
<li><a name="39" id="39"></a>J. M. Wing and J. Ockerbloom, "Respectful Type Converters", IEEE Transactions on Software Engeneering 26 (7), 2000.</li>
<li><a name="40" id="40"></a>J. Hunter and S. Choudhury, "PANIC: an integrated approach to the preservation of composite digital objects using Semantic Web services", International Journal on Digital Libraries 6 (2), pp. 174-183, 2006.</li>
<li><a name="41" id="41"></a>S. Graham, S. Simeonov, T. Boubez, D. Davis, G. Daniels, Y. Nakamura, and R. Neyama,<em> Building Web Services with Java: Making Sense of XML, SOAP, WSDL and UDDI</em>: Sams Publishing, 2002.</li>
<li><a name="42" id="42"></a>K. Thibodeau, "Overview of Technological Approaches to Digital Preservation and Challenges in Coming Years", presented at The State of Digital Preservation: An International Perspective, Washington D.C., 2002.</li>
<li><a name="43" id="43"></a>H. Hofman, "How to keep digital records understandable and usable through time?" presented at Long-Term Preservation of Electronic Records, Paris, France, 2001.</li>
<li><a name="44" id="44"></a>H. Heslop, S. Davis, and A. Wilson, "An Approach to the Preservation of Digital Records." Camberra, Australia: National Archives of Australia, 2002.</li>
<li><a name="45" id="45"></a>A. G. Howel, "Preserving Digital Information: Challenges and Solutions", Cooperative Action by Victorian Academic Libraries, Victorian university libraries, State Library of Victoria 2004.</li>
<li><a name="46" id="46"></a>G. Hodge and E. Frangakis, "Digital Preservation and Permanent Access to Scientific Information: The State of the Practice", International Council for Scientific and Technical Information &amp; CENDI, Report 2004-3: Rev. 05/04, 2004.</li>
<li><a name="47" id="47"></a>M. Hedstrom, "Digital Preservation: A time bomb for digital libraries", Computers and the Humanities 31, pp. 189-202, 1998.</li>
<li><a name="48" id="48"></a>PREMIS Working Group, "Data dictionary for preservation metadata: final report of the PREMIS Working Group", OCLC Online Computer Library Center &amp; Research Libraries Group, Dublin, Ohio, USA, Final report 2005.</li>
<li><a name="49" id="49"></a>Digital Formats Web site <a href="http://www.digitalpreservation.gov/formats/">http://www.digitalpreservation.gov/formats/</a></li>
<li><a name="50" id="50"></a>C. R. Arms and C. Fleischhauer, "Digital Formats: Factors for Sustainability, Functionality, and Quality", presented at IS&amp;T Archiving Conference, Washington, D.C., USA, 2005.</li>
<li><a name="51" id="51"></a>S. L. Abrams and D. Seaman, "Towards a global digital format registry", presented at World Library and Information Congress: 69th IFLA General Conference and Council, 2003.</li>
<li><a name="52" id="52"></a>Global Digital Format Registry <a href="http://hul.harvard.edu/gdfr/">http://hul.harvard.edu/gdfr/</a></li>
<li><a name="53" id="53"></a>OAIS Representation Information Registry/Repository <a href="http://dev.dcc.ac.uk/twiki/bin/view/Main/DCCRegRepV04">http://dev.dcc.ac.uk/twiki/bin/view/Main/DCCRegRepV04</a></li>
<li><a name="54" id="54"></a>Google Trends <a href="http://www.google.com/trends">http://www.google.com/trends</a></li>
<li><a name="55" id="55"></a>C. Rauch, A. Rauber, H. Hofman, J. Bogaarts, R. Vedegem, F. Pavuza, J. Ahmer, and M. Kaiser, "A Framework for Documenting the Behaviour and Funcionality of Digital Objects and Preservation Strategies", DELOS Network of Excellence, Glasgow 2005.</li>
<li><a name="56" id="56"></a>C. Rauch, "Preserving Digital Entities - A Framework for Choosing and Testing Preservation Strategies," in Institute for Software Technology and Interactive Systems. Vienna: Vienna University of Technology, 2004.</li>
<li><a name="57" id="57"></a>P. Weirich, B. Skyrms, E. W. Adams, K. Binmore, J. Butterfield, P. Diaconis, and W. L. Harper, <em>Decision Space: Multidimensional Utility Analysis</em>. Cambridge, 2001.</li>
<li><a name="58" id="58"></a>CRiB - Conversion and Recommendation of Digital Object Formats Web site <a href="http://crib.dsi.uminho.pt/">http://crib.dsi.uminho.pt/</a></li>
<li><a name="59" id="59"></a>TOM Conversion Service <a href="http://tom.library.upenn.edu/convert/">http://tom.library.upenn.edu/convert/</a></li>
<li><a name="60" id="60"></a>I. V. Tetko, D. J. Livingstone, and A. I. Luik, "Neural network studies. 1. Comparison of overfitting and overtraining", Journal of Chemical Information and Computer Sciences 35, pp. 826-833, 1995.</li>
</ol><p> Author Details <a name="author1" id="author1"></a> <strong>Miguel Ferreira</strong> PhD student Department of Information Systems University of Minho 4800-058 Azurém-Guimarães Portugal Email: <a href="mailto:mferreira@dsi.uminho.pt">mferreira@dsi.uminho.pt</a> Web site: <a href="http://www.dsi.uminho.pt/~ferreira">http://www.dsi.uminho.pt/~ferreira</a> Graduated as a Systems and Informatics Engineer, has worked as a consultant at the Arquivo Distrital do Porto (Oporto's Archive) and as a researcher at the University of Minho. Since 2003 has been publishing in field of digital archives/libraries and preservation. Currently, is developing work as a PhD student and coordinating several research projects at the Arquivo Distrital do Porto and the Portuguese National Archives (Instituto dos Arquivos Nacionais/Torre do Tombo). <a name="author2" id="author2"></a> <strong>Ana Alice Baptista</strong> Auxiliary professor Department of Information Systems University of Minho 4800-058 Guimarães Portugal Email: <a href="mailto:analice@dsi.uminho.pt">analice@dsi.uminho.pt</a> Web site: <a href="http://www.dsi.uminho.pt/~analice">http://www.dsi.uminho.pt/~analice</a> Auxiliary Professor at the Department of Information Systems of University of Minho, Ana has been publishing in the areas of Knowledge Society, Scholarly Communication, Information Access &amp; Retrieval and Semantic Web. She is also interested in the social aspects of the Internet, primarily on its impacts on scholarly communication. <a name="author3" id="author3"></a> <strong>José Carlos Ramalho</strong> Auxiliary Professor Computer Science Department University of Minho 4710-057 Braga Portugal Email: <a href="mailto:jcr@di.uminho.pt">jcr@di.uminho.pt</a> Web site: <a href="http://www.di.uminho.pt/~jcr">http://www.di.uminho.pt/~jcr</a> Auxiliary Professor at the Computer Science Department of the University of Minho, has a Masters on 'Compiler Construction' and a PhD on the subject 'Document Semantics and Processing''. Has been managing projects and publishing in the field of Markup Languages since 1995. <a href="#top">Return to top</a> Article Title: "A Foundation for Automatic Digital Preservation" Author: Miguel Ferreira, Ana Alice Baptista and José Carlos Ramalho Publication Date: 30-July-2006 Publication: Ariadne Issue 48 Originating URL: <a href="http://www.ariadne.ac.uk/issue48/ferreira-et-al/">http://www.ariadne.ac.uk/issue48/ferreira-et-al/</a></p>
</div></div></div><div class="field field-name-field-article-authors field-type-text-long field-label-hidden"><div class="field-items"><div class="field-item even"><p>Miguel Ferreira, Ana Alice Baptista, Jose Carlos Ramalho</p>
</div></div></div><div class="field field-name-taxonomy-vocabulary-3 field-type-taxonomy-term-reference field-label-above clearfix"><h3 class="field-label">Organisations: </h3><ul class="links"><li class="taxonomy-term-reference-0"><a href="/category/buzz/google">google</a></li><li class="taxonomy-term-reference-1"><a href="/taxonomy/term/1184">oclc</a></li><li class="taxonomy-term-reference-2"><a href="/taxonomy/term/1387">library of congress</a></li><li class="taxonomy-term-reference-3"><a href="/taxonomy/term/1582">university of cambridge</a></li><li class="taxonomy-term-reference-4"><a href="/taxonomy/term/1722">oasis</a></li><li class="taxonomy-term-reference-5"><a href="/taxonomy/term/2103">ieee</a></li><li class="taxonomy-term-reference-6"><a href="/taxonomy/term/2918">oais</a></li><li class="taxonomy-term-reference-7"><a href="/taxonomy/term/5852">dcc</a></li><li class="taxonomy-term-reference-8"><a href="/taxonomy/term/7747">premis</a></li><li class="taxonomy-term-reference-9"><a href="/taxonomy/term/12284">digital preservation coalition</a></li><li class="taxonomy-term-reference-10"><a href="/category/organisations/university-edinburgh">university of edinburgh</a></li><li class="taxonomy-term-reference-11"><a href="/taxonomy/term/13859">harvard university</a></li><li class="taxonomy-term-reference-12"><a href="/taxonomy/term/14070">d-lib magazine</a></li><li class="taxonomy-term-reference-13"><a href="/taxonomy/term/14078">carnegie mellon university</a></li><li class="taxonomy-term-reference-14"><a href="/taxonomy/term/14159">the national archives</a></li><li class="taxonomy-term-reference-15"><a href="/category/organisations/university-minho">university of minho</a></li><li class="taxonomy-term-reference-16"><a href="/taxonomy/term/16136">ifla</a></li></ul></div><div class="field field-name-taxonomy-vocabulary-2 field-type-taxonomy-term-reference field-label-above clearfix"><h3 class="field-label">Projects: </h3><ul class="links"><li class="taxonomy-term-reference-0"><a href="/taxonomy/term/13579">crib</a></li><li class="taxonomy-term-reference-1"><a href="/taxonomy/term/13580">reposit</a></li></ul></div><div class="sharethis-buttons"><div class="sharethis-wrapper"><span st_url="http://www.ariadne.ac.uk/issue48/ferreira-et-al" st_title="A Foundation for Automatic Digital Preservation" class="st_facebook_button" displayText="facebook"></span>
<span st_url="http://www.ariadne.ac.uk/issue48/ferreira-et-al" st_title="A Foundation for Automatic Digital Preservation" class="st_twitter_button" displayText="twitter"></span>
<span st_url="http://www.ariadne.ac.uk/issue48/ferreira-et-al" st_title="A Foundation for Automatic Digital Preservation" class="st_linkedin_button" displayText="linkedin"></span>
<span st_url="http://www.ariadne.ac.uk/issue48/ferreira-et-al" st_title="A Foundation for Automatic Digital Preservation" class="st_email_button" displayText="email"></span>
<span st_url="http://www.ariadne.ac.uk/issue48/ferreira-et-al" st_title="A Foundation for Automatic Digital Preservation" class="st_sharethis_button" displayText="sharethis"></span>
<span st_url="http://www.ariadne.ac.uk/issue48/ferreira-et-al" st_title="A Foundation for Automatic Digital Preservation" class="st_pinterest_button" displayText="pinterest"></span>
<span st_url="http://www.ariadne.ac.uk/issue48/ferreira-et-al" st_title="A Foundation for Automatic Digital Preservation" class="st_plusone_button" displayText="plusone"></span>
<span st_url="http://www.ariadne.ac.uk/issue48/ferreira-et-al" st_title="A Foundation for Automatic Digital Preservation" class="st_fblike_button" displayText="fblike"></span>
</div></div>
<div class="field field-name-taxonomy-vocabulary-5 field-type-taxonomy-term-reference field-label-above clearfix"><h3 class="field-label">Issue number: </h3><ul class="links"><li class="taxonomy-term-reference-0"><a href="/category/issue-number/issue48">issue48</a></li></ul></div><div class="field field-name-taxonomy-vocabulary-6 field-type-taxonomy-term-reference field-label-above clearfix"><h3 class="field-label">Article type: </h3><ul class="links"><li class="taxonomy-term-reference-0"><a href="/category/article-type/feature-article">feature article</a></li></ul></div><div class="field field-name-taxonomy-vocabulary-4 field-type-taxonomy-term-reference field-label-above clearfix"><h3 class="field-label">Buzz: </h3><ul class="links"><li class="taxonomy-term-reference-0"><a href="/category/buzz/data">data</a></li><li class="taxonomy-term-reference-1"><a href="/category/buzz/software">software</a></li><li class="taxonomy-term-reference-2"><a href="/category/buzz/java">java</a></li><li class="taxonomy-term-reference-3"><a href="/category/buzz/framework">framework</a></li><li class="taxonomy-term-reference-4"><a href="/category/buzz/semantic-web">semantic web</a></li><li class="taxonomy-term-reference-5"><a href="/category/buzz/open-source">open source</a></li><li class="taxonomy-term-reference-6"><a href="/category/buzz/database">database</a></li><li class="taxonomy-term-reference-7"><a href="/category/buzz/dissemination">dissemination</a></li><li class="taxonomy-term-reference-8"><a href="/category/buzz/web-services">web services</a></li><li class="taxonomy-term-reference-9"><a href="/category/buzz/xml">xml</a></li><li class="taxonomy-term-reference-10"><a href="/category/buzz/digital-library">digital library</a></li><li class="taxonomy-term-reference-11"><a href="/category/buzz/archives">archives</a></li><li class="taxonomy-term-reference-12"><a href="/category/buzz/metadata">metadata</a></li><li class="taxonomy-term-reference-13"><a href="/category/buzz/dublin-core">dublin core</a></li><li class="taxonomy-term-reference-14"><a href="/taxonomy/term/138">identifier</a></li><li class="taxonomy-term-reference-15"><a href="/taxonomy/term/139">vocabularies</a></li><li class="taxonomy-term-reference-16"><a href="/category/buzz/repositories">repositories</a></li><li class="taxonomy-term-reference-17"><a href="/taxonomy/term/167">eprints</a></li><li class="taxonomy-term-reference-18"><a href="/taxonomy/term/171">video</a></li><li class="taxonomy-term-reference-19"><a href="/taxonomy/term/176">preservation</a></li><li class="taxonomy-term-reference-20"><a href="/taxonomy/term/1175">bibliographic data</a></li><li class="taxonomy-term-reference-21"><a href="/taxonomy/term/1179">graphics</a></li><li class="taxonomy-term-reference-22"><a href="/taxonomy/term/1249">operating system</a></li><li class="taxonomy-term-reference-23"><a href="/taxonomy/term/1254">ascii</a></li><li class="taxonomy-term-reference-24"><a href="/taxonomy/term/1353">digital preservation</a></li><li class="taxonomy-term-reference-25"><a href="/taxonomy/term/1378">knowledge base</a></li><li class="taxonomy-term-reference-26"><a href="/taxonomy/term/1493">digital media</a></li><li class="taxonomy-term-reference-27"><a href="/taxonomy/term/1530">file format</a></li><li class="taxonomy-term-reference-28"><a href="/taxonomy/term/1535">data set</a></li><li class="taxonomy-term-reference-29"><a href="/taxonomy/term/1612">document format</a></li><li class="taxonomy-term-reference-30"><a href="/taxonomy/term/2050">digital repositories</a></li><li class="taxonomy-term-reference-31"><a href="/taxonomy/term/2065">soap</a></li><li class="taxonomy-term-reference-32"><a href="/taxonomy/term/2669">digital archive</a></li><li class="taxonomy-term-reference-33"><a href="/taxonomy/term/4253">wsdl</a></li><li class="taxonomy-term-reference-34"><a href="/taxonomy/term/4257">uddi</a></li><li class="taxonomy-term-reference-35"><a href="/taxonomy/term/4258">service registry</a></li><li class="taxonomy-term-reference-36"><a href="/taxonomy/term/4376">drm</a></li><li class="taxonomy-term-reference-37"><a href="/taxonomy/term/4433">digital curation</a></li><li class="taxonomy-term-reference-38"><a href="/taxonomy/term/4461">soa</a></li><li class="taxonomy-term-reference-39"><a href="/taxonomy/term/5043">dspace</a></li><li class="taxonomy-term-reference-40"><a href="/taxonomy/term/5207">wayback machine</a></li><li class="taxonomy-term-reference-41"><a href="/taxonomy/term/6809">service oriented architecture</a></li><li class="taxonomy-term-reference-42"><a href="/taxonomy/term/7750">google trends</a></li><li class="taxonomy-term-reference-43"><a href="/taxonomy/term/8490">fedora commons</a></li><li class="taxonomy-term-reference-44"><a href="/taxonomy/term/12122">licence</a></li><li class="taxonomy-term-reference-45"><a href="/taxonomy/term/12362">controlled vocabularies</a></li><li class="taxonomy-term-reference-46"><a href="/taxonomy/term/13703">droid</a></li><li class="taxonomy-term-reference-47"><a href="/taxonomy/term/13874">interoperability</a></li><li class="taxonomy-term-reference-48"><a href="/taxonomy/term/13898">preservation metadata</a></li><li class="taxonomy-term-reference-49"><a href="/taxonomy/term/13927">digital record object identification</a></li><li class="taxonomy-term-reference-50"><a href="/taxonomy/term/15219">algorithm</a></li><li class="taxonomy-term-reference-51"><a href="/taxonomy/term/15552">taxonomy</a></li><li class="taxonomy-term-reference-52"><a href="/taxonomy/term/15595">research</a></li><li class="taxonomy-term-reference-53"><a href="/taxonomy/term/15864">standards</a></li><li class="taxonomy-term-reference-54"><a href="/taxonomy/term/16133">jstor</a></li></ul></div><div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above clearfix"><h3 class="field-label">Authors: </h3><ul class="links"><li class="taxonomy-term-reference-0"><a href="/category/authors/miguel-ferreira">miguel ferreira</a></li><li class="taxonomy-term-reference-1"><a href="/category/authors/ana-alice-baptista">ana alice baptista</a></li><li class="taxonomy-term-reference-2"><a href="/category/authors/jose-carlos-ramalho">jose carlos ramalho</a></li></ul></div><div class="field field-name-field-pub-datestamp-article field-type-datestamp field-label-inline clearfix"><div class="field-label">Date published:&nbsp;</div><div class="field-items"><div class="field-item even"><span class="date-display-single">Sun, 07/30/2006</span></div></div></div><div class="field field-name-field-issue-number-article field-type-text field-label-hidden"><div class="field-items"><div class="field-item even">Issue 48</div></div></div><div class="field field-name-field-guid-article field-type-text field-label-hidden"><div class="field-items"><div class="field-item even">issue48_ferreira_et_al</div></div></div><div class="field field-name-field-pub-url-article field-type-text field-label-hidden"><div class="field-items"><div class="field-item even">http://www.ariadne.ac.uk/issue48/ferreira-et-al/</div></div></div><div class="field field-name-field-copyright-article field-type-text-long field-label-hidden"><div class="field-items"><div class="field-item even"><p>This article has been published under copyright; please see our <a href="/about/copyright">access terms and copyright</a> guidance regarding use of content from this article. See also our explanations of <a href="/citations">how to cite <em>Ariadne</em> articles</a> for examples of bibliographic format.</p>
</div></div></div>Sat, 29 Jul 2006 23:00:00 +0000editor1254 at http://www.ariadne.ac.uk