Highly Reusable Software

By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Math
Integer, Floating point, Matrix, Statistics, Boolean, ...

Processing
Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Communications
Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...

Reporting if a license is open source software according to the Open Source Definition

The Open Source Initiative maintains the "Open Source Definition" (the OSD) which are principles which a software license must fulfill to receive their approval. When the license description file includes a symbolic list of attributes (see Creating a LIDESC_COMBINE string) the symbolic attributes can be checked for consistency with the open source definition.

CAUTION: license compatibility reports are only as good as the description files created by human interpretation of license texts. You should obtain them from trusted suppliers, and be careful when creating them yourself. If a symbol list for a license is empty or incomplete, it is not possible to accurately report incompatibility.

The command line to check for consistency with the OSD is:

	lidesc [-d {license-dir}] combine osd.txt license.txt

{license-dir} is the optionally provided location of license description files. By default it is '.' license.txt is the name of the license text file to test.

Example output:

OK  No license conflicts detected (librock/license/osd.txt librock/license/bsdorig.txt)

WARNING: It is folly to assume that a simple program like this can do anything more than find and report some of the biggest problems, while leaving others undetected. This system does not match the educated human intelligence required to interpret and apply licenses. On the other hand, it can be useful to identify some of the license clauses which deserve extra scrutiny.

Up to: Reporting when incompatible licenses are used
Up to: LIDESC User Documentation
See also: Example licenses which were evaluated by the OSI as approved or not approved

Librock LIDESC. Software License Analyzer and Compatibility Reporter
Copyright 2001-2002, Forrest J. Cavalier III, Mib Software
You may reproduce verbatim copies of this page, but changing it is not allowed.
Email: Contact