<?xml version="1.0"?>
+<!DOCTYPE work-package SYSTEM "work-package.dtd">
+
<work-package number="5">
<name>Distribution</name>
<begin>Month 18</begin>
<description>
<p>The work is articulated in three, conceptually sequential
tasks:</p>
- <dl>
- <dt>T5.1</dt>
- <dd>Architectural Design of the Distribution Model. The big
+ <tasks>
+ <task name="T5.1">
+ <p>Architectural Design of the Distribution Model. 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>
mapping to Uniform Resource Locators, and the integration
of databases in the distribution model. The final aim is
to have a <I>phisically</I> distributed library with a
- single <I>logical</I> view.</dd>
-
- <dt>T5.2</dt>
- <dd>Prototype implementation. First prototyping implementation
- of the distribution layer.</dd>
-
- <dt>T5.3</dt>
- <dd>Integration with the Consultation Engine. First
+ single <I>logical</I> view.</p>
+ </task>
+ <task name="T5.2">
+ <p>Prototype implementation. First prototyping implementation
+ of the distribution layer.</p>
+ </task>
+ <task name="T5.3">
+ <p>Integration with the Consultation Engine. First
implementation of the library as a distributed repository.
Distribution should be completely transparent to users of
- the Consultation Engine.</dd>
- </dl>
+ the Consultation Engine.</p>
+ </task>
+ </tasks>
</description>
<deliverable file="D5.a"/>
<deliverable file="D5.b"/>
- <milestone>
+ <milestones>
<p>The main milestone is the release of the advanced MOWGLI
prototype, for the fourth meeting of the project, at month
24. The advanced prototype will integrate the previous one
with the new distribution facilities offered by the
distribution layer.</p>
- </milestone>
+ </milestones>
</work-package>
<?xml version="1.0"?>
+<!DOCTYPE work-package SYSTEM "work-package.dtd">
+
<work-package number="7">
<name>Information Dissemination and Exploitation</name>
<begin>Month 3</begin>
<deliverable file="D7.b"/>
<deliverable>Scientific Publications on professional journals
and conference proceedings.</deliverable>
- <milestone>
+ <milestones>
<p>Criteria for evaluating MOWGLI's dissemination and its
technological impact will be detailed in the Dissemination
and use Plan. The Project Dissemination & Exploitation
Committee will be in charge to monitor the state of
advancement of the Project according to these criteria.</p>
- </milestone>
+ </milestones>
</work-package>
<?xml version="1.0"?>
+<!DOCTYPE work-package SYSTEM "work-package.dtd">
+
<work-package number="4">
<name>Interfaces</name>
<begin>Month 3</begin>
</objectives>
<description>
<p>The work is organised in the following tasks:</p>
- <dl>
- <dt>T4.1</dt>
- <dd>MathML rendering/browsing engines. Our privileged
+ <tasks>
+ <task name="T4.1">
+ <p>MathML rendering/browsing engines. 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).</dd>
-
- <dt>T4.2</dt>
- <dd>Consultation Engine (archiving, searching and retrieving).
+ prototype).</p>
+ </task>
+ <task name="T4.2">
+ <p>Consultation Engine (archiving, searching and retrieving).
The task is devoted to the architectural design and
implementation of the main functionalities for the
- consultation and the management of the library.</dd>
-
- <dt>T4.3</dt>
- <dd>Assisted Annotation. This cover an additional
+ consultation and the management of the library.</p>
+ </task>
+ <task name="T4.3">
+ <p>Assisted Annotation. This cover an additional
functionality of the interface, aimed to support the user
in the process of annotating a proof in natural
- language.</dd>
-
- <dt>T4.4</dt>
- <dd>LaTeX-based authoring tool. A tool supporting automatic
+ language.</p>
+ </task>
+ <task name="T4.4">
+ <p>LaTeX-based authoring tool. A tool supporting automatic
generation of Content-MathML from a suitably
- (macro-)enriched version of LaTeX.</dd>
- </dl>
+ (macro-)enriched version of LaTeX.</p>
+ </task>
+ </tasks>
</description>
<deliverable file="D4.a"/>
<deliverable file="D4.b"/>
<deliverable file="D4.c"/>
<deliverable file="D4.d"/>
<deliverable file="D4.e"/>
- <milestone>
+ <milestones>
<p>The main milestone is the release of the first MOWGLI
prototype, at month 18.</p>
- </milestone>
+ </milestones>
</work-package>
<?xml version="1.0"?>
+<!DOCTYPE work-package SYSTEM "work-package.dtd">
+
<work-package number="3">
<name>Metadata</name>
<begin>Month 6</begin>
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 name="T3.1">
+ <p>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
+ library.</p>
+ </task>
+ <task name="T3.2">
+ <p>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 Framework of W3C.</p>
+ </task>
+ </tasks>
</description>
<deliverable file="D3.a"/>
<deliverable file="D3.b"/>
- <milestone>
+ <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>
<?xml version="1.0"?>
+<!DOCTYPE work-package SYSTEM "work-package.dtd">
+
<work-package number="0">
<name>Project Management</name>
<begin>Month 0</begin>
<deliverable file="D0.b"/>
<deliverable file="D0.c"/>
<deliverable file="D0.d"/>
- <milestone>
+ <milestones>
<p>Main milestones are the periodic meetings, at month 6, 12,
20, 24, 30.</p>
- </milestone>
+ </milestones>
</work-package>
<?xml version="1.0"?>
+<!DOCTYPE work-package SYSTEM "work-package.dtd">
+
<work-package number="1">
<name>Requirement Analysis</name>
<begin>Month 0</begin>
<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 name="T1.1">
+ <p>Mathematics and the Web. State of the art, standards and
+ tools.</p>
+ </task>
+ <task name="T1.2">
+ <p>Structured and Formal Mathematics. 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 name="T1.3">
+ <p>Metadata. 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 name="T1.4">
+ <p>Searching and Retrieving. State of the art, use cases and
+ application scenarios.</p>
+ </task>
+ <task name="T1.5">
+ <p>Distribution. Distributed document repositories and
+ peer-to-peer interoperability.</p>
+ </task>
+ <task name="T1.6">
+ <p>Document Authoring. 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
<deliverable file="D1.a"/>
<deliverable file="D1.b"/>
<deliverable file="D1.c"/>
- <milestone>
+ <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>
<?xml version="1.0"?>
+<!DOCTYPE work-package SYSTEM "work-package.dtd">
+
<work-package number="6">
<name>Testing and Validation</name>
<begin>Month 12</begin>
<p>Large scale testing and validation will start after the
release of the first MOWGLI prototype, at month 18. We
shall consider three main validation tests:</p>
- <dl>
- <dt>T6.1</dt>
- <dd>Education. Full development of a fragment of the library
+ <tasks>
+ <task name="T6.1">
+ <p>Education. Full development of a fragment of the library
covering a typical undergraduate course in algebra of
- analysis.</dd>
-
- <dt>T6.2</dt>
- <dd>Certified code. The aim is to be able to present the
+ analysis.</p>
+ </task>
+ <task name="T6.2">
+ <p>Certified code. 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.</dd>
-
- <dt>T6.3</dt>
- <dd>Electronic Publishing. The aim is to test the LaTeX-based
+ in accordance with the Common Criteria standard.</p>
+ </task>
+ <task name="T6.3">
+ <p>Electronic Publishing. 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.</dd>
- </dl>
+ content markup in journal articles.</p>
+ </task>
+ </tasks>
</description>
<deliverable file="D6.a"/>
<deliverable file="D6.b"/>
<deliverable file="D6.c"/>
<deliverable file="D6.d"/>
- <milestone>
+ <milestones>
<p>We expect a lot of feed-back during this phase, that will
be taken into account for the definition of the advanced and
final versions of the MOWGLI prototype.</p>
- </milestone>
+ </milestones>
</work-package>
<?xml version="1.0"?>
+<!DOCTYPE work-package SYSTEM "work-package.dtd">
+
<work-package number="2">
<name>Transformation</name>
<begin>Month 0</begin>
</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"/>
<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,
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>
--- /dev/null
+<?xml version="1.0" encoding="iso-8859-1"?>
+
+<!ELEMENT work-package (name,begin,end,person-month+,objectives,description,
+ deliverable*,milestones)>
+<!ATTLIST work-package
+ number CDATA #REQUIRED>
+
+<!ELEMENT name (#PCDATA)>
+
+<!ELEMENT begin (#PCDATA)>
+
+<!ELEMENT end (#PCDATA)>
+
+<!ELEMENT person-month EMPTY>
+<!ATTLIST person-month
+ participant CDATA #REQUIRED
+ number CDATA #REQUIRED>
+
+<!ELEMENT objectives (p|dl|ul)*>
+
+<!ELEMENT description ((p|dl|ul)*,tasks?,(p|dl|ul)*)>
+
+<!ELEMENT tasks (task*)>
+
+<!ELEMENT task (p|dl|ul)*>
+<!ATTLIST task
+ name ID #REQUIRED>
+
+<!-- Constraint: the element is empty iff the file attribute is specified -->
+<!ELEMENT deliverable (#PCDATA)>
+<!ATTLIST deliverable
+ file CDATA #IMPLIED>
+
+<!ELEMENT milestones (p|dl|ul)*>
+
+<!-- A subset of XHTML -->
+<!ELEMENT p (#PCDATA|I|a)*>
+<!ELEMENT I (#PCDATA)>
+<!ELEMENT a (#PCDATA)>
+<!ATTLIST a
+ href CDATA #REQUIRED>
+<!ELEMENT dl (dt|dd)+>
+<!ELEMENT dt (#PCDATA)>
+<!ELEMENT dd (#PCDATA)>
+<!ELEMENT ul (li)+>
+<!ELEMENT li (#PCDATA)>
<h2>Objectives:</h2>
<xsl:copy-of select="objectives/*"/>
<h2>Description:</h2>
- <xsl:copy-of select="description/*"/>
+ <xsl:apply-templates select="description/*"/>
<h2>Deliverables:</h2>
<ul>
<xsl:for-each select="deliverable">
<xsl:copy-of select="milestone/*"/>
</xsl:template>
+<xsl:template match="tasks">
+ <dl>
+ <xsl:apply-templates/>
+ </dl>
+</xsl:template>
+
+<xsl:template match="task">
+ <dt><xsl:value-of select="@name"/></dt>
+ <dd>
+ <xsl:copy-of select="*"/>
+ </dd>
+</xsl:template>
+
+<xsl:template name="p|ul|dl">
+ <xsl:copy-of select="."/>
+</xsl:template>
+
</xsl:stylesheet>
projects / helm.git / commitdiff