liblicense [creative commons work]

[Kevin Ottens]

Le mardi 28 août 2007, Rafael Fernández López a écrit :
> This morning I was suggested to visit:
> http://wiki.creativecommons.org/Liblicense

Yeah, cool idea. Not sure the end user cares about the license and wants to 
see it though. Let's show him anyway, it'll be part of his education. ;-)

> I really think this is a great work for Dolphin.

I'm not fully sure it should have a special status in the file manager, it 
probably be better to put it with the other metadata in the info panel. For 
more document or media oriented applications though that'd be terrific.

> I think what we could 
> do for 4.1 (4.0 deadline is very close) is getting liblicense on
> kdesupport and the part related to KDE on kdelibs. The code is
> CC-LGPL-GPL licensed. The code seems to be really clean, as far as I have
> seen [I took only a fast overview].

I'm pondering about this, at first it looked like a tempting idea, I 
thought "ok, one more C lib to wrap... no big deal". But the more I look at 
how it's done the more I wonder if it's in our best interest.

My current thinking on this is that we shouldn't use this lib, but share the 
RDF schema and data. Because what liblicense basically do (AFAIU) is 1) 
read/write tags from file to set their license, and 2) give information on a 
particular license based on the RDF information provided.

For 1) we already have the infrastructure in place thanks to Strigi analyzers 
and KFileWritePlugin. So we'd basically duplicate a specialized subset of our 
stack only for license while our framework is already able to do it.

About 2) we already have Nepomuk to access RDF information in a nice way. 
Since they already have all the RDF schemas and RDF files needed for this, I 
think it shouldn't be hard to feed Nepomuk this kind of information.

Both combined, that'd mean we'd have the whole data indexed for free, while 
using liblicense would require extra work (by at least patching our strigi 
analyzers).

> Probably we could discuss with artists if they like 
> those CC default icons or they prefer to be more like Oxygen icon
> style.

Well, it's their call really. Maybe the best course of action here, is to 
amend the xdg icon spec? This way you could have those icons depending on the 
icon theme like all our other icons.

Regards.
-- 
Kévin 'ervin' Ottens, http://ervin.ipsquad.net
"Ni le maître sans disciple, Ni le disciple sans maître,
Ne font reculer l'ignorance."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070830/065e1593/attachment.sig>