Thursday, 30. January 2003
Safer Internet events, Luxembourg on 27/ 28 February 2003
- A workshop on "Quality labels for websites - alternative approaches to content rating" is being held on 27 February.
- On 28 February the SIFKAL project, co-funded under the Safer Internet Action Plan, is organising a workshop on "legal and pedagogical aspects of a Safer Internet".
Machine readable licenses
Creative Commons want's to tinker with machine-readable licenses. Read more at:
- http://creativecommons.org/learn/technology/metadata/implement
- http://www.xml.com/pub/a/2003/01/15/creative.html
- http://creativecommons.org/weblog/archive/2003/01/#3588
To get this going it has to be dead simple to implement for content providers and convenient to implement for tool writers. First get rid of most of your fields or make them at least non-mandantory. You created a suite for encoding nearly all information related to IP for a certain document. Create a way to just encode a licence, without messing with variables for Title, Author etc. - so users just can drop some lines into their HTML without messing with template variables and the like.
KISS! Dublin Core Data does not follow the keep it simple style.
Get away from this HTML comment stuff. It is really, really hard to parse if there a dozends of them in a large HTML document. Regular Expression engines can get very slow at this and faster alternatives are a pain to code for. Besides being hard and slow to parse this commet thing can create a slew of other problems for tool writers. E.g. what to do if you see multiple licenses in a single document? To allow inline definition of a license use HTML metatags or something like this.
The prefered way should be a seperate license file. Usually vou want to put several files under the same license. You also could link to the creative commons site.
<link rel="license-terms" href="http://creativecommons.org/licenses/by-nd-nc/1.0.rdf" type="application/xml+rdf" />
That would be dead simple.
More on machine readable licenses.
After poting my last Item I have studied the the http://creativecommons.cc site further and found out that they provide you with a some HTML-comment-encoded-RDF wenn you request the data HTML Data for the creative commons license button.
OK that is dead simple. (But still ugly) And further down in the document they imply that the Dublin Core elements are not mandantory - also they are not used in their own RDF.
I still think the Implementing Creative Commons Metadata Document tires to archive to much at once.
Nevertheless the last posting was underinformed and i have to restrain myselv to keep from deleting it.
Even more machine readable licenses.
I'm trying to understand how to use Creative Commons Metadata to encode non creative commons licenses. While checking the licenses at http://www.ifross.de/ifross_html/lizenzcenter.html I came to the conclusion that we will never ba able to express all this variations in a machine readable form. So I suggest that there should be a way to express at least a subset of the rights provided by the license.
The most usable probably would be "allows at least unmodified digital reproduction". Many licenses also require that the "Disclaimer" is reproduced unmodified". Would be nice to be able to express this too. But reproduction would by its definition reproduce the disclaimer, too.
So for a BSD Handbook Licence I could use something like:
<License rdf:about="">http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ln16.html"> <permits rdf:resource="http://web.resource.org/cc/Reproduction" /> <permits rdf:resource="http://web.resource.org/cc/Distribution" /> <permits rdf:resource="http://web.resource.org/cc/FurtherUnspecifiedRights" /> </License>
If we would be able to encode some of the popular licenses and could convince some of the producers of this works to add a simple "http://XXX/nameoftheirlicense.rdf" type="application/xml+rdf" />" to their HTML generating Tools we could significantly incerase the number of resources with machine-readable.license on the Web.
Licenses which would be worth a try:
- http://dmoz.org/license.html
- http://www.tldp.org/COPYRIGHT.html
- http://www.fsf.org/copyleft/fdl.html
- http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ln16.html
disLEXia, a research project by Maximillian Dornseif
 |  |  | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
   |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |  |  | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||