Wf4Ever architecture prescribes interfaces to functionalities expected to be available in a scientific workflow preservation infrastructure. In the first phase of the architecture definition, we have identified a number of these functionalities, and have grouped them into functional entities representing areas addressed by such preservation infrastructure. This work has been done following a continuous design cycle that co-evolves with the implementation of prototype and tools, driven by categorized requirements as explained in Section 1.1, and drawing from experiences in workflow lifecycle management, social networks, semantic web and digital library communities. In defining these entities, we also aim at aiding designers of future systems by providing a more precise set of terms and concepts to use as reference model, and to enable easier alignment of our architecture with standards like the OAIS reference model.
We have identified four functional entities as depicted in the figure below. These entities can interact with each other as illustrated by the arrows in the figure.
Access & Usage provides functionalities that support consumers (users, agents) to determine the existence, description, location and availability of stored Research Objects (RO) resources; enable consumers to request and receive RO resources, and allow the edition, creation and annotation of RO resources. . In general, these are user-level functionalities.
Data Management & Analysis provides functionalities for generating, maintaining and accessing added-value data of available RO resources. This data includes quality-related information of the RO resources, such stability and completeness, recommendations, collaboration aspects and transformation to visualization formats. In general, these are extensional-level functionalities which provide added-value capacities to the preservation infrastructure.
Storage provides functionalities for the storage, maintenance and retrieval of RO resources, i.e., add resources to permanent storage, managing internal data models, maintaining the RO resources associated semantic metadata, basic versioning mechanisms, etc., and making these resources available for retrieval. In general these are part of the foundational-level functionalities, providing basic capacities to the preservation infrastructure, concerned mainly with the static aspects of preservation.
Lifecycle provides functionalities to support the dynamic nature of RO resources. They include the execution of RO resources, such as workflows, for living ROs, the publication of RO resources, including the management of versions and curation activities, or the archival of ROs, when the lifecycle reaches its end. In general these are part of the foundational-level functionalities, providing basic capacities to the preservation infrastructure, concerned mainly with the dynamic aspects of preservation.
A complete description of these functionalities are described in D1.3v1 and its addendum.
*Also a description of the main services currently implemented from the architecture is needed. If they are already provided under Wf4Ever toolkit, then a link is sufficient..