* issues
** <del>Nautilus writes a license to every file whose property dialog is displayed</del>
** <del>license chooser returns devnations -- should we mark this as retired and then not return retired licenses?</del> (added isReplacedBy by/3.0)
** <del>Unicode filename issues? Licenses aren't loaded for some test files with Japanese filenames.</del> (Um, seems to work fine, now) ('''0.4''')
** <del>Update gui_gtk.py to use license chooser API once the above is taken care of</del>
** <del>configure --prefix=/usr/local dies trying to install the python bindings</del>
*** libtool: install: error: cannot install `liblicense.la' to a directory not ending in /usr/lib/python2.4/site-packages/liblicense
*** Update: works after a 'make distclean'
** <del>new license chooser API not wrapped in Ruby</del> ('''0.4''')
** <del>nautilus emblems don't work for me</del> (Needed to touch /usr/share/icons/hicolor on installation)
** <del>No sampling licenses' RDF include the prohibits commericial use statement</del>

* <del>package press release</del>

* <del>tag svn</del>

* package
** <del>source </del>
** <del>rpm</del>
** deb
** <del>ebuild</del> (Exempi, nautilus-python, and Liblicense ebuilds, courtesy of jakin)

== publicity==
=== informal ===
* mailing lists
** cc-devel
** cc-community
* sourceforge
* <del>cc frontpage blog ('''written''')</del>
* digg
* Boing Boing
* lwn@lwn.net
* newstips@heise.de
* PR: theobroma@revelinux.com
* http://www.newsforge.com/submit.pl
* http://slashdot.org/submit.pl
* http://www.desktoplinux.com/ - http://www.desktoplinux.com/cgi-bin/news_post.cgi
* [http://freshmeat.net/ Freshmeat]
* [http://gnomedesktop.org/node/add/story gnome footnotes]
* [http://www.gnomefiles.org/ GnomeFiles] for software which supports Gnome
* http://del.icio.us/
* http://technorati.com/wtf

=== formal ===
* <del>press release</del>
* <del>packaged PRESS file</del>
* [http://prleap.com/ prleap] - another free pr service
* [http://prbuzz.com/ prbuzz] - another free pr service
* nettime-ann - http://www.nettime.org/
* See Kansas City infoZine: http://www.infozine.com/news/stories/op/storiesView/sid/5080/
* http://linuxformat.co.uk/ - webmaster@linuxformat.co.uk
** PR: login and submit news via top of page link
* http://linux-magazine.com/ - info@linux-magazine.com edit@linux-magazine.com
** PR: pr@linux-magazine.com
* http://linuxjournal.com/ - ljeditor@ssc.com
** PR: newproducts@ssc.com
* http://linuxmagazine.com/ - editors@linux-mag.com
** PR: ???
* http://linuxuser.co.uk - http://linuxuser.co.uk/index.php?option=com_content&task=view&id=48&Itemid=40
** PR: terry@linuxuser.co.uk
* http://www.tuxmagazine.com/ - editor@tuxmagazine.com
** PR: ???
* http://www.linuxworld.com/ - mrhinkle@linuxworld.com tim@linuxworld.com
=== other ===
* <del>cc techblog how to</del> ([[Liblicense_tutorial]])

Liblicense 03 release todo

2007-07-31T18:57:58Z

Scott Shawcroft:

Liblicense

2007-07-31T18:16:36Z

Scott Shawcroft: /* Get liblicense */

[[Category:Developer]]
[[Category:Metadata]]
[[Category:Desktop]]
[[Category:Labs]]
[[Category:Tools]]
[[Category:Specification]]
[[Category:Operating System]]
[[Category:Technology]]
A library for managing license metadata, in particular CC licensing information.

The idea of this library started out on the [[IRC]] channel, in a discussion on how to best help boost the community of software
developers working with things related to CC - mostly the metadata format.

Basically, the idea is to write a portable C library that manages metadata for CC licenses, and a bunch of other licenses of interest to the community.

The library will produce licensing information based on the specifications of calling libraries and programs. In addition to generating text for specific licenses, it will also allow an application to enumerate which licenses are currently available and provide descriptive text for each license, and for license features. It should also provide an easy way to specify "verify at" URLs.

The benefit of this library is that applications linking to it can correctly offer licensing choices, and these choices can be transparently updated through package managers as license versions are updated. Human readable descriptions will also be internationalized, preferably using the same .po files used by the CC web site. Hence liblicense will take advantage of package updating and i18n systems to allow applications to always provide c
current and correct licensing choices and license text.

Part of the project is also to provide wrappers for the library for other languages, and to help external developers add metadata support to their projects. A good start will probably be to wrap the library for Python, and use it for ccpublisher.

We will also integrate a module system so that libraries can be used to embed and extract metadata in/from common formats.

As liblicense itself deals only with text strings, we can also make GUI libraries to provide dialogs which present these strings to the user in desktop or web applications. This layering ensures that such dialogs present consistent licensing choices.

== Get liblicense ==

* [https://sourceforge.net/project/showfiles.php?group_id=80503&package_id=238700 Latest Release from Sourceforge.net]
* Checkout liblicense module from [[SVN]]
* Read the [[Liblicense tutorial| tutorial]].

=== Screenshots ===
<gallery perrow="3">
Image:Ll nautilus emblem.png|Nautilus emblem support.
Image:Ll nautilus.png|Nautilus file properties.
Image:Ll default 2.png|GTK default system license.
Image:Ll dolphin.png|KDE4 dolphin file properties.
Image:Ll kde default license.png|KDE4 default system license.
</gallery>

== System Overview ==

=== Purpose ===
To provide a simple way for developers to make their applications license aware. Additionally, supplemental modules aim to provide a method for users to track licenses of files on their system. This project complements [[Companion File metadata specification]] and [[Tracker CC Indexing]].

=== Architecture ===
[[Image:System_architecture.png]]

=== Implementation ===
This library will be implemented in C to provide maximum portability.

=== Interface ===
* module_wrangler
** get_config_modules() - ''returns a null terminates list of available config modules.''
** get_io_modules() - ''returns a null terminates list of available io modules.''
** get_module_symbol(module,symbol) - ''returns the requested symbol.''
** module_init(module) - ''Loads the module and calls its init function.''
** module_shutdown(module) - ''Calls the shutdown method of the module and unloads it.''
** io_module_mime_types(module0 - ''returns a null-terminated list of the supported mime-types.''
* read_license
** read(filename) - ''returns the uri of the license of the given file.''
** module_read(filename,module) - ''returns the uri of the license of the given file while using the given module.''
* write_license
** write(filename,uri) - ''writes the given license to the given file using all applicable modules.''
** module_write(filename,module,uri) - ''writes the given license to the given file using the given module.''
* system_default
** set_default(uri)
** get_default()
* system_licenses
** get_jurisdiction(uri) - ''returns the jurisdiction for the given license.''
** get_name(uri) – ''returns the name of the license.''
** get_version(uri) – ''returns the version of the license.''
** get_prohibits(uri)
** get_permits(uri)
** get_requires(uri)
** verify_uri(uri) - ''returns whether or not the given uri is recognized by the system.''
** get_all_licenses() - ''returns a null-terminated list of all general license uris available for new works.''
** get_licenses(juris_t) - ''returns a null-terminated list of all general licenses in a family.''

=== Data Structure ===
* Data Types (informal)
** uri
** name
** notification
** deed
** sampling

=== Config Modules ===
* '''init'''() - starts the module
* '''shutdown'''() - shuts the module down
* '''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 ===
I/O modules are shared objects that call LL_MODULE_DEFINE(name,description,version,features,mime_types,init_func,read_func,write_func).

* '''name'''
* '''description'''
* '''version'''
* '''features''' - If the module embeds the license within the file, pass LL_FEATURES_EMBED
* '''mime_types''' - A space-separated string of supported mime-types, or NULL if mime-type agnostic (i.e. XMP sidecar)
* '''init_func''' - This function will be called once before the module is used
* '''read_func''' - Function to be called when requested to read a license from a file. It takes a filename and returns the license URI, or NULL if no license is present. Should return an 'int' indicating success or failure.
* '''write_func''' - Function to be called when requested to write a license to a file. The first parameter is the filename and the second is the license URI to write. Should return an 'int' indicating success or failure.

=== Bindings ===
*Python

== License Files (.rdf) ==
=== Attributes ===

* cc:license
** 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. (country code from [http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html ISO3166])
* dc:relation
** hasVersion - version number
** isReplacedBy - indicates retired license ([http://www.ietf.org/rfc/rfc2396.txt URI])
** isBasedOn - indicates ported version ([http://www.ietf.org/rfc/rfc2396.txt URI])
* dc:type - always "License"
* dc:creator
* dc:publisher
* dc:identifier - URI of license ([http://www.ietf.org/rfc/rfc2396.txt URI])

=== Example ===
<pre><rdf:RDF
xmlns="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dcq="http://purl.org/dc/terms/"
>
<rdf:Description rdf:about="http://creativecommons.org/licenses/by-nd/2.0/za/">
<dc:title>Creative Commons Attribution No Derivatives</dc:title>
<dc:description>This license allows for redistribution, commercial and non-commercial,
as long as it is passed along unchanged and in whole, with credit to you.</dc:description>
<dc:coverage>
<dcq:ISO3166>
<rdf:value>za</rdf:value>
</dcq:ISO3166>
</dc:coverage>
<dc:hasVersion>2.0</dc:hasVersion>
<dc:isReplacedBy>
<dcq:URI>
<rdf:value>http://creativecommons.org/licenses/by-nd/2.5/za/</rdf:value>
</dcq:URI>
</dc:isReplacedBy>
<dc:isBasedOn>
<dcq:URI>
<rdf:value>http://creativecommons.org/licenses/by-nd/2.5/</rdf:value>
</dcq:URI>
</dc:isBasedOn>
<dc:type>License</dc:type>
<dc:creator>iCommons</dc:creator>
<dc:publisher>Creative Commons</dc:publisher>
<dc:identifier>http://creativecommons.org/licenses/by-nd/2.0/za/</dc:identifier>

<rdf:type rdf:resource="http://creativecommons.org/ns#License"/>
<permits rdf:resource="http://creativecommons.org/ns#Distribution"/>
<permits rdf:resource="http://creativecommons.org/ns#Reproduction"/>
<requires rdf:resource="http://creativecommons.org/ns#Attribution"/>
<requires rdf:resource="http://creativecommons.org/ns#Notice"/>
</rdf:Description>
</rdf:RDF></pre>

=== Example (i18n) ===
<pre><rdf:RDF
xmlns="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dcq="http://purl.org/dc/terms/"
>
<rdf:Description rdf:about="http://creativecommons.org/licenses/by-nd/2.0/">
<dc:title>
<rdf:Alt>
<rdf:li xml:lang="x-default">Creative Commons Attribution No Derivatives</rdf:li>
<rdf:li xml:lang="es-cl">Creative Commons Atribución-SinDerivadas</rdf:li>
</rdf:Alt>
</dc:title>
<dc:description>
<rdf:Alt>
<rdf:li xml:lang="x-default">This license allows for redistribution, commercial and non-commercial,
as long as it is passed along unchanged and in whole, with credit to you.</rdf:li>
</rdf:Alt>
</dc:description>
<dc:coverage>
<dcq:ISO3166>
<rdf:value>us</rdf:value>
</dcq:ISO3166>
</dc:coverage>
<dc:hasVersion>2.0</dc:hasVersion>
<dc:isReplacedBy>
<dcq:URI>
<rdf:value>http://creativecommons.org/licenses/by-nd/2.5/</rdf:value>
</dcq:URI>
</dc:isReplacedBy>
<dc:type>License</dc:type>
<dc:creator>Creative Commons</dc:creator>
<dc:publisher>Creative Commons</dc:publisher>
<dc:identifier>http://creativecommons.org/licenses/by-nd/2.0/</dc:identifier>

<rdf:type rdf:resource="http://creativecommons.org/ns#License"/>
<permits rdf:resource="http://creativecommons.org/ns#Distribution"/>
<permits rdf:resource="http://creativecommons.org/ns#Reproduction"/>
<requires rdf:resource="http://creativecommons.org/ns#Attribution"/>
<requires rdf:resource="http://creativecommons.org/ns#Notice"/>
</rdf:Description>
</rdf:RDF></pre>

== Desktop Integration ==

See [[Desktop Integration]]

=== Gnome Summit Discussion ===

At the Gnome Summit we explored adding CC licensing to various Gnome applications. Application developers appeared to have a few needs:

* They want to display the appropriate icon (or other) for a particular license. For instance, AbiWord could display a small icon representing license status in the tool bar. Music players could display the icon in the controls area. A music streaming app might want to play a 5 second "Now entering the Creative Commons" chime (much like radio station identification, but for licenses).
* They want to allow the user to easily select a license. This would probably be a wizard that asks the user questions and tries to select the most appropriate license from all that it knows about. Much like a file selection dialog, but navigating licenses instead of your file system.

A low-level liblicense could handle XML parsing required. It would allow the client to determine the questions that need to be asked to select a license, and to download any icons, blurbs, etc for all known license types.

The low-level library solves the first problem above, but not the second. It's still too difficult to ask the user to select a license. Layered on top of the low-level library would be any number of high level libraries that would convert the textual questions into GUI widgets and present them using the appropriate toolkit (GTK+ / KDE / Cocoa / Win32 / etc). This way, adding license awareness to an application should be as easy as "license=SFGetLicense(); saveDocument(license)".

=== Accessories ===
* CLI
** license (bundled) - simple cli program to license files.
** .license/default engine - a .license directory will contain the user's default setting, other config info and the user's licenses.
* Gnome
** Gnome Settings frontend. - set the default license through the gnome settings interface.
** Nautilus Frontend Extension - set and read licenses through nautilus.
** License chooser (app.) - license chooser for setting default and per file licenses. (GUI license)
** GTK widget
** Gconf config module.
* Sugar
** Journal Backend
** Journal Frontend
* KDE3 (???)
* KDE4

== Timeline ==
=== 6/18 ===
* Finalize liblicense API.

=== 6/25 ===
* Write liblicense.
* Stub config and IO modules.

=== 7/2 ===

=== 7/9 ===
* .license/default set default
* gnome settings UI

=== 7/16 ===
* Nautilus GUI frontend.
* Gnome control panel frontend.

=== 7/23 ===
* Sugar Journal backend.
* Sugar frontend.

=== 7/30 ===
* Bug hunting.
* Frontend polishing.

=== 8/6 ===
* shoot for milestone 3 for linuxworld pr

=== 8/13 ===
{{stub}}

=== 8/20 ===
{{stub}}

== Milestones ==
=== 0.1 ===
* Initial release. ('''done''')
* All CC licenses. ('''done''')
* CLI tools. ('''done''')
* Modules. ('''done''')
** Exempi embed. ('''done''')
** Exempi XMP sidecar. ('''done''')
* Make light blog post about release on techblog, explain early state ('''done''')

=== 0.3 ===
* Optimization - namely caching in some way. Should not access file every attribute request.
* Gnome tools. ('''done''')
** Nautilus frontend. ('''done''')
** Gnome settings frontend. ('''done''')
** GTK License chooser. (See mockups) ('''done''')
* File embed preference over external storage. (Use external only as needed.) ('''done''')
* Store default jurisdiction. ('''done - default license is in default jurisdiction''')
* Modules.
** vorbiscomment ('''done''')
** ...
* Do big release on main CC blog and across various chat and mailing lists to pick-up people, lots of them...
* Do [[liblicense 03 release todo]]

=== 0.4 ===
* Further refinement.
* Sugar tools.
** Journal integration.
* Another major announcement
* [[liblicense 04 release todo]]

Liblicense 03 release todo

2007-07-31T18:01:52Z

Scott Shawcroft:

Liblicense

2007-07-31T17:27:38Z

Scott Shawcroft: /* Screenshots */ gallery

[[Category:Developer]]
[[Category:Metadata]]
[[Category:Desktop]]
[[Category:Labs]]
[[Category:Tools]]
[[Category:Specification]]
[[Category:Operating System]]
[[Category:Technology]]
A library for managing license metadata, in particular CC licensing information.

The idea of this library started out on the [[IRC]] channel, in a discussion on how to best help boost the community of software
developers working with things related to CC - mostly the metadata format.

Basically, the idea is to write a portable C library that manages metadata for CC licenses, and a bunch of other licenses of interest to the community.

The library will produce licensing information based on the specifications of calling libraries and programs. In addition to generating text for specific licenses, it will also allow an application to enumerate which licenses are currently available and provide descriptive text for each license, and for license features. It should also provide an easy way to specify "verify at" URLs.

The benefit of this library is that applications linking to it can correctly offer licensing choices, and these choices can be transparently updated through package managers as license versions are updated. Human readable descriptions will also be internationalized, preferably using the same .po files used by the CC web site. Hence liblicense will take advantage of package updating and i18n systems to allow applications to always provide c
current and correct licensing choices and license text.

Part of the project is also to provide wrappers for the library for other languages, and to help external developers add metadata support to their projects. A good start will probably be to wrap the library for Python, and use it for ccpublisher.

We will also integrate a module system so that libraries can be used to embed and extract metadata in/from common formats.

As liblicense itself deals only with text strings, we can also make GUI libraries to provide dialogs which present these strings to the user in desktop or web applications. This layering ensures that such dialogs present consistent licensing choices.

== Get liblicense ==

* [https://sourceforge.net/project/showfiles.php?group_id=80503&package_id=238700 Latest Release from Sourceforge.net]
* Checkout liblicense module from [[SVN]]

=== Screenshots ===
<gallery perrow="3">
Image:Ll nautilus emblem.png|Nautilus emblem support.
Image:Ll nautilus.png|Nautilus file properties.
Image:Ll default 2.png|GTK default system license.
Image:Ll dolphin.png|KDE4 dolphin file properties.
Image:Ll kde default license.png|KDE4 default system license.
</gallery>

== System Overview ==

=== Purpose ===
To provide a simple way for developers to make their applications license aware. Additionally, supplemental modules aim to provide a method for users to track licenses of files on their system. This project complements [[Companion File metadata specification]] and [[Tracker CC Indexing]].

=== Architecture ===
[[Image:System_architecture.png]]

=== Implementation ===
This library will be implemented in C to provide maximum portability.

=== Interface ===
* module_wrangler
** get_config_modules() - ''returns a null terminates list of available config modules.''
** get_io_modules() - ''returns a null terminates list of available io modules.''
** get_module_symbol(module,symbol) - ''returns the requested symbol.''
** module_init(module) - ''Loads the module and calls its init function.''
** module_shutdown(module) - ''Calls the shutdown method of the module and unloads it.''
** io_module_mime_types(module0 - ''returns a null-terminated list of the supported mime-types.''
* read_license
** read(filename) - ''returns the uri of the license of the given file.''
** module_read(filename,module) - ''returns the uri of the license of the given file while using the given module.''
* write_license
** write(filename,uri) - ''writes the given license to the given file using all applicable modules.''
** module_write(filename,module,uri) - ''writes the given license to the given file using the given module.''
* system_default
** set_default(uri)
** get_default()
* system_licenses
** get_jurisdiction(uri) - ''returns the jurisdiction for the given license.''
** get_name(uri) – ''returns the name of the license.''
** get_version(uri) – ''returns the version of the license.''
** get_prohibits(uri)
** get_permits(uri)
** get_requires(uri)
** verify_uri(uri) - ''returns whether or not the given uri is recognized by the system.''
** get_all_licenses() - ''returns a null-terminated list of all general license uris available for new works.''
** get_licenses(juris_t) - ''returns a null-terminated list of all general licenses in a family.''

=== Data Structure ===
* Data Types (informal)
** uri
** name
** notification
** deed
** sampling

=== Config Modules ===
* '''init'''() - starts the module
* '''shutdown'''() - shuts the module down
* '''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 ===
I/O modules are shared objects that call LL_MODULE_DEFINE(name,description,version,features,mime_types,init_func,read_func,write_func).

* '''name'''
* '''description'''
* '''version'''
* '''features''' - If the module embeds the license within the file, pass LL_FEATURES_EMBED
* '''mime_types''' - A space-separated string of supported mime-types, or NULL if mime-type agnostic (i.e. XMP sidecar)
* '''init_func''' - This function will be called once before the module is used
* '''read_func''' - Function to be called when requested to read a license from a file. It takes a filename and returns the license URI, or NULL if no license is present. Should return an 'int' indicating success or failure.
* '''write_func''' - Function to be called when requested to write a license to a file. The first parameter is the filename and the second is the license URI to write. Should return an 'int' indicating success or failure.

=== Bindings ===
*Python

== License Files (.rdf) ==
=== Attributes ===

* cc:license
** 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. (country code from [http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html ISO3166])
* dc:relation
** hasVersion - version number
** isReplacedBy - indicates retired license ([http://www.ietf.org/rfc/rfc2396.txt URI])
** isBasedOn - indicates ported version ([http://www.ietf.org/rfc/rfc2396.txt URI])
* dc:type - always "License"
* dc:creator
* dc:publisher
* dc:identifier - URI of license ([http://www.ietf.org/rfc/rfc2396.txt URI])

=== Example ===
<pre><rdf:RDF
xmlns="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dcq="http://purl.org/dc/terms/"
>
<rdf:Description rdf:about="http://creativecommons.org/licenses/by-nd/2.0/za/">
<dc:title>Creative Commons Attribution No Derivatives</dc:title>
<dc:description>This license allows for redistribution, commercial and non-commercial,
as long as it is passed along unchanged and in whole, with credit to you.</dc:description>
<dc:coverage>
<dcq:ISO3166>
<rdf:value>za</rdf:value>
</dcq:ISO3166>
</dc:coverage>
<dc:hasVersion>2.0</dc:hasVersion>
<dc:isReplacedBy>
<dcq:URI>
<rdf:value>http://creativecommons.org/licenses/by-nd/2.5/za/</rdf:value>
</dcq:URI>
</dc:isReplacedBy>
<dc:isBasedOn>
<dcq:URI>
<rdf:value>http://creativecommons.org/licenses/by-nd/2.5/</rdf:value>
</dcq:URI>
</dc:isBasedOn>
<dc:type>License</dc:type>
<dc:creator>iCommons</dc:creator>
<dc:publisher>Creative Commons</dc:publisher>
<dc:identifier>http://creativecommons.org/licenses/by-nd/2.0/za/</dc:identifier>

<rdf:type rdf:resource="http://creativecommons.org/ns#License"/>
<permits rdf:resource="http://creativecommons.org/ns#Distribution"/>
<permits rdf:resource="http://creativecommons.org/ns#Reproduction"/>
<requires rdf:resource="http://creativecommons.org/ns#Attribution"/>
<requires rdf:resource="http://creativecommons.org/ns#Notice"/>
</rdf:Description>
</rdf:RDF></pre>

=== Example (i18n) ===
<pre><rdf:RDF
xmlns="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dcq="http://purl.org/dc/terms/"
>
<rdf:Description rdf:about="http://creativecommons.org/licenses/by-nd/2.0/">
<dc:title>
<rdf:Alt>
<rdf:li xml:lang="x-default">Creative Commons Attribution No Derivatives</rdf:li>
<rdf:li xml:lang="es-cl">Creative Commons Atribución-SinDerivadas</rdf:li>
</rdf:Alt>
</dc:title>
<dc:description>
<rdf:Alt>
<rdf:li xml:lang="x-default">This license allows for redistribution, commercial and non-commercial,
as long as it is passed along unchanged and in whole, with credit to you.</rdf:li>
</rdf:Alt>
</dc:description>
<dc:coverage>
<dcq:ISO3166>
<rdf:value>us</rdf:value>
</dcq:ISO3166>
</dc:coverage>
<dc:hasVersion>2.0</dc:hasVersion>
<dc:isReplacedBy>
<dcq:URI>
<rdf:value>http://creativecommons.org/licenses/by-nd/2.5/</rdf:value>
</dcq:URI>
</dc:isReplacedBy>
<dc:type>License</dc:type>
<dc:creator>Creative Commons</dc:creator>
<dc:publisher>Creative Commons</dc:publisher>
<dc:identifier>http://creativecommons.org/licenses/by-nd/2.0/</dc:identifier>

<rdf:type rdf:resource="http://creativecommons.org/ns#License"/>
<permits rdf:resource="http://creativecommons.org/ns#Distribution"/>
<permits rdf:resource="http://creativecommons.org/ns#Reproduction"/>
<requires rdf:resource="http://creativecommons.org/ns#Attribution"/>
<requires rdf:resource="http://creativecommons.org/ns#Notice"/>
</rdf:Description>
</rdf:RDF></pre>

== Desktop Integration ==

See [[Desktop Integration]]

=== Gnome Summit Discussion ===

At the Gnome Summit we explored adding CC licensing to various Gnome applications. Application developers appeared to have a few needs:

* They want to display the appropriate icon (or other) for a particular license. For instance, AbiWord could display a small icon representing license status in the tool bar. Music players could display the icon in the controls area. A music streaming app might want to play a 5 second "Now entering the Creative Commons" chime (much like radio station identification, but for licenses).
* They want to allow the user to easily select a license. This would probably be a wizard that asks the user questions and tries to select the most appropriate license from all that it knows about. Much like a file selection dialog, but navigating licenses instead of your file system.

A low-level liblicense could handle XML parsing required. It would allow the client to determine the questions that need to be asked to select a license, and to download any icons, blurbs, etc for all known license types.

The low-level library solves the first problem above, but not the second. It's still too difficult to ask the user to select a license. Layered on top of the low-level library would be any number of high level libraries that would convert the textual questions into GUI widgets and present them using the appropriate toolkit (GTK+ / KDE / Cocoa / Win32 / etc). This way, adding license awareness to an application should be as easy as "license=SFGetLicense(); saveDocument(license)".

=== Accessories ===
* CLI
** license (bundled) - simple cli program to license files.
** .license/default engine - a .license directory will contain the user's default setting, other config info and the user's licenses.
* Gnome
** Gnome Settings frontend. - set the default license through the gnome settings interface.
** Nautilus Frontend Extension - set and read licenses through nautilus.
** License chooser (app.) - license chooser for setting default and per file licenses. (GUI license)
** GTK widget
** Gconf config module.
* Sugar
** Journal Backend
** Journal Frontend
* KDE3 (???)
* KDE4

== Timeline ==
=== 6/18 ===
* Finalize liblicense API.

=== 6/25 ===
* Write liblicense.
* Stub config and IO modules.

=== 7/2 ===

=== 7/9 ===
* .license/default set default
* gnome settings UI

=== 7/16 ===
* Nautilus GUI frontend.
* Gnome control panel frontend.

=== 7/23 ===
* Sugar Journal backend.
* Sugar frontend.

=== 7/30 ===
* Bug hunting.
* Frontend polishing.

=== 8/6 ===
* shoot for milestone 3 for linuxworld pr

=== 8/13 ===
{{stub}}

=== 8/20 ===
{{stub}}

== Milestones ==
=== 0.1 ===
* Initial release. ('''done''')
* All CC licenses. ('''done''')
* CLI tools. ('''done''')
* Modules. ('''done''')
** Exempi embed. ('''done''')
** Exempi XMP sidecar. ('''done''')
* Make light blog post about release on techblog, explain early state ('''done''')

=== 0.3 ===
* Optimization - namely caching in some way. Should not access file every attribute request.
* Gnome tools. ('''done''')
** Nautilus frontend. ('''done''')
** Gnome settings frontend. ('''done''')
** GTK License chooser. (See mockups) ('''done''')
* File embed preference over external storage. (Use external only as needed.) ('''done''')
* Store default jurisdiction. ('''done - default license is in default jurisdiction''')
* Modules.
** vorbiscomment ('''done''')
** ...
* Do big release on main CC blog and across various chat and mailing lists to pick-up people, lots of them...
* Do [[liblicense 03 release todo]]

=== 0.4 ===
* Further refinement.
* Sugar tools.
** Journal integration.
* Another major announcement
* [[liblicense 04 release todo]]

Liblicense

2007-07-31T17:25:54Z

Scott Shawcroft: /* Screenshots */

[[Category:Developer]]
[[Category:Metadata]]
[[Category:Desktop]]
[[Category:Labs]]
[[Category:Tools]]
[[Category:Specification]]
[[Category:Operating System]]
[[Category:Technology]]
A library for managing license metadata, in particular CC licensing information.

The idea of this library started out on the [[IRC]] channel, in a discussion on how to best help boost the community of software
developers working with things related to CC - mostly the metadata format.

Basically, the idea is to write a portable C library that manages metadata for CC licenses, and a bunch of other licenses of interest to the community.

The library will produce licensing information based on the specifications of calling libraries and programs. In addition to generating text for specific licenses, it will also allow an application to enumerate which licenses are currently available and provide descriptive text for each license, and for license features. It should also provide an easy way to specify "verify at" URLs.

The benefit of this library is that applications linking to it can correctly offer licensing choices, and these choices can be transparently updated through package managers as license versions are updated. Human readable descriptions will also be internationalized, preferably using the same .po files used by the CC web site. Hence liblicense will take advantage of package updating and i18n systems to allow applications to always provide c
current and correct licensing choices and license text.

Part of the project is also to provide wrappers for the library for other languages, and to help external developers add metadata support to their projects. A good start will probably be to wrap the library for Python, and use it for ccpublisher.

We will also integrate a module system so that libraries can be used to embed and extract metadata in/from common formats.

As liblicense itself deals only with text strings, we can also make GUI libraries to provide dialogs which present these strings to the user in desktop or web applications. This layering ensures that such dialogs present consistent licensing choices.

== Get liblicense ==

* [https://sourceforge.net/project/showfiles.php?group_id=80503&package_id=238700 Latest Release from Sourceforge.net]
* Checkout liblicense module from [[SVN]]

=== Screenshots ===
<gallery>
Image:Ll nautilus emblem.png|Nautilus emblem support.
Image:Ll nautilus.png|Nautilus file properties.
Image:Ll default 2.png|GTK default system license.
Image:Ll dolphin.png|KDE4 dolphin file properties.
Image:Ll kde default license.png|KDE4 default system license.
</gallery>

== System Overview ==

=== Purpose ===
To provide a simple way for developers to make their applications license aware. Additionally, supplemental modules aim to provide a method for users to track licenses of files on their system. This project complements [[Companion File metadata specification]] and [[Tracker CC Indexing]].

=== Architecture ===
[[Image:System_architecture.png]]

=== Implementation ===
This library will be implemented in C to provide maximum portability.

=== Interface ===
* module_wrangler
** get_config_modules() - ''returns a null terminates list of available config modules.''
** get_io_modules() - ''returns a null terminates list of available io modules.''
** get_module_symbol(module,symbol) - ''returns the requested symbol.''
** module_init(module) - ''Loads the module and calls its init function.''
** module_shutdown(module) - ''Calls the shutdown method of the module and unloads it.''
** io_module_mime_types(module0 - ''returns a null-terminated list of the supported mime-types.''
* read_license
** read(filename) - ''returns the uri of the license of the given file.''
** module_read(filename,module) - ''returns the uri of the license of the given file while using the given module.''
* write_license
** write(filename,uri) - ''writes the given license to the given file using all applicable modules.''
** module_write(filename,module,uri) - ''writes the given license to the given file using the given module.''
* system_default
** set_default(uri)
** get_default()
* system_licenses
** get_jurisdiction(uri) - ''returns the jurisdiction for the given license.''
** get_name(uri) – ''returns the name of the license.''
** get_version(uri) – ''returns the version of the license.''
** get_prohibits(uri)
** get_permits(uri)
** get_requires(uri)
** verify_uri(uri) - ''returns whether or not the given uri is recognized by the system.''
** get_all_licenses() - ''returns a null-terminated list of all general license uris available for new works.''
** get_licenses(juris_t) - ''returns a null-terminated list of all general licenses in a family.''

=== Data Structure ===
* Data Types (informal)
** uri
** name
** notification
** deed
** sampling

=== Config Modules ===
* '''init'''() - starts the module
* '''shutdown'''() - shuts the module down
* '''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 ===
I/O modules are shared objects that call LL_MODULE_DEFINE(name,description,version,features,mime_types,init_func,read_func,write_func).

* '''name'''
* '''description'''
* '''version'''
* '''features''' - If the module embeds the license within the file, pass LL_FEATURES_EMBED
* '''mime_types''' - A space-separated string of supported mime-types, or NULL if mime-type agnostic (i.e. XMP sidecar)
* '''init_func''' - This function will be called once before the module is used
* '''read_func''' - Function to be called when requested to read a license from a file. It takes a filename and returns the license URI, or NULL if no license is present. Should return an 'int' indicating success or failure.
* '''write_func''' - Function to be called when requested to write a license to a file. The first parameter is the filename and the second is the license URI to write. Should return an 'int' indicating success or failure.

=== Bindings ===
*Python

== License Files (.rdf) ==
=== Attributes ===

* cc:license
** 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. (country code from [http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html ISO3166])
* dc:relation
** hasVersion - version number
** isReplacedBy - indicates retired license ([http://www.ietf.org/rfc/rfc2396.txt URI])
** isBasedOn - indicates ported version ([http://www.ietf.org/rfc/rfc2396.txt URI])
* dc:type - always "License"
* dc:creator
* dc:publisher
* dc:identifier - URI of license ([http://www.ietf.org/rfc/rfc2396.txt URI])

=== Example ===
<pre><rdf:RDF
xmlns="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dcq="http://purl.org/dc/terms/"
>
<rdf:Description rdf:about="http://creativecommons.org/licenses/by-nd/2.0/za/">
<dc:title>Creative Commons Attribution No Derivatives</dc:title>
<dc:description>This license allows for redistribution, commercial and non-commercial,
as long as it is passed along unchanged and in whole, with credit to you.</dc:description>
<dc:coverage>
<dcq:ISO3166>
<rdf:value>za</rdf:value>
</dcq:ISO3166>
</dc:coverage>
<dc:hasVersion>2.0</dc:hasVersion>
<dc:isReplacedBy>
<dcq:URI>
<rdf:value>http://creativecommons.org/licenses/by-nd/2.5/za/</rdf:value>
</dcq:URI>
</dc:isReplacedBy>
<dc:isBasedOn>
<dcq:URI>
<rdf:value>http://creativecommons.org/licenses/by-nd/2.5/</rdf:value>
</dcq:URI>
</dc:isBasedOn>
<dc:type>License</dc:type>
<dc:creator>iCommons</dc:creator>
<dc:publisher>Creative Commons</dc:publisher>
<dc:identifier>http://creativecommons.org/licenses/by-nd/2.0/za/</dc:identifier>

<rdf:type rdf:resource="http://creativecommons.org/ns#License"/>
<permits rdf:resource="http://creativecommons.org/ns#Distribution"/>
<permits rdf:resource="http://creativecommons.org/ns#Reproduction"/>
<requires rdf:resource="http://creativecommons.org/ns#Attribution"/>
<requires rdf:resource="http://creativecommons.org/ns#Notice"/>
</rdf:Description>
</rdf:RDF></pre>

=== Example (i18n) ===
<pre><rdf:RDF
xmlns="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dcq="http://purl.org/dc/terms/"
>
<rdf:Description rdf:about="http://creativecommons.org/licenses/by-nd/2.0/">
<dc:title>
<rdf:Alt>
<rdf:li xml:lang="x-default">Creative Commons Attribution No Derivatives</rdf:li>
<rdf:li xml:lang="es-cl">Creative Commons Atribución-SinDerivadas</rdf:li>
</rdf:Alt>
</dc:title>
<dc:description>
<rdf:Alt>
<rdf:li xml:lang="x-default">This license allows for redistribution, commercial and non-commercial,
as long as it is passed along unchanged and in whole, with credit to you.</rdf:li>
</rdf:Alt>
</dc:description>
<dc:coverage>
<dcq:ISO3166>
<rdf:value>us</rdf:value>
</dcq:ISO3166>
</dc:coverage>
<dc:hasVersion>2.0</dc:hasVersion>
<dc:isReplacedBy>
<dcq:URI>
<rdf:value>http://creativecommons.org/licenses/by-nd/2.5/</rdf:value>
</dcq:URI>
</dc:isReplacedBy>
<dc:type>License</dc:type>
<dc:creator>Creative Commons</dc:creator>
<dc:publisher>Creative Commons</dc:publisher>
<dc:identifier>http://creativecommons.org/licenses/by-nd/2.0/</dc:identifier>

<rdf:type rdf:resource="http://creativecommons.org/ns#License"/>
<permits rdf:resource="http://creativecommons.org/ns#Distribution"/>
<permits rdf:resource="http://creativecommons.org/ns#Reproduction"/>
<requires rdf:resource="http://creativecommons.org/ns#Attribution"/>
<requires rdf:resource="http://creativecommons.org/ns#Notice"/>
</rdf:Description>
</rdf:RDF></pre>

== Desktop Integration ==

See [[Desktop Integration]]

=== Gnome Summit Discussion ===

At the Gnome Summit we explored adding CC licensing to various Gnome applications. Application developers appeared to have a few needs:

* They want to display the appropriate icon (or other) for a particular license. For instance, AbiWord could display a small icon representing license status in the tool bar. Music players could display the icon in the controls area. A music streaming app might want to play a 5 second "Now entering the Creative Commons" chime (much like radio station identification, but for licenses).
* They want to allow the user to easily select a license. This would probably be a wizard that asks the user questions and tries to select the most appropriate license from all that it knows about. Much like a file selection dialog, but navigating licenses instead of your file system.

A low-level liblicense could handle XML parsing required. It would allow the client to determine the questions that need to be asked to select a license, and to download any icons, blurbs, etc for all known license types.

The low-level library solves the first problem above, but not the second. It's still too difficult to ask the user to select a license. Layered on top of the low-level library would be any number of high level libraries that would convert the textual questions into GUI widgets and present them using the appropriate toolkit (GTK+ / KDE / Cocoa / Win32 / etc). This way, adding license awareness to an application should be as easy as "license=SFGetLicense(); saveDocument(license)".

=== Accessories ===
* CLI
** license (bundled) - simple cli program to license files.
** .license/default engine - a .license directory will contain the user's default setting, other config info and the user's licenses.
* Gnome
** Gnome Settings frontend. - set the default license through the gnome settings interface.
** Nautilus Frontend Extension - set and read licenses through nautilus.
** License chooser (app.) - license chooser for setting default and per file licenses. (GUI license)
** GTK widget
** Gconf config module.
* Sugar
** Journal Backend
** Journal Frontend
* KDE3 (???)
* KDE4

== Timeline ==
=== 6/18 ===
* Finalize liblicense API.

=== 6/25 ===
* Write liblicense.
* Stub config and IO modules.

=== 7/2 ===

=== 7/9 ===
* .license/default set default
* gnome settings UI

=== 7/16 ===
* Nautilus GUI frontend.
* Gnome control panel frontend.

=== 7/23 ===
* Sugar Journal backend.
* Sugar frontend.

=== 7/30 ===
* Bug hunting.
* Frontend polishing.

=== 8/6 ===
* shoot for milestone 3 for linuxworld pr

=== 8/13 ===
{{stub}}

=== 8/20 ===
{{stub}}

== Milestones ==
=== 0.1 ===
* Initial release. ('''done''')
* All CC licenses. ('''done''')
* CLI tools. ('''done''')
* Modules. ('''done''')
** Exempi embed. ('''done''')
** Exempi XMP sidecar. ('''done''')
* Make light blog post about release on techblog, explain early state ('''done''')

=== 0.3 ===
* Optimization - namely caching in some way. Should not access file every attribute request.
* Gnome tools. ('''done''')
** Nautilus frontend. ('''done''')
** Gnome settings frontend. ('''done''')
** GTK License chooser. (See mockups) ('''done''')
* File embed preference over external storage. (Use external only as needed.) ('''done''')
* Store default jurisdiction. ('''done - default license is in default jurisdiction''')
* Modules.
** vorbiscomment ('''done''')
** ...
* Do big release on main CC blog and across various chat and mailing lists to pick-up people, lots of them...
* Do [[liblicense 03 release todo]]

=== 0.4 ===
* Further refinement.
* Sugar tools.
** Journal integration.
* Another major announcement
* [[liblicense 04 release todo]]

Liblicense

2007-07-31T17:21:22Z

Scott Shawcroft: /* Screenshots */ thumbnails

[[Category:Developer]]
[[Category:Metadata]]
[[Category:Desktop]]
[[Category:Labs]]
[[Category:Tools]]
[[Category:Specification]]
[[Category:Operating System]]
[[Category:Technology]]
A library for managing license metadata, in particular CC licensing information.

The idea of this library started out on the [[IRC]] channel, in a discussion on how to best help boost the community of software
developers working with things related to CC - mostly the metadata format.

Basically, the idea is to write a portable C library that manages metadata for CC licenses, and a bunch of other licenses of interest to the community.

The library will produce licensing information based on the specifications of calling libraries and programs. In addition to generating text for specific licenses, it will also allow an application to enumerate which licenses are currently available and provide descriptive text for each license, and for license features. It should also provide an easy way to specify "verify at" URLs.

The benefit of this library is that applications linking to it can correctly offer licensing choices, and these choices can be transparently updated through package managers as license versions are updated. Human readable descriptions will also be internationalized, preferably using the same .po files used by the CC web site. Hence liblicense will take advantage of package updating and i18n systems to allow applications to always provide c
current and correct licensing choices and license text.

Part of the project is also to provide wrappers for the library for other languages, and to help external developers add metadata support to their projects. A good start will probably be to wrap the library for Python, and use it for ccpublisher.

We will also integrate a module system so that libraries can be used to embed and extract metadata in/from common formats.

As liblicense itself deals only with text strings, we can also make GUI libraries to provide dialogs which present these strings to the user in desktop or web applications. This layering ensures that such dialogs present consistent licensing choices.

== Get liblicense ==

* [https://sourceforge.net/project/showfiles.php?group_id=80503&package_id=238700 Latest Release from Sourceforge.net]
* Checkout liblicense module from [[SVN]]

=== Screenshots ===

[[Image:Ll nautilus emblem.png|thumbnail|Nautilus emblem support.]]
[[Image:Ll nautilus.png|thumbnail|Nautilus file properties.]]
[[Image:Ll default 2.png|thumbnail|GTK default system license.]]
[[Image:Ll dolphin.png|thumbnail|KDE4 dolphin file properties.]]
[[Image:Ll kde default license.png|thumbnail|KDE4 default system license.]]

== System Overview ==

=== Purpose ===
To provide a simple way for developers to make their applications license aware. Additionally, supplemental modules aim to provide a method for users to track licenses of files on their system. This project complements [[Companion File metadata specification]] and [[Tracker CC Indexing]].

=== Architecture ===
[[Image:System_architecture.png]]

=== Implementation ===
This library will be implemented in C to provide maximum portability.

=== Interface ===
* module_wrangler
** get_config_modules() - ''returns a null terminates list of available config modules.''
** get_io_modules() - ''returns a null terminates list of available io modules.''
** get_module_symbol(module,symbol) - ''returns the requested symbol.''
** module_init(module) - ''Loads the module and calls its init function.''
** module_shutdown(module) - ''Calls the shutdown method of the module and unloads it.''
** io_module_mime_types(module0 - ''returns a null-terminated list of the supported mime-types.''
* read_license
** read(filename) - ''returns the uri of the license of the given file.''
** module_read(filename,module) - ''returns the uri of the license of the given file while using the given module.''
* write_license
** write(filename,uri) - ''writes the given license to the given file using all applicable modules.''
** module_write(filename,module,uri) - ''writes the given license to the given file using the given module.''
* system_default
** set_default(uri)
** get_default()
* system_licenses
** get_jurisdiction(uri) - ''returns the jurisdiction for the given license.''
** get_name(uri) – ''returns the name of the license.''
** get_version(uri) – ''returns the version of the license.''
** get_prohibits(uri)
** get_permits(uri)
** get_requires(uri)
** verify_uri(uri) - ''returns whether or not the given uri is recognized by the system.''
** get_all_licenses() - ''returns a null-terminated list of all general license uris available for new works.''
** get_licenses(juris_t) - ''returns a null-terminated list of all general licenses in a family.''

=== Data Structure ===
* Data Types (informal)
** uri
** name
** notification
** deed
** sampling

=== Config Modules ===
* '''init'''() - starts the module
* '''shutdown'''() - shuts the module down
* '''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 ===
I/O modules are shared objects that call LL_MODULE_DEFINE(name,description,version,features,mime_types,init_func,read_func,write_func).

* '''name'''
* '''description'''
* '''version'''
* '''features''' - If the module embeds the license within the file, pass LL_FEATURES_EMBED
* '''mime_types''' - A space-separated string of supported mime-types, or NULL if mime-type agnostic (i.e. XMP sidecar)
* '''init_func''' - This function will be called once before the module is used
* '''read_func''' - Function to be called when requested to read a license from a file. It takes a filename and returns the license URI, or NULL if no license is present. Should return an 'int' indicating success or failure.
* '''write_func''' - Function to be called when requested to write a license to a file. The first parameter is the filename and the second is the license URI to write. Should return an 'int' indicating success or failure.

=== Bindings ===
*Python

== License Files (.rdf) ==
=== Attributes ===

* cc:license
** 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. (country code from [http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html ISO3166])
* dc:relation
** hasVersion - version number
** isReplacedBy - indicates retired license ([http://www.ietf.org/rfc/rfc2396.txt URI])
** isBasedOn - indicates ported version ([http://www.ietf.org/rfc/rfc2396.txt URI])
* dc:type - always "License"
* dc:creator
* dc:publisher
* dc:identifier - URI of license ([http://www.ietf.org/rfc/rfc2396.txt URI])

=== Example ===
<pre><rdf:RDF
xmlns="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dcq="http://purl.org/dc/terms/"
>
<rdf:Description rdf:about="http://creativecommons.org/licenses/by-nd/2.0/za/">
<dc:title>Creative Commons Attribution No Derivatives</dc:title>
<dc:description>This license allows for redistribution, commercial and non-commercial,
as long as it is passed along unchanged and in whole, with credit to you.</dc:description>
<dc:coverage>
<dcq:ISO3166>
<rdf:value>za</rdf:value>
</dcq:ISO3166>
</dc:coverage>
<dc:hasVersion>2.0</dc:hasVersion>
<dc:isReplacedBy>
<dcq:URI>
<rdf:value>http://creativecommons.org/licenses/by-nd/2.5/za/</rdf:value>
</dcq:URI>
</dc:isReplacedBy>
<dc:isBasedOn>
<dcq:URI>
<rdf:value>http://creativecommons.org/licenses/by-nd/2.5/</rdf:value>
</dcq:URI>
</dc:isBasedOn>
<dc:type>License</dc:type>
<dc:creator>iCommons</dc:creator>
<dc:publisher>Creative Commons</dc:publisher>
<dc:identifier>http://creativecommons.org/licenses/by-nd/2.0/za/</dc:identifier>

<rdf:type rdf:resource="http://creativecommons.org/ns#License"/>
<permits rdf:resource="http://creativecommons.org/ns#Distribution"/>
<permits rdf:resource="http://creativecommons.org/ns#Reproduction"/>
<requires rdf:resource="http://creativecommons.org/ns#Attribution"/>
<requires rdf:resource="http://creativecommons.org/ns#Notice"/>
</rdf:Description>
</rdf:RDF></pre>

=== Example (i18n) ===
<pre><rdf:RDF
xmlns="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dcq="http://purl.org/dc/terms/"
>
<rdf:Description rdf:about="http://creativecommons.org/licenses/by-nd/2.0/">
<dc:title>
<rdf:Alt>
<rdf:li xml:lang="x-default">Creative Commons Attribution No Derivatives</rdf:li>
<rdf:li xml:lang="es-cl">Creative Commons Atribución-SinDerivadas</rdf:li>
</rdf:Alt>
</dc:title>
<dc:description>
<rdf:Alt>
<rdf:li xml:lang="x-default">This license allows for redistribution, commercial and non-commercial,
as long as it is passed along unchanged and in whole, with credit to you.</rdf:li>
</rdf:Alt>
</dc:description>
<dc:coverage>
<dcq:ISO3166>
<rdf:value>us</rdf:value>
</dcq:ISO3166>
</dc:coverage>
<dc:hasVersion>2.0</dc:hasVersion>
<dc:isReplacedBy>
<dcq:URI>
<rdf:value>http://creativecommons.org/licenses/by-nd/2.5/</rdf:value>
</dcq:URI>
</dc:isReplacedBy>
<dc:type>License</dc:type>
<dc:creator>Creative Commons</dc:creator>
<dc:publisher>Creative Commons</dc:publisher>
<dc:identifier>http://creativecommons.org/licenses/by-nd/2.0/</dc:identifier>

<rdf:type rdf:resource="http://creativecommons.org/ns#License"/>
<permits rdf:resource="http://creativecommons.org/ns#Distribution"/>
<permits rdf:resource="http://creativecommons.org/ns#Reproduction"/>
<requires rdf:resource="http://creativecommons.org/ns#Attribution"/>
<requires rdf:resource="http://creativecommons.org/ns#Notice"/>
</rdf:Description>
</rdf:RDF></pre>

== Desktop Integration ==

See [[Desktop Integration]]

=== Gnome Summit Discussion ===

At the Gnome Summit we explored adding CC licensing to various Gnome applications. Application developers appeared to have a few needs:

* They want to display the appropriate icon (or other) for a particular license. For instance, AbiWord could display a small icon representing license status in the tool bar. Music players could display the icon in the controls area. A music streaming app might want to play a 5 second "Now entering the Creative Commons" chime (much like radio station identification, but for licenses).
* They want to allow the user to easily select a license. This would probably be a wizard that asks the user questions and tries to select the most appropriate license from all that it knows about. Much like a file selection dialog, but navigating licenses instead of your file system.

A low-level liblicense could handle XML parsing required. It would allow the client to determine the questions that need to be asked to select a license, and to download any icons, blurbs, etc for all known license types.

The low-level library solves the first problem above, but not the second. It's still too difficult to ask the user to select a license. Layered on top of the low-level library would be any number of high level libraries that would convert the textual questions into GUI widgets and present them using the appropriate toolkit (GTK+ / KDE / Cocoa / Win32 / etc). This way, adding license awareness to an application should be as easy as "license=SFGetLicense(); saveDocument(license)".

=== Accessories ===
* CLI
** license (bundled) - simple cli program to license files.
** .license/default engine - a .license directory will contain the user's default setting, other config info and the user's licenses.
* Gnome
** Gnome Settings frontend. - set the default license through the gnome settings interface.
** Nautilus Frontend Extension - set and read licenses through nautilus.
** License chooser (app.) - license chooser for setting default and per file licenses. (GUI license)
** GTK widget
** Gconf config module.
* Sugar
** Journal Backend
** Journal Frontend
* KDE3 (???)
* KDE4

== Timeline ==
=== 6/18 ===
* Finalize liblicense API.

=== 6/25 ===
* Write liblicense.
* Stub config and IO modules.

=== 7/2 ===

=== 7/9 ===
* .license/default set default
* gnome settings UI

=== 7/16 ===
* Nautilus GUI frontend.
* Gnome control panel frontend.

=== 7/23 ===
* Sugar Journal backend.
* Sugar frontend.

=== 7/30 ===
* Bug hunting.
* Frontend polishing.

=== 8/6 ===
* shoot for milestone 3 for linuxworld pr

=== 8/13 ===
{{stub}}

=== 8/20 ===
{{stub}}

== Milestones ==
=== 0.1 ===
* Initial release. ('''done''')
* All CC licenses. ('''done''')
* CLI tools. ('''done''')
* Modules. ('''done''')
** Exempi embed. ('''done''')
** Exempi XMP sidecar. ('''done''')
* Make light blog post about release on techblog, explain early state ('''done''')

=== 0.3 ===
* Optimization - namely caching in some way. Should not access file every attribute request.
* Gnome tools. ('''done''')
** Nautilus frontend. ('''done''')
** Gnome settings frontend. ('''done''')
** GTK License chooser. (See mockups) ('''done''')
* File embed preference over external storage. (Use external only as needed.) ('''done''')
* Store default jurisdiction. ('''done - default license is in default jurisdiction''')
* Modules.
** vorbiscomment ('''done''')
** ...
* Do big release on main CC blog and across various chat and mailing lists to pick-up people, lots of them...
* Do [[liblicense 03 release todo]]

=== 0.4 ===
* Further refinement.
* Sugar tools.
** Journal integration.
* Another major announcement
* [[liblicense 04 release todo]]

Liblicense

2007-07-31T17:15:15Z

2007-07-31T03:34:15Z

Scott Shawcroft:

* features
** KDE4 integration
*** system settings module
*** file properties license tab
** OLPC integration
*** Journal integration

* bugs/issues
** License chooser api ironing out (http://lists.ibiblio.org/pipermail/cc-devel/2007-July/000539.html). I could wrap the flags to hide the bit-shifting -- but before I do that, I want feedback as to whether this design, in general, works.
** Use SONAME so applications can request a particular version of liblicense's API/ABI
*** Debian will require this (and everyone else is crazy if they don't)
*** I found [http://mail-index.netbsd.org/tech-toolchain/1998/07/17/0000.html one explanation] of it while Googling
** not clear what default-content-license does, exactly- maybe replace 'Default Content License' with 'choose the default license for new content you create' or something like that? (whatever is accurate :)
** I'd get rid of the frame around the license chooser. Not used by most gnome apps.
** URI: what goes there? I assume the license URI, but I'd expect the license chooser would set that, and it doesn't appear to.
** are there sample files somewhere I can test the nautilus extension on?
** good packaging practice would break this into liblicense and liblicense-devel, one with the apps and app data another with the libraries. Not a huge deal, but would be necessary before getting it into fedora, for example.

* tag svn

* package
** source
** rpm
** deb
** ebuilds (bugs 187196, 185689, and 187194 in gentoo's bugzilla)
** test them!
** Known dependencies.
*** libraptor
*** nautilus-python
*** exempi

* publicity
** freshmeat
** sourceforge
** ?

Liblicense 03 release todo

2007-07-30T23:03:19Z

Scott Shawcroft:

Liblicense 03 release todo

2007-07-30T18:24:05Z

Scott Shawcroft:

Liblicense 03 release todo

2007-07-30T05:24:51Z

Scott Shawcroft:

* issues
** <del>Nautilus writes a license to every file whose property dialog is displayed</del>
** license chooser returns devnations -- should we mark this as retired and then not return retired licenses?
** <del>Unicode filename issues? Licenses aren't loaded for some test files with Japanese filenames.</del> (Um, seems to work fine, now) ('''0.4''')
** <del>Update gui_gtk.py to use license chooser API once the above is taken care of</del> (Workaround in place)
** <del>configure --prefix=/usr/local dies trying to install the python bindings</del>
*** libtool: install: error: cannot install `liblicense.la' to a directory not ending in /usr/lib/python2.4/site-packages/liblicense
*** Update: works after a 'make distclean'
** <del>new license chooser API not wrapped in Ruby</del> ('''0.4''')
** <del>nautilus emblems don't work for me</del> (Needed to touch /usr/share/icons/hicolor on installation)
** No sampling licenses' RDF include the prohibits commericial use statement

* package press release

* tag svn

* package
** source
** rpm
** deb
** <del>ebuild</del> (Exempi, nautilus-python, and Liblicense ebuilds, courtesy of jakin)
** test them!

* publicity
** mailing lists
*** cc-devel
*** cc-community
** freshmeat
** sourceforge
** cc frontpage blog ('''written''')
** press release
*** packaged PRESS file
** <del>cc techblog how to</del> ([[Liblicense_tutorial]])
** digg (?)
** slashdot (?)

Liblicense 03 release todo

2007-07-30T00:25:36Z

Scott Shawcroft:

* issues
** <del>Nautilus writes a license to every file whose property dialog is displayed</del>
** license chooser returns devnations -- should we mark this as retired and then not return retired licenses?
** Unicode filename issues? Licenses aren't loaded for some test files with Japanese filenames.
** <del>Update gui_gtk.py to use license chooser API once the above is taken care of</del> (Workaround in place)
** <del>configure --prefix=/usr/local dies trying to install the python bindings</del>
*** libtool: install: error: cannot install `liblicense.la' to a directory not ending in /usr/lib/python2.4/site-packages/liblicense
*** Update: works after a 'make distclean'
** new license chooser API not wrapped in Ruby
** <del>nautilus emblems don't work for me</del> (Needed to touch /usr/share/icons/hicolor on installation)
** No sampling licenses' RDF include the prohibits commericial use statement

* tag svn

* package
** source
** rpm
** deb
** ebuild ([http://bugs.gentoo.org/show_bug.cgi?id=185689 ebuild for exempi])
** test them!

* publicity
** mailing lists
*** cc-devel
*** cc-community
** freshmeat
** sourceforge
** cc frontpage blog ('''written''')
** press release
*** packaged PRESS file
** <del>cc techblog how to</del> ([[Liblicense_tutorial]])
** digg (?)
** slashdot (?)

Liblicense tutorial

2007-07-29T21:03:22Z

Scott Shawcroft: /* Python and GTK */ added the second part

== Python and GTK ==
With the release of liblicense (ll) 0.3 we've introduced the beginnings of desktop integration. With this brief guide I hope to drive further integration into other apps. While I'll be using the python bindings for simplicity, the C bindings are very similar. In this section I will show how the integration through nautilus-python is done. Here is a screenshot from nautilus.

[[Image:ll_nautilus_emblem.png]]

The first step of writing any plugin is figuring out the relevant APIs. In this case, the relevant APIs are that of liblicense and nautilus-python. The former's API is familiar to me because I wrote it but for consistencies sake the documentation is on the wiki. The nautilus-python documentation is pretty sparse as is the nautilus extension C documentation. However, I found this documentation file on the gnome svn. There are two primary integrations which I'll talk about. The first is the license emblem shown in the screenshot above. The second is a license properties tab. We'll start with the emblem because it uses the read function of liblicense.

First off to have nautilus load the plugin we place the python file in either /usr/lib/nautilus/extensions-1.0/python or ~/.nautilus/python-extensions/. Our name for the file is nautilus-liblicense.py. We'll put both aspects of the integration in this file. Next we'll import the necessary modules.

<pre>import liblicense
import urllib

import gtk
import nautilus
from liblicense.gui_gtk import *</pre>

Urllib is used to replace things such as %20 (for space) with their correct character. Gtk can be ignored for now as we'll see it in the second part. The nautilus import provides the classes which we'll subclass to provide the desired functionality. Lastly, the two liblicense imports provide us with the library functions and the gtk selector widget which we'll use later.

In order to process the files upon load we'll subclass the InfoProvider class from nautilus-python (imported as nautilus). Within this class we need to override one function, update_file_info, which takes on argument, a FileInfo object, in addition to self.

The class so far:
<pre>class LicenseInfoProvider(nautilus.InfoProvider):
def __init__(self):
pass
def update_file_info(self, f):
pass</pre>

There is nothing we need to do upon init but we'll leave it there. In a nautilus-python example they did similar. So now in the update_file_info function we'll need to read the license of the file and assign a corresponding emblem. Currently, two emblems are used, one for Creative Commons licenses and another for anything else. Here is this final code of the update_file_info function.

<pre>
def update_file_info(self, f):
if f.get_uri()[:7]=="file://":
license = liblicense.read(urllib.unquote(f.get_uri()[7:]))
if license:
if "Creative Commons" in liblicense.get_attribute(license,"http://purl.org/dc/elements/1.1/creator",False):
f.add_emblem("cc")
else:
f.add_emblem("licensed")
</pre>
The first check that is done makes sure that the argument is a local file by check that it begins with "file://". Once that is confirmed, we then read the license of the file by calling liblicense.'''read'''(''filename''). Here urllib is used to convert url encoded characters, such as %20 for a space, so that we have an accurate file path. This is all done on everything after the first seven characters of the uri which '''get_uri'''() returned.

After the license is read we check that it is not null. If its not then we use liblicense.'''get_attribute''' to get the creator of the license to check if it is Creative Commons or not. We use python's keyword '''in''' because '''get_attribute''' returns a list of values. The arguments for '''get_attribute''' are the license uri, the desired attributes uri (the predicate in RDF terms) and finally a boolean toggling the locale awareness of the processing. Once all of this is done we add the corresponding emblem using the FileInfo object's '''add_emblem''' function which takes the emblem keyword. Upon install of liblicense these two icons are added. The keyword is taken from the filename (emblem-''keyword''.{png,svg}) not the .icon file. That explains all of the first part. If you have further questions visit #cc on irc.freenode.net or email cc-devel@lists.ibiblio.org.

The second part of this section and of the nautilus liblicense integration is the properties tab. Through this tab one can see the exact license the file is currently under and they can also modify the license. This is done by utilizing the packaged LicenseChooser liblicense gtk widget. Lets have a look.

First lets set up the nautilus API for a property page:
<pre>class LicensePropertyPage(nautilus.PropertyPageProvider):
def __init__(self):
pass

def get_property_pages(self, files):
pass
</pre>
Again, similar to the first section we're subclassing a nautilus class. And again, we need to subclass one function. This time we need to subclass the '''get_property_pages''' method. This method takes in a list of '''FileInfo''' objects and returns a sequence of '''PropertyPage'''s.

Alright, lets get started. While the first iteration of this integration only supported a single file, we'll jump straight to the multiple file version.
<pre>def get_property_pages(self, files):
self.files = files

self.files = filter(lambda f: f.get_uri_scheme() == 'file' and not f.is_directory(),self.files)
self.files = map(lambda f: urllib.unquote(f.get_uri()[7:]),self.files)

if len(self.files)==0:
return
</pre>
In this first bit we do some python wizardry. First we store the files list in the object itself, we'll need it later. Now we '''filter''' out the files with a different uri scheme and those which are directories. This leaves us with a list of '''FileInfo''' objects which have uris in the "file:///path/filename.ext" form. So to get a list of files in the liblicense form we use '''map''' and '''urllib.unquote''' like we did in the previous part. Finally, before we continue, we make sure we have not filtered out all of the selected items.

Now that we have a list of relevant files we need to do one of two things, if there is only one file selected we start the license chooser displaying the appropriate license or we display no license if multiple files are selected. '''get_property_pages''' continued:
<pre>self.property_label = gtk.Label('License')
self.property_label.show()

if len(files) == 1:
license = liblicense.read(self.files[0])
if license==None:
license = liblicense.get_default()
else:
license = None
self.box = LicenseWidget(license)
</pre>
First, we create the label for the property tab. After this we see how many files we are dealing with. If its one, we call read on the first and only element of the list and proceed to check whether it exists (in other words, is ''None'' or not). When the license is ''None'' we default to the system default license. If there is multiple files we simply set the license to ''None''. Finally, we create the '''LicenseWidget''' (which is a subclass of '''gtk.HBox''') passing the desired starting license uri in.

The last task we must complete is to write the license to the selected file(s) when the properties window is closed. To do this we attach a callback to the destroy signal of the '''LicenseWidget'''.
<pre> self.box.connect("destroy",self.license_chosen)
self.box.show()

return nautilus.PropertyPage("NautilusPython::license",
self.property_label, self.box),
</pre>

The above should be self explanatory. We simply use the PyGTK widget method '''connect''' to attach a method to the signal. Then we return a sequence (note the ending comma) of '''PropertyPage'''s created in the return statement. I copied this from the nautilus-python example and assume the arguments are an identifier, a label and a widget to be packed in the tab.

Lastly, the callback method is pretty simple.
<pre> def license_chosen(self, widget):
license = self.box.get_license()
if license:
for f in self.files:
liblicense.write(f,license)
</pre>

Like all GTK callbacks the first argument is the widget which emitted the signal along with self. Upon receiving this signal we get the current license of the widget by calling the '''LicenseWidget''''s get_license method which returns the uri for the selected license or ''None'' if no license is selected. Then we check to see if a license was selected and if so iterate through the selected files writing the license info to each one. This writing is done using the liblicense '''write''' method which takes the file path and the license uri. It utilizes liblicense modules which write to a variety of different file formats.

Well, thats the end of the liblicense nautilus integration. The entire file can be seen at [http://cctools.svn.sourceforge.net/viewvc/cctools/liblicense/trunk/src/gnome/nautilus-liblicense.py?revision=6398&view=markup Liblicense svn browse].

--[[User:Scott Shawcroft|Scott Shawcroft]] 17:03, 29 July 2007 (EDT)

== Command-line Interface ==
[[Incomplete]]

== License Chooser ==

Liblicense aims to make integration of license selection into applications seamless. The license chooser API allows for selecting licenses based on what the license permits, requires, and/or prohibits. For example, the license chooser API makes an excellent backend to the following:

[[Image:Kde_properties.png]]

=== C bindings ===

<pre>
#include <liblicense.h>
#include <stdio.h>

int main() {
ll_init();

char *attributes[] = {
"http://creativecommons.org/ns#Distribution",
"http://creativecommons.org/ns#CommercialUse",
"http://creativecommons.org/ns#DerivativeWorks",
"http://creativecommons.org/ns#ShareAlike",
"http://creativecommons.org/ns#Attribution",
NULL
};
ll_license_chooser_t *chooser = ll_new_license_chooser(NULL,attributes);

int permits, requires, prohibits;

//permits Distribution(0) and DerivativeWorks(2)
permits = (1 << 0) | (1 << 2);

//requires ShareAlike(3) and Attribution(4)
requires = (1 << 3) | (1 << 4);

//prohibits CommericalUse(1)
prohibits = (1 << 1);

const ll_license_list_t *licenses = ll_get_licenses_from_flags(chooser,permits,requires,prohibits);
while (licenses) {
printf("%s\n",licenses->license);
licenses = licenses->next;
}

ll_free_license_chooser(chooser);
ll_stop();

return 0;
}
</pre>

Note how flags are specified. For example, if we want a license that requires Attribution, we need to set the 4th bit of "requires". This is because Attribution is the 4th element in the attribute array (remember, zero-based indexes here).

=== Python bindings ===

Python bindings greatly simplify the above. This retrieves all licenses that permit Distribution and Derivative Works and don't require Attribution or Notice (in other words, Public Domain).

<pre>
from liblicense import LicenseChooser

attributes = ["http://creativecommons.org/ns#Distribution",
"http://creativecommons.org/ns#DerivativeWorks",
"http://creativecommons.org/ns#Attribution",
"http://creativecommons.org/ns#Notice"]
chooser = LicenseChooser(None,attributes)
print chooser.get_licenses(permits=(1 << 0) | (1 << 1))
</pre>

See the C bindings example for more details.

Liblicense tutorial

2007-07-29T03:49:19Z

Scott Shawcroft: first part of python/gtk tutorial

Liblicense 03 release todo

2007-07-27T23:31:22Z

Scott Shawcroft:

* tag svn

* package
** source
** rpm
** deb
** ebuild
** test them!

* publicity
** mailing lists
*** cc-devel
*** cc-community
** freshmeat
** sourceforge
** cc frontpage blog ('''written''')
** press release
*** packaged PRESS file
** cc techblog how to
** digg (?)
** slashdot (?)