Software Policies

Introduction

The goal of the software policies is to implement the Governance Model for uploading and exploiting EA-CoPCommunity of Practice. software resources and services in the wider iMarine e-InfrastructureAn operational combination of digital technologies (hardware and software), resources (data and services), communications (protocols, access rights and networks), and the people and organizational structures needed to support research efforts and collaboration in the large.. It extends the existing D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. software policies, and adds EA-CoPCommunity of Practice. related requirements and infrastructure related policies related to data exchange and application behaviour. It thus does not detail how these should be made operational in the e-InfrastructureAn operational combination of digital technologies (hardware and software), resources (data and services), communications (protocols, access rights and networks), and the people and organizational structures needed to support research efforts and collaboration in the large., but how the Governance Model defines their usage.

The discussion in the EA-CoPCommunity of Practice. is documented in the iMarine Board Channel, where the CoPCommunity of Practice. has been equipped with a document area and a discussion forum to facilitate an informal yet confidential discussion for 'members only'.

The outputs of that discussion are documented here, for comments by the Project Implementation partners of the consortium.

Why Software Policies?

The software policies aim to guarantee the proper functioning and maintenance of software developed in the EA-CoPCommunity of Practice., and those made available in the iMarine e-InfrastructureAn operational combination of digital technologies (hardware and software), resources (data and services), communications (protocols, access rights and networks), and the people and organizational structures needed to support research efforts and collaboration in the large. to maximize their interoperability and utilization while preserving the original policy settings.

Examples

NEAFC

OBIS

FAO Species Maps and intersection engine

OpenSDMX

Code List Mapper

Resources

To be developed

Data and Access Policy Chapters

The planned chapters for the EA-CoPCommunity of Practice. Software Policies are:

1. Purpose