Creativecommons Ccplus Technical Implementation For The World Wide Web Eng
Uploaded by
Creative CommonsCreativecommons Ccplus Technical Implementation For The World Wide Web Eng
Uploaded by
Creative CommonsCC+ Technical Implementation
for the World Wide Web
http://creativecommons.org/projects/ccplus
Creative Commons provides free copyright licenses which My Song’ is licensed under <a rel=”license”
empowers authors and creators to mark their creativity with the href=”http://creativecommons.org/licenses/by-
freedom they intend it to carry. In this document, we describe the sa/3.0/”>CC BY-SA</a>. For other permissions
implementation of a technology we have developed to enable <a xmlns:cc=”http://creativecommons.org/ns#”
a simple click-through to rights or opportunities beyond those rel=”cc:morePermissions” href=”http://
offered in the CC license. See this document’s non-technical example.com/store/mysong”>click here</a>.
companion, “CC and CC+ for the World Wide Web” for a
conceptual description of this approach.
Using RDFa1, the cc: namespace definition could be
Overview included in any parent element. Together the namespace
The round-trip implementation consists of two operations: and rel attribute of the second link denote the predicate of
http://creativecommons.org/ns#morePermissions with the
1. Publishing a creative work along with a Creative Commons current document as the subject and http://example.com/store/
license plus (+) a “more permissions” link on a web page. mysong as the object.
2. Reading the more permissions link. Simply put, more permissions for the web page at hand may be
found at http://example.com/store/mysong.
The first operation will be implemented by a publisher, typically
with software running on a web server. The second operation
will be implemented by a client, typically a web browser or Reading
web service. Both the CC license and more permissions links may be
extracted from a web page with an RDFa parser.
An application developer only needs to implement the operations
in scope of the aforementioned client and/or server application. What a client does with the links (once read) is highly application-
specific. Typically, the CC license and more permissions options
will be brought to the attention of the user.
Publishing
Examples of this include:
CC license
Making a notice that a creative work on the web has been 1. Creative Commons’ MozCC2 Extension for Mozilla Firefox
Creative Commons licensed is done with a textual and/or displays indicator icons in the browser’s status bar.
graphical notice visible on a web page with a link to the license
used marked-up in the underlying html. For example: 2. A bookmarklet could highlight relevent links on a page.
My Song’ is licensed under <a rel=”license” 3. Creative Commons license deeds 3 add notice of more
href=”http://creativecommons.org/licenses/by- permissions availability based on annotations found on the
sa/3.0/”>CC BY-SA</a>. referring page.
4. An industry or site-specific client could auto-discover
additional services available at the more permissions link.
More permissions link
Adding a more permissions link simply consists of linking to [1] http://rdfa.info
a page where more permissions for a work are available and [2] http://wiki.creativecommons.org/MozCC
annotating that link. For example: [3] See http://labs.creativecommons.org/metadata for live examples
More Information
Please visit http://creativecommons.org/
Except where otherwise noted, this work is licensed under
http://creativecommons.org/licenses/by/3.0/
Share, reuse, and remix — legally.
www.creativecommons.org
