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

Part III. Appendix 2: Data TransportThis list is not meant to be exhaustive or even adequate for a successful implementation. It is fullyexpected that other datatypes will be found useful and necessary. This list does not specify syntax,either; the ability of one type to contain another, for example, of arrays to contain structures, is extremelyimportant to the expressiveness possible with a given data model.ExtensibilityThere are several possible ways to consider “extensibility.” One addresses the ease of expanding theinstalled base of clients and servers by bringing on line more sites of an already supported platformtype. Another addresses the ease of extending the range of supported platforms, both servers andclients. Yet another addresses the extension of portions of the system; one might consider adding anew, basic datatype to the protocol at some point. One might also want to extend the system intoother disciplines: meteorology, geography, economics. It would be important that fundamentalparts of the IOOS Data Transport System be discipline-neutral to enable this coalescence of terrestrialdata systems.Coexistence with existing transport systems“Coexistence,” too, may be considered in a couple of senses. First, there is “coexistence” in the senseof “do no harm.” It would be unfriendly and unwise for the IOOS Data Transport System to impedeor restrict any site’s use of other transport systems, whether in the field of oceanography ornot. For example, if a repository already uses a system which depends upon a particular data storageformat, that site should not be forced to abandon their system in order to adopt IOOS.Second, there is “coexistence” in the sense of “actively associate with.” IOOS should exert itself tomake it as easy as possible for its data transport system to interact with other systems. If this abilityis not present universally through the IOOS system, then thought should be given to operatingportals between significant systems as part of the system’s base configuration.Non-dependence on proprietary softwareWe suggest that it is most important that the IOOS Data Transport system not depend critically onproprietary software at any point. For it to do so could exclude one of the most powerful enginesfor software development: the freely given efforts of programmers who simply like to see a systemwork better. Also, at least for the research sector, it is of utmost importance to be able to examinesource code to determine what a process actually does, rather than what a person or documentationsays it does.151