After an initial sorting and arrangement of logos into catgories such as clients, services, content providers, we realized that the organizations represented by logos often spanned these categories or did not fil well into a single category.

We then developed two overall structures:

We focused on application programming interfaces (APIs) and considered DO helping standardizing APIs for various content providers or DO could provide overall API that permit DO applications that talk to various entities like Google Ocean. THe diagram illustrates these two options.

Specific issues discussed included:
To attract and engage scientists and to increase the validity of the information being distributed, it is necessary to have a QA/QC system for information

In addition, we would like content to be individually generated like 'home video of a SCUBA trip' as well as to include vetted 'scientific' data. This would require available filters to avoid inappropriate content or hacking.

The tagging (i.e. metadata formating) should be accessible to a wide spectrum of user/providers, but be sufficient to permit information organization and searching.

Examples of interactive systems that may provide usual information include 'patientslike me.com' and 'delicious.com'