Creative Commons - User contributions [en]

A2K3

2008-08-02T05:22:38Z

Ahrash Bissell:

{{Event
|Mainurl=http://www.law.yale.edu/news/6191.htm
|EventType=Conference
|date=2008/09/08
|Location=Geneva, Switzerland
|EventCategory=Free Culture, Open Access, Open Data, Open Education
|Attendance=No
|invitation=No
|public=Yes
}}
Yale ISP will convene the third annual global conference on Access to Knowledge (A2K3) in Geneva, Switzerland on September 8-10, 2008. The conference will bring together scholars, policymakers, and civil society to discuss key issues of global knowledge policy.

Conference

2008-08-02T05:17:27Z

Ahrash Bissell: /* Upcoming Conferences */

Creative Commons is a small nonprofit. CC presents at several conferences a year, but our formal staff is limited. We often need other CC community members to help us at conferences by helping present projects, fliers, and other issues. Also, this is a great way to get into your favorite conference for free!

Check out our schedule and contact us if you want to get involved handing out swag and manning the booth. Also, make sure to subscribe to our [http://www.creativecommons.org/weblog webblog] where we will be sure to post about upcoming conferences/volunteer opportunities.

== Upcoming Conferences ==

*[[CC Nordic meeting]]
**Oct 23-25
**Stockholm, Sweden

*[[CCi Legal Day 2008]]
**July 29
**Sapporo, Japan

== Info Cheat Sheet ==

* Link to PDF

OSCON 2008

2008-06-22T05:45:24Z

Ahrash Bissell:

{{Event
|title=OSCON (Open Source Convention)
|Mainurl=http://en.oreilly.com/oscon2008/public/schedule/detail/2299
|EventType=Conference
|date=2008/07/21
|Location=Portland, Oregon, USA
|Division=CC, Learn
|Attendance=Yes
}}

Glossary

2008-06-10T20:14:03Z

Ahrash Bissell:

The Creative Commons world includes many buzzwords -- legal, social, and technical. Here's a quick guide to some of them, with links for more on each.

;[[BY]]: The short name for the attribution term of CC licenses. "[http://creativecommons.org/licenses/by/3.0/ CC BY]" is a CC license that only requires giving credit -- allowing commercial and derivative use.

;[[CCPlus|CC+]]: A protocol describing the offering of a work under a CC license plus other options, such as the availability of private agreements that provide permissions or warranties beyond the scope of the CC license on offer. Note that one cannot add restrictions to a CC license via this or any other mechanism.

;[[CC0]]: A waiver that attempts to offer users as many rights as possible, currently in beta.

;[[ccHost]]: A remix-oriented content management system that powers ccMixter, licensed under the GPL.

;[http://creativecommons.org/international CCi]: Creative Commons International refers to the project to legally and linguistically "port" CC licenses to jurisdictions around the world and the global network of teams engaged in this and follow-on activites.

;[http://learn.creativecommons.org ccLearn]: A division of Creative Commons that works to minimize legal, technical and social barriers to reuse of educational materials.

;[http://ccmixter.org ccMixter]: A remix-focused music community developed by Creative Commons to demonstrate the creative re-use of openly licensed music.

;[http://en.wikipedia.org/wiki/Copyleft Copyleft]: Usually refers to a license that requires distributed modifications of licensed works be shared under the same license, most prominently in the case of the GPL. CC calls this property of licenses ShareAlike. [http://creativecommons.org/licenses/by-sa/3.0/ CC BY-SA] is unambiguously a copyleft license, while some consider [http://creativecommons.org/licenses/by-nc-sa/3.0/ CC BY-NC-SA] to not be in the spirit of copyleft.

;[http://en.wikipedia.org/wiki/Copyright Copyright]: A right automatically granted to authors to prevent others from using their works without permission for a very long time and with limited exceptions. The expansion of copyright in length and scope with the increased costs of copyright enforcement in the digital age are some reasons Creative Commons exists.

;[[ccREL]]: Creative Commons Rights Expression Language, a composite recommendation of technologies for marking digital media with license information and other metadata.

;[http://en.wikipedia.org/wiki/Fair_Use Fair Use]: The right to make certain uses of a work without permission of the copyright holder.

;[http://en.wikipedia.org/wiki/Free_Culture Free Culture]: The name of a movement of which CC is a part, a [http://free-culture.cc book by Lawrence Lessig], and [http://freeculture.org Students for Free Culture]. The [http://freedomdefined.org Definition of Free Cultural Works] specifies which licenses its authors believe qualify as free culture licenses -- CC BY and CC BY-SA qualify, while licenses with NC or ND terms do not.

;Jurisdiction: A legal system. The CCi project "ports" CC licenses to individual jurisdictions. Often a jurisdiction is the same as a "country" but in some cases there is more than one legal system within a country or disagreement about exactly what legal systems and corresponding geographies make up a country, so we use the term jurisdiction for maximum accuracy.

;[[liblicense]]: A software library in the C programming language that makes functions such as reading and embedding license metadata and discovering license properties available to other programs.

;[[NC]]: The short name for the NonCommercial term of some CC licenses, often used by itself to refer to the term in any of these licenses or as part of their short names, e.g., "[http://creativecommons.org/licenses/by-nc/3.0/ CC BY-NC]".

;[[ND]]: The short name for the NoDerivatives term of some CC licenses, often used by itself to refer to the term in any of these licenses or as part of their short names, e.g., "[http://creativecommons.org/licenses/by-nc-nd/3.0/ CC BY-NC-ND]".

;[http://en.wikipedia.org/wiki/Open_access_publishing OA]: Open Access

;[http://en.wikipedia.org/wiki/Open_educational_resources OER]: Open Educational Resources. OER are educational materials and resources offered freely and openly for anyone to use and under some licenses to re-mix, improve and redistribute.

;[http://en.wikipedia.org/wiki/Public_Domain Public Domain]: Works that are not restricted by copyright either because they are very old or not copyrightable (e.g., data).

;[http://en.wikipedia.org/wiki/Resource_Description_Framework RDF]: Resource Description Framework, a model for representing statements about things on the web. CC uses RDF to model license properties and describe licensed works.

;[[RDFa]]: RDF in attributes, a mechanism for annotating web pages such that machine-readable data is colocated with human-visible markup, allowing metadata to be retained through operations like copy and paste. The key recommendation of ccREL.

;[[SA]]: The short name for the ShareAlike term of some CC licenses, often used by itself to refer to the term in any of these licenses or as part of their short names, e.g., "[http://creativecommons.org/licenses/by-sa/3.0/ CC BY-SA]".

;[http://sciencecommons.org Science Commons]: A division of Creative Commons that applies open tools to the problem of unlocking the value of research so more people can benefit from the work scientists are doing.

;[http://en.wikipedia.org/wiki/Semantic_Web Semantic Web]: The project to make the web machine-readable using technologies such as RDF.

;Some Rights Reserved: A descriptive tagline for any CC license -- the licensor offers some rights to the public, but withholds others.

;Unported: Since version 3 of the CC licenses, "unported" licenses are those written with reference to international treaties in language recognized globally to the extent possible, as opposed to "ported" licenses with language written to be familiar to copyright law in a particular jurisdiction.

;[[XMP]]: eXtensible Metadata Protocol, a format for embedding metadata in many different file formats, most significantly PDF and JPEG. A recommendation of ccREL.

CcLearn and Universal Design

2008-06-04T05:14:33Z

Ahrash Bissell: New page: {{Presentation |venue=CSU Sacramento |date=2008/05/29 |presenter=Ahrash Bissell |slidesurl=http://www.slideshare.net/ahrashb/cclearn-and-universal-design-29-may-2008 }} Presentation for a ...

{{Presentation
|venue=CSU Sacramento
|date=2008/05/29
|presenter=Ahrash Bissell
|slidesurl=http://www.slideshare.net/ahrashb/cclearn-and-universal-design-29-may-2008
}}
Presentation for a summer workshop of faculty learning how to teach with technology, with a focus on universal design.

CcLearn at the Stanford Open Source Lab

2008-05-28T19:55:22Z

Ahrash Bissell: New page: {{Presentation |venue=Stanford Open Source Lab |date=2008/04/23 |presenter=Ahrash Bissell |slidesurl=https://www.stanford.edu/group/opensource/cgi-bin/blog/2008/05/12/video-of-cclearn-work...

{{Presentation
|venue=Stanford Open Source Lab
|date=2008/04/23
|presenter=Ahrash Bissell
|slidesurl=https://www.stanford.edu/group/opensource/cgi-bin/blog/2008/05/12/video-of-cclearn-workshop-is-live/
}}

USF law school presentation

2008-05-28T19:23:52Z

Ahrash Bissell: New page: {{Presentation |venue=University of San Francisco (USF) law school |date=2008/04/09 |presenter=Ahrash Bissell |slidesurl=http://www.scribd.com/doc/3138466/USF-Law-School-presentation-09-Ap...

{{Presentation
|venue=University of San Francisco (USF) law school
|date=2008/04/09
|presenter=Ahrash Bissell
|slidesurl=http://www.scribd.com/doc/3138466/USF-Law-School-presentation-09-Apr-2008
}}
This presentation is a wiki, also available at CC TS.

CcLearn and the Carnegie Foundation KML

2008-05-28T19:18:53Z

Ahrash Bissell: New page: {{Presentation |venue=Carnegie Foundation Knowledge Media Lab |date=2008/04/07 |presenter=Ahrash Bissell |slidesurl=http://www.scribd.com/doc/3138387/Carnegie-KML-presentation-07-Apr-2008 ...

{{Presentation
|venue=Carnegie Foundation Knowledge Media Lab
|date=2008/04/07
|presenter=Ahrash Bissell
|slidesurl=http://www.scribd.com/doc/3138387/Carnegie-KML-presentation-07-Apr-2008
}}
The presentation is on a wiki, also located at CC TS.

Building the Infrastructure of Open Education: Legal, Technical, and Social Challenges

2008-05-28T18:53:53Z

Ahrash Bissell: New page: {{Presentation |venue=Florida DistanceLearn consortium (webinar) |date=2008/04/25 |presenter=Ahrash Bissell |slidesurl=http://www.oncoreblueprint.org/Webinars.htm#cclearn }}

{{Presentation
|venue=Florida DistanceLearn consortium (webinar)
|date=2008/04/25
|presenter=Ahrash Bissell
|slidesurl=http://www.oncoreblueprint.org/Webinars.htm#cclearn
}}

Category:Organization

2008-04-16T01:56:51Z

Ahrash Bissell:

<h1>ccLearn: ODEPO Project 
(Open Database of Educational Projects and Organizations)</h1>

Welcome to the home page of ccLearn's ODEPO project! ODEPO (Open Database of Educational Projects and Organizations) is an interactive database for individuals and organizations involved in education. The list below spans more than 1,000 web sites affiliated with various organizations. The majority of this list was donated to us by educational repositories who are involved in the creation and expansion of [http://en.wikipedia.org/wiki/Open_educational_resources Open Educational Resources] (OER). If you find that your project or organization (and others you know of) is not listed here, we invite you to [http://wiki.creativecommons.org/index.php?title=Special:Userlogin&type=signup&returnto=Main_Page create] a wiki account.

Once you have created an account, feel free to browse ODEPO's '''[[:Category:Organization/FAQ | FAQ]]''' (Category:Organization/FAQ). If you are already familiar with wiki's, go ahead and get started at [[Form:Organization]]. More information on how to add your project or organization will be on this page.

Keep in mind that we are still in the developing stages, so any feedback on the functionality, design and accessibility of this site is valuable and appreciated.

== Search Organizations by: ==
*[[Special:SearchByProperty/Affiliation | Affiliation]]
*[[Special:SearchByProperty/Mainurl | Main url]]
*[[Special:SearchByProperty/Resource URL | Resource url]]
*[[Special:SearchByProperty/Tag | Tag]]
*[[Special:SearchByProperty/Organization Type | Organization type]]
*[[Special:SearchByProperty/Open or Free Statement | Open or free statement]]
*[[Special:SearchByProperty/License provider | License provider]]
*[[Special:SearchByProperty/License short name | License short name]]
*[[Special:SearchByProperty/License | License (url)]]

== Browse Organizations by: ==
<h3>[http://wiki.creativecommons.org/index.php?title=Category:Organization&from=A#mw-pages A] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=B#mw-pages B]
[http://wiki.creativecommons.org/index.php?title=Category:Organization&from=C#mw-pages C]
[http://wiki.creativecommons.org/index.php?title=Category:Organization&from=D#mw-pages D] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=E#mw-pages E]
[http://wiki.creativecommons.org/index.php?title=Category:Organization&from=F#mw-pages F] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=G#mw-pages G] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=H#mw-pages H]
[http://wiki.creativecommons.org/index.php?title=Category:Organization&from=I#mw-pages I] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=J#mw-pages J] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=K#mw-pages K]
[http://wiki.creativecommons.org/index.php?title=Category:Organization&from=L#mw-pages L] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=M#mw-pages M] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=N#mw-pages N]
[http://wiki.creativecommons.org/index.php?title=Category:Organization&from=O#mw-pages O] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=P#mw-pages P] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=Q#mw-pages Q]
[http://wiki.creativecommons.org/index.php?title=Category:Organization&from=R#mw-pages R] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=S#mw-pages S] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=T#mw-pages T]
[http://wiki.creativecommons.org/index.php?title=Category:Organization&from=U#mw-pages U] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=V#mw-pages V] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=W#mw-pages W]
[http://wiki.creativecommons.org/index.php?title=Category:Organization&from=X#mw-pages X] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=Y#mw-pages Y] [http://wiki.creativecommons.org/index.php?title=Category:Organization&from=Z#mw-pages Z]</h3>
[[Has default form::Form:Organization| ]]

Category:Organization/FAQ

2008-04-15T18:01:58Z

Ahrash Bissell:

== What is ODEPO (Open Database of Educational Projects and Organizations)? ==

ODEPO is a project of [http://learn.creativecommons.org ccLearn], the education division of [http://creativecommons.org Creative Commons]. Its aim is to enable networking among individuals and organizations involved in education, particularly those creating and expanding [http://en.wikipedia.org/wiki/Open_educational_resources open educational resources (OER)].

This wiki provides an interactive archive of potential projects, programs, and organizations for (open) education. This means that, on some level, these websites curate their own educational resources, or point to places that do. We have also included some non-curatorial organizations, especially those involved in the open education movement, such as the [[William_and_Flora_Hewlett_Foundation | William and Flora Hewlett Foundation]]. Other websites are either highly informational, host online publications, or point to resources for research and higher education. (For further explanation on this topic, please see [[Property:Status As An Educational Resource]].)

Although not all of these projects are involved in open education, we hope that this wiki will provide an initial and discerning tool for those interested in collaborating within the movement. For more information about OER, please see [http://learn.creativecommons.org/resources/faq ccLearn's FAQ page].

== Where do I begin? ==
The point of this database is to allow you (the educator, researcher, student or advocate) to find the projects, programs, and organizations appropriate to your needs. Therefore, we welcome you to first browse through our [[:Category:Organization#Browse_Organizations_by: | 1,000+ websites]]. Take a look at the information on the pages, and if you already have a wiki account with us, feel free to edit anything you find inaccurate or incomplete, adding additional description in the free text section if you feel you have helpful things to say about a particular resource.

== How do I contribute? ==
Since this database is a community project, it will be fueled by your contributions and edits. It is set up in wiki format so you can add your own projects and give feedback on others'. If you don't already have a wiki account, you can [http://wiki.creativecommons.org/index.php?title=Special:Userlogin&type=signup&returnto=Main_Page create] one. All you need is your full name and a valid email address.

After you have created an account and logged in, return to ODEPO's home page at [[:Category:Organization]]. From there, you can access the FAQ again, or immediately start browsing our database.

You can contribute by editing or adding projects, programs or organizations that you believe should be included in the database. We are particularly interested in projects and organizations engaged in open education and the creation of open educational resources (OER).

We especially encourage you to edit existing pages, adding descriptions and helpful tips wherever you can. More information about adding and editing is provided below.

== How do I search for ==
=== Projects and Organizations? ===
You can search for existing projects and organizations by [[:Category:Organization#Browse_Organizations_by: | browsing by alphabet]], or by entering the name in the "Search" box at the top right of every page. Note that this box searches the entire CC wiki, which includes more than just ODEPO's organizations. To see more information about this, go to [[#Additional Issues | Additional Issues]].

=== Everything else? ===
You can also search for projects by their affiliation, organization type, and more. Go to [[:Category:Organization#Search_Organizations_by: | Search Organization by]] on the home page.

=== Existing values? ===
On any given project/organization page, you will notice that all values are linked. See [[Creative Commons - ccLearn]] for an example. In the field column, all entries are in blue. This means they are linked to a search of all pages containing the specific value for that property. For instance, if you click on the value "nonprofit" under [[Property:Organization Type]], you will be directed to a page listing all organizations whose type is [[:Special:SearchByProperty/Organization_Type::nonprofit | nonprofit]]. The internal wiki link of this page is [[:Special:SearchByProperty/Organization_Type::nonprofit]]. But you don't have to worry about that--just click on any value to find other organizations with the same. It's that easy!

== Adding a project or organization ==
'''Does this organization already exist?''' 
Since we have over 1,000 organizations stored in our database, it just might. To avoid duplicate pages, search for the organization or web site title to see if it is already in our archive at [[:Category:Organization]]. The organizations are listed in alphabetical order for easy browsing. You can also search for the organiation in the search box at the top of the page to the right.

'''Nope, it doesn't exist. How do I add it?''' 
Great. Go to [[Form:Organization]] and type its name in this format:

"Organization name" - "Project or Website name"

For example, if the educational web page is titled "Biology" and your organization is the "Public Library of Science," you would put:

[[Public Library of Science (PLoS) - Biology]]

If there isn't a separate title for the site, just put the organization name.

'''Question 1: Should I enter it in exactly this format, with the space after the name, then dash, then space, then name again?''' 
Yes.

'''Question 2: What about the abbreviation? Do I have to put one?''' 
Only if it is a popular abbreviation. If it is (like PLoS), put the abbreviation in parentheses after the organization's full name. This will ensure greater searchability of the organization. For instance, NASA shows up: National Aeronautics and Space Administration (NASA).

'''I am ready to add my organization!''' 
If you are satisfied with the titling of your project, go ahead and enter it at [[Form:Organization]]. Later, this will show up as the page name in big, bold letters at the top, so it is important that it is accurate and identifiable. If a page with that name already exists, you will be sent to a form to edit that page.

== Editing or adding information ==
When adding a project, you will automatically be directed to a form with eleven fields for you to populate.

When you want to edit a project, always click "edit with form" from the right-hand column of the page. This will direct you to the same form, and make it much easier for you to edit information.

'''What are the eleven fields?''' 
The eleven fields are actually eleven properties whose value (what you enter in the field) is for you to determine. The eleven fields are:

[[Property:Affiliation | Affiliation]] 
[[Property:Mainurl | Main url]] 
[[Property:Resource URL | Resource url]] 
[[Property:Tag | Tags]] 
[[Property:Organization Type | Organization type]] 
[[Property:Status As An Educational Resource | Status as an educational resource]] 
[[Property:Open or Free Statement | Open or free statement]] 
[[Property:License provider | License provider]] 
[[Property:License short name | License short name]] 
[[Property:License | License]] 
and finally, the free text field (Notes about this resource...).

On the form, you will notice that these terms are linked to their property pages. These pages provide information about the properties and address questions about what to put in the fields. Go ahead and hover your mouse over each one and click for more information.

When it comes to the free text field ("Notes about this resource..."), we encourage you to type in a description of your project. See [[Creative Commons - ccLearn]] for an example. You can also add description on other pages and even comment on issues with a particular website.

== Additional Issues ==
'''Some pages have two info boxes: "Organization Information" and "Content Directory". Why is this?''' 
One example of this is [[China_Open_Resources_for_Education_(CORE)]]. If you go this page, it will show you two boxes, one with a light blue header--Organization Information--and one with a green header--Content Directory. This occurs because ODEPO's database is included in the general Creative Commons wiki. If you are specifically looking for organizations within our database, don't worry about the green box. All the information you need is under "Organization Information".

'''But when I run a search, how do I know the page I get is part of ODEPO, and not just part of the larger wiki?''' 
As noted above, any project in our database will have a box with the light blue header. If it shows up in any other form, you can assume it is part of the larger CC wiki.

Category:Organization/FAQ

2008-04-15T17:58:05Z

Ahrash Bissell: /* What is ODEPO (Open Database of Educational Projects and Organizations)? */

== What is ODEPO (Open Database of Educational Projects and Organizations)? ==

ODEPO is a project of [http://learn.creativecommons.org ccLearn], the education division of [http://creativecommons.org Creative Commons]. Its aim is to enable networking among individuals and organizations involved in education, particularly those creating and expanding [http://en.wikipedia.org/wiki/Open_educational_resources open educational resources (OER)].

This wiki provides an interactive archive of potential projects, programs, and organizations for (open) education. This means that, on some level, these websites curate their own educational resources, or point to places that do. We have also included some non-curatorial organizations, especially those involved in the open education movement, such as the [[William_and_Flora_Hewlett_Foundation | William and Flora Hewlett Foundation]]. Other websites are either highly informational, host online publications, or point to resources for research and higher education. (For further explanation on this topic, please see [[Property:Status As An Educational Resource]].)

Although not all of these projects are involved in open education, we hope that this wiki will provide an initial and discerning tool for those interested in collaborating within the movement. For more information about OER, please see [http://learn.creativecommons.org/resources/faq ccLearn's FAQ page].

== Where do I begin? ==
The point of this database is to allow you (the educator, researcher, student or advocate) to find the projects, programs, and organizations appropriate to your needs. Therefore, we welcome you to first browse through our [[:Category:Organization#Browse_Organizations_by: | 1,000+ websites]]. Take a look at the information on the pages, and if you already have a wiki account with us, feel free to edit anything you find inaccurate or incomplete, adding additional description in the free text section if you feel you have helpful things to say about a particular resource.

== How do I contribute? ==
Since this database is a community project, it will be fueled by your contributions and edits. It is set up in wiki format so you can add your own projects and give feedback on others'. If you don't already have a wiki account, you can [http://wiki.creativecommons.org/index.php?title=Special:Userlogin&type=signup&returnto=Main_Page create] one. All you need is your full name and a valid email address.

After you have created an account and logged in, return to ODEPO's home page at [[:Category:Organization]]. From there, you can access the FAQ again, or immediately start browsing our database.

You can contribute by editing or adding projects, programs or organizations that you believe should be included in the database. We are particularly interested in projects and organizations engaged in open education and the creation of open educational resources (OER).

We especially encourage you to edit existing pages, adding descriptions and helpful tips wherever you can. More information about adding and editing is provided below.

== How do I search for ==
=== Projects and Organizations? ===
You can search for existing projects and organizations by [[:Category:Organization#Browse_Organizations_by: | browsing by alphabet]], or by entering the name in the "Search" box at the top right of every page. Note that this box searches the entire CC wiki, which includes more than just ODEPO's organizations. To see more information about this, go to [[#Additional Issues | Additional Issues]].

=== Everything else? ===
You can also search for projects by their affiliation, organization type, and more. Go to [[:Category:Organization#Search_Organizations_by: | Search Organization by]] on the home page.

=== Existing values? ===
On any given project/organization page, you will notice that all values are linked. See [[Creative Commons - ccLearn]] for an example. In the field column, all entries are in blue. This means they are linked to a search of all pages containing the specific value for that property. For instance, if you click on the value "nonprofit" under [[Property:Organization Type]], you will be directed to a page listing all organizations whose type is [[:Special:SearchByProperty/Organization_Type::nonprofit | nonprofit]]. The internal wiki link of this page is [[:Special:SearchByProperty/Organization_Type::nonprofit]]. But you don't have to worry about that--just click on any value to find other organizations with the same. It's that easy!

== Adding a project or organization ==
'''Does this organization already exist?''' 
Since we have over 1,000 organizations stored in our database, it just might. To avoid duplicate pages, search for the organization or web site title to see if it is already in our archive at [[:Category:Organization]]. The organizations are listed in alphabetical order for easy browsing. You can also search for the organiation in the search box at the top of the page to the right.

'''Nope, it doesn't exist. How do I add it?''' 
Great. Go to [[Form:Organization]] and type its name in this format:

"Organization name" - "Project or Website name"

For example, if the educational web page is titled "Biology" and your organization is the "Public Library of Science," you would put:

[[Public Library of Science (PLoS) - Biology]]

If there isn't a separate title for the site, just put the organization name.

'''Question 1: Should I enter it in exactly this format, with the space after the name, then dash, then space, then name again?''' 
Yes.

'''Question 2: What about the abbreviation? Do I have to put one?''' 
Only if it is a popular abbreviation. If it is (like PLoS), put the abbreviation in parentheses after the organization's full name. This will ensure greater searchability of the organization. For instance, NASA shows up: National Aeronautics and Space Administration (NASA).

'''I am ready to add my organization!''' 
If you are satisfied with the titling of your project, go ahead and enter it at [[Form:Organization]]. Later, this will show up as the page name in big, bold letters at the top, so it is important that it is accurate and identifiable. If a page with that name already exists, you will be sent to a form to edit that page.

== Editing or adding information ==
When adding a project, you will automatically be directed to a form with eleven fields for you to populate.

When you want to edit a project, always click "edit with form" from the right-hand column of the page. This will direct you to the same form, and make it much easier for you to edit information.

'''What are the eleven fields?''' 
The eleven fields are actually eleven properties whose value (what you enter in the field) is for you to determine. The eleven fields are:

[[Property:Affiliation | Affiliation]] 
[[Property:Mainurl | Main url]] 
[[Property:Resource URL | Resource url]] 
[[Property:Tag | Tags]] 
[[Property:Organization Type | Organization type]] 
[[Property:Status As An Educational Resource | Status as an educational resource]] 
[[Property:Open or Free Statement | Open or free statement]] 
[[Property:License provider | License provider]] 
[[Property:License short name | License short name]] 
[[Property:License | License]] 
and finally, the free text field (Notes about this resource...).

On the form, you will notice that these terms are linked to their property pages. These pages provide information about the properties and address questions about what to put in the fields. Go ahead and hover your mouse over each one and click for more information.

When it comes to the free text field ("Notes about this resource..."), we encourage you to type in a description of your project. See [[Creative Commons - ccLearn]] for an example. You can also add description on other pages and even comment on issues with a particular website.

== Additional Issues ==
'''Some pages have two info boxes: "Organization Information" and "Content Directory". Why is this?''' 
One example of this is [[China_Open_Resources_for_Education_(CORE)]]. If you go this page, it will show you two boxes, one with a light blue header--Organization Information--and one with a green header--Content Directory. This occurs because ODEPO's database is included in the general Creative Commons wiki. If you are specifically looking for organizations within our database, don't worry about the green box. All the information you need is under "Organization Information".

'''But when I run a search, how do I know the page I get is part of Network and Collaborate, and not just part of the larger wiki?''' 
As noted above, any project in our database will have a box with the light blue header. If it shows up in any other form, you can assume it is part of the larger CC wiki.

Category:Organization/FAQ

2008-04-15T17:57:03Z

Ahrash Bissell:

== What is ODEPO (Open Database of Educational Projects and Organizations)? ==

ODEPO is a project of [http://learn.creativecommons.org ccLearn], the education division of [http://creativecommons.org Creative Commons]. Its aim is to enable networking among individuals and organizations involved in education, and especially the creation and expansion of [http://en.wikipedia.org/wiki/Open_educational_resources open educational resources (OER)].

This wiki provides an interactive archive of potential projects, programs, and organizations for (open) education. This means that, on some level, these websites curate their own educational resources, or point to places that do. We have also included some non-curatorial organizations, especially those involved in the open education movement, such as the [[William_and_Flora_Hewlett_Foundation | William and Flora Hewlett Foundation]]. Other websites are either highly informational, host online publications, or point to resources for research and higher education. (For further explanation on this topic, please see [[Property:Status As An Educational Resource]].)

Although not all of these projects are involved in open education, we hope that this wiki will provide an initial and discerning tool for those interested in collaborating within the movement. For more information about OER, please see [http://learn.creativecommons.org/resources/faq ccLearn's FAQ page].

== Where do I begin? ==
The point of this database is to allow you (the educator, researcher, student or advocate) to find the projects, programs, and organizations appropriate to your needs. Therefore, we welcome you to first browse through our [[:Category:Organization#Browse_Organizations_by: | 1,000+ websites]]. Take a look at the information on the pages, and if you already have a wiki account with us, feel free to edit anything you find inaccurate or incomplete, adding additional description in the free text section if you feel you have helpful things to say about a particular resource.

== How do I contribute? ==
Since this database is a community project, it will be fueled by your contributions and edits. It is set up in wiki format so you can add your own projects and give feedback on others'. If you don't already have a wiki account, you can [http://wiki.creativecommons.org/index.php?title=Special:Userlogin&type=signup&returnto=Main_Page create] one. All you need is your full name and a valid email address.

After you have created an account and logged in, return to ODEPO's home page at [[:Category:Organization]]. From there, you can access the FAQ again, or immediately start browsing our database.

You can contribute by editing or adding projects, programs or organizations that you believe should be included in the database. We are particularly interested in projects and organizations engaged in open education and the creation of open educational resources (OER).

We especially encourage you to edit existing pages, adding descriptions and helpful tips wherever you can. More information about adding and editing is provided below.

== How do I search for ==
=== Projects and Organizations? ===
You can search for existing projects and organizations by [[:Category:Organization#Browse_Organizations_by: | browsing by alphabet]], or by entering the name in the "Search" box at the top right of every page. Note that this box searches the entire CC wiki, which includes more than just ODEPO's organizations. To see more information about this, go to [[#Additional Issues | Additional Issues]].

=== Everything else? ===
You can also search for projects by their affiliation, organization type, and more. Go to [[:Category:Organization#Search_Organizations_by: | Search Organization by]] on the home page.

=== Existing values? ===
On any given project/organization page, you will notice that all values are linked. See [[Creative Commons - ccLearn]] for an example. In the field column, all entries are in blue. This means they are linked to a search of all pages containing the specific value for that property. For instance, if you click on the value "nonprofit" under [[Property:Organization Type]], you will be directed to a page listing all organizations whose type is [[:Special:SearchByProperty/Organization_Type::nonprofit | nonprofit]]. The internal wiki link of this page is [[:Special:SearchByProperty/Organization_Type::nonprofit]]. But you don't have to worry about that--just click on any value to find other organizations with the same. It's that easy!

== Adding a project or organization ==
'''Does this organization already exist?''' 
Since we have over 1,000 organizations stored in our database, it just might. To avoid duplicate pages, search for the organization or web site title to see if it is already in our archive at [[:Category:Organization]]. The organizations are listed in alphabetical order for easy browsing. You can also search for the organiation in the search box at the top of the page to the right.

'''Nope, it doesn't exist. How do I add it?''' 
Great. Go to [[Form:Organization]] and type its name in this format:

"Organization name" - "Project or Website name"

For example, if the educational web page is titled "Biology" and your organization is the "Public Library of Science," you would put:

[[Public Library of Science (PLoS) - Biology]]

If there isn't a separate title for the site, just put the organization name.

'''Question 1: Should I enter it in exactly this format, with the space after the name, then dash, then space, then name again?''' 
Yes.

'''Question 2: What about the abbreviation? Do I have to put one?''' 
Only if it is a popular abbreviation. If it is (like PLoS), put the abbreviation in parentheses after the organization's full name. This will ensure greater searchability of the organization. For instance, NASA shows up: National Aeronautics and Space Administration (NASA).

'''I am ready to add my organization!''' 
If you are satisfied with the titling of your project, go ahead and enter it at [[Form:Organization]]. Later, this will show up as the page name in big, bold letters at the top, so it is important that it is accurate and identifiable. If a page with that name already exists, you will be sent to a form to edit that page.

== Editing or adding information ==
When adding a project, you will automatically be directed to a form with eleven fields for you to populate.

When you want to edit a project, always click "edit with form" from the right-hand column of the page. This will direct you to the same form, and make it much easier for you to edit information.

'''What are the eleven fields?''' 
The eleven fields are actually eleven properties whose value (what you enter in the field) is for you to determine. The eleven fields are:

[[Property:Affiliation | Affiliation]] 
[[Property:Mainurl | Main url]] 
[[Property:Resource URL | Resource url]] 
[[Property:Tag | Tags]] 
[[Property:Organization Type | Organization type]] 
[[Property:Status As An Educational Resource | Status as an educational resource]] 
[[Property:Open or Free Statement | Open or free statement]] 
[[Property:License provider | License provider]] 
[[Property:License short name | License short name]] 
[[Property:License | License]] 
and finally, the free text field (Notes about this resource...).

On the form, you will notice that these terms are linked to their property pages. These pages provide information about the properties and address questions about what to put in the fields. Go ahead and hover your mouse over each one and click for more information.

When it comes to the free text field ("Notes about this resource..."), we encourage you to type in a description of your project. See [[Creative Commons - ccLearn]] for an example. You can also add description on other pages and even comment on issues with a particular website.

== Additional Issues ==
'''Some pages have two info boxes: "Organization Information" and "Content Directory". Why is this?''' 
One example of this is [[China_Open_Resources_for_Education_(CORE)]]. If you go this page, it will show you two boxes, one with a light blue header--Organization Information--and one with a green header--Content Directory. This occurs because ODEPO's database is included in the general Creative Commons wiki. If you are specifically looking for organizations within our database, don't worry about the green box. All the information you need is under "Organization Information".

'''But when I run a search, how do I know the page I get is part of Network and Collaborate, and not just part of the larger wiki?''' 
As noted above, any project in our database will have a box with the light blue header. If it shows up in any other form, you can assume it is part of the larger CC wiki.

Public domain

2008-03-18T19:01:55Z

Ahrash Bissell:

When a work is in the public domain, it is free for use by anyone for any purpose. Public domain is the purest form of open/free, since no one owns owns or controls the material in any way. In other words, it is free of any license. For more information, see Wikipedia's [http://en.wikipedia.org/wiki/Public_domain entry] on public domain.

=== When does a work enter the public domain? ===

This varies by country. To see when a work in the United States enters the public domain, see copyright.gov's [http://www.copyright.gov/pr/pdomain.html public domain page].

License provider

2008-03-18T19:00:27Z

Ahrash Bissell: /* What do you mean by "none"? */

=== What are the different License providers? ===

There are five different categories of "License provider". They are:

*CC (Creative Commons)
*FSF (Free Software Foundation)
*public domain
*various
*none

=== What is Creative Commons? ===

Creative Commons is a nonprofit that offers licenses that are "some rights reserved." For more information, please visit our website: http://creativecommons.org/about/.

=== What is the Free Software Foundation? ===

The Free Software Foundation is also a nonprofit that grants licenses for free or open source software. Although they do offer a free documentation license, their primary focus is software. To find out more, visit their website: http://www.fsf.org/about/.

=== What is the public domain? ===

Please see our [[public domain]] page.

=== Does "various" mean that there are various license providers for the resources offered on this particular site? ===

Yes. Generally, we try to reserve this term for large repositories where it is difficult to name all the license providers without going through every single resource. On the other hand, if we know that this site only offers resources from two license providers (say CC and FSF) then we would not mark it "various" but "CC" and "FSF." (If you know the specific license providers, you can check more than one when entering the organization/site.)

=== What do you mean by "none"? ===

Essentially, whenever something is created, it defaults to an "all rights reserved" copyright under United States law. See the United States copyright site for more details: http://www.copyright.gov/circs/circ1.html#hsc. In this case, there is no license indicated that would supersede the standard "all rights reserved" copyright; therefore, there is no license provider. We mark these cases as "none".

DiscoverEd Metadata

2008-01-29T20:00:37Z

Ahrash Bissell: /* Embedding license data */

{{draft}}

== Overview ==
This document outlines the format in which ccLearn would like to receive syndication feeds for the data that will go into our OER database.

The data must be supplied in an [http://www.atomenabled.org/developers/syndication/ Atom] or [http://www.rssboard.org/rss-specification RSS] format. Both of these standards are in widespread use on the Internet for content syndication.

Presently, ccLearn is looking for the following data:
* Link: Full URL of the referenced resource.
* Title: A brief descriptive title for the resource.
* Summary: A relatively short summary/synopsis of the resource.
* License: This should be a URL to the license; e.g., http://creativecommons.org/licenses/by/3.0/.
* Grade level (cc:gradelevel): What grade(s) or age-level(s) this material is suitable for.
* Language (cc:lang): The language(s) of the referenced resource (not of your site).
* Subject (cc:subject): The subject(s) of the resource; e.g., math.

<div style="border: 1px dashed #06f; margin: 0.5em auto 1em; padding:1em; margin-left:2em" class="boilerplate plainlinks" id="stub">
'''NOTE''': The sample Atom and RSS 2.0 feeds below mostly implement the minimum elements required by the respective specification plus the fields that ccLearn needs. For our purposes, a feed must minimally contain most of the elements in the examples below, but may also contain any other valid elements. Also, though '''we prefer an Atom feed''', there is no reason that another type of feed cannot be used, as long as it is able to include all of the data CC needs ''AND'' includes the data in such a way that the [http://feedparser.org Universal Feed Parser] can extract it in a normalized way.
</div>

== CC-specific categories (tags/fields) ==

The CC Specific fields do not have native Atom or RSS element definitions. For these fields we suggest that they be embedded as category or tag specifications (<code><category></code> in Atom) with a specific prefix. These have the general format of:

<pre>cc:<field>:<data></pre>

For example, the <code><category></code> content for Language would become something like:

<pre>cc:lang:es</pre>

Examples for Grade level could be:

<pre>cc:gradelevel:3
cc:gradelevel:primary</pre>

The Creative Commons-specific fields build upon existing category/tag support in feeds. Therefore any <code>cc:</code> field may be specified multiple times if needed. The fields we currently use for refining search results include:

* Subject: cc:subject:<data>
* Grade level: cc:gradelevel:<data>
* Language: cc:lang:<data>

=== Specifying Subject ===

The subject refers to the actual content in the resource; i.e., what is this resource ''about''? For many resources, more than one subject will be necessary; in this case, specify multiple subject <category> elements. We ask that you try to limit the number of elements to only those subjects that are objectively reflective of the entire resource. If you want to include other types of categories (opinions, metrics, etc), please add those as normal (un-prefixed) <category> elements instead.

=== Specifying Grade level ===

The grade level should indicate all grade levels (student ages) for which the resource is deemed appropriate. Though we will accept any descriptions that seem appropriate to you, please consider using one of the following schemas:

* primary, secondary, tertiary, adult;
* K,1,2,3,...,20 (where the number refers to the actual grade-level).

You may include equivalent terms as well by specifying more than one <code>cc:gradelevel</code> <category>. For example, you might include a <code>cc:gradelevel</code> for <code>9</code>, <code>10</code>, and <code>secondary</code>.

=== Specifying Language ===

When specifying the language for a resource, the value should be specified as the [http://en.wikipedia.org/wiki/ISO_639-1 ISO-639-1] code. For example, <code>en</code> for English. When specifying a national dialect, the [http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 IS-3166 alpha-2] code should be appended. For example, to distinguish English (United States) from English (United Kindgom), the language would be specified as <code>en-US</code> and <code>en-GB</code>, respectively.

In general, we are expecting that most resources will consist of a single language, but if more than one language is present, provide a <code>cc:lang</code> <category> for each.

=== Embedding license data ===

Since the licensing of a resource is expected to be conveyed via URL, we can leverage the Atom <link> element. However we must markup the link element so as to identify it as a license URL. This is accomplished with adding the attribute rel="license" to the <link> element. For example:

<pre><link rel="license" href="http://creativecommons.org/licenses/by/3.0/" /></pre>

See the complete [[Syndication|CC with syndication formats]] documentation for more information.

== Examples ==

=== Atom 1.0 example ===
Here is a sample, one entry Atom 1.0 feed which implements the guidelines above.

<pre>
<feed xmlns="http://www.w3.org/2005/Atom">
<id>http://oersite.org/cc/</id>
<title>OER Aggregation Web Site</title>
<updated>2008-01-16T12:00:00Z</updated>
<link rel="self" href="http://oersite.org/cc/atom.xml" type="application/atom+xml" />
<author>
<name>John Q. Public</name>
<email>webmaster@oersite.org</email>
</author>
<entry>
<id>tag:ocw.org,2007-10-15:/math/101</id>
<updated>2007-10-15T12:00:00Z</updated>
<link href="http://ocw.org/math/101" />
<title>Math 101</title>
<summary>Basic mathematics for 5th graders</summary>
<link rel="license" href="http://creativecommons.org/licenses/by/3.0/" />
<category term="cc:subject:Math" />
<category term="cc:gradelevel:5" />
<category term="cc:lang:en" />
</entry>
</feed>
</pre>

=== RSS 2.0 example ===
Here is a sample, one entry RSS 2.0 feed which implements the guidelines above.

<pre>
<?xml version="1.0"?>
<rss version="2.0"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>
<channel>
<title>OER Web Site</title>
<link>http://oersite.org/</link>
<atom:link rel="self" href="http://oersite.org/cc/rss20.xml" type="application/atom+xml" />
<description>OER Aggregation Web Site</description>
<lastBuildDate>Wed, 16 Jan 2008 15:00:00 -0800</lastBuildDate>
<webMaster>webmaster@oersite.org (John Q. Public)</webMaster>
<item>
<guid isPermaLink="false">tag:ocw.org,2007-10-15:/math/101</guid>
<pubDate>Mon, 12 Nov 2007 09:15:00 -0800</pubDate>
<link>http://ocw.org/math/101</link>
<title>Math 101</title>
<description>Basic mathematics for 5th graders</description>
<creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
<category>cc:subject:Math</category>
<category>cc:gradelevel:5</category>
<category>cc:lang:en</category>
</item>
</channel>
</rss>

</pre>

DiscoverEd Metadata

2008-01-29T20:00:15Z

Ahrash Bissell: /* Specifying Language */

{{draft}}

== Overview ==
This document outlines the format in which ccLearn would like to receive syndication feeds for the data that will go into our OER database.

The data must be supplied in an [http://www.atomenabled.org/developers/syndication/ Atom] or [http://www.rssboard.org/rss-specification RSS] format. Both of these standards are in widespread use on the Internet for content syndication.

Presently, ccLearn is looking for the following data:
* Link: Full URL of the referenced resource.
* Title: A brief descriptive title for the resource.
* Summary: A relatively short summary/synopsis of the resource.
* License: This should be a URL to the license; e.g., http://creativecommons.org/licenses/by/3.0/.
* Grade level (cc:gradelevel): What grade(s) or age-level(s) this material is suitable for.
* Language (cc:lang): The language(s) of the referenced resource (not of your site).
* Subject (cc:subject): The subject(s) of the resource; e.g., math.

<div style="border: 1px dashed #06f; margin: 0.5em auto 1em; padding:1em; margin-left:2em" class="boilerplate plainlinks" id="stub">
'''NOTE''': The sample Atom and RSS 2.0 feeds below mostly implement the minimum elements required by the respective specification plus the fields that ccLearn needs. For our purposes, a feed must minimally contain most of the elements in the examples below, but may also contain any other valid elements. Also, though '''we prefer an Atom feed''', there is no reason that another type of feed cannot be used, as long as it is able to include all of the data CC needs ''AND'' includes the data in such a way that the [http://feedparser.org Universal Feed Parser] can extract it in a normalized way.
</div>

== CC-specific categories (tags/fields) ==

The CC Specific fields do not have native Atom or RSS element definitions. For these fields we suggest that they be embedded as category or tag specifications (<code><category></code> in Atom) with a specific prefix. These have the general format of:

<pre>cc:<field>:<data></pre>

For example, the <code><category></code> content for Language would become something like:

<pre>cc:lang:es</pre>

Examples for Grade level could be:

<pre>cc:gradelevel:3
cc:gradelevel:primary</pre>

The Creative Commons-specific fields build upon existing category/tag support in feeds. Therefore any <code>cc:</code> field may be specified multiple times if needed. The fields we currently use for refining search results include:

* Subject: cc:subject:<data>
* Grade level: cc:gradelevel:<data>
* Language: cc:lang:<data>

=== Specifying Subject ===

The subject refers to the actual content in the resource; i.e., what is this resource ''about''? For many resources, more than one subject will be necessary; in this case, specify multiple subject <category> elements. We ask that you try to limit the number of elements to only those subjects that are objectively reflective of the entire resource. If you want to include other types of categories (opinions, metrics, etc), please add those as normal (un-prefixed) <category> elements instead.

=== Specifying Grade level ===

The grade level should indicate all grade levels (student ages) for which the resource is deemed appropriate. Though we will accept any descriptions that seem appropriate to you, please consider using one of the following schemas:

* primary, secondary, tertiary, adult;
* K,1,2,3,...,20 (where the number refers to the actual grade-level).

You may include equivalent terms as well by specifying more than one <code>cc:gradelevel</code> <category>. For example, you might include a <code>cc:gradelevel</code> for <code>9</code>, <code>10</code>, and <code>secondary</code>.

=== Specifying Language ===

When specifying the language for a resource, the value should be specified as the [http://en.wikipedia.org/wiki/ISO_639-1 ISO-639-1] code. For example, <code>en</code> for English. When specifying a national dialect, the [http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 IS-3166 alpha-2] code should be appended. For example, to distinguish English (United States) from English (United Kindgom), the language would be specified as <code>en-US</code> and <code>en-GB</code>, respectively.

In general, we are expecting that most resources will consist of a single language, but if more than one language is present, provide a <code>cc:lang</code> <category> for each.

=== Embedding license data ===

Since the licensing of a resource is expected to be conveyed via URL, we can leverage the Atom <link> element. However we must markup the link element so as to identify is as a license URL. This is accomplished with adding the attribute rel="license" to the <link> element. For example:

<pre><link rel="license" href="http://creativecommons.org/licenses/by/3.0/" /></pre>

See the complete [[Syndication|CC with syndication formats]] documentation for more information.

== Examples ==

=== Atom 1.0 example ===
Here is a sample, one entry Atom 1.0 feed which implements the guidelines above.

<pre>
<feed xmlns="http://www.w3.org/2005/Atom">
<id>http://oersite.org/cc/</id>
<title>OER Aggregation Web Site</title>
<updated>2008-01-16T12:00:00Z</updated>
<link rel="self" href="http://oersite.org/cc/atom.xml" type="application/atom+xml" />
<author>
<name>John Q. Public</name>
<email>webmaster@oersite.org</email>
</author>
<entry>
<id>tag:ocw.org,2007-10-15:/math/101</id>
<updated>2007-10-15T12:00:00Z</updated>
<link href="http://ocw.org/math/101" />
<title>Math 101</title>
<summary>Basic mathematics for 5th graders</summary>
<link rel="license" href="http://creativecommons.org/licenses/by/3.0/" />
<category term="cc:subject:Math" />
<category term="cc:gradelevel:5" />
<category term="cc:lang:en" />
</entry>
</feed>
</pre>

=== RSS 2.0 example ===
Here is a sample, one entry RSS 2.0 feed which implements the guidelines above.

<pre>
<?xml version="1.0"?>
<rss version="2.0"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>
<channel>
<title>OER Web Site</title>
<link>http://oersite.org/</link>
<atom:link rel="self" href="http://oersite.org/cc/rss20.xml" type="application/atom+xml" />
<description>OER Aggregation Web Site</description>
<lastBuildDate>Wed, 16 Jan 2008 15:00:00 -0800</lastBuildDate>
<webMaster>webmaster@oersite.org (John Q. Public)</webMaster>
<item>
<guid isPermaLink="false">tag:ocw.org,2007-10-15:/math/101</guid>
<pubDate>Mon, 12 Nov 2007 09:15:00 -0800</pubDate>
<link>http://ocw.org/math/101</link>
<title>Math 101</title>
<description>Basic mathematics for 5th graders</description>
<creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
<category>cc:subject:Math</category>
<category>cc:gradelevel:5</category>
<category>cc:lang:en</category>
</item>
</channel>
</rss>

</pre>

DiscoverEd Metadata

2008-01-29T19:59:55Z

Ahrash Bissell: /* Specifying Grade level */

{{draft}}

== Overview ==
This document outlines the format in which ccLearn would like to receive syndication feeds for the data that will go into our OER database.

The data must be supplied in an [http://www.atomenabled.org/developers/syndication/ Atom] or [http://www.rssboard.org/rss-specification RSS] format. Both of these standards are in widespread use on the Internet for content syndication.

Presently, ccLearn is looking for the following data:
* Link: Full URL of the referenced resource.
* Title: A brief descriptive title for the resource.
* Summary: A relatively short summary/synopsis of the resource.
* License: This should be a URL to the license; e.g., http://creativecommons.org/licenses/by/3.0/.
* Grade level (cc:gradelevel): What grade(s) or age-level(s) this material is suitable for.
* Language (cc:lang): The language(s) of the referenced resource (not of your site).
* Subject (cc:subject): The subject(s) of the resource; e.g., math.

<div style="border: 1px dashed #06f; margin: 0.5em auto 1em; padding:1em; margin-left:2em" class="boilerplate plainlinks" id="stub">
'''NOTE''': The sample Atom and RSS 2.0 feeds below mostly implement the minimum elements required by the respective specification plus the fields that ccLearn needs. For our purposes, a feed must minimally contain most of the elements in the examples below, but may also contain any other valid elements. Also, though '''we prefer an Atom feed''', there is no reason that another type of feed cannot be used, as long as it is able to include all of the data CC needs ''AND'' includes the data in such a way that the [http://feedparser.org Universal Feed Parser] can extract it in a normalized way.
</div>

== CC-specific categories (tags/fields) ==

The CC Specific fields do not have native Atom or RSS element definitions. For these fields we suggest that they be embedded as category or tag specifications (<code><category></code> in Atom) with a specific prefix. These have the general format of:

<pre>cc:<field>:<data></pre>

For example, the <code><category></code> content for Language would become something like:

<pre>cc:lang:es</pre>

Examples for Grade level could be:

<pre>cc:gradelevel:3
cc:gradelevel:primary</pre>

The Creative Commons-specific fields build upon existing category/tag support in feeds. Therefore any <code>cc:</code> field may be specified multiple times if needed. The fields we currently use for refining search results include:

* Subject: cc:subject:<data>
* Grade level: cc:gradelevel:<data>
* Language: cc:lang:<data>

=== Specifying Subject ===

The subject refers to the actual content in the resource; i.e., what is this resource ''about''? For many resources, more than one subject will be necessary; in this case, specify multiple subject <category> elements. We ask that you try to limit the number of elements to only those subjects that are objectively reflective of the entire resource. If you want to include other types of categories (opinions, metrics, etc), please add those as normal (un-prefixed) <category> elements instead.

=== Specifying Grade level ===

The grade level should indicate all grade levels (student ages) for which the resource is deemed appropriate. Though we will accept any descriptions that seem appropriate to you, please consider using one of the following schemas:

* primary, secondary, tertiary, adult;
* K,1,2,3,...,20 (where the number refers to the actual grade-level).

You may include equivalent terms as well by specifying more than one <code>cc:gradelevel</code> <category>. For example, you might include a <code>cc:gradelevel</code> for <code>9</code>, <code>10</code>, and <code>secondary</code>.

=== Specifying Language ===

When specifying the language for a resource, the value should be specifed as the [http://en.wikipedia.org/wiki/ISO_639-1 ISO-639-1] code. For example, <code>en</code> for English. When specifying a national dialect, the [http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 IS-3166 alpha-2] code should be appeneded. For example, to distinguish English (United States) from English (United Kindgom), the language would be specified as <code>en-US</code> and <code>en-GB</code>, respectively.

In general, we are expecting that most resources will consist of a single language, but if more than one language is present, provide a <code>cc:lang</code> <category> for each.

=== Embedding license data ===

Since the licensing of a resource is expected to be conveyed via URL, we can leverage the Atom <link> element. However we must markup the link element so as to identify is as a license URL. This is accomplished with adding the attribute rel="license" to the <link> element. For example:

<pre><link rel="license" href="http://creativecommons.org/licenses/by/3.0/" /></pre>

See the complete [[Syndication|CC with syndication formats]] documentation for more information.

== Examples ==

=== Atom 1.0 example ===
Here is a sample, one entry Atom 1.0 feed which implements the guidelines above.

<pre>
<feed xmlns="http://www.w3.org/2005/Atom">
<id>http://oersite.org/cc/</id>
<title>OER Aggregation Web Site</title>
<updated>2008-01-16T12:00:00Z</updated>
<link rel="self" href="http://oersite.org/cc/atom.xml" type="application/atom+xml" />
<author>
<name>John Q. Public</name>
<email>webmaster@oersite.org</email>
</author>
<entry>
<id>tag:ocw.org,2007-10-15:/math/101</id>
<updated>2007-10-15T12:00:00Z</updated>
<link href="http://ocw.org/math/101" />
<title>Math 101</title>
<summary>Basic mathematics for 5th graders</summary>
<link rel="license" href="http://creativecommons.org/licenses/by/3.0/" />
<category term="cc:subject:Math" />
<category term="cc:gradelevel:5" />
<category term="cc:lang:en" />
</entry>
</feed>
</pre>

=== RSS 2.0 example ===
Here is a sample, one entry RSS 2.0 feed which implements the guidelines above.

<pre>
<?xml version="1.0"?>
<rss version="2.0"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>
<channel>
<title>OER Web Site</title>
<link>http://oersite.org/</link>
<atom:link rel="self" href="http://oersite.org/cc/rss20.xml" type="application/atom+xml" />
<description>OER Aggregation Web Site</description>
<lastBuildDate>Wed, 16 Jan 2008 15:00:00 -0800</lastBuildDate>
<webMaster>webmaster@oersite.org (John Q. Public)</webMaster>
<item>
<guid isPermaLink="false">tag:ocw.org,2007-10-15:/math/101</guid>
<pubDate>Mon, 12 Nov 2007 09:15:00 -0800</pubDate>
<link>http://ocw.org/math/101</link>
<title>Math 101</title>
<description>Basic mathematics for 5th graders</description>
<creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
<category>cc:subject:Math</category>
<category>cc:gradelevel:5</category>
<category>cc:lang:en</category>
</item>
</channel>
</rss>

</pre>

DiscoverEd Metadata

2008-01-22T06:13:28Z

Ahrash Bissell: /* CC-specific categories (fields) */

__TOC__

== General ==
This document outlines the format in which ccLearn would like to receive syndication feeds for the data that will go into our OER database.

The data must be supplied in an [http://www.atomenabled.org/developers/syndication/ Atom] or [http://www.rssboard.org/rss-specification RSS] format. These are two very well documented XML formats and are implemented by many content management systems.

'''NOTE''': The sample Atom and RSS feeds below mostly implement the minimum elements required by the respective specification plus the fields that ccLearn needs. For our purposes, a feed must minimally contain the elements in the examples below, but may also contain any other valid elements. Also, though we prefer an Atom feed, there is no reason that another type of feed cannot be used, as long as it is able to include all of the data CC needs ''AND'' includes the data in such a way that the [http://feedparser.org Universal Feed Parser] can extract it in a normalized way.

Presently, ccLearn is looking for the following data:
* Link: Full URL of the referenced resource.
* Title: A brief descriptive title for the resource.
* Summary: A relatively short summary/synopsis of the resource.
* License: This should be a URL to the license; e.g., http://creativecommons.org/licenses/by/3.0/.
* Grade level (cc:gradelevel): What grade(s) or age-level(s) this material is suitable for.
* Language (cc:lang): The language(s) of the referenced resource (not of your site).
* Subject (cc:subject): The subject(s) of the resource; e.g., math.

If you want to use more than one entry for any or all of the grade-level, language, and subject fields, simply comma-separate each annotation.

== CC-specific categories (fields) ==

Some of these fields do not have native Atom or RSS element definitions. For these fields we suggest that they be embedded as tags. In order for us to be able to recognize these within the feed, the tag content should be of the format

<blockquote>cc:<field>:<data></blockquote>

For example, the tag for Language would become something like:

<pre>cc:lang:es</pre>

Another example for Grade level could be:

<pre>cc:gradelevel:3,4,5,primary</pre>

The "cc:" specific fields should be embedded precisely as specified above in parentheses:
* Subject: cc:subject:<data>
* Grade level: cc:gradelevel:<data>
* Language: cc:lang:<data>

=== Specifying Subject ===

The subject refers to the actual content in the resource; i.e., what is this resource 'about'? For many resources, more than one subject will be necessary (comma-separated), but we ask that you try to limit the number of tags to only those subjects that are objectively reflective of the entire resource. If you want to include other types of tags (opinions, metrics, etc), please add those to the free-form "tag" field instead.

=== Specifying Grade level ===

The grade level should indicate all grade levels (student ages) for which the resource is deemed appropriate. While we are not asking for everyone to adhere to a single standard, you might consider using one of the following schemas: 1) primary, secondary, tertiary, adult; or 2) K,1,2,3,...,20 (where the number refers to the actual grade-level). You may include equivalent terms as well (e.g., grades 9-10 are part of secondary education, so you can annotate: 9,10,secondary), separated by commas. If we are confused by a grade-evel schema, we may contact you for further clarification.

=== Specifying Language ===

When specifying the language for a resource, the value should be specifed as the [http://en.wikipedia.org/wiki/ISO_639-1 ISO-639-1] code. For example, <code>en</code> for English. When specifying a national dialect, the [http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 IS-3166 alpha-2] code should be appeneded. For example, to distinguish English (United States) from English (United Kindgom), the language would be specified as <code>en-US</code> and <code>en-GB</code>, respectively.

In general, we are expecting that most resources will consist of a single language, but if more than one language is present, separate each entry with a comma.

=== Embedding license data ===

Since the licensing of a resource is expected to be conveyed via URL, we can leverage the Atom <link> element. However we must markup the link element so as to identify is as a license URL. This is accomplished with adding the attribute rel="license" to the <link> element. For example:

<pre><link rel="license" href="http://creativecommons.org/licenses/by/3.0/" /></pre>

See the [[Atom|complete CC+Atom]] documentation for more information.

== Examples ==

=== Atom 1.0 example ===
Here is a sample, one entry Atom 1.0 feed which implements the guidelines above.

<pre>
<feed xmlns="http://www.w3.org/2005/Atom">
<id>http://oersite.org/cc/</id>
<title>OER Aggregation Web Site</title>
<updated>2008-01-16T12:00:00Z</updated>
<link rel="self" href="http://oersite.org/cc/atom.xml" type="application/atom+xml" />
<author>
<name>John Q. Public</name>
<email>webmaster@oersite.org</email>
</author>
<entry>
<id>tag:ocw.org,2007-10-15:/math/101</id>
<updated>2007-10-15T12:00:00Z</updated>
<link href="http://ocw.org/math/101" />
<title>Math 101</title>
<summary>Basic mathematics for 5th graders</summary>
<link rel="license" href="http://creativecommons.org/licenses/by/3.0/" />
<category term="cc:subject:Math" />
<category term="cc:gradelevel:5-7" />
<category term="cc:lang:en" />
</entry>
</feed>
</pre>

=== RSS 2.0 example ===
Here is a sample, one entry RSS 2.0 feed which implements the guidelines above.

<pre>
<?xml version="1.0"?>
<rss version="2.0"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>
<channel>
<title>OER Web Site</title>
<link>http://oersite.org/</link>
<atom:link rel="self" href="http://oersite.org/cc/rss20.xml" type="application/atom+xml" />
<description>OER Aggregation Web Site</description>
<lastBuildDate>Wed, 16 Jan 2008 15:00:00 -0800</lastBuildDate>
<webMaster>webmaster@oersite.org (John Q. Public)</webMaster>
<item>
<guid isPermaLink="false">tag:ocw.org,2007-10-15:/math/101</guid>
<pubDate>Mon, 12 Nov 2007 09:15:00 -0800</pubDate>
<link>http://ocw.org/math/101</link>
<title>Math 101</title>
<description>Basic mathematics for 5th graders</description>
<creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
<category>cc:subject:Math</category>
<category>cc:gradelevel:5-7</category>
<category>cc:lang:en</category>
</item>
</channel>
</rss>

</pre>

DiscoverEd Metadata

2008-01-22T06:04:50Z

Ahrash Bissell: /* CC-specific categories (fields) */

__TOC__

== General ==
This document outlines the format in which ccLearn would like to receive syndication feeds for the data that will go into our OER database.

The data must be supplied in an [http://www.atomenabled.org/developers/syndication/ Atom] or [http://www.rssboard.org/rss-specification RSS] format. These are two very well documented XML formats and are implemented by many content management systems.

'''NOTE''': The sample Atom and RSS feeds below mostly implement the minimum elements required by the respective specification plus the fields that ccLearn needs. For our purposes, a feed must minimally contain the elements in the examples below, but may also contain any other valid elements. Also, though we prefer an Atom feed, there is no reason that another type of feed cannot be used, as long as it is able to include all of the data CC needs ''AND'' includes the data in such a way that the [http://feedparser.org Universal Feed Parser] can extract it in a normalized way.

Presently, ccLearn is looking for the following data:
* Link: Full URL of the referenced resource.
* Title: A brief descriptive title for the resource.
* Summary: A relatively short summary/synopsis of the resource.
* License: This should be a URL to the license; e.g., http://creativecommons.org/licenses/by/3.0/.
* Grade level (cc:gradelevel): What grade(s) or age-level(s) this material is suitable for.
* Language (cc:lang): The language(s) of the referenced resource (not of your site).
* Subject (cc:subject): The subject(s) of the resource; e.g., math.

If you want to use more than one entry for any or all of the grade-level, language, and subject fields, simply comma-separate each annotation.

== CC-specific categories (fields) ==

Some of these fields do not have native Atom or RSS element definitions. For these fields we suggest that they be embedded as tags. In order for us to be able to recognize these within the feed, the tag content should be of the format

<blockquote>cc:<field>:<data></blockquote>

For example, the tag for Language would become something like:

<pre>cc:lang:es</pre>

Another example for Grade level could be:

<pre>cc:gradelevel:3,4,5,primary</pre>

The "cc:" specific fields should be embedded precisely as specified above in parentheses:
* Subject: cc:subject:<data>
* Grade level: cc:gradelevel:<data>
* Language: cc:lang:<data>

=== Specifying Language ===

When specifying the language for a resource, the value should be specifed as the [http://en.wikipedia.org/wiki/ISO_639-1 ISO-639-1] code. For example, <code>en</code> for English. When specifying a national dialect, the [http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 IS-3166 alpha-2] code should be appeneded. For example, to distinguish English (United States) from English (United Kindgom), the language would be specified as <code>en-US</code> and <code>en-GB</code>, respectively.

In general, we are expecting that most resources will consist of a single language, but if more than one language is present, separate each entry with a comma.

=== Embedding license data ===

Since the licensing of a resource is expected to be conveyed via URL, we can leverage the Atom <link> element. However we must markup the link element so as to identify is as a license URL. This is accomplished with adding the attribute rel="license" to the <link> element. For example:

<pre><link rel="license" href="http://creativecommons.org/licenses/by/3.0/" /></pre>

See the [[Atom|complete CC+Atom]] documentation for more information.

== Examples ==

=== Atom 1.0 example ===
Here is a sample, one entry Atom 1.0 feed which implements the guidelines above.

<pre>
<feed xmlns="http://www.w3.org/2005/Atom">
<id>http://oersite.org/cc/</id>
<title>OER Aggregation Web Site</title>
<updated>2008-01-16T12:00:00Z</updated>
<link rel="self" href="http://oersite.org/cc/atom.xml" type="application/atom+xml" />
<author>
<name>John Q. Public</name>
<email>webmaster@oersite.org</email>
</author>
<entry>
<id>tag:ocw.org,2007-10-15:/math/101</id>
<updated>2007-10-15T12:00:00Z</updated>
<link href="http://ocw.org/math/101" />
<title>Math 101</title>
<summary>Basic mathematics for 5th graders</summary>
<link rel="license" href="http://creativecommons.org/licenses/by/3.0/" />
<category term="cc:subject:Math" />
<category term="cc:gradelevel:5-7" />
<category term="cc:lang:en" />
</entry>
</feed>
</pre>

=== RSS 2.0 example ===
Here is a sample, one entry RSS 2.0 feed which implements the guidelines above.

<pre>
<?xml version="1.0"?>
<rss version="2.0"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>
<channel>
<title>OER Web Site</title>
<link>http://oersite.org/</link>
<atom:link rel="self" href="http://oersite.org/cc/rss20.xml" type="application/atom+xml" />
<description>OER Aggregation Web Site</description>
<lastBuildDate>Wed, 16 Jan 2008 15:00:00 -0800</lastBuildDate>
<webMaster>webmaster@oersite.org (John Q. Public)</webMaster>
<item>
<guid isPermaLink="false">tag:ocw.org,2007-10-15:/math/101</guid>
<pubDate>Mon, 12 Nov 2007 09:15:00 -0800</pubDate>
<link>http://ocw.org/math/101</link>
<title>Math 101</title>
<description>Basic mathematics for 5th graders</description>
<creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
<category>cc:subject:Math</category>
<category>cc:gradelevel:5-7</category>
<category>cc:lang:en</category>
</item>
</channel>
</rss>

</pre>

DiscoverEd Metadata

2008-01-22T06:02:24Z

Ahrash Bissell: /* General */

__TOC__

== General ==
This document outlines the format in which ccLearn would like to receive syndication feeds for the data that will go into our OER database.

The data must be supplied in an [http://www.atomenabled.org/developers/syndication/ Atom] or [http://www.rssboard.org/rss-specification RSS] format. These are two very well documented XML formats and are implemented by many content management systems.

'''NOTE''': The sample Atom and RSS feeds below mostly implement the minimum elements required by the respective specification plus the fields that ccLearn needs. For our purposes, a feed must minimally contain the elements in the examples below, but may also contain any other valid elements. Also, though we prefer an Atom feed, there is no reason that another type of feed cannot be used, as long as it is able to include all of the data CC needs ''AND'' includes the data in such a way that the [http://feedparser.org Universal Feed Parser] can extract it in a normalized way.

Presently, ccLearn is looking for the following data:
* Link: Full URL of the referenced resource.
* Title: A brief descriptive title for the resource.
* Summary: A relatively short summary/synopsis of the resource.
* License: This should be a URL to the license; e.g., http://creativecommons.org/licenses/by/3.0/.
* Grade level (cc:gradelevel): What grade(s) or age-level(s) this material is suitable for.
* Language (cc:lang): The language(s) of the referenced resource (not of your site).
* Subject (cc:subject): The subject(s) of the resource; e.g., math.

If you want to use more than one entry for any or all of the grade-level, language, and subject fields, simply comma-separate each annotation.

== CC-specific categories (fields) ==

Some of these fields do not have native Atom or RSS element definitions. For these fields we suggest that they be embedded as tags. In order for us to be able to recognize these within the feed, the tag content should be of the format

<blockquote>cc:<field>:<data></blockquote>

For example, the tag for Language would become something like:

<pre>cc:lang:es</pre>

Another example for Grade level could be:

<pre>cc:gradelevel:5-7</pre>

The "cc:" specific fields should be embedded precisely as specified above in parentheses:
* Subject: cc:subject:<data>
* Grade level: cc:gradelevel:<data>
* Language: cc:lang:<data>

=== Specifying Language ===

When specifying the language for a resource, the value should be specifed as the [http://en.wikipedia.org/wiki/ISO_639-1 ISO-639-1] code. For example, <code>en</code> for English. When specifying a national dialect, the [http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 IS-3166 alpha-2] code should be appeneded. For example, to distinguish English (United States) from English (United Kindgom), the language would be specified as <code>en-US</code> and <code>en-GB</code>, respectively.

=== Embedding license data ===

Since the licensing of a resource is expected to be conveyed via URL, we can leverage the Atom <link> element. However we must markup the link element so as to identify is as a license URL. This is accomplished with adding an the attribute rel="license" to the <link> element. For example:

<pre><link rel="license" href="http://creativecommons.org/licenses/by/3.0/" /></pre>

See the [[Atom|complete CC+Atom]] documentation for more information.

== Examples ==

=== Atom 1.0 example ===
Here is a sample, one entry Atom 1.0 feed which implements the guidelines above.

<pre>
<feed xmlns="http://www.w3.org/2005/Atom">
<id>http://oersite.org/cc/</id>
<title>OER Aggregation Web Site</title>
<updated>2008-01-16T12:00:00Z</updated>
<link rel="self" href="http://oersite.org/cc/atom.xml" type="application/atom+xml" />
<author>
<name>John Q. Public</name>
<email>webmaster@oersite.org</email>
</author>
<entry>
<id>tag:ocw.org,2007-10-15:/math/101</id>
<updated>2007-10-15T12:00:00Z</updated>
<link href="http://ocw.org/math/101" />
<title>Math 101</title>
<summary>Basic mathematics for 5th graders</summary>
<link rel="license" href="http://creativecommons.org/licenses/by/3.0/" />
<category term="cc:subject:Math" />
<category term="cc:gradelevel:5-7" />
<category term="cc:lang:en" />
</entry>
</feed>
</pre>

=== RSS 2.0 example ===
Here is a sample, one entry RSS 2.0 feed which implements the guidelines above.

<pre>
<?xml version="1.0"?>
<rss version="2.0"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>
<channel>
<title>OER Web Site</title>
<link>http://oersite.org/</link>
<atom:link rel="self" href="http://oersite.org/cc/rss20.xml" type="application/atom+xml" />
<description>OER Aggregation Web Site</description>
<lastBuildDate>Wed, 16 Jan 2008 15:00:00 -0800</lastBuildDate>
<webMaster>webmaster@oersite.org (John Q. Public)</webMaster>
<item>
<guid isPermaLink="false">tag:ocw.org,2007-10-15:/math/101</guid>
<pubDate>Mon, 12 Nov 2007 09:15:00 -0800</pubDate>
<link>http://ocw.org/math/101</link>
<title>Math 101</title>
<description>Basic mathematics for 5th graders</description>
<creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
<category>cc:subject:Math</category>
<category>cc:gradelevel:5-7</category>
<category>cc:lang:en</category>
</item>
</channel>
</rss>

</pre>

DiscoverEd Metadata

2008-01-22T06:00:36Z

Ahrash Bissell: /* General */

__TOC__

== General ==
This document outlines the format in which ccLearn would like to receive syndication feeds for the data that will go into our OER database.

The data must be supplied in an [http://www.atomenabled.org/developers/syndication/ Atom] or [http://www.rssboard.org/rss-specification RSS] format. These are two very well documented XML formats and are implemented by many content management systems.

'''NOTE''': The sample Atom and RSS feeds below mostly implement the minimum elements required by the respective specification plus the fields that ccLearn needs. For our purposes, a feed must minimally contain the elements in the examples below, but may also contain any other valid elements. Also, though we prefer an Atom feed, there is no reason that another type of feed cannot be used, as long as it is able to include all of the data CC needs ''AND'' includes the data in such a way that the [http://feedparser.org Universal Feed Parser] can extract it in a normalized way.

Presently, ccLearn is looking for the following data:
* Link: Full URL of the referenced resource.
* Title: A brief descriptive title for the resource.
* Summary: A relatively short summary/synopsis of the resource.
* License: This should be a URL to the license; e.g., http://creativecommons.org/licenses/by/3.0/.
* Grade level (cc:gradelevel): What grade(s) or age-level(s) this material is suitable for.
* Language (cc:lang): The language(s) of the referenced resource (not of your site).
* Subject (cc:subject): The subject(s) of the resource; e.g., math.

== CC-specific categories (fields) ==

Some of these fields do not have native Atom or RSS element definitions. For these fields we suggest that they be embedded as tags. In order for us to be able to recognize these within the feed, the tag content should be of the format

<blockquote>cc:<field>:<data></blockquote>

For example, the tag for Language would become something like:

<pre>cc:lang:es</pre>

Another example for Grade level could be:

<pre>cc:gradelevel:5-7</pre>

The "cc:" specific fields should be embedded precisely as specified above in parentheses:
* Subject: cc:subject:<data>
* Grade level: cc:gradelevel:<data>
* Language: cc:lang:<data>

=== Specifying Language ===

When specifying the language for a resource, the value should be specifed as the [http://en.wikipedia.org/wiki/ISO_639-1 ISO-639-1] code. For example, <code>en</code> for English. When specifying a national dialect, the [http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 IS-3166 alpha-2] code should be appeneded. For example, to distinguish English (United States) from English (United Kindgom), the language would be specified as <code>en-US</code> and <code>en-GB</code>, respectively.

=== Embedding license data ===

Since the licensing of a resource is expected to be conveyed via URL, we can leverage the Atom <link> element. However we must markup the link element so as to identify is as a license URL. This is accomplished with adding an the attribute rel="license" to the <link> element. For example:

<pre><link rel="license" href="http://creativecommons.org/licenses/by/3.0/" /></pre>

See the [[Atom|complete CC+Atom]] documentation for more information.

== Examples ==

=== Atom 1.0 example ===
Here is a sample, one entry Atom 1.0 feed which implements the guidelines above.

<pre>
<feed xmlns="http://www.w3.org/2005/Atom">
<id>http://oersite.org/cc/</id>
<title>OER Aggregation Web Site</title>
<updated>2008-01-16T12:00:00Z</updated>
<link rel="self" href="http://oersite.org/cc/atom.xml" type="application/atom+xml" />
<author>
<name>John Q. Public</name>
<email>webmaster@oersite.org</email>
</author>
<entry>
<id>tag:ocw.org,2007-10-15:/math/101</id>
<updated>2007-10-15T12:00:00Z</updated>
<link href="http://ocw.org/math/101" />
<title>Math 101</title>
<summary>Basic mathematics for 5th graders</summary>
<link rel="license" href="http://creativecommons.org/licenses/by/3.0/" />
<category term="cc:subject:Math" />
<category term="cc:gradelevel:5-7" />
<category term="cc:lang:en" />
</entry>
</feed>
</pre>

=== RSS 2.0 example ===
Here is a sample, one entry RSS 2.0 feed which implements the guidelines above.

<pre>
<?xml version="1.0"?>
<rss version="2.0"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>
<channel>
<title>OER Web Site</title>
<link>http://oersite.org/</link>
<atom:link rel="self" href="http://oersite.org/cc/rss20.xml" type="application/atom+xml" />
<description>OER Aggregation Web Site</description>
<lastBuildDate>Wed, 16 Jan 2008 15:00:00 -0800</lastBuildDate>
<webMaster>webmaster@oersite.org (John Q. Public)</webMaster>
<item>
<guid isPermaLink="false">tag:ocw.org,2007-10-15:/math/101</guid>
<pubDate>Mon, 12 Nov 2007 09:15:00 -0800</pubDate>
<link>http://ocw.org/math/101</link>
<title>Math 101</title>
<description>Basic mathematics for 5th graders</description>
<creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license>
<category>cc:subject:Math</category>
<category>cc:gradelevel:5-7</category>
<category>cc:lang:en</category>
</item>
</channel>
</rss>

</pre>

CcLearn and licensing for education

2007-11-27T18:22:44Z

Ahrash Bissell: New page: {{Presentation |venue=UN IGF forum - Rio de Janeiro, Brazil |date=November 12, 2007 |presenter=Ariel Vercelli }} Ariel Vercelli (CCi - Argentina) represented ccLearn on a special panel on ...

{{Presentation
|venue=UN IGF forum - Rio de Janeiro, Brazil
|date=November 12, 2007
|presenter=Ariel Vercelli
}}
Ariel Vercelli (CCi - Argentina) represented ccLearn on a special panel on licensing, fair-use, and exceptions in education at the United Nations Internet Government Forum.

Open Education Video Studio launch

2007-11-27T18:20:30Z

Ahrash Bissell: New page: {{Presentation |venue=Hewlett Foundation |date=November 15, 2007 |presenter=Ahrash Bissell }} Invitation only event to launch Intelligent TV's Open Education Video Studio. Many contacts.

{{Presentation
|venue=Hewlett Foundation
|date=November 15, 2007
|presenter=Ahrash Bissell
}}
Invitation only event to launch Intelligent TV's Open Education Video Studio. Many contacts.

EUN project - LRE conference

2007-11-27T18:19:10Z

Ahrash Bissell: New page: {{Presentation |venue=Brussels, Netherlands |date=November 9, 2007 |presenter=Martijn Arnoldus }} Martijn (CCi - Netherlands) represented ccLearn at the Learning Resource Exchange (LRE) co...

{{Presentation
|venue=Brussels, Netherlands
|date=November 9, 2007
|presenter=Martijn Arnoldus
}}
Martijn (CCi - Netherlands) represented ccLearn at the Learning Resource Exchange (LRE) conference for the European Schoolnet (EUN) project.

Virtual Environments for Learning

2007-11-27T18:12:08Z

Ahrash Bissell: New page: {{Presentation |venue=NSF hosted - Boulder, CO |date=November 8, 2007 |presenter=Ahrash Bissell }} Invitation-only conference. Included many major foundations and tech companies. Many cont...

{{Presentation
|venue=NSF hosted - Boulder, CO
|date=November 8, 2007
|presenter=Ahrash Bissell
}}
Invitation-only conference. Included many major foundations and tech companies. Many contacts.

OpenLearn conference

2007-11-27T18:10:44Z

Ahrash Bissell: New page: {{Presentation |venue=Open University, UK |date=October 30, 2007 |presenter=Ahrash Bissell }} No formal presentation. Many contacts.

{{Presentation
|venue=Open University, UK
|date=October 30, 2007
|presenter=Ahrash Bissell
}}
No formal presentation. Many contacts.

Professional and Organizational Development (POD) in Higher Education annual conference

2007-11-27T18:09:20Z

Ahrash Bissell:

{{Presentation
|venue=POD - Pittsburgh, PA
|date=October 26, 2007
|presenter=Ahrash Bissell
}}
Tabled for CC and ccLearn.

Professional and Organizational Development (POD) in Higher Education annual conference

2007-11-27T18:07:48Z

Ahrash Bissell:

{{Presentation
|venue=POD - Pittsburgh, PA
|date=October 26, 2007
|presenter=Ahrash Bissell
}}

Professional and Organizational Development (POD) in Higher Education annual conference

2007-11-27T18:07:20Z

Ahrash Bissell: New page: {{Presentation |venue=POD - Pittsburgh, PA |date=October 26, 2007 |presenter=Ahrash Bissell, Amanda Curtin }}

{{Presentation
|venue=POD - Pittsburgh, PA
|date=October 26, 2007
|presenter=Ahrash Bissell, Amanda Curtin
}}

Cape Town meeting: Mapping the Open Educational Space

2007-11-27T18:05:09Z

Ahrash Bissell: New page: {{Presentation |venue=Shuttleworth Foundation |date=September 14, 2007 |presenter=Ahrash Bissell }} Invitation-only meeting - leading to Declaration on Open Education.

{{Presentation
|venue=Shuttleworth Foundation
|date=September 14, 2007
|presenter=Ahrash Bissell
}}
Invitation-only meeting - leading to Declaration on Open Education.

User:Ahrash Bissell

2007-11-27T17:40:41Z

Ahrash Bissell: New page: Ahrash N Bissell, Ph.D Executive Director, ccLearn Creative Commons 415-369-8490 ahrash@creativecommons.org

Ahrash N Bissell, Ph.D
Executive Director, ccLearn
Creative Commons
415-369-8490
ahrash@creativecommons.org

CcLearn: Open Education Search project

2007-11-27T17:39:40Z

Ahrash Bissell:

{{Presentation
|venue=Consortium for Open and Sustainable Learning (COSL) annual meeting
|date=September 27, 2007
|presenter=Ahrash Bissell,Nathan Yergler,Phoenix Wang
}}

What is ccLearn?

2007-11-27T17:38:03Z

Ahrash Bissell: New page: {{Presentation |venue=Open Courseware Consortium (OCWC) annual meeting |date=September 25, 2007 |presenter=Ahrash Bissell, Nathan Yergler }} Utah State University

{{Presentation
|venue=Open Courseware Consortium (OCWC) annual meeting
|date=September 25, 2007
|presenter=Ahrash Bissell, Nathan Yergler
}}
Utah State University

The Open Education Movement at a Crossroads: Silos, Services and Sustainability

2007-11-27T17:33:39Z

Ahrash Bissell: New page: {{Presentation |venue=UC Berkeley School of Information |date=October 23, 2007 |presenter=Ahrash Bissell }} ccLearn,interoperability

{{Presentation
|venue=UC Berkeley School of Information
|date=October 23, 2007
|presenter=Ahrash Bissell
}}
ccLearn,interoperability

CcLearn: Open Education Search project

2007-11-27T17:31:22Z

Ahrash Bissell: New page: {{Presentation |venue=Consortium for Open and Sustainable Learning (COSL) annual meeting |date=September 26, 2007 |presenter=Ahrash Bissell }}

{{Presentation
|venue=Consortium for Open and Sustainable Learning (COSL) annual meeting
|date=September 26, 2007
|presenter=Ahrash Bissell
}}

Guiding Principles for Open Education...

2007-11-27T17:29:27Z

Ahrash Bissell: New page: {{Presentation |venue=Consortium for Open and Sustainable Learning (COSL) annual meeting |date=September 27, 2007 |presenter=Ahrash Bissell }} Utah State University,ccLearn,licensing

{{Presentation
|venue=Consortium for Open and Sustainable Learning (COSL) annual meeting
|date=September 27, 2007
|presenter=Ahrash Bissell
}}
Utah State University,ccLearn,licensing

Towards a Global Learning Commons: ccLearn

2007-11-27T17:17:57Z

Ahrash Bissell: New page: {{Press |publication=Educational Technology Magazine |date=November 1, 2007 |author=Ahrash Bissell and Jamie Boyle }}

{{Press
|publication=Educational Technology Magazine
|date=November 1, 2007
|author=Ahrash Bissell and Jamie Boyle
}}

Version 3

2007-10-12T21:03:59Z

Ahrash Bissell: /* ''by Mia Garlick, General Counsel Creative Commons'' */

= Creative Commons Version 3.0 Licenses — A Brief Explanation =

===''by Mia Garlick, General Counsel Creative Commons''===

Since April 2005, Creative Commons has been working on versioning up its core licensing suite. The Creative Commons licenses (For an overview of the licenses, ''see:'' [http://creativecommons.org/about/licenses/meet-the-licenses]) serve as an important vehicle by which many millions of creators clearly signal to the world that they are happy for members of the public to engage in some of the exciting new uses of content that are made possible by digital technologies. Using a CC license, an artist can, for example, invite the public to share their work or mash it up (on certain conditions).

A distinctive feature of CC’s licensing infrastructure is ensuring that it is comprehensible to both humans (the Commons Deed) and machines (the metadata) as well as enforceable in a court of law (the Legal Code, which is the actual license). But another important aspect of the CC licensing system is to ensure that it respected by the community of people who apply our licenses to their content, who use CC-licensed content and who are committed to enabling free culture.

Creative Commons regularly invites and receives feedback about its licenses and how they may be able to be improved to better serve the people who use them and who use CC-licensed content. Obviously, all things can be improved with the benefit of hindsight and experience; also, the environment within which CC licenses are used is always changing. When CC first released its licenses, for example, the use of video and video-sharing sites had not yet been deployed, let alone used to the extent they are today.

We released version 1.0 of our licenses in December 2002 (''See'' CC Weblog, Creative Commons Launches, December 15, 2002, [http://creativecommons.org/weblog/entry/3484]). Like software releases, we track the different licenses by version. In May 2004, we versioned to 2.0 (''See'' CC Weblog, Announcing (and explaining) our new 2.0 licenses, May 25, 2004, [http://creativecommons.org/weblog/entry/4216]) and then made a minor tweak to the attribution clause in June 2005 (''See'' CC Weblog, Comments Period Drawing to a Close for Draft License Version 2.5, May 29, 2006, [http://creativecommons.org/weblog/entry/5457]) and versioned to 2.5. Now, CC is versioning to 3.0. We announced a timetable for versioning to 3.0 back in May 2006 (''See'' Mia Garlick, ‘Getting to Version 3.0,’ May 17, 2006, [http://lists.ibiblio.org/pipermail/cc-licenses/2006-May/003557.html]); and we have followed the consultation process in the timetable even though the schedule itself has been considerably delayed while we take account of all of the different interest groups that are relevant to CC licenses.

==Background to Version 3.0==

The process of versioning to 3.0 began back around April 2005 as part of discussions with Debian [http://www.debian.org/] and the Massachusetts Institute of Technology (MIT) [http://mit.edu/] about ways to improve the clarity of our licenses. Although discussions with Debian and MIT initiated consideration of a new license version, ultimately, version 3.0 grew to be about much more than these two projects — it focused on internationalizing the “generic” license and international harmonization of the CC licenses. Additionally, it expanded to encompass Creative Commons' long-held vision [http://creativecommons.org/weblog/entry/5709] of establishing a compatibility structure to allow interoperability between different flexible content copyright licenses.

===''Debian''===

As you may know, Debian describes itself as “an association of individuals who have made common cause to create a free operating system” [http://www.us.debian.org/intro/about] and the volunteer group has worked together to create an operating system called Debian GNU/Linux. The project and all developers working on the project adhere to the Debian Social Contract [http://www.us.debian.org/social_contract]. The Debian Free Software Guidelines (DSFG) [http://www.us.debian.org/social_contract#guidelines] form part of the Debian Social Contract and define the criteria for “free software” and so what software is permissible in the distribution.

One part of the Debian community is debian-legal [http://lists.debian.org/debian-legal/] — a mailing list whose members provide “guidance for the Debian project on, among other things, the acceptability of software and other content for inclusion in the Debian operating system.” [http://people.debian.org/~evan/ccsummary.html] They work primarily involves reviewing software against the DFSG to determine if the packages constitute “free software” per the DFSG. Contributors to the Debian project can then take these determination into account when making decisions about what to include in individual packages.

From time to time the debian-legal list provides a review of a well-known software license to express a rough consensus opinion on whether software released solely under the license would satisfy the definition of “free software” according to the DSFG. Although these summaries are not binding, they do provide some basis for the Debian project to make decisions about individual packages. Although debian-legal work primarily in reviewing software programs and Creative Commons licenses are not designed for software, debian-legal notes that the:

“Creative Commons licenses are still of interest to the Debian project. Debian includes documentation for programs, and many programs included in Debian use digital data such as images, sounds, video, or text that are included with the programs in Debian.” (''Id.'')

Consequently, debian-legal reviewed the CC licenses and concluded that none of the Creative Commons core licensees were free according to the DFSG and recommended that works released under these license “should not be included in Debian.” (''Id.'')

It is clear that the licenses that contain a NonCommercial or a NoDerivatives restriction (e.g. Attribution-NonCommercial, Attribution-NonCommercial-ShareAlike, Attribution-NoDerivatives, Attribution-NonCommercial-NoDerivatives ) will never be able to comply with the DFSG because these violate basic principles articulate in the DSFG — specifically, DSFG 1 which requires that a licensee be able to sell copies of the work, DSFG 3 which requires a license to permit the making of derivative works and DSFG 6 which proscribes discrimination against any field of endeavor.

But this should still leave the CC Attribution and Attribution-ShareAlike licenses as DSFG-compliant. On reviewing debian-legal’s issues with these licenses, it seemed clear to Creative Commons that, for the most part, minor amendments and clarifications to the licenses should be able to address debian-legal’s concerns. (For an outline of these concerns, see [http://people.debian.org/~evan/ccsummary]) One topic, however, that was not minor and proved to be much debated as part of the version 3.0 license discussions was the anti-TPM clause in the CC licenses; TPM being technological protection measures such as encryption which have received legal protection in many jurisdictions around the world, which make it a civil (and sometimes) a criminal offence to circumvent these measures.

The Creative Commons licenses prohibit a licensee applying a TPM to a licensed work that restricts the rights granted under the license. (''See e.g.,'' clause 4(a) “You may not distribute, publicly display, publicly perform, or publicly digitally perform the Work with any technological measures that control access or use of the Work in a manner inconsistent with the terms of this License Agreement.” of the CC Attribution license ([http://creativecommons.org/licenses/by/2.5/legalcode])) In essence, this clause is intended to ensure that a person cannot exercise the freedoms granted by a CC license to apply technologies that restrict those freedoms for others.

In Debian’s view, this prohibition violates DSFG #1 because it prevents a licensee from being able to distribute works in the format of their choice. The consequence of this is that CC-licensed content cannot, for example, be included by a licensee in a Sony Playstation game or other platforms that exist on TPM.

An important thing to note, however, is that this limitation only applied to CC licensees. CC licensors are of course free to license their works on a Sony or other TPM-ed platform whilst also CC licensing it. One example of this is the Beastie Boys track ‘Now Get Busy’ that appeared on the WIRED CD under a CC Sampling license [http://creativecommons.org/wired] but was then also made available on iTunes [http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewAlbum?playlistId=15146499&selectedItemId=15146497&s=143441 ].

To avoid interfering with the freedom of the licensed content and allowing a licensee to lock up the content on a TPM-ed platform, Debian proposed that CC’s so-called “anti-TPM” provision to allow a licensee to distribute the CC-licensed work in any format, including a TPM-ed format, provided that the license distributed the work in at least one format that did not restrict another person’s exercise of rights under the license. This proposal became known as the “parallel distribution” proposal.

Creative Commons initially agreed to include the parallel distribution proposal as part of the discussion draft for the Version 3.0 amendments. The rationale for this initial acceptance was that it could accommodate the objectives of the anti-TPM clause (being free culture) whilst also addressing Debian’s concerns that people be free to create works for distribution on TPM-ed platforms.

The parallel distribution proposal did not, however, survive discussions with the Creative Commons International affiliates [http://creativecommons.org/worldwide/]. The affiliates are responsible for “porting” the CC licenses to their local jurisdiction (discussed in greater detail below) and for fielding a wide range of questions about CC licenses and their implementation in various projects throughout the world. Based on their experience with the diverse communities that use and rely on CC licenses and explaining the licenses to different constituencies, the CCi affiliates were strongly opposed to the introduction of a parallel distribution scenario for various reasons, including: (1) the lack of demonstrated use cases showing a strong need among CC licensees for this kind of an exception to the existing “anti-TPM” language; (2) risks of unduly complicating the licenses which defeats alot of the purpose of CC licenses, namely to be simple and easy to use and to understand; and, (3) the strong opposition to technological protection measures in general by many in the CC community.

CC did, however, include the parallel distribution proposal as part of the public license discussions when those were launched in August 2006 (''See'' Mia Garlick, Version 3.0 – Public Discussion, August 9, 2006, [http://lists.ibiblio.org/pipermail/cc-licenses/2006-August/003855.html]) so that the community on those lists could debate the merits of the proposal.

The discussions about the parallel distribution proposal on the cc-licenses email list were very intense. Various participants argued in favor of the parallel distribution amendment on the grounds that the “anti-TPM” clause violated DSFG #1 and achieved little, if anything. Taking the advantage of a Sony Playstation again, if CC-licensed content cannot be included in games for the PS2 platform, the CC licensee is restricted in what they can do with the content, the PS2 gamer cannot play a game with CC-licensed content and Sony are unlikely to notice the absence of this content and will continue along as business as usual with a TPM-ed platform, irrespective of any anti-TPM ban in the CC licenses.

When asked about the extent to which there was a demonstrated need by developers (as licensees) to be able to utilize CC-licensed content in TPM-ed environments, advocates of the parallel distribution amendment argued that it was better to address the problem before a need arose.

However, the overall tenor of the cc-licenses list discussions tended not to favor adoption of the parallel distribution proposal. There was concern that if parallel distribution were permitted in the CC licenses this would reinforce, if not expand, a platform monopoly enjoyed by a TPM-ed platform that only allows the playing of TPM-ed content (''See'' Greg London, Re:Subject: Version 3.0 – List Discussion Responses, September 28, 2006, [http://lists.ibiblio.org/pipermail/cc-licenses/2006-September/004130.html]; ''see also,'' Terry Hancock, Debian and Creative Commons, October 18, 2006, at [http://www.freesoftwaremagazine.com/blogs/debian_and_the_creative_commons]). Other concerns were voiced that the non-TPMed copy may not be able to played as well as the TPM-ed copy and, generally, that the community was not in favor of supporting a TPM option at this stage (For an overview of the discussions, ''see ''the discussion archives for August [http://lists.ibiblio.org/pipermail/cc-licenses/2006-August/thread.html], September [http://lists.ibiblio.org/pipermail/cc-licenses/2006-September/thread.html] and October [http://lists.ibiblio.org/pipermail/cc-licenses/2006-October/thread.html].)

Whether Debian now declare the CC Attribution and Attribution-ShareAlike licenses to be free according to the DSFG or not — given all negotiated amendments are included in version 3.0 with the exception of the parallel distribution provision — remains an open question.

Certainly, Debian voted (''See'' ‘General Resolution: Why the GNU Free Documentation License is not suitable for Debian main, [http://www.debian.org/vote/2006/vote_001]). earlier in 2006 to allow works licensed under the Free Documentation License to be used in Debian projects. The vote specifically says that the anti-TPM clause in the FDL does not render the FDL incompatible with the DSFG. However, it is not clear whether this treatment is an exception or will also enable the CC Attribution and Attribution-ShareAlike license to also be held to be compatible with the DSFG.

===''MIT''===

With MIT, their OpenCourseWare (OCW) project [http://ocw.mit.edu/index.html] was initially launched in September 2002 prior to the formal release of the Creative Commons core licensing suite in December 2002 and thus, used an early version of the Attribution-NonCommercial-ShareAlike license. “OpenCourseWare” is the free and open digital publication of high quality educational materials, organized as courses. Flexible licenses such as Creative Commons licenses are key to enabling the openness of these materials.

MIT’s OpenCourseWare project has initiated a global opencourseware movement. Most recently, the OpenCourseWare Consortium [http://ocwconsortium.org/] has been formed which involves the collaboration of more than 100 higher education institutions and associated organizations from around the world — including China, France, Japan, the UK, the USA and Vietnam — who are committed to creating a broad and deep body of open educational content using a shared model.

Given CC licenses have improved over time, both CC and MIT wanted to work together to address any issues MIT had about the CC licenses so that MIT could switch over to a more recent version of the CC BY-NC-SA license. However, a key concern for MIT, given its illustrious reputation, is to ensure that when people translate and locally adapt MIT content under the terms of the BY-NC-SA license, they make it clear that they are doing so under the terms of the license and not as a result of a special relationship between MIT and that person — essentially, a “No Endorsement” clause.

Given “No Endorsement” clauses are a standard feature of free and open source software, CC felt that it would be easy issue to make this express in the CC licenses. In CC’s view, a licensee should not interpret the attribution requirement of the CC licenses as a basis (whether intentionally or not) to misrepresent the nature of the relationship with the licensor. Certainly, in most jurisdictions laws other than copyright law will proscribe this misconduct by a licensee. But CC agreed with MIT that it was useful to make this express in the license — both to give the licensor comfort and to ensure that the licensee was under no misapprehensions.

This feedback from both Debian and MIT was the impetus for CC commencing the version 3.0 process. However, as many projects do — versioning to 3.0 rapidly developed to encompass new and additional issues. These issues can effectively be described as further internationalization and international harmonization of the CC licenses

==Further Internationalization==

When CC’s core licensing suite was first released in December 2002, the licenses were drafted based on US copyright law and referred to as the “generic” license because the license did not identify a specific jurisdiction or governing law to apply to the interpretation of the license. Towards the end of 2003, Creative Commons launched its license internationalization project [http://creativecommons.org/worldwide/], which involves the “porting” of the generic licenses to different jurisdictions around the world.

Since this project started, the CC core licenses have been “ported” to over 30 jurisdictions around the world to countries as diverse as Argentina, Australia, Brazil, Croatia, China, France, Italy, Japan, Malaysia, Mexico, South Africa and South Korea. (''Id.'')

While the internationalization has taken off far beyond Creative Commons’ expectations and has demonstrated the amazing energy around the globe for a more flexible and permissive copyright licensing approach, two issues arose.

The first is that as Creative Commons’ license internationalization project continued to grow, the “generic” license and the US license were one and the same. For the casual visitor to the CC worldwide page (''Id.''), it seemed that the licenses had not been “ported” to the US, when in fact they had started out there. The challenge becomes though — if CC recognizes a specific US license, on what law should the “generic” license be based?

The approach Creative Commons adopted to respond this issue required further internationalization of our licenses. We decided to spin off the “generic” license to be a US license and recraft the “generic” license to have it utilize the language of the international intellectual property treaties, in place of the language of US copyright law.

The new license relies on the language of the Berne Convention for the Protection of
Literary and Artistic Works [http://wipo.int/treaties/en/ip/berne/], the Rome Convention of 1961 [http://wipo.int/treaties/en/ip/rome/], the WIPO Copyright Treaty of 1996 [http://wipo.int/treaties/en/ip/wct/], the WIPO Performances and Phonograms Treaty of 1996 [http://wipo.int/treaties/en/ip/wppt/] and the Universal Copyright Convention [http://www.unesco.org/culture/laws/copyright/html_eng/page1.shtml ]. Because treaties are matters of international agreement between countries and, as a general rule, require adoption into national law to be effective in a particular country, simply basing the license wording on these treaties is not, of itself, sufficient. Consequently, clause 8(f) of the new generic specifically provides that the license takes effect according to the corresponding provisions of the implementation of those treaty provisions in the applicable national law.

To reflect the nature of the new “generic” license we also decided to change its name to “unported.” This description is intended to highlight the different nature of the new generic license and to utilize the “porting” terminology that Creative Commons has been using in its license internationalization project since its launch in 2003 to more clearly illustrate the nature of the license that has not been adapted for a local jurisdiction.

The result of this further internationalization is that CC will now offer both an “unported” license and a US license, in addition to the 30-plus ported licenses; the unported license can be selected by those creators to whose jurisdiction CC has not yet ported a license.

===''International Harmonization – Moral Rights''===

The second more major issue that arose through the porting process was that different jurisdictions had different approaches to issues relating to moral rights and collecting societies.

Moral rights, to described them briefly, are author’s right that are distinct from the economic copyright that can be bought and sold (''See generally,'' [http://en.wikipedia.org/wiki/Moral_rights]). Moral rights recognize an author’s personal attachment to their creativity and seek to protect that connection.

While there can be many different moral rights depending on the jurisdiction, the two main ones that are consistently present in most countries around the globe are the moral right of attribution and the moral right of integrity (''See ''Article 6bis of the Berne Convention (as amended September 1979) [http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html#P123_20726]). Obviously, since attribution became a default CC license characteristic with version 2.0 there is less of an issue regarding the moral right of attribution.

However, the moral right of integrity presents a more complex issue for Creative Commons licenses. CC licenses are intended to enable and promote reuse of creative content, particularly the making of derivative works. And those copyright owners who use CC licenses have acknowledged this with over two-thirds of CC licensors consistently choosing to allow derivative works.

But the moral right of integrity, as a general rule, gives the author of a creative work the right to object to alterations or mutilations of the work that are prejudicial to their reputation or honor. Obviously, this has potential to impact the freedom to exercise the right to make derivatives — a derivative will likely always qualify as an alteration of the original work and there may be some instances where it is arguable that it is prejudicial to the original author’s reputation or honor.

Obviously, the first generic version 1.0 license suite released in December 2002 did not mention moral rights because it was based on US copyright law and US copyright law only grants very limited moral rights to works of fine art. However, as the CC licenses began the porting process to other countries, it became necessary for CC licenses to address the moral right of integrity.

To do so, the Creative Commons licenses, with one exception, have taken the approach of not interfering with the author’s moral right of integrity in those jurisdictions that recognize this right.

The one exception is in Canada where the moral right of integrity is waivable. Because Canada was one of the first ten countries to port the CC licenses and one of the first (if not the only) to have a waivable moral right of integrity, on advice of our local affiliate, the CC Canada licenses choose to waive the right of integrity in order to ensure that the licensor’s intention in choosing to permit derivative works was not compromised. However, in all other CC licenses for jurisdictions that recognize the moral right of integrity, the right was retained albeit in different forms; again, on advice from local affiliates.

For example, in most European jurisdictions, the right was expressly retained in the Legal Code because of the strong level of protection for the right in these jurisdictions, as evidenced by the fact that courts would take a dim view of a license that did not expressly include it. In most Latin American jurisdictions, the license was not expressly retained in the Legal Code on the rationale that courts would read it in the license. In Japan, the moral right of integrity was retained in those licenses that prohibited derivative works but not fully retained in those licenses that permit derivative works. The local CC Japan team recommended this approach because the moral right of integrity can be interpreted so broadly as to render any change or alteration to the original work a violation of the right.

Although there is overall consistency in the treatment of the moral right of integrity at the Legal Code level (with the exception of Canada) among the CC licenses, now that the licenses have been ported to over 30 jurisdictions, we felt that it was time to harmonize the approach to this issue at both the Legal Code level and the Commons Deed level. The different approaches towards recognizing the right of integrity in the CC licenses arose because, as CC engaged in the novel process of license porting, we became familiar with the different treatment of this right in different jurisdictions. With the benefit of experience with more than 30 different treatments, CC now felt comfortable to adopt a unified approach.

As a consequence, as part of version 3.0 all CC licenses for jurisdictions that recognize the moral right of integrity will expressly retain that right in the Legal Code to the extent that this is feasible given the status of derivative works under the license. In those jurisdictions in which retention of the moral right of integrity may be completely block exercise of the derivative works right (ie. in Japan) the right will be tempered to the extent necessary to enable the exercise of the derivative works right in a manner intended by the licensor.

In addition, because of the importance of the moral right of integrity in protecting both the author’s rights and for its impact on the derivative works right, from version 3.0 the CC Commons Deeds will clearly state that the author retains their moral rights.

===International Harmonization — Collecting Societies===

Collecting societies are organizations that are established either by private agreements between copyright owners or by copyright law (''See generally,'' [http://en.wikipedia.org/wiki/Collecting_society]). Societies license works and process royalty payments from various individuals and groups who use copyrighted works either as part of a statutory scheme (compulsory schemes) or by entering into an agreement with the copyright owner to represent the owners interests when dealing with licensees and potential licensees (voluntary schemes). The rationale underlying societies is that it is more efficient and effective for copyright holders to be represented collectively in negotiating and levying license fees.

CC licenses also contained different treatments of whether and how a licensor can collect royalties via collecting societies because of the differences in the status of collecting societies amongst different jurisdictions.

In the United States, where the CC licenses originated, an artist can be a member of a collecting society and use CC licenses for those of their works that suit them. This is because of the rigorous enforcement of antitrust laws in the US during the early 20th century that requires that US collecting societies take a non-exclusive license from artists. This allows artists to then engage in direct licensing, including via CC licenses, to their fans and others who wish to share and remix their music.

Consequently, in the original CC licenses language was introduced into the licenses as part of version 2.0 to clarify what was considered to be the obvious interaction between CC licenses and collecting society membership. This initial approach stated that under those licenses that permitted commercial use (Attribution, Attribution-NoDerivatives and Attribution-ShareAlike) the licensor waived the right to collect both compulsory and voluntary royalties. Under those licenses that permitted noncommercial use only, the licensor reserved the right to collect royalties for any uses that were commercial in nature but otherwise authorized royalty-free noncommercial use of the work under the CC license. This approach reflected the fact that by choosing to apply a CC license to their work, a CC licensor clearly intends to permit “free” (as in both price and freedom) uses under the terms of the applicable CC license.

However, the situation regarding collecting society membership in many other jurisdictions around the world is remarkably different to the US position. Elsewhere, collecting societies take either an assignment of copyright ownership or an exclusive license to a work of the rights that they represent (which tends to include all of the works an artist creates). This means, for the most part, that an artist cannot directly license their works online, including via CC licenses. The consequence of this is that artists who use CC licenses cannot receive voluntary royalties collected by a society because they are not able to become a member of the society.

Thus, the treatment of collecting society royalties in the CC licenses differed according to the jurisdiction — in many jurisdictions the collection of voluntary royalties was not mentioned so as not to give any misleading impression that membership of a collecting society was possible for a CC licensor. In addition, many CC licenses retained the right to collect compulsory royalties in all licenses, both those that permitted commercial use and those that permit noncommercial use only, because of the advice of local affiliates that local law would not permit the waiver of such a right.

In version 3.0, after the benefit of seeing the different permutations of collecting society membership in over 30 countries and having had a dedicated team working on the issue of the interaction of CC licenses and collecting society membership for more than a year, CC has decided to harmonize the treatment of collecting societies in the CC licenses.

The harmonized approach still allows different jurisdictions to adopt an approach towards collective royalty collection that suits their jurisdiction but ensures that this is consistently applied across jurisdictions. Specifically, as regards compulsory royalty collection, the licensor will reserve the right to collect these royalties in those jurisdictions in which this cannot be waived. In those jurisdictions in compulsory royalty collection can be waived, it will be waived completely for those licenses that permit commercial use and reserved only for commercial uses in those licenses that permit noncommercial use only.

For voluntary royalties, the licensor will reserve the right to collect this “in the event that they are a member of a collecting society” that collects such royalties. This then allows for those jurisdictions in which an artist can be a member of a collecting society and use CC licenses. It also allows for flexibility for those artists who are members of collecting societies and use CC licenses anyway or if in future collecting society membership structures do allow some use of CC licenses, to also enjoy the benefits of their membership if their collecting society moves towards being able to collect for commercial uses of CC-licensed works.

==BY-SA — Compatibility Structure Introduced==

A final change incorporated into Version 3.0 is that the CC BY-SA 3.0 licenses now include a compatibility structure that will enable CC to certify particular licenses, stewarded by other organizations similarly committed to promoting a freer culture, as being compatible with the CC BY-SA. Once certified as compatible [http://creativecommons.org/compatiblelicenses], licensees of both the BY-SA 3.0 and the certified CC compatible license will be able to relicense derivatives under either license (eg., under either the BY-SA or the certified CC compatible license).

Creative Commons CEO Lawrence Lessig first outlined the vision of allowing an ecology of flexible content licenses to flourish in November 2005 (''See'' CC in Review: Lawrence Lessig on Compatibility, [http://creativecommons.org/weblog/entry/5709]). As Lessig explained:

"Even if all the creative work you want to remix is licensed under a copyleft license, because those licenses are different licenses, you can’t take creative work from one, and remix it in another. Wikipedia, for example, is licensed under the FDL. It requires derivatives be licensed under the FDL only. And the same is true of the Creative Commons Attribution-ShareAlike license that governs Opsound content, as well as much of the creativity within Flickr. All of these licenses were written without regard to the fundamental value of every significant advance in the digital age — interoperability."

This incompatibility also serves as a barrier to dual licensing works under the FDL and CC BY-SA (''See'' Evan Prodromou, Derivatives of dual-licensed Creative Commons Attribution-ShareAlike and GFDL works, May 3, 2005 [http://lists.ibiblio.org/pipermail/cc-licenses/2005-May/002265.html]).

Simply put, the problem is that any license with a "ShareAlike" or similar copyleft provision requires that any derivatives be licensed under exactly the same license (or family of licenses) as the original. This means that an article about Rio de Janeiro on Wikipedia [http://wikipedia.org/] (which is currently licensed under the FDL) cannot be mixed with an article about Rio on Wikitravel [http://wikitravel.org/en/Main_Page] (which is currently licensed under the CC BY-SA 1.0). Even if a project were dual licensed, none of the derivatives of the project could be returned back to the dual-licensed project (because they must be licensed under one ''or'' the other license), thus causing "project bleed." The result of the ShareAlike or "copyleft" license terms is seemingly antithetical to the very purpose of the licenses that contain them. Content, rather than being "free" to remix, is instead locked within particular licensing systems.

Consequently, CC has been working to ensure that, to again quote Lessig:

"[C]reative work[s] will more easily be able to move from one license to another, as creativity is remixed. And this ability for creative work to move to compatible free licenses will provide a market signal about which licenses are deemed more stable, or reliable, by the free licensing community. Free culture will no longer be ghettoized within a particular free license. It will instead be able to move among all relevantly compatible licenses. And the world of “autistic freedom” that governs much of the free software world will be avoided in the free culture world."

There are several obvious candidates for compatibility with the CC BY-SA. The Free Art License [http://artlibre.org/licence/lal/en/] and the Free Software Foundation's Free Documentation License (FDL) [http://www.gnu.org/copyleft/fdl.html].

Creative Commons' initial work has focused on achieving compatibility with the FDL. As part of this work, CC explored the possibility of introducing one-way compatibility with the FDL. (''See'' Discussion Draft — Proposed License Amendment to Avoid Content Ghettos in the Commons [http://creativecommons.org/weblog/entry/5701]), which generated some discussion. CC then responded to some of the concerns raised by this discussion [http://creativecommons.org/weblog/entry/5731] but ultimately concluded that one-way comaptibility with the FDL was not possible because CC licensors could not be guaranteed the same protections under the FDL that they enjoyed under the CC BY-SA.

Despite the inability to implement one-way compatibility with the FDL, Creative Commons is still hopeful of being able to announce licenses that effect the same freedoms as the CC BY-SA to be compatible with the CC BY-SA at some date in the future. To allow the compatibility negotiations to occur separate and apart from the timing of the license versioning process, we have included a structure for certifying licenses as compatible with CC BY-SA as part of Version 3.0 (''See'' Version 3.0 — It's Happening & With BY-SA Compatibility Language Too [http://creativecommons.org/weblog/entry/7234]).

==Summary of Links==

The following list provides the CC blog posts that relate to Version 3.0:

* Getting to Version 3.0 [http://creativecommons.org/weblog/entry/5908]
* Version 3.0 — Public Discussion Launched [http://creativecommons.org/weblog/entry/6017]
* Version 3.0 — Revised License Drafts [http://creativecommons.org/weblog/entry/6120]
* Version 3.0 — It's Happening & With BY-SA Compatibility Language Too [http://creativecommons.org/weblog/entry/7234]
* Version 3.0 — Launched [http://creativecommons.org/weblog/entry/7249]

Birthday Party 2007

2007-10-06T05:07:03Z

Ahrash Bissell: /* Who */

[[Category:Party]]
[[Category:Event]]
[[Category:Worldwide]]

This is the general planning space for a December 2007 event synchronized with other CC Parties around the world, all throwing a party to celebrate Creative Commons' 5th birthday.

== Plan ==

=== Who ===

Anyone interested in or who already knows the young Creative Commons anywhere in the world.

=== What ===

A birthday party for Creative Commons for all of the friends, users, developers, and soon-to-be friends of Creative Commons. There will be drinks, music, videos and so much fun. Also, the event will be coordinated with other CC Birthday Parties in hopes of having a continuous birthday celebration and synchronization to light up the blogosphere, explore CC-licensed content, and to meet up with friends.

=== When ===

Saturday, December 15, 2007, 8 PM - 2 AM (San Francisco time -- other locations within 24 hours of this time will be considered "synchronized")

=== Where ===

Add yours to [[#Parties]].

=== Why ===

To celebrate Creative Commons birthday for the young Creative Commons and all of its friends in the global community, but in local meetings.

=== How ===

This will be executed by Creative Commons staff, affiliates, the community and partners. The party in your location may be big or may be small, but the important thing is to celebrate CC's 5th birthday.

=== Proposed Areas of Planning ===
*Content
*Venue
*Attendees
*Format and Synchronization
*Funding
*Volunteers
*Creating a Digital Trail
*Swag

==== Small ideas ====
* House party
* Dinner
* Bar
* Cafe meetup

==== Big ideas ====
* Art gallery
* With CC art
* Music

==== All parties ====
* Add to [[#Parties]] list below
* Take pictures, post to Flickr or elsewhere on web under a CC license

=== Content Suggestions ===
(collected from http://wiki.creativecommons.org/Salon_Ideas, http://www.mozilla24.com/, meetings in Dubrovnik, mailing lists, etc.)
* Launch of Version 3.0 in your jurisdiction
** coordinated release of 3.0 and/or initial license launch for new jurisdictions
* Podcast, Streaming, #cc chat channel, SecondLife
* Performances
** DJs, musicians, dancing, acting, PowerPoint Karaoke
* Global Coordination
** synchronization tips from events like Mozilla 24? (http://www.mozilla24.com)
* Open Salon Time
** open mic, Birds of a Feather
* Film Screening
* Live Visuals
* Kiosk
** sign up names/emails to the wiki page and discussion lists, paypal donations to artist, CC, other projects
* Brainstorm Session
** Wish List: "We want to see this CC-ed!"
** License improvements
* Speaker Challenges
* Speakers who have well known topics could be challenged to speak about new and different topics, or have to rapidly develop some topic on the spot.
* Auction (also works as fundraiser)
** signed books, for example from Lessig, Doctorow, local author
** mix CDs, posters, tshirts, work from local artist
* Contests
** photos, videos, tracks, contributions to the Commons
** "They use CC here!" map: http://www.mozilla24.com/en-US/get_involved/places/ (geo-tagged map of people/place using CC)

=== Swag and Party Favors ===
*LiveContent CD http://wiki.creativecommons.org/LiveContent
*Open Source Water http://creativecommons.at/projects/water/
*FREE BEER http://www.freebeer.org
*Burn Station (for souvenir CD of the event or of CC-licensed material)
*local and global presskit
*Cshirts

== Parties ==

* [[Birthday Party 2007 San Francisco|San Francisco]]
* [[Birthday Party 2007 Berlin|Berlin]]

== See Also ==

* [[Birthday Party 2006]] - The big 4th b-day bash (partial global collaboration)

Birthday Party 2007

2007-10-06T05:05:54Z

Ahrash Bissell: /* What */

[[Category:Party]]
[[Category:Event]]
[[Category:Worldwide]]

This is the general planning space for a December 2007 event synchronized with other CC Parties around the world, all throwing a party to celebrate Creative Commons' 5th birthday.

== Plan ==

=== Who ===

Anyone interested in and already who knows the young Creative Commons anywhere in the world.

=== What ===

A birthday party for Creative Commons for all of the friends, users, developers, and soon-to-be friends of Creative Commons. There will be drinks, music, videos and so much fun. Also, the event will be coordinated with other CC Birthday Parties in hopes of having a continuous birthday celebration and synchronization to light up the blogosphere, explore CC-licensed content, and to meet up with friends.

=== When ===

Saturday, December 15, 2007, 8 PM - 2 AM (San Francisco time -- other locations within 24 hours of this time will be considered "synchronized")

=== Where ===

Add yours to [[#Parties]].

=== Why ===

To celebrate Creative Commons birthday for the young Creative Commons and all of its friends in the global community, but in local meetings.

=== How ===

This will be executed by Creative Commons staff, affiliates, the community and partners. The party in your location may be big or may be small, but the important thing is to celebrate CC's 5th birthday.

=== Proposed Areas of Planning ===
*Content
*Venue
*Attendees
*Format and Synchronization
*Funding
*Volunteers
*Creating a Digital Trail
*Swag

==== Small ideas ====
* House party
* Dinner
* Bar
* Cafe meetup

==== Big ideas ====
* Art gallery
* With CC art
* Music

==== All parties ====
* Add to [[#Parties]] list below
* Take pictures, post to Flickr or elsewhere on web under a CC license

=== Content Suggestions ===
(collected from http://wiki.creativecommons.org/Salon_Ideas, http://www.mozilla24.com/, meetings in Dubrovnik, mailing lists, etc.)
* Launch of Version 3.0 in your jurisdiction
** coordinated release of 3.0 and/or initial license launch for new jurisdictions
* Podcast, Streaming, #cc chat channel, SecondLife
* Performances
** DJs, musicians, dancing, acting, PowerPoint Karaoke
* Global Coordination
** synchronization tips from events like Mozilla 24? (http://www.mozilla24.com)
* Open Salon Time
** open mic, Birds of a Feather
* Film Screening
* Live Visuals
* Kiosk
** sign up names/emails to the wiki page and discussion lists, paypal donations to artist, CC, other projects
* Brainstorm Session
** Wish List: "We want to see this CC-ed!"
** License improvements
* Speaker Challenges
* Speakers who have well known topics could be challenged to speak about new and different topics, or have to rapidly develop some topic on the spot.
* Auction (also works as fundraiser)
** signed books, for example from Lessig, Doctorow, local author
** mix CDs, posters, tshirts, work from local artist
* Contests
** photos, videos, tracks, contributions to the Commons
** "They use CC here!" map: http://www.mozilla24.com/en-US/get_involved/places/ (geo-tagged map of people/place using CC)

=== Swag and Party Favors ===
*LiveContent CD http://wiki.creativecommons.org/LiveContent
*Open Source Water http://creativecommons.at/projects/water/
*FREE BEER http://www.freebeer.org
*Burn Station (for souvenir CD of the event or of CC-licensed material)
*local and global presskit
*Cshirts

== Parties ==

* [[Birthday Party 2007 San Francisco|San Francisco]]
* [[Birthday Party 2007 Berlin|Berlin]]

== See Also ==

* [[Birthday Party 2006]] - The big 4th b-day bash (partial global collaboration)