Building Links with Creative Commons

One of the members of Cre8asite Forums has a couple of sites that he’s filled with images of the locations of his sites. He’s a talented photographer, in addition to a skilled web master, and the pictures he has on his site are terrific. He has also placed those images under licenses from Creative Commons.

Because of the licenses, he’s had people use images from his site on their own noncommercial web sites, with links pointing back to his sites. He’s also had inquiries from people wanting to use his images in commercial works. Since the images are likely to be of interest to people who may want to find out more about what he has to offer, having links back to his site brings traffic to his pages from people who could possibly become customers of his.

The beauty of Creative Commons licenses are that they inform people that they could possibly use material created by other people under conditions expressed in the licenses. They don’t harm people’s rights under copyright law, but rather make communication about possible uses of those materials easier. The Creative Commons pages show how to use a license, and provide many examples.

Google and Creative Commons

On Thursday, October 26th, a team from Creative Commons came to speak at Google.

With Google’s acquistion of YouTube, it makes sense that they would learn more about copyright, and copyright licenses. Creative Commons came to visit to see if they could get some help from Google as well as sharing information about what the Creative Commons organization is doing. What might this mean to people who use Google?

The primary speaker was Mike Linksvayer (link is to his personal blog), who is the Chief Technical Officer from Creative Commons. His presentation is the subject of a Google Tech Talk – Creative Commons for Googlers. His main focus was on some of the technical aspects of Creative Commons licenses and metadata, and being able to put information on pages, so that it is easier to find Creative Commons licensed materials on the web.

Non-Technical Information about Creative Commons

Before Mike Linksvayer began talking about Metadata, he wanted to cover some non-technical aspects of what they do.

1. He began with a first semi-public showing of a new video from Creative Commons on copyright, and the value of a creative commons license which could allow others to easily share and distribute artistic works.

2. He noted that there were a number of ways to think about copyright and Creative Commons. One was to consider some of the GPL releases of software, and he asked if media was twenty years behind software, and concepts of open source software.

3. To further than analogy, the concept of reuse of code, could possibly be expanded to content? Could there be a content license interoperability in the same way as a code license interoperability?

4. He also noted that there were a number of legal materials on the Creative Commons web site, such as a podcasting legal guide, discussion about the legal use of copyright. He also mentioned that the Version 3.0 of licenses are being worked upon.

5. He also pointed out some “cool things” being worked upon at Creative Commons. For example, some Creative Commons materials were used in the loneligirl15 videos. Another example was of a Brazilian movie that was released simultaneously in theatres, and on the web under a CC license.

Technical aspects of CC licenses

In 2002, the focus of their efforts were to provide the following in their licenses:

  1. Human readible code,
  2. Lawyer readible code, and;
  3. Machine readible code.

One thing that they were hoping for was for someone to develop a search engine that would look for materials licensed under Creative Commons.

No one was working on developing something like that, so in 2004, they started working on a prototype search engine that could find CC licensed material. Their first one was slow. They then switched to Nutch, to make a newer version.

In early 2005, Yahoo built a search engine that could find CC material. In late 2005, Google did the same, and as their help section on Usage Rights notes, that is incorporated into their advanced search.

The Yahoo and Google searches are available on a Creative Commons search page , and also includes a search of Flickr and blip.tv (warning, audio starts on blip.tv automatically).

Metadata infrastructure

1. The original CC licenses included RDF, XML, and HTML comments

2. In looking for something more effective (and interoperable), they decided against making up their own meta data in lieu of using something else out in the world.

3. There are issues with using comments like they had been, such as it:

  • Being prone to spamming,
  • May not get updated when pages change, and;
  • It can be hard for people to learn and use.

4. Microformats have taken off in the last year, and they looked at those. They may be useful. But they have some limitations, too. One main one is that they are on a page level, rather than a smaller level of granulairity, so they may not be helpful when images or videos on a page may not share the same license as the rest of the page.

5. They want information about meta data showing on the page, so that it is easy for people to see and use, and so that it is flexible.

6. They started exploring something called RDFa. Creative Commons has some wiki pages on the subject – RDFa Mike Linksvayer noted that there are some problems with it, such as being developed for XHTML 2, which no one uses. Examples at http://rdfa.info/ (added 10/30/2006 – Mike did note in his presentation that RDFa is still very viable and usable inspite of the ties to XHTML 2. Thanks to Mike Birbeck for reinforcing that in the comments here.)

(Unfortunately, many of the slides being used for examples are difficult to read in the video. )

Ben Adida’s works on interoperativity and meta data is recommended at this point in the video. Interesting looking document: Building Interoperable Metadata (pdf)

Why talk with Google?

1. The Creative Commons organization would like to get feedback on ideas involving metadata, and microformats that might be able to apply to images, videos, audio, and other objects on pages.

2. Embedded metadata doesn’t work well:

  • Can’t be seen on a web page,
  • Isn’t often used, and;
  • can’t be trusted, because you don’t know who may add it.

The technical term for embedded metadata’s and its failings is that “it sucks.”

The best type of metadata is metadata that refers to a specific web page via a URL, so that people can visit that web page, and learn more about it. Embedded metadata doesn’t.

3. Adobe is using some metadata built into their media that may be an improvement on embedded metadata.

Creative Commons also Wants to Do Other Things with Metadata

This is the part of the presentation that may be of the most interest to people who create works that may be issued under a license, and people who build and market web sites.

1. Metadata should also include attribution. (A way to encourage people to link to you.) A standard way to attribute with meta data, and with a link may have been the biggest mistake that CC made. The general feeling is that they should have included it

2. Other questions could be answered with improved metadata, such as:

  • Where can I buy related media,
  • where can I a commercial license
  • Where can I make a donation
  • 3. There are examples of commerce sites using Creative Commerce Licenses, and they would like to encourage more. Here are a couple:

    4. They would also like to see Google incorporate Creative Commons metadata into Blogger and other Google applications where people can create, such as Docs and Spreadsheets, and other tools, and include it in places like their blog search.

    Questions and Answers from the Presentation

    As with many Google Tech Talk videos, participants have been warned that the presentations are being taped, and anything that might be best not shared with the world shouldn’t be discussed during filming. A couple of questions and answers survived for public scrutiny, but a team of folks were present from Creative Commons for one-on-one questions and answers.

    q: BBC creative licenses seem similar to CC licenses.
    a: There are some similarities, and they’ve talked, but BBC is free only to UK tax payers.

    q: Should they (BBC and CC) talk some more?
    a: Probably, because if everyone comes up with different licenses, there is a risk that they won’t be interoperable.

    Conclusion

    Some Google videos are issued under a creative commons license. Perhaps the most noteworthy so far was a music video from Pearl Jam back in May. I didn’t see the option to use a Creative Commons license on YouTube. It would be interesting to see that happen.

    The laws regarding copyright, and the use of information (snippets and cached versions) that search engines collect to present to searchers are murky and unclear. Would a metadata framework involving licenses for images, video, audio also involve web pages? Would it possibly be used in that way? Would the possibility keep search engines from getting involved in helping to build a more intelligent kind of metadata, or would it benefit them if such a framework existed that could be expanded to web pages?

    It surprised me that when I presented some videos here from Google Video in the past, and they had a way to copy and embed those videos, they didn’t require a link back to the source, and didn’t include such a link in what I copied onto my pages. The benefits of a Creative Commons license is that it can explicitly state that a link attributing the source be included to use the material provided under the license.

    Share

    17 thoughts on “Building Links with Creative Commons”

    1. A very useful post! I wonder if I could add a clarification though.

      Mike Linksvayer said that RDFa was developed for XHTML 2, possibly implying that it has limited use. This is not correct.

      It certainly originates in work that was carried out for XHTML 2, but it was always the intention that it would be a set of attributes that could be used in any XML langauge, from SVG to XForms to XHTML 1.

      For more on this, see RDFa: The Gentle Road to RDF.

      Regards,

      Mark

    2. Thanks, Dave.

      I look forward to seeing what you come up with. I can imagine that it be some brilliant work.

      Hi Mark,

      Thanks for your clarification. I may have given the wrong impression in what I wrote about what he said in the video. I will add a line in the post above to change that. He did try to stress the same thing that you are, that it is still has value, inspite of XHTML 2.

      Cheers.

      Bill

    3. Hi. Sorry for the text being unreadable in the video. I was using w3slidy for the first time and forgot to hit cntrl-+ a few times to make the text size appropriate for the display. Slides are here.

      Apologies for any oversimplifications. The RDFa Primer does say

      This document is a W3C Working Draft. It is a companion document to the XHTML 2.0 specification and explains the expected use of the XHTML Metainformation Module and XHTML Metainformation Attributes Module. This Working Draft is non-normative; the XHTML2 specification is the normative description of the features described in this primer. At the time of publication of this Working Draft the published XHTML2 Working Draft lags in some details. This is expected to be corrected with the next XHTML2 Working Draft.

      That’s where I got XHTML2 from. FWIW I think RDFa is an ideal solution for [X]HTML any version, but I don’t care much about validation.

    4. Thanks, Mike.

      I enjoyed your presentation tremendously inspite of the text in the slides. Thanks for the link to them – they do add to your presentation a great deal.

      I’m a big fan of the ability to share ideas and collaborate with others that can be brought to us by articulately and well defined license statements on copyrighted works like those from Creative Commons.

      I’d love to see Google implement the ability to use Creative Commons licenses more fully into what they offer.

    5. Hi Bill,

      Two small points here..relating to wiki commons

      a. When i read about the Google visit it reminded me that Google’s image search rarely brings any images from this large database of pictures. Hopefully this will change soon.

      b. Secondly you can create a page with your images on wiki commons and then, subject permitting, there is a template you can add to a main wikipedia page which will cross link to your commons page. This can drive traffic and links through to your website. A small way to get some more exposure :-)

    6. Hi Colin,

      Thanks for stopping by. I’m guessing that you are referring to the Wikimedia Commons, sister project to the Wikipedia.

      I only looked at the code behind a few of the images, but I think that there might be things that you could do that might help Google index more images from the commons.

      1. Use alt text with those images

      2. Underscores and colons in page names and in file names of images probably aren’t helping.

      The search engines try to use information such as file names, alt text, and anchor text pointing to pages linked to as meta data to help them understand what an image is about.

      A hyphen is a much better choice as a separator of words than an underscore or a colon. If it’s possible, you might want to experiment with a few images, and see if making those types of changes make a difference.

      Thanks for the idea of placing images on the wiki commons. You may have me out running around taking a bunch of photos this week. I’m only seeing a few images in some categories that would benefit from having more pictures. :)

    7. Cheers for the heads up.
      Have just changed my articles to include a creative commons license. Looks like a good way forward.

    8. Nice to hear, Mike.

      It’s an approach worth thinking about. I’ve been been giving it some serious consideration on a couple of blogs that I write at.

    9. Pingback: Adam Moro
    10. Thank you, spirit.

      Seems like a static site rather than a blog, without any post dates. It appears pretty informative, but there might be things that you can do like include a link to your home page in your logo. I do like that you have contact phone information very easy to see at the top right of the page. Any thoughts to making a blog section of the site?

    11. Ok, so let me see if I get it right.

      Let’s say due to the industry of my websites, I don’t take pics but create clip art like images related to my niche. I license them through Creative Commons. Then what?

      1) Do I need to upload them somewhere for people to find and use them?
      2) If I license the images that are already on my sites, do they have to display the creative commons logo? (that would be impossible for us, as it is a commercial site and it would look unprofessional).
      3) If I license the images that are already on my site, do I also upload them on some directory?

      I think what I’m trying to ask, is how do I make sure they’re found so that people can use them and link back to me.

      Thanks! BTW Love your blog, been reading it for some time now. It is one of the best, most underrated resources in SEO. I mean it.

    Comments are closed.