Difference between revisions of "HN Interoperability Org"
Line 9: | Line 9: | ||
The implementation of an effective service architecture calls for redefinition of roles and responsibility and also for potential changes in business practices and procedures. | The implementation of an effective service architecture calls for redefinition of roles and responsibility and also for potential changes in business practices and procedures. | ||
The task force is asked to provide input and suggestions on requirements needed to achieve effective deployment of Helix Nebula and interoperability among publicly funded e-Infrastructures and commercial providers in the following areas (not exhaustive list): | The task force is asked to provide input and suggestions on requirements needed to achieve effective deployment of Helix Nebula and interoperability among publicly funded e-Infrastructures and commercial providers in the following areas (not exhaustive list): | ||
* Uniform access to service catalogues | |||
*Uniform processes to request/allocate/consume/pay services | |||
*Common change management processes | |||
*Harmonised user management processes | |||
*Contract management | |||
*Service Level Agreements | |||
*User support | |||
It is also important that, in the processing of information from external sources terminology used keep a meaningful significance. The meaning of exchanged information has to be clearly and unequivocally understood and preserved throughout exchanges between parties. | It is also important that, in the processing of information from external sources terminology used keep a meaningful significance. The meaning of exchanged information has to be clearly and unequivocally understood and preserved throughout exchanges between parties. | ||
The task force is asked to identify (not exhaustive list): | The task force is asked to identify (not exhaustive list): | ||
*agreed processes and methodologies for developing semantic interoperability assets; | |||
*agreement by sector-specific and cross-sectoral communities on the use of semantic | |||
*interoperability assets at EU level | |||
=== Useful Links=== | === Useful Links=== | ||
Revision as of 11:40, 11 February 2013
Main | Political/Legal TF | Organisational/Semantic TF | Technical TF |
Helix Nebula - Interoperability Task Force - Organisational and Semantic Legal
Mailing List: HelixNebula-Interop-Org-TF@mailman.egi.eu (subscribe)
Purpose
The implementation of an effective service architecture calls for redefinition of roles and responsibility and also for potential changes in business practices and procedures. The task force is asked to provide input and suggestions on requirements needed to achieve effective deployment of Helix Nebula and interoperability among publicly funded e-Infrastructures and commercial providers in the following areas (not exhaustive list):
- Uniform access to service catalogues
- Uniform processes to request/allocate/consume/pay services
- Common change management processes
- Harmonised user management processes
- Contract management
- Service Level Agreements
- User support
It is also important that, in the processing of information from external sources terminology used keep a meaningful significance. The meaning of exchanged information has to be clearly and unequivocally understood and preserved throughout exchanges between parties. The task force is asked to identify (not exhaustive list):
- agreed processes and methodologies for developing semantic interoperability assets;
- agreement by sector-specific and cross-sectoral communities on the use of semantic
- interoperability assets at EU level
Useful Links
Participants
Massimiliano Alvioli - INFN
Owen Appleton - Emergence Tech Ltd.
Hervé Caumont - Terradue
Olivier Gendrin - Visioterra
Roberto Monsorno - EURAC
Roberto Sabatino - DANTE
Michael Symonds - ATOS