Update ds_eoscpilot.tex

contributions/ds_eoscpilot/ds_eoscpilot.tex

@@ -41,14 +41,14 @@ principles, and {\bf Service interoperability}, ensuring that services operated
 within different infrastructures can interchange and interwork. 
 
 In the framework of the EOSCpilot project INFN, and in particular CNAF is the 
-coordinator of the activities of the task T6.3 - “Interoperability pilots 
+coordinator of the activities of the task T6.3 - “Interoperability pilots 
 (service implementation, integration, validation, provisioning for Science 
-Demonstrators)â€.
+Demonstrators)â€.
 
 One of the project's main Objectives related to WP6 is to:
 \begin{itemize}
-\item “Develop a number of pilots that integrate services and infrastructures 
-    to demonstrate interoperability in a number of scientific domains†
+\item “Develop a number of pilots that integrate services and infrastructures 
+    to demonstrate interoperability in a number of scientific domains†
 \end{itemize}
 mapped into some specific Objectives addressed by the T6.3 task:
 \begin{itemize}
@@ -69,12 +69,12 @@ During 2018 the main activities coordinated by INFN-CNAF were:
     interoperability requirements and matching them again with available services and solutions
 \item Setup of different pilot addressing different interoperability aspects:
 \begin{itemize}
-\item Transparent Networking – PiCo2 (Pilot for COnnection between COmputing centers)
-\item Grid and Cloud interoperability – pilot demonstrator for one of the HEP experiments
-\item AAI – through the setup of a scoped interoperability pilot as part of the 
+\item Transparent Networking – PiCo2 (Pilot for COnnection between COmputing centers)
+\item Grid and Cloud interoperability – pilot demonstrator for one of the HEP experiments
+\item AAI – through the setup of a scoped interoperability pilot as part of the 
     WLCG Authorization WG, AARC and EOSCpilot collaboration
-\item Resource Brokering \& orchestration – leveraging INDIGO-DataCloud solutions
-\item Data accessibility \& interoperability of underlying storage systems – 
+\item Resource Brokering \& orchestration – leveraging INDIGO-DataCloud solutions
+ 
     distributed Onedata deployment
 \end{itemize}
 \item Continuous interaction and communication with Science Demonstrators shepherds 
@@ -86,13 +86,13 @@ implementation of the SDs specific use cases.
 
 The {\bf PiCO2 (Pilot for COnnecting  COmputing centers)} is one of the first 
 interoperability pilots between generic, community agnostic, infrastructures, 
-especially Tier-1 (National HPC/HTC centres), and Tier-2 (HPC/HTC regional centres). 
+especially Tier 1 (National HPC/HTC centers), and Tier 2 (HPC/HTC regional centers). 
 Its main objective is the automation of frequent, community agnostic, data flow 
 (many large files) and code exchange between HPC (National, Regional) and HTC (national, grid) infrastructures
 During 2018 technical groups have been set up:
 \begin{itemize}
 \item one for building a network of peer to peer federations between iRODS zones
-    (data storage service), between Tier1 \& Tier 2, between Tier2, and between Tier 2 and the grid
+    (data storage service), between Tier 1 \& Tier 2, between Tier 2, and between Tier 2 and the grid
 \item one for connecting the infrastructures within a L3VPN network and 
     monitoring the performance of the network between sites 
 \item one for facilitating the mobility and use of codes between different 
@@ -130,7 +130,7 @@ Overall, integration has been successful and much experience has been gained
 resulting in improved understanding of weaknesses and aspects to improve and to optimise. 
 Weaknesses, and aspects to be improved include:
 \begin{itemize}
-\item Federation: federated access to underlying IaaS is a key. So far we ha€™ve 
+\item Federation: federated access to underlying IaaS is a key. So far we ha€™ve 
 experienced several issues. Frequently we had issues with the IaaS provider 
 already using OpenID Connect Authorisation Server and thus unable to federate 
 additional services. We adopted ESACO  solution to solve such a problem. It 
@@ -143,7 +143,7 @@ benefit of such functionality for counting the overall HEPSpec .
 \item Transparent Data Access: so far the only scalable solution we can use is 
 XrootD . However, this might not fit all possible use cases.  A more generic 
 solution would be a big plus.
-\item Resource monitoring: we didn'€™t find a common solution for monitoring 
+\item Resource monitoring: we didn'€™t find a common solution for monitoring 
 cloud resources. Although we implemented our own we are convinced that a 
 common strategy would be extremely valuable. 
 \item PaaS Orchestration: Although the current INDIGO PaaS Orchestrator has 
@@ -160,7 +160,7 @@ in the field of authorisation and authentication, policies and recommendations
 regarding their design, that took shape, in the scope of the WP6 activities, 
 under the form of an AAI interoperability demonstrator setup as part of the 
 AARC pilots Task 1: {\bf Pilots with research communities based on use cases 
-provided  - the WLCG use case}, regarding the {\it “Implementation of IdP/SP Proxy, 
+provided  - the WLCG use case}, regarding the {\it “Implementation of IdP/SP Proxy, 
 mainly to provide Token Translation Services to allow end users to login without 
 the need of manually managing X.509 certificates}. A team of people was formed, 
 under the WLCG coordination, to deal with the various activities, the {\bf WLCG 
@@ -260,10 +260,10 @@ After the delivery of the first draft of the strategy and recommendations done i
 2017 and beginning of 2018, four data interoperability demonstrators have been 
 proposed to test components of the strategy: 
 \begin{itemize}
-  \item Evaluation of the EDMI (EOSC Datasets Minimum Information) metadata guidelines to find and access datasets 

-  \item Discovery of compliant data resources and metadata catalogues 

-  \item Research schemas for exposing dataset metadata 

-  \item Description and guidelines per metadata property 

+  \item Evaluation of the EDMI (EOSC Datasets Minimum Information) metadata guidelines to find and access datasets 

+  \item Discovery of compliant data resources and metadata catalogues 

+  \item Research schemas for exposing dataset metadata 

+  \item Description and guidelines per metadata property 

 \end{itemize}
 
 Our role during 2018 was to: