| | |
| | |
| | h2.Section IV: Principles and Philosophy |
| | \\ |
| | Several key principles inform and guide the OCKHAM philosophy to promote interoperability to build a more effective extended digital library community. These principles have been selected as best pratices from a large number of previous projects ranging from the Open Archives Initiative to the Apache Software Foundation. Utilization of these principles make any public collaborative software initiative more likely to succeed: |
| | \\ |
| | \\ |
| | | * *Open Standards:* We are commited to open standards. Open standards are unencumbered by restrictions on platforms or vendors. Most often, the standards are set by a third party (e.g. ISO) in order to encourage competion in implementation. We are commited both to using products based on open standards in our implementation, as well as the open-ness of our own products. The OCKHAM network will be better with competing implementations. |
| | | * *Open Standards:* We are commited to open standards. Open standards are unencumbered by restrictions on platforms or vendors. Most often, the standards are set by a third party (e.g. ISO) in order to encourage competion in implementation. We are commited both to using products based on open standards in our implementation, as well as the open-ness of our own products. The OCKHAM network will benefit from development based on public, non-commercially controlled standards. |
| | \\ |
| | \\ |
| | * *Component Based Development:* Advancing software development through the incremental development of modular components is a well-established best practice arising from industry and open source development efforts. We favor a component-based approach to development over monolithic models. Every service on the OCKHAM network will be designed to stand alone, and is should be functional absent other services. The functionality may, however, by augmented with other services. For example, the cataloging service can accept and modify records in a wider variety of formats when assisted by the conversion service, but is still functional alone. |
| | \\ |
| | \\ |
| | * *Ease of Adoption:* Using strategies such as open source package software distribution, we will minimize the barriers to adoption of the OCKHAM network software. By removing barriers of price and installation complexity, everything possible will be done to provide value to the traditional library community by maximizing our base of users, testers, and developers. We will do this by providing a freely available core software framework that installs with minimal effort, requiring minimal knowledge of system administration, and on a maximal variety of hardware. |
| | \\ |
| | \\ |
| | * *Open Collaboration:* The OCKHAM network will be based on an open, documented process of collaboration on component software. By providing not only a framework for software components to interoperate, but also for multiple individuals and institutions to collaborate on development, the network will enable widespread leverage between development efforts. |
| | \\ |
| | \\ |
