Date: Thu, 28 Mar 2024 15:27:48 +0100 (CET) Message-ID: <521133111.128.1711636068233@czmuims01.ops.egi.eu> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_127_2105125347.1711636068232" ------=_Part_127_2105125347.1711636068232 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Copyright. The=
EOSC Portal Glossary is a derivative of the <=
a class=3D"external-link" href=3D"https://eoscpilot.eu/eosc-glossary#overla=
y-context=3Deosc-glossary" rel=3D"nofollow">EOSCpilot Glossary by =
EOSCpilot used under
EOSC-hub, OpenAIRE-Advan=
ce and eInfraCentral are projects are co-funded by the European Union Horizon 2020 programme respe=
ctively under grant numbers: 777536, 777541 and 7=
31049.
An EOSC Supplier focusing on the provision of one or more D= ata Services, i.e. building blocks enacting the implementation and= provisioning of an EOSC Service.
Notes: The services these suppliers are expected to contribute = represent a specific typology of service whose value resides more on the da= ta it gives access to than on the functionality it offers. One of the prima= ry service built by relying on Data Services is the EOSC Data Registry<= /em> service typology.
(Abbreviated EOSC) The European Open Science Cloud promoted by the E= uropean Commission to provide all researchers, innovators, companies and ci= tizens with seamless access to an open-by-default, efficient and cross-disc= iplinary environment for storing, accessing, reusing data, tools, publicati= ons and any EOSC Resource for research, innovation and ed= ucational purposes. EOSC is implemented by the EOSC System and governed by the EOSC Governance.
The architecture of the EOSC System. The =
service-oriented architecture consists of the EOSC Services <=
em>forming the EOSC System. The deploym=
ent architecture consists of the EOSC Nodes contributing =
to the EOSC System.
Notes: Every =E2=80=9Csystem=E2=80=9D has its own architecture.= According to ISO/IEC/IEEE 42010 the architecture of a system is "funda= mental concepts or properties of a system in its environment embodied in it= s elements, relationships, and in the principles of its design and evolutio= n".
The EOSC Governance component gathering Member Sta= tes and the Commission to ensure effective supervision of the EOSC= implementation.
An EOSC Service providing EOSC System Use= rs with a list of live / ready-to-use descriptions of datasets (a = specific type of EOSC Resource) offered by the E= OSC System.
Notes: Datasets are made available by EOSC Service(s).= Many EOSC Data Registry instances may exist, each tailored to serve the ne= eds of a designated community. Moreover, an overarching EOSC Data Registry = is likely to be built / populated by relying on EOSC Service Component(s) i= ncluding thematic catalogues, registries and repositories. Every entry of a= n EOSC Data Registry must give relevant information (aka metadata) on the l= isted datasets thus to enact its informed discovery and use, e.g. a descrip= tion of dataset intent and scope, a description on how to access it, a desc= ription of the license governing its usage.
An EOSC System User consuming EOSC Resource(s) by means of EOSC Service(s) (e.g. the EOSC Portal) to a= ccomplish a task. She can be a Researcher, a Research Administrator, or= a Third-party Service Provider.
The EOSC Governance component called to provide th= e EOSC Board with advices and proposals on EOSC<= /em> implementation.
The set of committees and bodies governing the functioning of = em>EOSC and its EOSC System. It includes the= EOSC Executive Board, the EOSC Board, = and the EOSC Stakeholders Forum. It liaises with the EOSC System Steering Committee, the EOSC Service Por= tfolio Management Committee, the EOSC System Executive Committee r= egarding the development of the EOSC System. &= nbsp;
The component of the EOSC System that is calle=
d to contribute to the provisioning of one or more EOSC Services=
em>. An EOSC Node: (a) is the place where EOSC Services
A documented set of principles, rules and requirements adopted b= y the EOSC Governance to support and/or drive the activit= ies and mission of the EOSC. Policies may concern an= y aspect of the EOSC, such as ethics, openness, security, cost-eff= ectiveness or others.
The EOSC Service providing online access to and use of the EOSC Reso=
urces.
Note: The list of Resources includes the EOSC Resource Registry= for the discovery of other EOSC Resource.
Any asset made available (by means of the EOSC system<= em> and according to the EOSC Rules of Participation) to = EOSC System Users to perform a process useful to deliver = value in the context of the EOSC. EOSC Resources include = assets like services, datasets, software, support, training, and consultanc= y.
An EOSC Service providing EOSC System Use= rs with a list of live / ready-to-use descriptions of EOS= C Resource offered by the EOSC System.
Note: Various EOSC Resource Registry instances may exist, each tailored = to serve the needs of a designated community. At least one overall EOSC Res= ource Registry is likely to be operated to list the entire EOSC offering. M= oreover, every EOSC Resource Registry is likely to be built / populated by = relying on EOSC Service Component(s) including discipline-specific registri= es and repositories. Every entry of an EOSC Resource Registry must give rel= evant information (aka metadata) on the listed resources to enable semantic= interoperability. The following attributes are example of resource metadat= a: mechanism of access, the applicable acceptable use policy, the provider.= At least two specific typologies of EOSC Resource Registry are envisaged: = the EOSC Dataset Registry and the EOSC Service Registry.<= /p>
The principles defined by the EOSC Governance to drive the processes ena= cting an actor to play the role of EOSC System User (and any specialization= of it).
Note: Various types of role (see EOSC System Users) are envisag= ed in EOSC to capture the specific participation requirements posed for act= ors expected to play a certain role (e.g. EOSC Service Provider an= d EOSC End-users).
An EOSC Resource providing ready-to-use c= apabilities. EOSC Services are supplied by an EOSC Service Provide= r in accordance with the EOSC Rules of Participation= for EOSC Service Providers. EOSC Services are approv= ed by the EOSC Service Portfolio Management Committee and= populate the EOSC Service Portfolio and the EOS= C Service Catalogue.
Note: According to FitSM a Service is "Way to provide value to cus= tomers through bringing about results that they want to achieve". Moreover,= the text of the definition aims at stressing the fact that there is a serv= ice-orientation in EOSC. EOSC Services are usually IT services. EOSC Servic= es provide value when taken on their own =E2=80=93 unlike the specific EOSC= Service Components of which they are composed of.
The list of all live EOSC Services that can be req= uested by EOSC System Users. It is a subset of the <= em>EOSC Service Portfolio and it populates the EOSC Servi= ce Registry.
Note: It is a duty of the EOSC Service Provider to provide acce= ss to relevant service information to its EOSC System Users and ot= her interested parties.
A logical part of an EOSC Service, i.e. it is a bu= ilding block enacting the implementation and provisioning of an EO= SC Service. An EOSC Service Component can be an EOSC Serv= ice on its own.
Note: According to FitSM, a Service Component is a "logical part o= f a service that provides a function enabling or enhancing a service.". Suc= h a definition is accompanied by some notes: (a) "A service is usually comp= osed of several service components.", (b) "A service component is usually b= uilt from one or more configuration items (CIs).", and (c) "Although a serv= ice component underlies one or more services, it usually does not create va= lue for a customer alone and is therefore not a service by itself".
An EOSC Supplier focusing on the provision of one = or more EOSC Service Component(s).  = ;
Note: According to FitSM, a Supplier is an "External organisation = that provides a (supporting) service or service component(s) to the service= provider, which they need to provide services to their customers / users".= This term should not be confused with the EOSC Service Provider for severa= l reasons including the =E2=80=9Cwhat=E2=80=9D (namely an EOSC Service Comp= onent rather than an EOSC Service) and the =E2=80=9Chow=E2=80=9D (i.e. serv= ice provisioning is regulated by an Underpinning Agreement).
An EOSC Supplier called to implement the software = component needed to deliver and operate an EOSC Service.<= /em>
The internal list of EOSC Services including those= in preparation, live and discontinued. The development of this list is con= trolled by the EOSC Service Portfolio Management Committee.
Note: According to FitSM, a Service Portfolio is an "Internal list that = details all the services offered by a service provider, including those in = preparation, live and discontinued". This is expected to be a key component= enacting the definition of the overall offering the EOSC System i= s focusing on, e.g. to define new services to be delivered as well as servi= ces that are going to be dismissed. For EOSC Services offered by <= em>EOSC Service Providers to EOSC System End Users, the scope= of responsibility of the EOSC Service Portfolio Management is mai= nly to ensure the verification of the compliance with the EOSC Rules of= Participation and that the service correctly integrates into the = EOSC System. The EOSC Service Provider retains full control o= f the functional evolution of the service in accordance to users=E2=80=99 n= eeds. For EOSC Services offered by EOSC Service Providers= to enable the EOSC System, the EOSC Service Portfolio Management = can retain a higher level of control on the planning, design and release of= those services.
Definition: the process performed by the EOSC Serv= ice Portfolio Management Committee to drive the development of the= EOSC Service Portfolio.
An EOSC System Manager managing and delivering an = EOSC Service.
Note: According to FitSM, a Service Provider is defined as an "Org= anisation or federation (or part of an organisation or federation) that man= ages and delivers a service or services to customers". An EOSC Service Prov= ider is a FitSM Service Provider called to manage and deliver an EOSC Servi= ce.
An EOSC Service providing EOSC System Use= rs with a list of live / ready-to-use descriptions of EOS= C Services offered by the EOSC System. The = list includes (a subset of) the entries in the EOSC Service Catalogue= em> as well as any other service worth being discoverable via the service i= nstance.
Note: This is a specialization of the EOSC Resource Registry. Many = Service Registry instances may exist, each tailored to serve the needs of = a designated community. At least one overall EOSC Service Registry is likel= y to be operated to list the entire EOSC offering. Moreover, every EOSC Ser= vice Registry is likely to be built / populated by relying on EOSC Service = Component(s) including discipline-specific registries and repositories. Eve= ry entry of an EOSC Service Registry must give relevant information (aka me= tadata) on the listed services thus to enact its informed discovery and use= , e.g. a description of service intent and scope, a description on how to a= ccess it, a description of the license governing its usage.
An EOSC System User responsible for the provisioni= ng of one or more EOSC Service Component(s) enacting an <= /em>EOSC Service within the EOSC System. It = is further specialised in the following sub-roles: EOSC Service Co= mponent Supplier, Data Service Supplier, and EOSC Service Developer.
The IT system implementing EOSC. Such a system is = called to put in place the policies, procedures and technical solutions nee= ded to enact the delivery of the EOSC Services in accorda= nce with the EOSC Governance guidelines.
Note: Such a system is not a monolithic, stand-alone and ce= ntralised IT system. Rather the EOSC System is designed and developed to be= a system of systems distributed across EOSC Nodes.<= /p>
The role played by every actor (human or machine) exploiting the EOSC System according to the EOSC Policy. An EOSC S= ystem User might be further specialised in roles including EOSC En= d-users, EOSC Suppliers, and EOSC Syste= m Managers.
An EOSC End-user willing to develop and operate a = service by relying on one or more EOSC Services. &nb= sp;
Glossary version |
Changes |
Date |
---|---|---|
v.1.0 |
Shortening of dfinitions and notes from EOSCpilot Glossary v1.0. A few i= tems of the glossary omitted. |
&nbs= p; |