System architectures define the structure and configuration of the computer networks that are needed to deliver data originating with data providers and network participants located throughout the hemisphere. The IABIN network is envisioned as a distributed system in which IABIN partners play a key role in the development and maintenance of the network, while IABIN plays the role of facilitator and architect. In most cases, data providers will store and maintain source data, and be responsible for releasing only data that they acknowledge will be offered freely throughout the network. In addition, IABIN's data retrieval services will be provided through a series of networks, each implemented to support a specific area of interest or theme (e.g. Invasive Species, Biological Collections, etc.).

System architectures adopted by IABIN will be based on flexible, widely supported software standards in web-based software development, and have an inherent capability to support the requirements for a distributed system. IABIN system architectures will be applied to the IABIN Gateway and to the design of Project Networks accessed by the Gateway. The intent is to minimize the number of technology restrictions that are imposed on data providers while establishing a limited number of standards that ensure interoperability. For example, users and participants of the IABIN network should have the freedom to choose operating systems, database management systems, web servers and programming tools according to local conditions. To supply data to the network, data providers will be required to implement system interfaces developed to specifications defined by the IABIN network architecture. Given the collaborative nature of the IABIN networks, architectures used by IABIN must support component-based software development methodologies that will allow geographically dispersed groups to independently develop system components according to standards documented by the architecture, and using locally supported software tools.

Given the system architectures options available, IABIN endorses the Web Services network architecture. The Web Services model is currently the architecture of choice for implementation of broad, distributed networks like IABIN. This architecture offers the greatest degree of technological separation between different data providers because all communications between systems are based on XML document interchanges. This model is being rapidly adopted as a standard within the e-Business and e-Commerce communities, but also within the biological informatics community. As an example, GBIF has adopted this architecture to support its global network. More information on the Web Services architecture is available at http://www.w3c.org.

IABIN will also support Z39.50 based network architectures. This is due primarily to the broad utilization of this technology in existing networks, including the Species Analyst project and the FGDC Metadata Clearinghouse that contains relevant IABIN information. In general, the biodiversity community is moving away from Z39.50 in favor of more open, XML based architectures. It is expected that continuing activities to integrate XML with the Z39.50 data retrieval standard may provide the means to more easily migrate existing Z39.50 networks into the Web Services model. IABIN will provide support for Z39.50 based models, but will encourage its partners to implement the more open and flexible XML-based Web Services model.