From: Luca Padovani Date: Tue, 19 Feb 2002 16:43:01 +0000 (+0000) Subject: - renamed some files X-Git-Tag: V_0_3_0_debian_8~297 X-Git-Url: http://matita.cs.unibo.it/gitweb/?a=commitdiff_plain;h=f55cd17459171f1f16631cb9301f9c46a7aaebf4;p=helm.git - renamed some files - added links to the home page - changed news on front page --- diff --git a/helm/mowgli/home/html/.cvsignore b/helm/mowgli/home/html/.cvsignore index 8a53bb955..957e5abd7 100644 --- a/helm/mowgli/home/html/.cvsignore +++ b/helm/mowgli/home/html/.cvsignore @@ -2,7 +2,7 @@ home.html index.html menu.html project-management.html -project_summary.html +project-summary.html consortium.html project.html news.html diff --git a/helm/mowgli/home/html/Makefile b/helm/mowgli/home/html/Makefile index 0cdc0faae..0112de5de 100644 --- a/helm/mowgli/home/html/Makefile +++ b/helm/mowgli/home/html/Makefile @@ -47,7 +47,7 @@ DOCUMENTS = \ home.html \ menu.html \ project-management.html \ - project_summary.html \ + project-summary.html \ consortium.html \ project.html \ news.html \ @@ -149,11 +149,13 @@ software/index.html: $(XMLROOT)/software/index.xml \ menu.html: $(TEMPLATESROOT)/menu.html sed s/\@DATE\@/"`date`"/ $< >$@ -project-management.html: $(TEMPLATESROOT)/project-management.html - cp $< $@ +project-management.html: $(TEMPLATESROOT)/project-management.xml \ + $(XSLROOT)/xhtml-content.xsl + $(XSLTP) --param path_to_top "'.'" -o $@ $(XSLROOT)/xhtml-content.xsl $< -project_summary.html: $(TEMPLATESROOT)/project_summary.html - cp $< $@ +project-summary.html: $(TEMPLATESROOT)/project-summary.xml \ + $(XSLROOT)/xhtml-content.xsl + $(XSLTP) --param path_to_top "'.'" -o $@ $(XSLROOT)/xhtml-content.xsl $< people-list.html: $(XSLROOT)/person-entry.xsl $(XSLROOT)/people-list.xsl $(PEOPLE_SOURCE) ( \ diff --git a/helm/mowgli/home/templates/home.html.bot b/helm/mowgli/home/templates/home.html.bot index f4e51f343..e60979863 100644 --- a/helm/mowgli/home/templates/home.html.bot +++ b/helm/mowgli/home/templates/home.html.bot @@ -6,6 +6,8 @@ +
+

diff --git a/helm/mowgli/home/templates/home.html.top b/helm/mowgli/home/templates/home.html.top index cc6605475..062621346 100644 --- a/helm/mowgli/home/templates/home.html.top +++ b/helm/mowgli/home/templates/home.html.top @@ -33,19 +33,28 @@

The World Wide Web is already the largest resource of mathematical knowledge, and its importance will be exponentiated by emerging display - technologies like MathML. However, almost all mathematical documents + technologies like MathML. + However, almost all mathematical documents available on the Web are marked up only for presentation, severely crippling the potentialities for automation, interoperability, sophisticated searching mechanisms, intelligent applications, transformation and processing. The goal of the project is to overcome these limitations, passing form a machine-readable to a machine-understandable representation of the information, and developing - the technological infrastructure for its exploitation. MOWGLI builds on + the technological infrastructure for its exploitation. MoWGLI builds on previous ``standards'' for the management and publishing of mathematical - documents (MathML, OpenMath, OMDoc), integrating them with different XML - technology (XSLT, RDF, ...).

+ documents (MathML, + OpenMath, + OMDoc), + integrating them with different + XML technologies + (XSLT, + RDF, etc).

- Read more... +

Summary
Management

diff --git a/helm/mowgli/home/templates/project-management.html b/helm/mowgli/home/templates/project-management.html deleted file mode 100644 index 6986c9897..000000000 --- a/helm/mowgli/home/templates/project-management.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - Project Management - - - - -

Project Management

The Project management will be assured by the following relevant - roles:

Project Manager
Exploitation manager
Work-package Leaders
Technical Contributors

and by the following Project Bodies:

Project Coordination Committee (PCC)
Project Exploitation Board
Work-package Teams.

Project Manager: The mandate of the Project Manager is - to represent the Project, report to the Commission, monitor - overall performance of the project, ensure accomplishment - of the technical objectives, promote project visibility, - promote dissemination of project results in the relevant international - forums, promote acceptance of project results, administer - project resources and monitor project spending.
Exploitation Manager: S/he will be responsible for coordinating - exploitation activities undertaken by the Project Exploitation Board - (PEB) in close cooperation with the Project Coordination Committee - (PCC).
Work-package Leaders: They are responsible for the performance of - Work-packages, and they must be committed to the Work-package for at - least five man months per year.
Technical Contributors: Technical Contributors are specialised - staff provided by the partners. They could be either people active on - a stable basis into a Work-package, or people who contribute from time - to time on specific tasks related to the work-plan (external - contributors).
Project Coordination Committee: The PCC is chaired by the Project - Manager and constituted by one representative from each Partner, and - is the main decision body of the Consortium. It is in charge - of all formal decisions regarding technical direction of the work, - proper interrelation between Work-packages, - relations with IST Office, policies for promotion of results, - administrative arrangements. In view of minimising management overhead - and project costs, partners providing the Project Manager, - and the Work-packages Leaders are required to appoint the same - person as their official representative in the Project - Coordination Committee.
Project Exploitation Board: The PEB will be chaired by the - Project Exploitation Manager, and composed by the Exploitation - Managers of each partner. It will monitor the state of the art in - the domains of content-based information technologies, W3C activities, - Web publishing, and digital libraries. It will be responsible for - planning the dissemination and exploitation strategies for the - consortium, to be approved by the PCC.
Work-package Teams: They are constituted of the technical contributors. - Each team will be chaired by a Work-package Leader, and it will be in - charge of carrying out the technical work described in Section - \ref{Workpackages}.

- -

Decision Process

Decisions will normally be taken by seeking consensus. However, - after a reasonable amount of time has been allowed to illustrate - and defend of conflicting positions, in order to avoid deadlock - in project operational progress, the approval of two-third majority - of the partners will be sufficient. If the decision being taken - is unacceptable - to partners found in the minority positions, the resolution of the - conflict will be elevated to each partner's higher executive level. - If no resolution is possible, than the standard ``red flag'' procedure - will be used, as a last resort. Either the PCC or the Project Manager - can initiate the conflict resolution procedure.

- -

Information Flow

Information flow within the Project will be ensured by exchange of - internal technical papers, notification of relevant new publications - technologies or standards, and reports from external meetings. - All technical documentation generated by the project should be - exchangeable in electronic format, according to a set of guidelines - to be agreed at project start-up. The project Manager will enforce - adherence to these guidelines. Only strictly formal correspondence - will be exchanged by ordinary mail and telefax. Urgent correspondence - over e-mail will be sent with a request for explicit acknowledgement.

The Coordinating Partner will be responsible to prepare and maintain - a Web page of the project and a CVS repository (also available via Web). - The CVS repository is meant to keep the trace of the overall - progress of the Project, and it will be used by the PCC to monitor - the state of advancement of the work. Each partner periodically - submit reports to the prime contractor, listing all technical - contributions, publications, meeting attendance and other information - which may help in understanding the provided effort and cost figures.

The Project will establish a high quality Web site for internal and - external communications. It will be operational as from one month of - the commencement date and will be maintained during the project duration. - The ``members only'' area will include e.g. all private deliverables, - progress and management reports, and cost statements. The open area will - include - the project presentation as defined in Appendix 2 of the ``Guidelines - for Contract Preparation'' document, all public deliverables, and any - relevant information suggested by the Project Exploitation Board.

- -

Quality Procedures

For all deliverables, the following review procedure - will be adopted: release by the Work-Package Leader, two-week review - period for comments by the PCC, two-week amendment period to incorporate - PCC recommendations, one-week balloting period for approval by the - PCC.

- -

Confidentiality and IPR handling

Matters related to Confidentiality and IPR handling will be defined - in the ``Consortium Agreement''. As regards literature papers - originated from work in the Project, there will be two - categories of papers:

Project Endorsed Publications, requiring notification and approval by - the PCC.
Project-related publications, only requiring notification to - the PCC. They must contain an acknowledgement of support by the - project Consortium and, if required by the PCC, a disclaimer that - the views are not necessarily those of the Consortium.

Concerning possible contributions to Standards, they will be - directly submitted by project members.

- - diff --git a/helm/mowgli/home/templates/project-management.xml b/helm/mowgli/home/templates/project-management.xml new file mode 100644 index 000000000..a8f57814d --- /dev/null +++ b/helm/mowgli/home/templates/project-management.xml @@ -0,0 +1,144 @@ + + + + + Project Management + + +

Project Management

The Project management will be assured by the following relevant + roles:

Project Manager
Exploitation manager
Work-package Leaders
Technical Contributors

and by the following Project Bodies:

Project Coordination Committee (PCC)
Project Exploitation Board
Work-package Teams.

Project Manager: The mandate of the Project Manager is + to represent the Project, report to the Commission, monitor + overall performance of the project, ensure accomplishment + of the technical objectives, promote project visibility, + promote dissemination of project results in the relevant international + forums, promote acceptance of project results, administer + project resources and monitor project spending.
Exploitation Manager: S/he will be responsible for coordinating + exploitation activities undertaken by the Project Exploitation Board + (PEB) in close cooperation with the Project Coordination Committee + (PCC).
Work-package Leaders: They are responsible for the performance of + Work-packages, and they must be committed to the Work-package for at + least five man months per year.
Technical Contributors: Technical Contributors are specialised + staff provided by the partners. They could be either people active on + a stable basis into a Work-package, or people who contribute from time + to time on specific tasks related to the work-plan (external + contributors).
Project Coordination Committee: The PCC is chaired by the Project + Manager and constituted by one representative from each Partner, and + is the main decision body of the Consortium. It is in charge + of all formal decisions regarding technical direction of the work, + proper interrelation between Work-packages, + relations with IST Office, policies for promotion of results, + administrative arrangements. In view of minimising management overhead + and project costs, partners providing the Project Manager, + and the Work-packages Leaders are required to appoint the same + person as their official representative in the Project + Coordination Committee.
Project Exploitation Board: The PEB will be chaired by the + Project Exploitation Manager, and composed by the Exploitation + Managers of each partner. It will monitor the state of the art in + the domains of content-based information technologies, W3C activities, + Web publishing, and digital libraries. It will be responsible for + planning the dissemination and exploitation strategies for the + consortium, to be approved by the PCC.
Work-package Teams: They are constituted of the technical contributors. + Each team will be chaired by a Work-package Leader, and it will be in + charge of carrying out the technical work described in Section + \ref{Workpackages}.

+ +

Decision Process

Decisions will normally be taken by seeking consensus. However, + after a reasonable amount of time has been allowed to illustrate + and defend of conflicting positions, in order to avoid deadlock + in project operational progress, the approval of two-third majority + of the partners will be sufficient. If the decision being taken + is unacceptable + to partners found in the minority positions, the resolution of the + conflict will be elevated to each partner's higher executive level. + If no resolution is possible, than the standard ``red flag'' procedure + will be used, as a last resort. Either the PCC or the Project Manager + can initiate the conflict resolution procedure.

+ +

Information Flow

Information flow within the Project will be ensured by exchange of + internal technical papers, notification of relevant new publications + technologies or standards, and reports from external meetings. + All technical documentation generated by the project should be + exchangeable in electronic format, according to a set of guidelines + to be agreed at project start-up. The project Manager will enforce + adherence to these guidelines. Only strictly formal correspondence + will be exchanged by ordinary mail and telefax. Urgent correspondence + over e-mail will be sent with a request for explicit acknowledgement.

The Coordinating Partner will be responsible to prepare and maintain + a Web page of the project and a CVS repository (also available via Web). + The CVS repository is meant to keep the trace of the overall + progress of the Project, and it will be used by the PCC to monitor + the state of advancement of the work. Each partner periodically + submit reports to the prime contractor, listing all technical + contributions, publications, meeting attendance and other information + which may help in understanding the provided effort and cost figures.

The Project will establish a high quality Web site for internal and + external communications. It will be operational as from one month of + the commencement date and will be maintained during the project duration. + The ``members only'' area will include e.g. all private deliverables, + progress and management reports, and cost statements. The open area will + include + the project presentation as defined in Appendix 2 of the ``Guidelines + for Contract Preparation'' document, all public deliverables, and any + relevant information suggested by the Project Exploitation Board.

+ +

Quality Procedures

For all deliverables, the following review procedure + will be adopted: release by the Work-Package Leader, two-week review + period for comments by the PCC, two-week amendment period to incorporate + PCC recommendations, one-week balloting period for approval by the + PCC.

+ +

Confidentiality and IPR handling

Matters related to Confidentiality and IPR handling will be defined + in the ``Consortium Agreement''. As regards literature papers + originated from work in the Project, there will be two + categories of papers:

Project Endorsed Publications, requiring notification and approval by + the PCC.
Project-related publications, only requiring notification to + the PCC. They must contain an acknowledgement of support by the + project Consortium and, if required by the PCC, a disclaimer that + the views are not necessarily those of the Consortium.

Concerning possible contributions to Standards, they will be + directly submitted by project members.

+ + diff --git a/helm/mowgli/home/templates/project-summary.xml b/helm/mowgli/home/templates/project-summary.xml new file mode 100644 index 000000000..e020a4ec2 --- /dev/null +++ b/helm/mowgli/home/templates/project-summary.xml @@ -0,0 +1,85 @@ + + + + + Project Summary + + +

Project Summary

+ +

Objectives

The World Wide Web is already the largest resource of mathematical + knowledge, and its importance will be exponentiated by emerging display + technologies like MathML. However, almost all mathematical documents + available on the Web are marked up only for presentation, severely + crippling the potentialities for automation, interoperability, + sophisticated searching mechanisms, intelligent applications, + transformation and processing. The goal of the project is to overcome + these limitations, passing form a machine-readable to a + machine-understandable representation of the information, and developing + the technological infrastructure for its exploitation. MOWGLI builds on + previous ``standards'' for the management and publishing of mathematical + documents (MathML, OpenMath, OMDoc), integrating them with different XML + technology (XSLT, RDF, ...).

+ +

Description of Work

The goal of the project is to provide a comprehensive description, from + content to metadata, of a given field of knowledge (in our case + mathematics), in order to enhance its accessibility, exchange and + elaboration via the World Wide Web. MOWGLI will make an essential use of + standard XML technology and aspires to become an example of ``best + practice'' in its use, and a leading project in the new area of the + Semantic Web.

In particular, we shall deeply explore the potentialities of XML in the + following directions:

+ +

Publishing: XML offers sophisticated publishing technologies (Stylesheets, MathML, + SVG, ...) which can be profitably used to solve, in a standard way, the + annoying notational problems that traditionally afflict + content based and machine-understandable encodings of the + information.
Searching and Retrieving: Metadata will play a major role in MOWGLI. New W3C languages such as + the Resource Description Framework or XML Query are likely to produce + major innovative solutions in this field.
Interoperability: Disposing of a common, machine understandable layer is a major and + essential step in this direction.
Distribution: All XML technology is finally aimed to the access of the Web as a + single, distributed resource, with no central authority and few, + simple rules.

+ +

MOWGLI builds on the solid ground already provided by previous European + projects (Such as OpenMAth and Euler) and several XML dialects for the + management of mathematical documents (MathML, OpenMath, OMDoc, ...). + All these languages cover different and orthogonal aspects of the + information; our aim is not to propose a new standard, but to study and + to develop the technological infrastructure required for taking advantage + of the potentialities of all of them.

+ +

Milestones and Expected Results

First MOWGLI prototype (month 18): Supporting browsing, rendering and on-line consultation of large + repositories of (content-based) mathematical knowledge. The translation + from content to presentation will be done via suitable notational + stylesheets.
Advanced MOWGLI prototype (month 24): Supporting distribution, indexing, searching and retrieval (based on a + sophisticated metadata model).
Final MOWGLI prototype (month 30): Result of validation.

+ + + + diff --git a/helm/mowgli/home/templates/project_summary.html b/helm/mowgli/home/templates/project_summary.html deleted file mode 100644 index 1834a868d..000000000 --- a/helm/mowgli/home/templates/project_summary.html +++ /dev/null @@ -1,87 +0,0 @@ - - - - - Project Summary - - - - -

Project Summary

- -

Objectives

The World Wide Web is already the largest resource of mathematical - knowledge, and its importance will be exponentiated by emerging display - technologies like MathML. However, almost all mathematical documents - available on the Web are marked up only for presentation, severely - crippling the potentialities for automation, interoperability, - sophisticated searching mechanisms, intelligent applications, - transformation and processing. The goal of the project is to overcome - these limitations, passing form a machine-readable to a - machine-understandable representation of the information, and developing - the technological infrastructure for its exploitation. MOWGLI builds on - previous ``standards'' for the management and publishing of mathematical - documents (MathML, OpenMath, OMDoc), integrating them with different XML - technology (XSLT, RDF, ...).

- -

Description of Work

The goal of the project is to provide a comprehensive description, from - content to metadata, of a given field of knowledge (in our case - mathematics), in order to enhance its accessibility, exchange and - elaboration via the World Wide Web. MOWGLI will make an essential use of - standard XML technology and aspires to become an example of ``best - practice'' in its use, and a leading project in the new area of the - Semantic Web.

In particular, we shall deeply explore the potentialities of XML in the - following directions:

- -

Publishing: XML offers sophisticated publishing technologies (Stylesheets, MathML, - SVG, ...) which can be profitably used to solve, in a standard way, the - annoying notational problems that traditionally afflict - content based and machine-understandable encodings of the - information.
Searching and Retrieving: Metadata will play a major role in MOWGLI. New W3C languages such as - the Resource Description Framework or XML Query are likely to produce - major innovative solutions in this field.
Interoperability: Disposing of a common, machine understandable layer is a major and - essential step in this direction.
Distribution: All XML technology is finally aimed to the access of the Web as a - single, distributed resource, with no central authority and few, - simple rules.

- -

MOWGLI builds on the solid ground already provided by previous European - projects (Such as OpenMAth and Euler) and several XML dialects for the - management of mathematical documents (MathML, OpenMath, OMDoc, ...). - All these languages cover different and orthogonal aspects of the - information; our aim is not to propose a new standard, but to study and - to develop the technological infrastructure required for taking advantage - of the potentialities of all of them.

- -

Milestones and Expected Results

First MOWGLI prototype (month 18): Supporting browsing, rendering and on-line consultation of large - repositories of (content-based) mathematical knowledge. The translation - from content to presentation will be done via suitable notational - stylesheets.
Advanced MOWGLI prototype (month 24): Supporting distribution, indexing, searching and retrieval (based on a - sophisticated metadata model).
Final MOWGLI prototype (month 30): Result of validation.

- - - diff --git a/helm/mowgli/home/xsl/latest-news.xsl b/helm/mowgli/home/xsl/latest-news.xsl index dbbd9f0d2..29ba8003f 100644 --- a/helm/mowgli/home/xsl/latest-news.xsl +++ b/helm/mowgli/home/xsl/latest-news.xsl @@ -9,7 +9,9 @@ - + + + diff --git a/helm/mowgli/home/xsl/news.xsl b/helm/mowgli/home/xsl/news.xsl index 7ce85ac1a..83c531376 100644 --- a/helm/mowgli/home/xsl/news.xsl +++ b/helm/mowgli/home/xsl/news.xsl @@ -30,6 +30,7 @@ +

@@ -41,7 +42,7 @@

- +