The Aperture Framework itself is distributed under a BSD-style license. The copyright holder for each particular source file is given within the file itself.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Licenses for third party libraries used in Aperture can be found in ./lib/
The use of BSD in the core framework allows developers to license implementations of Aperture APIs under any license they see fit, including proprietary and commercial licenses.
The aperture framework is free to use and to extend. Through use of BSD, we experience that the framework is more useful and users are willing to contribute to the project.
The core project APIs and architecture are licensed under the Academic Free License (AFL) version 3.0. (AFL 3.0) (original source).
The implementations of these APIs are licensed under the Open Software License (OSL) version 3.0. (OSL 3.0) (original source).
The use of these two licenses allows developers to license implementations of Aperture APIs under any license they see fit, including proprietary and commercial licenses.
The API implementations contained in Aperture are licensed under the OSL, which is a reciprocal license. This effectively means that changes to these implementations have to be made available to the community, while these implementations and their derivatives can be used in applications licensed under a different license.
The core parts (APIs and closely associated classes) are free to use and to extend. They should be as open as possible so that anyone can include Aperture in a project, commercial, closed source or not. Especially, people should not be required (or even think they are required) to disclose their own implementations for accessing proprietary document formats, data sources, etc., as these may necessarily contain trade secrets, require patent licenses, etc.
Besides a framework, Aperture contains a number of concrete implementations, e.g. Crawlers for various information sources and Extractors for various document types. A lot of time and effort has been put in their creation and maintenance and they are therefore licensed under a reciprocal license. This means that changes to this code such as functional extentions, bugfixes and performance improvements, that are redistributed or externally deployed in one way or another, have to be made available to the community under the same open source license. However, this restriction has no effect on the code using these standard and derived implementations, so your own applications are never at risk.