Liblicense: Difference between revisions

From CC Public Wiki

Latest revision as of 20:53, 23 September 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.

Features

Extract and write license information for files
Supports enumeration of available licenses
Wraps internationalized license information for Creative Commons licenses
Bindings for dynamic languages (currently Python and Ruby)
Extensible support for file types using module system
No specific GUI library dependency allows applications to build the graphical chooser most appropriate for their platform.

Future Improvements

Supports verification URLs for metadata verification

Architecture

Liblicense Architecture - SVG

Bindings

Python
Ruby

Media

See Operating System Mockups for ideas on how liblicense could be integrated into various platforms.

Download

Latest Release tar.gz
Debian and Ubuntu repositories.
Read the tutorial.

Developers: Using git

If you want to check out the source code and develop on it, use this command:

git clone git://code.creativecommons.org/liblicense.git
git submodule init
git submodule update

That should give you a working copy you can commit to. In case you wonder: the latter two commandsfill the directories

icons/jurisdictions
license.rdf
licenses

with content from external repositories similar to svn:externals for Subversion.

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.

Liblicense
Have an idea about this page? Want to help build the CC ecosystem? Check out the challenges related to Liblicense, or add one of your own below.
Open Challenges
{{#ask: Is Complete::no Related To::Liblicense\|format=table}}
Completed Challenges
{{#ask: Is Complete::yes Related To::Liblicense\|format=table}}
{{#forminput:Challenge\|35	Challenge[related_to]=Liblicense }}

Retrieved from "https://wiki-dev.creativecommons.org/index.php?title=Liblicense&oldid=114426"

Categories:

@@ Line 1: / Line 1: @@
-== System Overview ==
+{{Software Project
+|Description=Low-level license metadata integration for applications.
+|Bug tracker=http://code.creativecommons.org/issues/issue?status=-1,1,2,3,4,5,6,7&@sort=-activity&@search_text=&@dispname=liblicense&@filter=status,project&@group=priority&project=4&@columns=id,activity,title,creator,assignedto,status&@pagesize=50&@startwith=0
+|Code repository=http://code.creativecommons.org/viewgit/liblicense.git/
+|Mailing list=http://lists.ibiblio.org/mailman/listinfo/cc-devel
+}}
+== What is liblicense? ==
-[[Image:Liblicense_system_architecture.png]]
+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.
-[[Image:Liblicense_system_architecture.svg | svg version]]
+* For a brief introduction video, check [http://blip.tv/file/1142312/ Asheesh Laroia talking about liblicense]
+* To see '''liblicense in action''' take a look at [[License tagger]], the cross platform file metadata editor.
-== Config Modules ==
+== Features ==
-* '''in_use'''() - returns whether or not the corresponding config system exists on the computer
-* '''get'''() - returns the current default license uri
-* '''set'''(uri) - sets the default license uri and returns 0 upon success (non-zero for errors)
-== I/O Modules ==
+* Extract and write license information for files
-* '''mime_types''' - null terminated list of handled mime-types (all indicates external storage method which works for any file)
+* Supports enumeration of available licenses
-* '''read'''(filename) - returns the license uri for the given file (embedded license takes precedence)
+* Wraps internationalized license information for Creative Commons licenses
-* '''write'''(filename,uri) - writes the license uri for the given file
+* Bindings for dynamic languages (currently Python and Ruby)
+* Extensible support for file types using module system
+* No specific GUI library dependency allows applications to build the graphical chooser most appropriate for their platform.
-== License Files (.rdf) ==
+== Future Improvements ==
-=== Attributes ===
-* cc:license
+* Supports [[WebStatement|verification]] URLs for metadata verification
-** about
-** permits
-** requires
-** prohibits
-* dc:title - The human readable name of the license.
-* dc:description - Description of the license.
-* dc:coverage - The jurisdiction of the license.
-* dc:language - The language of the license.
-* dc:relation
-** hasVersion - version number
-** isReplacedBy - indicates retired license
-** isBasedOn - indicates ported version
-* dc:license - license the license is available under
-* dc:type - always license
-* dc:creator
-* dc:publisher
-* dc:identifier - URI of license
-=== Example ===
+== Architecture ==
+[[Image:System_architecture.png]]
-== Frontends ==
+[[:Image:System_architecture.svg|Liblicense Architecture - SVG]]
-See [[Desktop Integration]]
-== Timeline ==
+== Bindings ==
-=== 6/18 ===
-* Finalize liblicense API.
-=== 6/25 ===
+* [[Liblicense/Python|Python]]
-* Write liblicense.
+* [[Liblicense/Ruby|Ruby]]
-* Stub config and IO modules.
-=== 7/2 ===
+== Media ==
-* liblicense python bindings.
-=== 7/9 ===
+See [[Operating System Mockups]] for ideas on how '''liblicense''' could be integrated into various platforms.
-* Gconf config module.
-* Nautilus IO module.
-=== 7/16 ===
+== Download ==
-* Nautilus GUI frontend.
-* Gnome control panel frontend.
-=== 7/23 ===
+* [http://mirrors.creativecommons.org/software/liblicense/liblicense-0.8.1.tar.gz Latest Release tar.gz]
-* Sugar Journal backend.
+* Debian and Ubuntu [http://mirrors.creativecommons.org/packages/ repositories].
-* Sugar frontend.
+* Read the [[Liblicense tutorial| tutorial]].
-=== 7/30 ===
+=== Developers: Using git ===
-* Bug hunting.
-* Frontend polishing.
-=== 8/6 ===
+If you want to check out the source code and develop on it, use this command:
-{{stub}}
-=== 8/13 ===
+ git clone git://code.creativecommons.org/liblicense.git
-{{stub}}
+ git submodule init
+ git submodule update
-=== 8/20 ===
+That should give you a working copy you can commit to.  In case you wonder: the latter two commandsfill the directories
-{{stub}}
+* icons/jurisdictions
+* license.rdf
+* licenses
+with content from external repositories similar to ''svn:externals'' for Subversion.
+== More Information ==
+* [[Liblicense/Releases|Release History]] and [[Liblicense/Roadmap|Roadmap]]
+* [[Liblicense/Desktop_Integration|Desktop Integration]]
+* [[Liblicense/Screenshots|Screenshots]]
+* [[License RDF|RDF Reference]]
+* [[Liblicense/Metadata_Table|File Metadata Information]]
+* [http://code.creativecommons.org/doc/liblicense/ Library Documentation] (generated from source)
+* [[Buildbot]] helps test out liblicense on various platforms.
+== See Also ==
+* [[Companion File metadata specification]]
+* [[Tracker CC Indexing]] - also there is a great chart showing progress on reading/writing different filetypes (copied above).
+{{Challenge Enabled}}
+[[Category:Developer]]
+[[Category:Metadata]]
+[[Category:Desktop]]
+[[Category:Labs]]
+[[Category:Tools]]
+[[Category:Specification]]
+[[Category:Operating System]]
+[[Category:Technology]]
+[[Category:Integration]]
+__NOTOC__
+{{lowercase}}