Hi Fred,
Ah, the perils of using an example which changes... it looks like Phil's changing blog theme so the licence has temporarily gone. It was/ will be a line of html saying in part: <a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/3.0/">
As has been pointed out by others I'll note that in this case this the tool is picking up the licence info off the blog footer as such it's a licence for the whole blog - i've not tried embedded a different licence in a post to see what happens if it finds 2 licences.
One easy approach to adding licence information/ creating the html is to go to http://creativecommons.org/choose/ . You'll notice that, as well as picking a CC licence you can add additional information like attribution or a link to contact page to ask about other uses/licenses. If you then select choose it will give you a html snippet to paste into your post/ blog footer. That's what I did.
I'm not immediately aware of a similar way to produce RDFa, you could use the examples given as a template and/or we could try creating something at the OERhackday and/or ask Creative Commons if there could be an option to produce this in a similar manner.
Kind regards,
john
R. John Robertson
skype: rjohnrobertson
Research Fellow/ Open Education Resources programme support officer (JISCCETIS), Centre for Academic Practice and Learning Enhancement University of Strathclyde
Tel: +44 (0) 141 548 3072
http://blogs.cetis.ac.uk/johnr/
The University of Strathclyde is a charitable body, registered in Scotland, with registration number SC015263
-----Original Message-----
From: Open Educational Resources [mailto:[log in to unmask]] On Behalf Of Fred Riley
Sent: 09 February 2011 12:28
To: [log in to unmask]
Subject: Re: OpenAttribute tool
> A quick note for members of the list who may not have caught this on
> twitter - there's a new browser plugin (for: opera, firefox, chrome)
> (for: opera, firefox, chrome) to simplify the process of attributing
> creative commons works.
>
> http://openattribute.com/
Thanks again for this tip, John. I've only now had time to look at it properly. I've installed the add-on in Firefox and waltzed off to Phil Barker's blog (http://blogs.cetis.ac.uk/philb/) and a CC icon appears in the URL bar. Now, here's a real dumbo question: where is the cc:licence info on Phil's page that's being picked up? A search in the page source for 'cc:' fails and there's too much source to look through every line. Or, more generically, what does the author have to put into a page for it to be picked up by this tool? I would RTFM but there's not a whole lot on the open attribute site as yet.
I ask mainly because I want to mark pages on a site I'm developing (http://www.nottingham.ac.uk/~ntzfr/oer/) as CC and have put a dc:rights item in the header. Pat's suggested putting RDF data into the page which would be fine, but again the practical Q is: how? (As it happens, this is the sort of practical how to I can put into the site, which is aimed at teachers and technical developers.)
<gripe>Sorry, folks, I feel like Homer Simpson at times in this company. I thought I knew a fair bit about metadata and implementation but I'm plainly still at the demo level and have many more levels of knowledge to pass through before reaching that of the wizards on this list :(. This is a gripe I've had for some years now, having attended metadata events where the wonders of interoperability are discussed and angels-on-a-pin discussions of metadata elements take place for hours, but at no point in thoseevents I've attended has a technical developer demonstrated practical implementations in code. And in the end it's us techs who have to implement feeds and services and XML exposures and whatnot. </gripe>
And yes, <gripe> is a semantic element (invent your own attributes) ;)
Fred
----
This email represents my own personal views and is not at all reflective of policy or opinions at my institution. So there.
----
This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.
This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.
|