The Handbook working group has started to work on the next version of the Handbook (V3). The group is composed of first and second wave node contributors who will be updating the current version (V2) of the handbook. The main goal of V3 is to describe how the EOSC Federation and Nodes will move into production.
Any comments or feedback on what else should be added to the Handbook are welcome.
Please post your comments + feedback on the User Forum!
I have the following points: 1. The “EOSC Federation User Forum” is a new body in the Federation not codified by the MoU, it is not a WG. I wonder whether the Handbook should refer to this Forum.
2. The Handbook does not define what a use case is. It is not clear whether a use case belong to the comprehensive term of “resource” and whether a use case must involve multiple Nodes. The use cases may be considered as an application to showcase the Federation or as a publication explaining how to use federated resources.
3. In my opinion cybersecurity should be described as an additional federating capability and not included in the SMS FC-5. In the same way as the helpdesk is FC-3 and relates to SMS processes (primarily Incident and Service Request Management), cybersecurity should also be a separated FC that relates to SMS processes (ISM and ISRM).
4. Nice to have: a description of the Federation from the user perspective, as an overall service with its components adding value to the onboarded resources towards the end-users.
what is a federating service? the handbook refers to them as the services implementing the federating capabilities. Does it mean that the federating services are the actions of providing a service or the softwares permitting the capability?
Example, supposing that the service monitoring capability uses Argo as a software for monitoring, is the act of managing the monitoring across Nodes that makes the service or is the software?