3 <!DOCTYPE work-packages [
4 <!ELEMENT work-packages (work-package+)>
6 <!ELEMENT work-package EMPTY>
12 <work-package file="project-management"/>
13 <work-package file="requirement-analysis"/>
14 <work-package file="transformation"/>
15 <work-package file="metadata"/>
16 <work-package file="interfaces"/>
17 <work-package file="distribution"/>
18 <work-package file="testing-and-validation"/>
19 <work-package file="information-dissemination-and-exploitation"/>
21 <p>The previous work packages are not strictly sequential.</p>
22 <p> WP1 should be reasonably short; apart from a few topics requiring a
23 deeper analysis (Tasks 1.3-5), this phase is essentially meant to rapidly
24 reach a good level of inter-operability among the different sites.</p>
25 <p>Most part of the work is based on the possibility to have at our
26 disposal, and as soon as possible, large collections of documents encoded
27 with semantic markup. One strategy is the import of material (e.g.
28 journal articles) written in LaTeX. The development of a suitable LaTeX
29 based authoring tool (Task 4.4) will need to begin immediately, as an
30 appropriate semantic encoding in LaTeX has to be developed first.
31 The delivery of the first prototype of the authoring tool is scheduled
33 <p>A more rapid way to get meaningful repositories of fully structured
34 mathematical knowledge is by exporting them from the available
35 libraries of Logical Frameworks and Proof Assistants (Task 2.1).
36 The intelligence contained in the exported XML files should reflect the
38 in the previous work package, requiring a deep analysis of the markup
39 model. After six months from the beginning of the project we plan to have
40 a first prototype of the Exportation Module and a first draft of the
41 Document Type Descriptor for thelow, logical level. This is our first
43 <p>At this point we may start the study of the intermediate format of the
44 information, and the implementation of the stylesheets performing the
45 transformation (tasks T2.2-3). This part of the work is expected to be
46 essentially completed after one year (second Milestone). Since a strong
47 feedback is expectedwith presentational issues, we plan to begin the
48 development of presentational stylesheets around month 9. In turn, the
49 need of rapidly have at our disposal good presentational engines suggests
50 to begin their development as soon as possible (task 4.1).</p>
51 <p>In parallel with these transformation issues, we shall start the study and
52 classification of metadata, and their concrete modelling.</p>
53 <p>Summing up, at the end of first year we plan to have:</p>
55 <li>a formal Document Type Descriptor of the intermediate level;</li>
56 <li>a bunch of stylesheet performing the transformation to intermediate
57 representation, both for formulae and proofs;</li>
58 <li>a detailed report on metadata;</li>
59 <li>a first prototype model of metadata (in RDF format);</li>
60 <li>a prototype MathML-viewer.</li>
62 <p>During the first half of second year we shall perform, in parallel, four
65 <li>study and development of presentational stylesheets, both for expressions
66 and proofs, and automatic extraction of metadata (tasks T2.4-6).</li>
67 <li>architectural design and implementation of the consultation engine (task
68 T4.2, requiring the metadata model), and of the functionalities for
69 assisted annotation in natural language of the documents (task T4.3,
70 requiring both the MathML-viewer, and a detailed description of the
71 intermediate level).</li>
72 <li>overall architectural design and first prototype implementation of the
73 distribution model (task T5.1-T5.2).</li>
74 <li>finalize the first prototype of a LaTeX based authoring tool
77 <p>The second half of the second year is devoted to the completion of the
78 previous tasks, and to their integration inside a single, compound
79 application. Around this time we shall also start a detailed validation
80 of the application, according to three pilot applications:</p>
82 <li>Formalisation of a full undergraduate course in algebra or analysis for
83 didactical purposes.</li>
84 <li>Formalization of (part of) the process of loading, verifying and
85 executing an applet into a smart card. This application will provide
86 a case study close to both information technology (IT) industry and
87 Computer Science research, where the presentation and layout needs are
88 not exactly the same as in Mathematics. The example concerns the
89 representation of different abstract state machines, transition systems,
90 typing calculus, and program code. Such concepts are pragmatic use cases
91 of the formal concepts that usually appears in security evaluations of
92 IT products and Computer Science articles.</li>
93 <li>Make maximal use of content marked-up articles in a solely
94 electronic scientific physics journal. This will allow us to demonstrate
95 the benefits of content mark-up for search, retrieval, and re-use of
96 mathematical content, and user customisable content presentation.
97 Several articles will be processed to test scope, functionality, and
98 user friendliness of the authoring tool developed in Task 4.4. The tool
99 will be refined and the mathematical semantics covered extended. The
100 suite of articles will be used to show benefits of automated
101 annotation and cross-linking between related mathematical concepts.</li>
103 <p>The last six months are mainly devoted to testing, debugging, validation,
104 dissemination of results and exploitation plans.</p>