27.02.2013 iMarine, SdmxSource and OpenSDMX

From D4Science Wiki
Revision as of 11:38, 28 February 2013 by Luigi.fortunati (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Meeting notes: iMarine, SdmxSource and OpenSDMX (Skype)

Date: 27-February-2013
Topics: iMarine, SdmxSource, OpenSDMX

Participants:

  • FAO: E.Van Ingen
  • CNR: L. Fortunati

Overview:

  • Using as much as possible the iMarine FusionRegistry for structural metadata (SM). The Registry instance can be therefore used as the main repository for structural metadata. FAO can tunnel this registry in the data.fao.org namespace. This aspect has yet to be confirmed by the data.fao.org architect.
  • OpenSDMX will try never to duplicate SdmxSource functionalites.
  • OpenSDMX is the holder for those functionalites thar are missing in SdmxSource and are needed for our purposes. Further functionalities can be built on top of SdmxSource library or development effort can be put on SdmxSource when it will be officially released with OpenSource license.
  • OpenSDMX is a shared platform of iMarine, IRD and FAO for SDMX software development.
  • OpenSDMX may have clients for publishing SM in the iMarine Registry. Actual implementation of iMarine registry is FusionRegistry.
  • Cotrix and iMarine can use OpenSDMX software to publish SM in a SDMX Registry. When SdmxSource will be adopted in in OpenSDMX registry client libraries developed in CNR can be moved in OpenSDMX. According to Luigi OpenSDMX can be seen as a set of client and server components which can work separately: registry client library (supporting all registry operations), plugin-based sdmx datasource (providing access to dataset), plugin-based sdmx SM adapter (providing access to SM). We can also foresee the implementation of a new Registry implementation if FusionRegistry will not provide required future functionalities. Those aspects can be defined at the next TCom meeting.
  • OpenSDMX will implement the SDMX REST interface for data, including the periodfilter and the keyfilter. This implementation can be used for iMarine, data.fao.org and IRD. Along with the filtering of periods and keys there are also other filters that should probably be provided: detail filter, first/last observations, lastUpdate, etc. These capabilties can be supported by the data backend if its interface can be leveraged for this purpose or by OpenSDMX libraries. These details can be discussed at the TCom meeting.
  • The data.fao.org team will migrate the SDMX Mondrian adapter to SdmxSource. This could be reused in iMarine, since iMarine is also considering Mondrian.

Next Actions:

  • Organize a meeting with the data.fao.org SDMX developer, Luigi and myself during the upcoming March TCOM. The technical meeting will be held in Pisa in a parallel session.