Cooperation with SeaDataNet.

Mr Belov reported that there was activity earlier this year. There is a strategy with 3 scenarios: metadata exchange with direct link to data (at ODP level); pre-agreed list of data sets that should be available without registration on both sides. We asked SDN to set up a storage of these data; arrange a “circle of trust” so we encourage ODP users to register which then also allows them to obtain data from SDN.  Now we have to talk to SDN how we can make the scenarios available, first of all through a document. SDN is interested in obtaining the ODP metadata. However there is no mentioning in SDN of this arrangement. So the visibility of ODP in SDN needs further discussions.

Cooperation with WMO/WIS.

We have to make this cooperation more formal through an agreement. There is good cooperation with the German team. It is not difficult to make the WIS catalogue (with 120,000 entries) available through ODP.

Cooperation with ODIP.

We identified that IODE is a bridging structure between Europe and USA but it is unclear how this fits with ODIP. It is expected that Tobias Spears and Sergey Belov will attend the December ODIP meeting in La Jolla, USA. It was recalled that “IODE will participate in the project as a sub-contractor to NERC for the purposes of knowledge exchange and dissemination of results to the global user community. IODE will be active in particular in WP2 (meetings), WP3 (definition of prototypes_, WP4 and WP5”. In particular:

Work Package 2 – Workshop participation

Extract from draft agreement between IOC/IODE and BGS (project leader): As a sub-contracted partner it is expected that IODE will participate in ODIP workshops that are scheduled for months 14 (November 2013), 23 (August 2014) and 32 (May 2015).

Work Package 3 – Definition of prototypes

ODIP will develop a series of prototype interoperability solutions as part of the project tasks. The development of these prototypes will be based on the input received from partners and other domain experts during the ODIP workshops.

IODE will contribute to the development of these prototypes and also participate in any testing as part of a subgroup where relevant.

Work Package 4 –

This work package is tasked with assessing the impact of implementing the ODIP prototypes within existing operational systems. It will also analyse how the selected solutions can contribute to the further development of the IODE Ocean Data Portal (ODP).

As part of this work package IODE will contribute to this analysis and also produce a short report outlining those outcomes of the ODIP project which have had a direct impact of the development of the ODP.

Work Package 5 – Dissemination of results

IODE will support the dissemination of the results from ODIP.  A key activity will be contributing to task WP5.3 Submission to the IODE Ocean Data Standards (ODS) process.  This task is led by partner NERC-BODC and supported by IODE with the objective of submitting any standards adopted by ODIP to the JCOMM/IODE Ocean Data Standards process for ratification as the approved global standards.  IODE will also contribute directly to deliverables D5.5 and D5.8 Common ODIP standards submitted to the IODE Ocean Data Standards (ODS) process due in months 18 and 36 respectively. A short report for each deliverable will be produced by NERC-BODC with contributions from IODE, which outlines those standards that have been selected and submitted for adoption as the global standards.

IODE will also seek to utilise the outcomes of ODIP for the purposes of establishing the IODE Ocean Data Portal (ODP) where appropriate.

Cooperation with RDA.

Peter Pissierssens informed the meeting that a marine interoperability working group had been established and had met at its first plenary in Goteborg. P. Pissierssens will attend the second meeting in Washington DC between 17-19 September. He also noted that the next plenary will take place in Ireland, early 2014 and called on Sergey Belov and Tobias Spears to attend that meeting, taking into account that discussions will become more technical. See more on

Cooperation with EuroGOOS(Patrik Gorringe to join remotely)

(notes by Tobias)

GOOS is not managing metadata like we do (our system is metadata driven). GOOS is more data driven. So we need to get information where metadata can be found.