The EOSC-hub project has ended. This space is READ ONLY

AreaEOSC Policies
Procedure status

APPROVED

Owner
To be agreed with EOSC EB
Approval status

APPROVED

Approved version and date

Executive Board, EOSCpilot project,  

Statement

This page contains the first set of terms forming the EOSC Portal Glossary.

Next procedure review

 


Copyright. The EOSC Portal Glossary is a derivative of the EOSCpilot Glossary by  EOSCpilot  used under Creative Commons Attribution 4.0 International LicenseThe "EOSC Portal Glossary" is licensed under Creative Commons Attribution 4.0 International License by  EOSC-hub, OpenAIRE-Advance and eInfraCentral.

EOSC-hub, OpenAIRE-Advance and eInfraCentral are projects are co-funded by the European Union Horizon 2020 programme respectively under grant numbers: 777536, 777541 and 731049.


Data Service Supplier

An EOSC Supplier focusing on the provision of one or more Data 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 data it gives access to than on the functionality it offers. One of the primary service built by relying on Data Services is the EOSC Data Registry service typology.

European Open Science Cloud

(Abbreviated EOSC) The European Open Science Cloud promoted by the European Commission to provide all researchers, innovators, companies and citizens with seamless access to an open-by-default, efficient and cross-disciplinary environment for storing, accessing, reusing data, tools, publications and any EOSC Resource for research, innovation and educational purposes. EOSC is implemented by the EOSC System and governed by the EOSC Governance.

EOSC Architecture

The architecture of the EOSC System. The service-oriented architecture consists of the EOSC Services forming the EOSC System. The deployment architecture consists of the EOSC Nodes contributing to the EOSC System.      

Notes: Every “system” has its own architecture. According to ISO/IEC/IEEE 42010 the architecture of a system is "fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution".

EOSC Board

The EOSC Governance component gathering Member States and the Commission to ensure effective supervision of the EOSC implementation.

EOSC Data Registry

An EOSC Service providing EOSC System Users with a list of live / ready-to-use descriptions of datasets (a specific type of EOSC Resource) offered by the EOSC System.

Notes: Datasets are made available by EOSC Service(s). Many EOSC Data Registry instances may exist, each tailored to serve the needs of a designated community. Moreover, an overarching EOSC Data Registry is likely to be built / populated by relying on EOSC Service Component(s) including thematic catalogues, registries and repositories. Every entry of an EOSC Data Registry must give relevant information (aka metadata) on the listed datasets thus to enact its informed discovery and use, e.g. a description of dataset intent and scope, a description on how to access it, a description of the license governing its usage.

EOSC End User

An EOSC System User consuming EOSC Resource(s) by means of EOSC Service(s) (e.g. the EOSC Portal) to accomplish a task. She can be a Researcher, a Research Administrator, or a Third-party Service Provider.

EOSC Executive Board

The EOSC Governance component called to provide the EOSC Board with advices and proposals on EOSC implementation.

EOSC Governance

The set of committees and bodies governing the functioning of 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 Portfolio Management Committee, the EOSC System Executive Committee regarding the development of the EOSC System.   

EOSC Node

The component of the EOSC System that is called to contribute to the provisioning of one or more EOSC Services. An EOSC Node: (a) is the place where EOSC Services and/or EOSC Service Components reside; (b) is operated by an EOSC Service Provider and/or an EOSC Supplier.

EOSC Policy

A documented set of principles, rules and requirements adopted by the EOSC Governance to support and/or drive the activities and mission of the EOSC. Policies may concern any aspect of the EOSC, such as ethics, openness, security, cost-effectiveness or others.

EOSC Portal

The EOSC Service providing online access to and use of the EOSC Resources.

Note: The list of Resources includes the EOSC Resource Registry for the discovery of other EOSC Resource.  

EOSC Resource

Any asset made available (by means of the EOSC system 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 consultancy.

EOSC Resource Registry

An EOSC Service providing EOSC System Users with a list of live / ready-to-use descriptions of EOSC 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 Resource Registry is likely to be operated to list the entire EOSC offering. Moreover, every EOSC Resource Registry is likely to be built / populated by relying on EOSC Service Component(s) including discipline-specific registries and repositories. Every entry of an EOSC Resource Registry must give relevant information (aka metadata) on the listed resources to enable semantic interoperability. The following attributes are example of resource metadata: 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.

EOSC Rules Of Participation

The principles defined by the EOSC Governance to drive the processes enacting 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 envisaged in EOSC to capture the specific participation requirements posed for actors expected to play a certain role (e.g. EOSC Service Provider and EOSC End-users).  

EOSC Service

An EOSC Resource providing ready-to-use capabilities. EOSC Services are supplied by an EOSC Service Provider in accordance with the EOSC Rules of Participation for EOSC Service Providers. EOSC Services are approved by the EOSC Service Portfolio Management Committee and populate the EOSC Service Portfolio and the EOSC Service Catalogue

Note: According to FitSM a Service is "Way to provide value to customers through bringing about results that they want to achieve". Moreover, the text of the definition aims at stressing the fact that there is a service-orientation in EOSC. EOSC Services are usually IT services. EOSC Services provide value when taken on their own – unlike the specific EOSC Service Components of which they are composed of.  

EOSC Service Catalogue

The list of all live EOSC Services that can be requested by EOSC System Users. It is a subset of the EOSC Service Portfolio and it populates the EOSC Service Registry.

Note: It is a duty of the EOSC Service Provider to provide access to relevant service information to its EOSC System Users and other interested parties.

EOSC Service Component

A logical part of an EOSC Service, i.e. it is a building block enacting the implementation and provisioning of an EOSC Service. An EOSC Service Component can be an EOSC Service on its own. 

Note: According to FitSM, a Service Component is a "logical part of a service that provides a function enabling or enhancing a service.". Such a definition is accompanied by some notes: (a) "A service is usually composed of several service components.", (b) "A service component is usually built from one or more configuration items (CIs).", and (c) "Although a service component underlies one or more services, it usually does not create value for a customer alone and is therefore not a service by itself".

EOSC Service Component Supplier

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 several reasons including the “what” (namely an EOSC Service Component rather than an EOSC Service) and the “how” (i.e. service provisioning is regulated by an Underpinning Agreement).

EOSC Service Developer

An EOSC Supplier called to implement the software component needed to deliver and operate an EOSC Service.     

EOSC Service Portfolio

The internal list of EOSC Services including those in preparation, live and discontinued. The development of this list is controlled 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 is focusing on, e.g. to define new services to be delivered as well as services that are going to be dismissed. For EOSC Services offered by EOSC Service Providers to EOSC System End Users, the scope of responsibility of the EOSC Service Portfolio Management is mainly 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 of the functional evolution of the service in accordance to users’ needs. 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.

EOSC Service Portfolio Management

Definition: the process performed by the EOSC Service Portfolio Management Committee to drive the development of the EOSC Service Portfolio.

EOSC Service Provider

An EOSC System Manager managing and delivering an EOSC Service.      

Note: According to FitSM, a Service Provider is defined as an "Organisation or federation (or part of an organisation or federation) that manages and delivers a service or services to customers". An EOSC Service Provider is a FitSM Service Provider called to manage and deliver an EOSC Service.

EOSC Service Registry

An EOSC Service providing EOSC System Users with a list of live / ready-to-use descriptions of EOSC Services offered by the EOSC System. The list includes (a subset of) the entries in the EOSC Service Catalogue as well as any other service worth being discoverable via the service instance.

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 likely to be operated to list the entire EOSC offering. Moreover, every EOSC Service Registry is likely to be built / populated by relying on EOSC Service Component(s) including discipline-specific registries and repositories. Every entry of an EOSC Service Registry must give relevant information (aka metadata) 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 access it, a description of the license governing its usage.

EOSC Supplier

An EOSC System User responsible for the provisioning of one or more EOSC Service Component(s) enacting an EOSC Service within the EOSC System. It is further specialised in the following sub-roles: EOSC Service Component Supplier, Data Service Supplier, and EOSC Service Developer.

EOSC System

The IT system implementing EOSC. Such a system is called to put in place the policies, procedures and technical solutions needed to enact the delivery of the EOSC Services in accordance with the EOSC Governance guidelines.

Note: Such a system is not a monolithic, stand-alone and centralised IT system. Rather the EOSC System is designed and developed to be a system of systems distributed across EOSC Nodes.

EOSC System User

The role played by every actor (human or machine) exploiting the EOSC System according to the EOSC Policy. An EOSC System User might be further specialised in roles including EOSC End-users, EOSC Suppliers, and EOSC System Managers.   

Third-party Service Provider

An EOSC End-user willing to develop and operate a service by relying on one or more EOSC Services.  

Change log

Glossary version

Changes

Date

v.1.0

Shortening of dfinitions and notes from EOSCpilot Glossary v1.0. A few items of the glossary omitted.

 


  • No labels