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

Part II. Phased Implementation Plan for DMAC2.5. The following simple and compound types shall be provided:2.5.1. Simple types:2.5.1.1. Integers (signed 16, 32, 64-bit; unsigned 8, 16, 32, 64-bit); floating point (32, 64-bit);2.5.1.2. Strings2.5.1.3. Pointers to types2.5.2. Compound2.5.2.1. Structures2.5.2.2. Arrays2.5.2.3. others TBD2.6. The DT shall be capable of accessing data in a variety of formats.2.7. The DT shall be capable of delivering data of a given data type in a structurally consistent formacross all data sets in the system.2.8. The DT shall provide the metadata needed to transform the data to a consistent semantic form,or it must be capable of delivering the data in a consistent semantic form.2.9. The DT shall provide access to metadata in a variety of forms, including the standard FGDCforms of the metadata, to take advantage of the metadata developed by different communities.The DT shall be capable of providing access to metadata from a site other than that of the dataserver.2.10. The DT shall be capable of providing access to metadata from a site other than that of thedata server together with the data. The DT shall be capable of binding these metadata to a datarequest where appropriate.3. Modular approach3.1. The DT shall be constructed in a modular fashion that allows capabilities to be utilized overalternative transport protocols to HTTP.3.2. Format –The DT shall be capable of moving data from a site in which they may be stored inone format to a client application that may require them in another format.3.2.1. Transport between sites will be implemented via an intermediate format, referred to asthe DT syntactic data model.3.2.1.1. The data model shall be discipline-neutral.3.3. Structure - The system shall provide the capability of delivering data to clients in a structurallyconsistent form where appropriate. In this context, structure means the way that the dataare organized, for example, grid, array, etc.3.3.1. The structure layer protocol will define the organization of like data objects in a data set.3.3.2. Operations and the associated modules in the structure layer that can be performed in adiscipline-neutral fashion shall be logically separated from those that require a semanticunderstanding of the data.64