Federating existing infrastructures

Where resources are phased out, EOSC will need careful planning to ensure that access to existing resources is not lost. If a community expends six months of effort integrating service X, which then disappears in two years because of lack of use or support, then communities will cease to see EOSC as a benefit. Equally, strict adherence to standards regarding APIs may be a good thing in that it minimises risks to communities, but it also serves to stifle innovation and will ultimately lead to services being considered outdated. Balancing these I think is essential to the long term uptake and sustainability of EOSC.