<?xml version="1.0"?>
+<!DOCTYPE work-package SYSTEM "work-package.dtd">
+
<work-package number="1">
<name>Requirement Analysis</name>
<begin>Month 0</begin>
<end>Month 6</end>
+ <leader file="nijmegen/geuvers"/>
<person-month participant="bologna" number="3"/>
<person-month participant="inria" number="4"/>
<person-month participant="dfki" number="3"/>
<p>The work plan is naturally organised in subtasks according
to the different basic kind of interactions and manipulation
to be considered, namely:</p>
- <dl>
- <dt>T1.1</dt>
- <dd>Mathematics and the Web. State of the art, standards and
- tools.</dd>
-
- <dt>T1.2</dt>
- <dd>Structured and Formal Mathematics. Delineation and
+ <tasks>
+ <task id="T1.1">
+ <name>Mathematics and the Web.</name>
+ <p>State of the art, standards and
+ tools.</p>
+ </task>
+ <task id="T1.2">
+ <name>Structured and Formal Mathematics.</name>
+ <p>Delineation and
layering of Semantic Components. Requirements for
the interaction with tools for the automation of formal
- reasoning.</dd>
-
- <dt>T1.3</dt>
- <dd>Metadata. Classification and data mining for content-based
+ reasoning.</p>
+ </task>
+ <task id="T1.3">
+ <name>Metadata.</name>
+ <p>Classification and data mining for content-based
mathematical documents, and key architectural guidelines
- for the metadata model.</dd>
-
- <dt>T1.4</dt>
- <dd>Searching and Retrieving. State of the art, use cases and
- application scenarios.</dd>
-
- <dt>T1.5</dt>
- <dd>Distribution. Distributed document repositories and
- peer-to-peer interoperability.</dd>
-
- <dt>T1.6</dt>
- <dd>Document Authoring. State of the art, use cases and
- application scenarios.</dd>
- </dl>
+ for the metadata model.</p>
+ </task>
+ <task id="T1.4">
+ <name>Searching and Retrieving.</name>
+ <p>State of the art, use cases and
+ application scenarios.</p>
+ </task>
+ <task id="T1.5">
+ <name>Distribution.</name>
+ <p>Distributed document repositories and
+ peer-to-peer interoperability.</p>
+ </task>
+ <task id="T1.6">
+ <name>Document Authoring.</name>
+ <p>State of the art, use cases and
+ application scenarios.</p>
+ </task>
+ </tasks>
<p>Part of the activity, covering Tasks T1.1-2-6 should be
concluded within the first three months, with the
preliminary report D1.a. The main aim of this phase is
the Project (month six), when all the reports will be
discussed and approved.</p>
</description>
- <deliverable file="D1.a"/>
- <deliverable file="D1.b"/>
- <deliverable file="D1.c"/>
- <milestone>
+ <deliverable file="requirement-analysis/d1a"/>
+ <deliverable file="requirement-analysis/d1b"/>
+ <deliverable file="requirement-analysis/d1c"/>
+ <milestones>
<p>The preliminary report D1.a is not a realmilestone:
it should be considered as a first internal draft summarising
the main functionalities required by the system and the basic
eventually detailed in D1.b and D1.c, which are real
Milestones, since the rest of the work will be largely
driven by them.</p>
- </milestone>
+ </milestones>
</work-package>