<?xml version="1.0"?>
+<!DOCTYPE work-package SYSTEM "work-package.dtd">
+
<work-package number="3">
<name>Metadata</name>
<begin>Month 6</begin>
<end>Month 21</end>
+ <leader file="dfki/melis"/>
<person-month participant="bologna" number="3"/>
<person-month participant="inria" number="3"/>
<person-month participant="dfki" number="8"/>
main functionalities of the library, and especially for
archiving, searching and retrieving issues. The work will
be articulated in two main, almost sequential, tasks:</p>
- <dl>
- <dt>T3.1</dt>
- <dd>Use, meaning and classification. This task, based on the
+ <tasks>
+ <task id="T3.1">
+ <name>Use, meaning and classification.</name>
+ <p>This task, based on the
previous documents D1 and D2, is aimed to provide a
precise definition and classification of all metadata
required for an effective and efficient management of the
- library.</dd>
-
- <dt>T3.2</dt>
- <dd>Modelling. This is devoted to the definition of a precise
+ library.</p>
+ </task>
+ <task id="T3.2">
+ <name>Modelling.</name>
+ <p>This is devoted to the definition of a precise
markup model. To this aim, we plan to use the Resource
- Description Framework of W3C.</dd>
- </dl>
+ Description Framework of W3C.</p>
+ </task>
+ </tasks>
</description>
- <deliverable file="D3.a"/>
- <deliverable file="D3.b"/>
- <milestone>
+ <deliverable file="metadata/d3a"/>
+ <deliverable file="metadata/d3b"/>
+ <milestones>
<p>The definition of the Metadata model is amain milestone,
since the architectural design and implementation of the
consultation engine (Task 4.2) will be essentially based on
it. Similarly, it is required for Task 2.4 (automatic
extraction of metadata).</p>
- </milestone>
+ </milestones>
</work-package>