DTD improved (and committed) with new elements "task" and "tasks".

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

diff --git a/helm/mowgli/home/xml/work-packages/transformation.xml b/helm/mowgli/home/xml/work-packages/transformation.xml
index 1cffe28a322733b7450513e0c6d98aa4ad6b0fd5..ac1e6d89c19c875a334c7f8bbb7d5107067c3a44 100644 (file)
--- a/helm/mowgli/home/xml/work-packages/transformation.xml
+++ b/helm/mowgli/home/xml/work-packages/transformation.xml
@@ -1,5 +1,7 @@
 <?xml version="1.0"?>
 
+<!DOCTYPE work-package SYSTEM "work-package.dtd">
+
 <work-package number="2">
  <name>Transformation</name>
  <begin>Month 0</begin>
@@ -25,50 +27,51 @@
  </objectives>
  <description>
   <p>The work package is articulated in the following tasks:</p>
-  <dl>
-   <dt>T2.1</dt>
-   <dd>XML exportation. The task is devoted to the translation
+  <tasks>
+   <task name="T2.1">
+    <p>XML exportation. The task is devoted to the translation
        of the standard library of the COQ Proof assistant into a
        suitable XML dialect, and to the definition of a low-level
        DTD for the terms of the Calculus of Inductive
-       Construction (the logical system used by COQ).</dd>
-
-   <dt>T2.2</dt>
-   <dd>Stylesheets to intermediate representation.
+       Construction (the logical system used by COQ).</p>
+   </task>
+   <task name="T2.2">
+    <p>Stylesheets to intermediate representation.
        Implementation of a bunch of stylesheets transforming the
        low-level logical description of COQ-expressions into a
        ``standard'' intermediate, content-level representation
-       such as MathML content.</dd>
-
-   <dt>T2.3</dt>
-   <dd>Proof transformation. Similar to the previous task, but
+       such as MathML content.</p>
+   </task>
+   <task name="T2.3">
+    <p>Proof transformation. Similar to the previous task, but
        for proofs. The delicate point, here, is the fact that no
        ``standard'' intermediate representation currently exists,
-       and thus it has to be defined.</dd>
-
-   <dt>T2.4</dt>
-   <dd>Automatic extraction of metadata. Relevant metadata such
+       and thus it has to be defined.</p>
+   </task>
+   <task name="T2.4">
+    <p>Automatic extraction of metadata. Relevant metadata such
        as list of identifiers in critical positions inside
        statements can be automatically extracted from the fully
        structured representation of mathematical objects. This
        information can then be exploited for searching and
        retrieving. The precise list of metadata will be defined
-       in Work Package 3.</dd>
-
-   <dt>T2.5</dt>
-   <dd>Presentational Stylesheets. Implementation of a bunch of
+       in Work Package 3.</p>
+   </task>
+   <task name="T2.5">
+    <p>Presentational Stylesheets. Implementation of a bunch of
        stylesheets transforming the intermediate content
        representation into a suitable rendering format (MathML
-       presentation, HTML, etc.)</dd>
-
-   <dt>T2.6</dt>
-   <dd>Automatic Proof Generation in Natural Language. Similar
+       presentation, HTML, etc.)</p>
+   </task>
+   <task name="T2.6">
+    <p>Automatic Proof Generation in Natural Language. Similar
        to the previous task but for proofs. In this case, a fully
        automated approach is unlikely to produce really
        satisfactory results, and the process should be possibly
        integrated with some mechanism for interactive annotation
-       (see Task 4.3).</dd>
-  </dl>
+       (see Task 4.3).</p>
+   </task>
+  </tasks>
  </description>
  <deliverable file="D2.a"/>
  <deliverable file="D2.b"/>
@@ -77,7 +80,7 @@
  <deliverable file="D2.e"/>
  <deliverable file="D2.f"/>
  <deliverable file="D2.g"/>
- <milestone>
+ <milestones>
   <p>The exportation module D2.a. is our first
      milestone: without a large amount of available documents it
      would be impossible to test the transformations. Similarly,
@@ -92,5 +95,5 @@
      particular, for MathML).</p>
   <p>For the end of month 18, we expect to have a first working
      prototype of the whole application.</p>
- </milestone>
+ </milestones>
 </work-package>