-
Notifications
You must be signed in to change notification settings - Fork 14
/
Copy pathabstract.tex
128 lines (114 loc) · 6.61 KB
/
abstract.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
\TODO{In this abstract we want to summarize the vision of the project;
- Context: Open Science; what is Jupyter; Jupyter is big
- Who are we
- What is our goal
- What is our strategy / concept
Points to hit:
- Open Science should be practical, not just available
- Jupyter is part of the solution
- *brief* highlight of how/why Jupyter and Binder make sense:
- Jupyter is widely adopted
- notebook encapsulate computation
- Binder builds on Jupyter to enable shareable reproducible environments
- Jupyter is web-based, enabling building services
- What we plan to do
- improve Jupyter/Binder toward open science
- operate Jupyter-based services on EOSC
- Open Science training (skip?)
- Who we are
- Core Jupyter experts
- Domain experts motivating/validating Jupyter improvements
}
% \begin{verbatim}
% Call: Increasing the service offer of the EOSC Portal
% Title: Open Science Publication of Research Environments (OSPRE)
% Points to hit:
% - Open Science should be practical, not just available
% - Jupyter is part of the solution
% - *brief* highlight of how/why Jupyter and Binder make sense:
% - Jupyter is widely adopted
% - notebook encapsulate computation
% - Binder builds on Jupyter to enable shareable reproducible environments
% - Jupyter is web-based, enabling building services
% - What we plan to do
% - improve Jupyter/Binder toward open science
% - operate Jupyter-based services on EOSC
% - Open Science training (skip?)
% - Who we are
% - Core Jupyter experts
% - Domain experts motivating/validating Jupyter improvements
% \end{verbatim}
\begin{abstract}
% (a3) prompt: Services supporting scholarly communication and open access (4M): based on existing initiatives across Europe (institutional and thematic repositories, aggregators, etc.), the services should empower researchers and research communities and initiatives with the necessary tools and functionalities for systematic publishing, analysing and re-using of scientific results beyond publications (data, software and other artefacts), as well as supporting long-term preservation and curation. The services should also enable scientific workflows with adequate metrics and monitoring mechanisms supporting career development and the monitoring of funding and research impact. Support to a catch-all repository for open research should be provided.
% To truly achieve the societal goals of Open Science,
% we must make progress beyond the `mere availability' of scientific results,
% to the practical usability and exploitation of such data once it is made available,
% an area where there is much room for improvement.
% The Jupyter project and its ecosystem show great promise
% as tools for bridging this gap; for making Open Science
% useful and accessible to all,
% from researchers to educators to public citizens.
% The Jupyter Notebook and Jupyter ecosystem are of increasing
% importance in computational science, data science, academia,
% industry, governments, and service providers,
% used by millions worldwide.
% Jupyter notebooks have great potential to push Open Science
% forward because they provide a complete description of a
% computational study that can be turned into a publication
% or produce part of a publication, such as a figure,
% making complex tasks reproducible.
% The Jupyter-based Binder project adds a means to execute notebooks
% in specified computational environments, an aspect of reproducibility
% not yet widely supported.
% In \TheProject, we will extend the capabilities of the Jupyter
% tools and ecosystem to add functionality that we view as having great
% importance for EOSC and Open Science more
% widely and operate services on EOSC as a demonstration.
%
% Many \TheProject partners have longstanding experience and
% leadership roles in the Jupyter ecosystem,
% and in deploying services built on Jupyter to many users across the globe.
% Complementary to this core expertise,
% we integrate partners focussing on the application of these tools from a wide range of disciplines,
% both to demonstrate and ensure that our developments serve
% real-world Open Science use cases.
%
To truly achieve the societal goals of Open Science,
we must make progress beyond the `mere availability' of scientific results as Open Access,
to the practical usability and exploitation of such artefacts once they are made available,
an area where there is much room for improvement.
The Jupyter ecosystem shows great promise as a collection of tools for bridging this gap;
for making Open Science useful and accessible to all,
empowering researchers, educators, and public citizens.
Jupyter is of increasing importance in computational science,
data science, academia, industry, governments, and service providers, and used by millions worldwide.
Jupyter notebooks have great potential to push Open Science beyond publications
because they encapsulate a computational study that may be part of a publication,
such as the creation of a figure,
a major part of making complex tasks reproducible.
The Jupyter-based Binder project adds a means to execute notebooks in specified computational environments,
an aspect of reproducibility not yet widely supported,
and of great falue to re-using scientific results.
Tools such as Jupyter and Binder increase the value of all existing Open Access initiatives
by adding the axis of interactive computability,
empowering researchers to produce derivative and validating (or refuting) work.
Services such as Binder also expose public metrics and monitoring,
supporting the monitoring of research impact and career development for any users of the system.
We will (i) extend the capabilities of the Jupyter tools and ecosystem
to add functionality that we view as essential to and providing great value for EOSC and Open Science,
focused on accessibility, interactive publications, and reproducibility.
Based on this framework of improved Jupyter tools,
it will be possible to build Open Science Publication of Research Environments (\TheProject),
and (ii) build a range of diverse innovative open services on EOSC as
part of this project,
both to demonstrate and ensure that our developments serve real-world Open Science use cases.
Many \TheProject partners have longstanding experience and leadership roles in the Jupyter ecosystem,
and in deploying services built on Jupyter to many users across the globe.
Complementary to this core expertise,
we integrate partners focusing on the application of these tools to a wide range of scientific disciplines and communities,
for which EOSC-hosted demonstrator services are developed.
\end{abstract}
%%% Local Variables:
%%% mode: latex
%%% TeX-master: "proposal"
%%% End: