Welcome to the EOSC Future wiki!

IMPORTANT: Please be aware that this Wiki space is no longer actively maintained. The information in it applies to the discontinued EOSC Marketplace and Provider Portal, which have been replaced by the EOSC EU Node.
Information related to the EOSC EU Node is available via the official page <here>

TitleEOSC Service Catalogue Interoperability Guidelines
URI

https://doi.org/10.5281/zenodo.8333871

Revised version links
Link to Metadatahttps://docs.google.com/spreadsheets/d/1vvKYdxcHD-sU63XP8Payytyn2rVkN8KbCRfi7MI9Z-I/edit?usp=sharing
Date Issued to EIAC18.04.2023
Submitted byThanassis Mantes, ATHENA RC
Outcome of EIAC reviewendorsed online. 07.09.2023
Date Issued to EIAB22.09.23
Outcome of EIAB review27.09.23
On portal?yes

Overview

The proposed document has been submitted for inclusion in the EOSC Interoperability Framework. 

Comments should be made either on eiac@eoscfuture.eu, where they will be archived for future reference or added to the change log below.  Comments posted to other discussion methods will not be included in the review.

Statements of Support/Deny

All members of the EIAC are encouraged to make a statement of support or dissension in consideration of this proposal.

Name

Organisation

Support or Deny

Reason (if denied)

Gavin Farrell

ELIXIR/EMBL-EBISupport

John Shepherdson

CESSDA ERICSupport
Andrea Manzi
EGI FoundationSupport
Andreas Czerniak
Bielefeld University Library/OpenAIRESupport
Bielefeld UniversitySupport

Comment/Change Log

Please fill in any comments or proposed changes below.

Number

Current Text

Proposed Text / Query

Commenter

Action

1Various

Typos, as marked

John Shepherdson

Addressed

2Abstractmissing

Addressed

3Table of contents

refine the numbering

Addressed

4clarification of terms

use of resource, services or mixed up

Addressed

5linking like "Resource/Provider Profiles (v 3.0, v 4.0)" and some "dead links"

should be double-check

Andreas Czerniak 

Addressed

6double-check on references and table numbers


Andreas Czerniak 

Addressed

7Acronyms table

In suggested mode for minor changes

Gavin Farrell 

Addressed

8Section 3. Intended Audience 

Minor suggested revisions for readability, accessibility of acronyms

Addressed

9Section 4. Description and main features

Sugested reference links and abbreviations harmonisation to table/first use

Minor text suggested edits 

Description and main features overall note: section should be geared as the most easy to understand section, use as many refs to outsider terms or even cross ref to further explanations if further down the doc. Should be inviting to EOSC outsider to understand and consider the audience carefully to ensure they make it past this first point equipped with all the knowledge they need or ability to find this knowoledge on all insider terms e.g. of terms in use: Research Infrastructure/Cluster/EOSC Future(Core) Components/EOSC Resource Catalogue/EOSC Research Product Catalogue/EOSC Service Catalogue/EOSC Providers Portal/EOSC Service Registry/+...

All very heavy bulky concepts for the average service provider/researcher - perhaps consider a pre explainer section on these main concepts in a few sentences or outlinks to where info can be found before this section? 

Partially Addressed
Regarding terminology, Architecture etc,, I have added a reference to the D3.2 that elaborates on the entire EOSC Future Architecture. I think it is too much to go into details here, and this part refers to other core components which in any case have a prior knowledge of the entire architecture. However this document may also be used by providers for using the API to onboard resources. Maybe we need two distinct documents/guidelines for two audiences.

10Section 5. Response to Community Need

Very minor bullet format edits - full stops/commas

Addressed

11Section 6. High-level Service Architecture

Very minor suggested edits

Settle on use of M or Mi - then for B vs Bi for highlighting numeric units of scle

Addressed

11Section 9/ Related Guidelines

OpenAIRE Explore is not an EOSC IF IG - Suggested subbing in one of Alessia/Paolos upcoming Guideliens instead if they make mention of this/ otherwise just change section to 'Related Guideines and Services '

Addressed

12All on doc

Refernece to the EOSC Core and Components then to settle on use of terminology for this: EOSC Future components is in use but it is the EOSC Future Core components that are being mentioned and referenced. Prefeence would be to harmonise the temrinology to mentino Core especially when we have Core EOSC IF IGs

Gavin Farrell 

Addressed

13Sections 10-13

Very minor edits - very good and clear

Addressed

14Section 14. References

More references needed throughout as suggested in doc - first half of doc lacks in average non-EOSC person accessibility for the volume of internal terms and lack of refs to what they are. 

Partially Addressed, same as comment 9

15Various

Post update typos, as marked

John Shepherdson

Addressed

  • No labels