Difference between revisions of "Liblicense"
Line 34: | Line 34: | ||
* [http://code.creativecommons.org/doc/liblicense/ Library Documentation] (generated from source) | * [http://code.creativecommons.org/doc/liblicense/ Library Documentation] (generated from source) | ||
* [[Buildbot]] helps test out liblicense on various platforms. | * [[Buildbot]] helps test out liblicense on various platforms. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 21:08, 27 August 2015
Description of Software | Low-level license metadata integration for applications. |
---|---|
Bug Tracker | Link to Bug Tracker |
Code Repository | Link to Code repository |
Mailing List | Link to Mailing list |
What is liblicense?
liblicense provides a straight-forward way for developers to build license-aware applications. liblicense utilizes a pluggable module system for reading and writing metadata from specific file types, allowing extensibility for specific content types.
- For a brief introduction video, check Asheesh Laroia talking about liblicense
- To see liblicense in action take a look at License tagger, the cross platform file metadata editor.
Future Improvements
- Supports verification URLs for metadata verification
Architecture
Media
See Operating System Mockups for ideas on how liblicense could be integrated into various platforms.
More Information
- Release History and Roadmap
- Desktop Integration
- Screenshots
- RDF Reference
- File Metadata Information
- Library Documentation (generated from source)
- Buildbot helps test out liblicense on various platforms.