compared with
Current by Markus Plangg
on Sep 05, 2012 15:08.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View Page History
{note} This is a draft document {note}
From the point of view of PW a component can be a migration tool, characterization tool, or a QA tool. The implementation specific details for these components are not relevant to PW. However, new components could be defined by combining existing tools within a Taverna workflow. These workflows should also be available on the component catalogue. 
From the point of view of PW components include migration actions, characterization and quality assurance as well as a combination of components. Components must provide a common interface and must be available on the component catalogue. An Overview of goals and requirements can be found in the document [^GoalsandrequirementsforPTfromtheperspectiveofPW.pdf].

[Component interfaces|SP:Preservation Component Profiles] and lookup were discussed at the [Registry Workshop at AIT|SP:Preservation Components, Workflows, Planning and Platform integration].


h2. Specific Feature Requirements 


{note}
These requirements were refined in [^GoalsandrequirementsforPTfromtheperspectiveofPW.pdf] and further discussed at the [Registry Workshop at AIT|SP:Preservation Components, Workflows, Planning and Platform integration]

{note}

h3. List of all components