Better rendering of the work-packages index (the tasks are shown).
<p>The work is articulated in three, conceptually sequential
tasks:</p>
<tasks>
- <task name="T5.1">
- <p>Architectural Design of the Distribution Model. The big
+ <task id="T5.1">
+ <name>Architectural Design of the Distribution Model.</name>
+ <p>The big
issue it to find the right compromise between two opposite
requirements: <I>distribution</I> (in the sense of the
Web: few rules, no central authority) and <I>coherence</I>
to have a <I>phisically</I> distributed library with a
single <I>logical</I> view.</p>
</task>
- <task name="T5.2">
- <p>Prototype implementation. First prototyping implementation
+ <task id="T5.2">
+ <name>Prototype implementation.</name>
+ <p>First prototyping implementation
of the distribution layer.</p>
</task>
- <task name="T5.3">
- <p>Integration with the Consultation Engine. First
+ <task id="T5.3">
+ <name>Integration with the Consultation Engine.</name>
+ <p>First
implementation of the library as a distributed repository.
Distribution should be completely transparent to users of
the Consultation Engine.</p>
<description>
<p>The work is organised in the following tasks:</p>
<tasks>
- <task name="T4.1">
- <p>MathML rendering/browsing engines. Our privileged
+ <task id="T4.1">
+ <name>MathML rendering/browsing engines.</name>
+ <p>Our privileged
rendering language will be MathML. In order to be able to
test the presentational stylesheets,(Task 2.5) we need a
MathML compliant browser, that will be developed as a
part of the project (starting from a previous
prototype).</p>
</task>
- <task name="T4.2">
- <p>Consultation Engine (archiving, searching and retrieving).
- The task is devoted to the architectural design and
+ <task id="T4.2">
+ <name>Consultation Engine (archiving, searching and retrieving).</name>
+ <p>The task is devoted to the architectural design and
implementation of the main functionalities for the
consultation and the management of the library.</p>
</task>
- <task name="T4.3">
- <p>Assisted Annotation. This cover an additional
+ <task id="T4.3">
+ <name>Assisted Annotation.</name>
+ <p>This cover an additional
functionality of the interface, aimed to support the user
in the process of annotating a proof in natural
language.</p>
</task>
- <task name="T4.4">
- <p>LaTeX-based authoring tool. A tool supporting automatic
+ <task id="T4.4">
+ <name>LaTeX-based authoring tool.</name>
+ <p>A tool supporting automatic
generation of Content-MathML from a suitably
(macro-)enriched version of LaTeX.</p>
</task>
archiving, searching and retrieving issues. The work will
be articulated in two main, almost sequential, tasks:</p>
<tasks>
- <task name="T3.1">
- <p>Use, meaning and classification. This task, based on the
+ <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.</p>
</task>
- <task name="T3.2">
- <p>Modelling. This is devoted to the definition of a precise
+ <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.</p>
</task>
to the different basic kind of interactions and manipulation
to be considered, namely:</p>
<tasks>
- <task name="T1.1">
- <p>Mathematics and the Web. State of the art, standards and
+ <task id="T1.1">
+ <name>Mathematics and the Web.</name>
+ <p>State of the art, standards and
tools.</p>
</task>
- <task name="T1.2">
- <p>Structured and Formal Mathematics. Delineation and
+ <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.</p>
</task>
- <task name="T1.3">
- <p>Metadata. Classification and data mining for content-based
+ <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.</p>
</task>
- <task name="T1.4">
- <p>Searching and Retrieving. State of the art, use cases and
+ <task id="T1.4">
+ <name>Searching and Retrieving.</name>
+ <p>State of the art, use cases and
application scenarios.</p>
</task>
- <task name="T1.5">
- <p>Distribution. Distributed document repositories and
+ <task id="T1.5">
+ <name>Distribution.</name>
+ <p>Distributed document repositories and
peer-to-peer interoperability.</p>
</task>
- <task name="T1.6">
- <p>Document Authoring. State of the art, use cases and
+ <task id="T1.6">
+ <name>Document Authoring.</name>
+ <p>State of the art, use cases and
application scenarios.</p>
</task>
</tasks>
release of the first MOWGLI prototype, at month 18. We
shall consider three main validation tests:</p>
<tasks>
- <task name="T6.1">
- <p>Education. Full development of a fragment of the library
+ <task id="T6.1">
+ <name>Education.</name>
+ <p>Full development of a fragment of the library
covering a typical undergraduate course in algebra of
analysis.</p>
</task>
- <task name="T6.2">
- <p>Certified code. The aim is to be able to present the
+ <task id="T6.2">
+ <name>Certified code.</name>
+ <p>The aim is to be able to present the
formalization and the demonstration of some security
properties related to the code embedded into a smart card.
The presentation must be in a format understandable by
the company in charge of the evaluation of the code and
in accordance with the Common Criteria standard.</p>
</task>
- <task name="T6.3">
- <p>Electronic Publishing. The aim is to test the LaTeX-based
+ <task id="T6.3">
+ <name>Electronic Publishing.</name>
+ <p>The aim is to test the LaTeX-based
authoring tool and to demonstrate how an electronic
physics journal benefits from the exploitation of
content markup in journal articles.</p>
<description>
<p>The work package is articulated in the following tasks:</p>
<tasks>
- <task name="T2.1">
- <p>XML exportation. The task is devoted to the translation
+ <task id="T2.1">
+ <name>XML exportation.</name>
+ <p>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).</p>
</task>
- <task name="T2.2">
- <p>Stylesheets to intermediate representation.
- Implementation of a bunch of stylesheets transforming the
+ <task id="T2.2">
+ <name>Stylesheets to intermediate representation.</name>
+ <p>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.</p>
</task>
- <task name="T2.3">
- <p>Proof transformation. Similar to the previous task, but
+ <task id="T2.3">
+ <name>Proof transformation.</name>
+ <p>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.</p>
</task>
- <task name="T2.4">
- <p>Automatic extraction of metadata. Relevant metadata such
+ <task id="T2.4">
+ <name>Automatic extraction of metadata.</name>
+ <p>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
retrieving. The precise list of metadata will be defined
in Work Package 3.</p>
</task>
- <task name="T2.5">
- <p>Presentational Stylesheets. Implementation of a bunch of
+ <task id="T2.5">
+ <name>Presentational Stylesheets.</name>
+ <p>Implementation of a bunch of
stylesheets transforming the intermediate content
representation into a suitable rendering format (MathML
presentation, HTML, etc.)</p>
</task>
- <task name="T2.6">
- <p>Automatic Proof Generation in Natural Language. Similar
+ <task id="T2.6">
+ <name>Automatic Proof Generation in Natural Language.</name>
+ <p>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
<!ELEMENT tasks (task*)>
-<!ELEMENT task (p|dl|ul)*>
+<!ELEMENT task (name,(p|dl|ul)*)>
<!ATTLIST task
- name ID #REQUIRED>
+ id ID #REQUIRED>
<!-- Constraint: the element is empty iff the file attribute is specified -->
<!ELEMENT deliverable (#PCDATA)>
</xsl:for-each>
</ul>
<h2>Milestones and Expected Results:</h2>
- <xsl:copy-of select="milestone/*"/>
+ <xsl:copy-of select="milestones/*"/>
</xsl:template>
<xsl:template match="tasks">
</xsl:template>
<xsl:template match="task">
- <dt><xsl:value-of select="@name"/></dt>
+ <dt>
+ <a name="{@id}"/>
+ <xsl:value-of select="@id"/>
+ <xsl:text> </xsl:text>
+ <xsl:value-of select="name"/>
+ </dt>
<dd>
<xsl:copy-of select="*"/>
</dd>
<xsl:variable name="work-package"
select="document(concat('../xml/work-packages/',@file,'.xml'))/work-package"/>
<tr>
- <td><xsl:value-of select="$work-package/@number"/>.</td>
+ <td valign="top"><xsl:value-of select="$work-package/@number"/>.</td>
<td>
<a href="{@file}.html">
<xsl:value-of select="$work-package/name"/>
</a>
+ <xsl:apply-templates select="$work-package/description/tasks">
+ <xsl:with-param name="url" select="concat(@file,'.html')"/>
+ </xsl:apply-templates>
</td>
</tr>
</xsl:template>
+<xsl:template match="tasks">
+ <xsl:param name="url"/>
+ <ul>
+ <xsl:apply-templates>
+ <xsl:with-param name="url" select="$url"/>
+ </xsl:apply-templates>
+ </ul>
+</xsl:template>
+
+<xsl:template match="task">
+ <xsl:param name="url"/>
+ <li>
+ <a href="{$url}#{@id}">
+ <xsl:value-of select="@id"/>
+ <xsl:text> </xsl:text>
+ <xsl:value-of select="name"/>
+ </a>
+ </li>
+</xsl:template>
+
</xsl:stylesheet>
projects / helm.git / commitdiff