download as a pdf - Southern California Coastal Ocean Observing ...

Part I. OverviewDMAC standards and protocols. This designation will (in the mature DMAC) include commonGIS applications, common scientific analysis and visualization applications, educational software,and common business tools, such as spreadsheets and word processors.Because IOOS is a user-driven system, the IOOS User Outreach and Governance mechanisms mustensure that the users’ needs for Information Products and DMAC-ready applications are continuallyassessed and accommodations made within IOOS to meet them. Information Products will begenerated at all levels of IOOS: by Primary Data Assembly Centers/sites (e.g., the Argo GDACS);by the DMAC Communications Infrastructure (see On-line Browse above); by DMAC ModelingCenters and Archive Centers; and by the regional, international, and discipline-specific data managementsystems that interoperate with DMAC data. It is understood, however, that these productsalone will not be sufficient to meet the needs of all user groups. There is a vital role for privatesector IOOS partners in providing users with specialized value-added Information Products andDMAC-ready applications.INTEROPERABILITY WITH OTHER DATAMANAGEMENT SYSTEMSThe DMAC Data Communications Infrastructure provides for interoperable communications betweenDMAC components and other data management systems containing data that are of interestto IOOS users. These entities include data management systems operated by disciplines lying outsideof marine sciences (e.g., public health), data management systems operated by other nationsor international bodies, and specialized data management systems that may be operated by RegionalAssociations within IOOS. Like the DMAC Subsystem these systems may be highly complex andinvolve multiple distributed partners. They may use data communications infrastructures that aredistinct from the DMAC Standards and Protocols. To achieve interoperability with these entities,software “gateways” must be built that will translate between standards and protocols used withinthe DMAC Subsystem and those used in the other data systems. Similar considerations apply tocommercial organizations that have adopted custom “enterprise” solutions 16 , as well as frameworksadopted by communities that share specialized computing needs, such as the high performancecomputing community’s DataGrid 17 and the GIS community’s geospatial data systems. Thus, asIOOS matures, it should be viewed as a system of systems in which the DMAC Data CommunicationsInfrastructure provides a uniform language for communications.16“Enterprise” solutions are typically commercial interoperability frameworks that operate on secure network connections.17http://www.globus.org/datagrid35