Initial commit of the XML/XSLT stuff.

[helm.git] / helm / mowgli / home / xml / work-packages / metadata.xml

diff --git a/helm/mowgli/home/xml/work-packages/metadata.xml b/helm/mowgli/home/xml/work-packages/metadata.xml
new file mode 100644 (file)
index 0000000..911da28
--- /dev/null
+++ b/helm/mowgli/home/xml/work-packages/metadata.xml
@@ -0,0 +1,51 @@
+<?xml version="1.0"?>
+
+<work-package number="3">
+ <name>Metadata</name>
+ <begin>Month 6</begin>
+ <end>Month 21</end>
+ <person-month participant="bologna" number="3"/>
+ <person-month participant="inria" number="3"/>
+ <person-month participant="dfki" number="8"/>
+ <person-month participant="nijmegen" number="3"/>
+ <person-month participant="aei" number="3"/>
+ <person-month participant="trusted-logic" number="0"/>
+ <objectives>
+  <ul>
+   <li>Delineation of the basic intelligence to be considered
+       for encapsulation in metadata, in order to meet the needs
+       delineated during Requirement Analysis (WP1).</li>
+   <li>Definition and Development of a specific Markup Model
+       in RDF.</li>
+  </ul>
+ </objectives>
+ <description>
+  <p>The precise definition of metadata and their actual
+     Markup Model are essential aspects for implementing the
+     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
+       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
+       markup model. To this aim, we plan to use the Resource
+       Description Framework of W3C.</dd>
+  </dl>
+ </description>
+ <deliverable file="D3.a"/>
+ <deliverable file="D3.b"/>
+ <milestone>
+  <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>
+</work-package>