...

Commits (2)
 ... ... @@ -12,7 +12,7 @@ \begin{wpdescription} The project will be managed by \site{FAU}, which has extensive experience in administrating and leading EU funded and national projects. The coordinator together with administrating and leading EU funded and national projects. The coordinator, together with the WP leaders, will be responsible for monitoring WP status, coordination of work plan updates and annual internal progress reports. The project management structure and roles of partners in the consortium are presented in Section~\ref{sect:mgt}. ... ... @@ -67,7 +67,7 @@ This task will be led by the coordinating site with minor contributions from all PM=6,wphases=27-36!.66] It is a central aim of the \pn project to set open standards for all three kinds of mathematical data. To maximize the impact of the \pn standard developed in \taskref{foundations}{standard}, we will develop it into an ISO standard. The ISO/IEC JTC 1 Information technology'', which have already standardized base technologies like MathML, and/or the ISO/TC 37 Language and terminology'', which has standardized ontology languages like OntoIOp, are likely venues for this. The committee ISO/IEC JTC 1 Information technology'', which has already standardized base technologies like MathML, and/or the ISO/TC 37 Language and terminology'', which has standardized ontology languages like OntoIOp, are likely venues for this. In this task, we carry out the administrative and political work as well as the work of all necessary revisions necessary to submit our standard. We aim to file the submission at the end of the project duration. ... ... @@ -80,7 +80,7 @@ This submission process will be led by \site{EMS} with minor contributions from PM=6,wphases=24-36!.5] The aim of the \pn project is to kick-start the development of mathematical data and services on the EOSC by standardizing a framework and providing initial datasets and services. After the project will be easy (technically tractable, well-documented, and well-advertised) to extend the EOSC datasets and services. services. After the project it will be easy (technically tractable, well-documented, and well-advertised) to extend the EOSC datasets and services. In fact it will be simpler -- e.g. for Ph.D. students in Mathematics who create mathematical datasets or services -- to integrate them into the \pn framework at EOSC than building/hosting their own. In essence the proposed \pn framework will provide a ... ...
 ... ... @@ -22,7 +22,7 @@ The \textbf{overall structure of the work plan} is very simple and follows immed \item \WPtref{foundations} builds the data representation framework. This includes the standardization of the data formats, the specification of the core APIs (which serve as the foundation for building the services), and legal aspects. \item \WPtref{services} builds the services. This includes both the design and implementation of the software as well as the setup of appropriate hardware and the deployment of the services. This includes both the design and implementation of the software, as well as the setup of appropriate hardware and the deployment of the services. \item \WPtref{cases} seeds our infrastructure by deploying a collection of datasets on it. This includes at least the datasets specified in the respective deliverables but will likely involve more datasets based on feedback from the community. \item \WPtref{dissem} handles all community outreach and advertisement within new user communities. ... ...