Commit a3391063 authored by Michael Kohlhase's avatar Michael Kohlhase
Browse files

fixing references

parent 0a1ce487
......@@ -40,7 +40,7 @@ Paris Region Systems and ICT Cluster.
\input{CVs/Nicolas.Thiery.tex}
\begin{participant}[type=R,PM=33]{Software Developer}
We will hire a full time experienced software developer to work on
Tasks~\ref{cases}{recorddata}, \taskref{services}{A}, and~\taskref{services}{I}, %longtaskref
Tasks~\taskref{cases}{recorddata}, \taskref{services}{A}, and~\taskref{services}{I}, %longtaskref
under the leadership of Nicolas M. Thi\'ery.
The fellow will have a strong software engineering experience,
......
......@@ -89,7 +89,7 @@ This task will be led by \site{UL}, which has already conducted the survey of da
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{task}[id=lmfdbdata,title=LMFDB Datasets,lead=CHA,partners={PS},PM=15,wphases=6-36!.66]
This task integrates the datasets from LMFDB.
The procedure is essentially the same as for the datasets in \localtaskref{recorddata}. The writing of schema theories will be done in dialog with other members of the management board of the LMFDB, and the systematic processing of the datasets is analogous to \localtaskref{recorddata}. This task is necessary for the full implementation of the service in \taskref{Services}{lmfdbservice} and will also be a show case for future integration of other mathematical datasets.
The procedure is essentially the same as for the datasets in \localtaskref{recorddata}. The writing of schema theories will be done in dialog with other members of the management board of the LMFDB, and the systematic processing of the datasets is analogous to \localtaskref{recorddata}. This task is necessary for the full implementation of the service in \taskref{services}{lmfdbservice} and will also be a show case for future integration of other mathematical datasets.
This task will be led by \site{CHA}, whose PI is a member of the LMFDB management board and has contributed some of the LMFDB datasets.
LMFDB heavily uses SageMath, and \site{PS} will contribute SageMath to simplify the work.
......@@ -123,7 +123,7 @@ we need to create user interfaces that allow for data curation,
facilitating the involvement of the mathematical community (starting
with $> 7,000$ zbMATH reviewers) into the editorial process.
The analysis of these datasets also allow to develop standards for symbolic data within the FORCE11 community in \taskref{DisseminationCommunityBuilding}{outreachems}.
The analysis of these datasets also allow to develop standards for symbolic data within the FORCE11 community in \taskref{dissem}{outreachems}.
This task will be led by \site{FIZ}, which creates and maintains the
dataset.
......
......@@ -85,7 +85,7 @@ itself. This is most apparent for provenance data. An example of this is symboli
where the provenance for a single datum (e.g. in the form of a theorem or lemma) is given by a proof and its
metadata, up to whole libraries, gigabytes in size, that are generated from earlier versions by knowledge compilation.
These enhanced metadata will allow to employ functions of like MathHub by \site{FAU} or RADAR by \site{FIZ} and facilitate the development of the services in \taskref{Services}{A}.
These enhanced metadata will allow to employ functions of like MathHub by \site{FAU} or RADAR by \site{FIZ} and facilitate the development of the services in \taskref{services}{A}.
This task will be led by \site{FIZ}, which has extensive experience due to their development and maintenance of the zbMATH service.
\site{FAU} will provide feedback regarding usability and integration into the overall standard.
......
......@@ -46,7 +46,7 @@ But the various representations are non-interoperable, and the datasets therefor
\noindent\textbf{Open Source/Data Ethos}: The mathematical community predominantly shares the ethos of open access to publications, software (including source code), and datasets. In fact, all of the examples above are either fully open, partly open, or are currently in the process of opening up the data/software further.
For mathematical software, the Open Source ethos has been established already for more than 50 years in subroutine libraries such as LAPACK, % SCALAPACK, SLICOT, or MUMPS
which are produced according to a widely accepted documentation and implementation standard and are at the core of almost all successful commercial and non-commercial software packages including MATLAB~\cite{MATLAB:on} and SageMath \cite{sagemath:on}.
which are produced according to a widely accepted documentation and implementation standard and are at the core of almost all successful commercial and non-commercial software packages including MATLAB~\cite{MATLAB:on} and SageMath \cite{SageMath:on}.
Throughout this project we will reuse and extend open source code, and \TheProject will benefit from future open source contributions during and beyond the lifetime of the project. Moreover, the \pn project will follow the example of the H2020 OpenDreamKit project and conduct all of its development openly in public repositories. In fact like the OpenDreamKit project, which \pn follows up on, the \pn proposal was developed publicly (on \url{https://gl.kwarc.info/mathhub/data-proposal/}).
Thanks to this by-users-for-users model, \TheProject will be steered by the actual needs of the community.
......
No preview for this file type
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment