From 47bb31cc5d3577ba65f55c1e76188cfad50e8282 Mon Sep 17 00:00:00 2001
From: Michael Kohlhase <michael.kohlhase@fau.de>
Date: Tue, 29 Jan 2019 10:30:48 +0100
Subject: [PATCH] integrating the rest of Volker's comments

---
 Proposal/WorkPackages/Management.tex             |  2 +-
 Proposal/ambition.tex                            | 12 +++++-------
 Proposal/impact.tex                              |  4 ++--
 Proposal/management_structure_and_procedures.tex |  3 +--
 lib/kbibs/extpubs.bib                            |  7 ++++++-
 5 files changed, 15 insertions(+), 13 deletions(-)

diff --git a/Proposal/WorkPackages/Management.tex b/Proposal/WorkPackages/Management.tex
index f0d824a..7d8512a 100644
--- a/Proposal/WorkPackages/Management.tex
+++ b/Proposal/WorkPackages/Management.tex
@@ -43,7 +43,7 @@ This task will be led by the coordinating site with minor contributions from all
   lead=FAU,PM=6,partners={CAE,CHA,EMS,FIZ,UL,PS}]
   A quality assurance plan will be established to ensure coherent and sufficient quality of the work and results.
   The plan will be developed by \site{FAU}, involving all partners, and will be followed up regularly.
-  In addition, the project coordinator with support from the coordination team and quality review board will establish and review annually a risk management plan and self-assessment to ensure that technical barriers / potential risks are identified and corrective measures are put into place on time (\delivref{management}{ipr}).
+  In addition, the CT with support from the SC will establish and review annually a risk management plan and self-assessment to ensure that technical barriers / potential risks are identified and corrective measures are put into place on time (\delivref{management}{ipr}).
   
   This task will be led by the coordinating site with minor contributions from all partners.
 \end{task}
diff --git a/Proposal/ambition.tex b/Proposal/ambition.tex
index 1da0a28..ae16468 100644
--- a/Proposal/ambition.tex
+++ b/Proposal/ambition.tex
@@ -55,7 +55,7 @@ Systems are connected by a MitM mediator system, which reads the interface speci
 This mediator is built on top of and inherits most of the functionality from the MMT API~\cite{mmt:repo:on}, an open knowledge management system for symbolic data developed at \site{FAU}. 
 
 Figure~\ref{fig:mitm} shows a workflow and mathematical use case that makes use of the flexible delegation of sub-problems to external systems, which is not possible in SageMath alone.
-Additionally, this MitM workflows can be set up just as easily for systems, e.g., where a GAP user delegates to SageMath and PARI/GP~\cite{KohMuePfe:kbimss17}. 
+Additionally, this MitM workflows can be set up just as easily with other systems as the master, e.g., where a user working in the computer algebra system GAP~\cite{GAP:on} delegates to SageMath and the number theory library PARI/GP~\cite{PARIGP:on}; see~\cite{KohMuePfe:kbimss17} for details. 
 
 In addition to computation systems and as a major inspiration for the \TheProject proposal, MitM also allows integrating mathematical \emph{databases}.
 Here the MitM mediator directly connects to the database-level API and automatically decodes the encoded concrete mathematical data into mathematical objects via semantic annotations to the database tables.
@@ -85,7 +85,7 @@ can have different mechanisms for sharing or locating models or libraries.
 All of these systems tend to have open licenses for both the source code and the library.
 While FAIR sharing within each system is quite easy (except that search is notoriously difficult), the sharing across languages is extremely difficult and often prohibitively expensive in practice.
 MathML \cite{CarlisleEd:MathML3:on} and OMDoc \cite{Kohlhase:OMDoc1.2} are XML-based standardized representation languages that were developed in order to overcome this segregation into disconnected islands of FAIRness.
-MathML in particular was sanctioned by the W3C and is partially included into the HTML5 standard.
+MathML in particular was sanctioned by the World Wide Web Consortium (W3C) and is partially included into the HTML5 standard.
 It has two sub-languages: presentation MathML for the layout in browsers etc. and content MathML for the meaning of formulas; the latter is based on the OpenMath standard~\cite{BusCapCar:2oms04}, which represents symbolic data in the form of operator trees using function application, variables, binding, and symbols.
 However, practical adoption has been limited due to the high cost and lack of incentives for researchers to make their symbolic data interoperable across language boundaries.
 
@@ -159,9 +159,7 @@ Large collaborations (e.g., the Classification of Finite Simple Groups or the Po
 Therefore, most datasets are collected and most services are provided by individual mathematicians or small communities and are not archived systematically.
 
 This is connected to a financial challenge: even top researchers in mathematics have little research funding that could be devoted to hosting large databases and services.
-That precludes them from the computing resources necessary to host TRL 8 services
-
-This shows the need for and potential of an EOSC-like initiative.
+That precludes them from the computing resources necessary to host TRL 8 services, which shows the need for and potential of an EOSC-like initiative.
 But so far only one mathematical dataset has been published via the EOSC infrastructure --- Jukka Kohonen's collection of lattices.
 In conversations with him and others, we learned that this is primarily due to the lack of awareness of and the lack of semantics-aware services provided by the EOSC infrastructure.
 
@@ -170,8 +168,8 @@ Mathematics is traditionally performed in journal articles.
 Even though there is a growing mathematical Open Source community, mathematicians receive little reputation and career benefit from maintaining services and sharing data.
 Consequently, data sharing is often only an afterthought, and mathematicians publish datasets at whatever site makes sharing easiest.
 Sometimes datasets are not even published at all.
-For example, Kohonen told us his dataset included one more object than a dataset computed by colleagues in previous work.
-But due to the lack of services that make accessibility and reusability easy, he could not easily determine which of the two datasets is in error.
+For example, Kohonen's dataset includes one more object than a dataset computed by colleagues in previous work.
+But due to the lack of services that make accessibility and reusability easy, it was impossible to determine which of the two datasets is in error.
 
 Mathematicians also require very high standards for the reliability of the data.
 They expect every listed object to be 100\% correct and might be wary of using data unless it has a reputable source (provenance).
diff --git a/Proposal/impact.tex b/Proposal/impact.tex
index 0a2dd6b..802c35e 100644
--- a/Proposal/impact.tex
+++ b/Proposal/impact.tex
@@ -53,11 +53,11 @@ Through the outreach in the \pn project (see \WPref{dissem}) and the integration
 
 We are very confident about the community of computational and applied mathematics embracing the EOSC as a useful resource --- as they have eagerly embraced other open technologies like \url{http:arxiv.org}, {\LaTeX}, or SageMath in the past.
 In all cases, the mathematical community has directly contributed back -- be it via arXiv submissions, {\LaTeX} packages, and SageMath components.
-Moreover, mathematical users are highly innovative actors in these ecosystems as they are highly intelligent, driven, and far-thinking while constrained by tight budgets that require them to automate as much as possible.
+Moreover, mathematical users are highly innovative actors in these ecosystems as they are highly capable, motivated, and far-thinking while constrained by tight budgets that require them to automate as much as possible.
 In many cases, crucial technology innovations came from users in mathematics and related sciences such as {\LaTeX} by Don Knuth and Leslie Lamport and the SageMath system by William Stein.
 \inparahighlight{By directly working with these users and systematically integrating our services with their favorite systems, we allow this highly innovative community to adopt and contribute to the EOSC ecosystem.}
 
-For a concrete innovation example, consider a \site{FAU}-Bachelor's student Enxhell Luzhnica's work \cite{LuzKoh:fsarfo16}, who extracted 50K generating functions of OEIS sequences and computed relations between these to obtain relations between the corresponding sequences.
+For a concrete innovation example, consider Enxhell Luzhnica's work \cite{Luzhnica:bsc16} (a bachelor's thesis later published as~\cite{LuzKoh:fsarfo16}), who extracted 50K generating functions of OEIS sequences and computed relations between these to obtain relations between the corresponding sequences.
 This work was only possible due to research contacts between the thesis advisor and the OEIS team.
 %Interestingly, 99\% of Luzhnica's work was in extracting the generating functions, writing the SageMath program for calculating identities took an afternoon, and it ran for a couple of days. 
 The \pn project will make all kinds of datasets, including the OEIS, openly accessible, findable, and interoperable on the EOSC so that innovations like this can be done without personal contacts between researchers.
diff --git a/Proposal/management_structure_and_procedures.tex b/Proposal/management_structure_and_procedures.tex
index ca78ab1..d119f23 100644
--- a/Proposal/management_structure_and_procedures.tex
+++ b/Proposal/management_structure_and_procedures.tex
@@ -11,8 +11,7 @@ Describe any critical risks, relating to project implementation, that the stated
 \subsubsection{Overview of the Organisational Structure}
 
 The following bodies will form the organizational structure of the \TheProject project:
-Coordination Team (CT), Steering Committee (SC), Advisory Board (AB), End User Group (EUG)
-and Quality Review board (QRB).
+Coordination Team (CT), Steering Committee (SC), Advisory Board (AB), and End User Group (EUG).
 The organizational structure, shown in the Figure~\ref{fig:management}, has been designed to enable efficient coordination of the project --- the development and evaluation of innovative math-data-centric services involving both academic actors and industrial stakeholders.
 
 The structure is a simplified form of the one employed in the OpenDreamKit Project, where it has worked very well.
diff --git a/lib/kbibs/extpubs.bib b/lib/kbibs/extpubs.bib
index f8cf1b9..85e3dc3 100644
--- a/lib/kbibs/extpubs.bib
+++ b/lib/kbibs/extpubs.bib
@@ -45,7 +45,12 @@
   author = {Eric Prud'hommeaux and Andy Seaborne},
   url = {http://www.w3.org/TR/2006/CR-rdf-sparql-query-20060406/}}
 
-
+@online{PARIGP:on,
+ label = {PG},
+ title = {{PARI/GP} Home},
+ url = {https://pari.math.u-bordeaux.fr/},
+ urldate = {2019-01-29}}
+ 
 @article{WilDumAal:FAIR16,
 	author = {Wilkinson, Mark D. and Dumontier, Michel and Aalbersberg, IJsbrand Jan and Appleton, Gabrielle and Axton, Myles and Baak, Arie and Blomberg, Niklas and Boiten, Jan-Willem and da Silva Santos, Luiz Bonino and Bourne, Philip E. and Bouwman, Jildau and Brookes, Anthony J. and Clark, Tim and Crosas, Merc{\`e} and Dillo, Ingrid and Dumon, Olivier and Edmunds, Scott and Evelo, Chris T. and Finkers, Richard and Gonzalez-Beltran, Alejandra and Gray, Alasdair J. G. and Groth, Paul and Goble, Carole and Grethe, Jeffrey S. and Heringa, Jaap and 't Hoen, Peter A. C and Hooft, Rob and Kuhn, Tobias and Kok, Ruben and Kok, Joost and Lusher, Scott J. and Martone, Maryann E. and Mons, Albert and Packer, Abel L. and Persson, Bengt and Rocca-Serra, Philippe and Roos, Marco and van Schaik, Rene and Sansone, Susanna-Assunta and Schultes, Erik and Sengstag, Thierry and Slater, Ted and Strawn, George and Swertz, Morris A. and Thompson, Mark and van der Lei, Johan and van Mulligen, Erik and Velterop, Jan and Waagmeester, Andra and Wittenburg, Peter and Wolstencroft, Katherine and Zhao, Jun and Mons, Barend},
 	journal = {Scientific Data},
-- 
GitLab