omewhat ambiguous, as MIT used different flavors of that license at different times for different projects. It imposes very fewrestrictions and, as it is rather short, here we provide the full text of the one of the MIT license variants: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Soft- ware without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to per- mit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS," WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON- INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. The BSD License family is another example of a "permissive" license, conceptually sim- ilar to the MIT license. It was originally introduced for the BSD version of Unix. The Apache license is essentially similar to the permissive BSD license. It was written by the Apache Software Foundation (ASF) to be used for their extremely popular web server software. The language of the Apache license is somewhat more elaborate compared with BSD, making it more appealing to enterprises and therefore more popular. One of the important aspects of this license is that it ensures that people can use the software licensed under Apache terms without concerns for royalties. 6 Enabling Technologies The OAI Public License, even though nowhere near as popular as the ones mentioned above, is imp