CC Ideas
From Rejon.org Wiki
Contents |
Messaging
Basically, CC is focused on three groups of people: artists/creators, developers/technical, and lawyers/legal. This maps to the focus of the CC-licenses: human readable, machine readable, and legal readable. Seems like messaging should rap around these functions.
CC Tenets
The primary functionality of CC is to both aid in publishing cc-licensed content (and embedding these tasks) and also finding cc-licensed content. This is another main tenet of cc:
publish
find
Ideas
Challenges
Right now there are only really tech challenges, but there should be challenges and goals for all the three main areas of cc types of users/developers.
Creative
- CC Content on a public billboard
- CC Content to go gold/platinum
- CC content to be viewed by 2 million ppl.
Developer
- libcc/etc
- document managmement system (c-based)
- libarchiveorg
Legal
- ?
CC Salons
DONE
Large Scale View of CC and Media
One should be able to open application and do a search and get media that can be used directly in any application. Also, one should be able to publish to the world through different sites and license content, edit metadata, etc.
Basically, there should be services that allow you to easily "publish" to the web (or to some globally accessible storage). Archive.org and others could just represent just a node in a larger network (possibly p2p-like).
You should be able to save/open files from the web within any application so there is no/low latency between capturing content and actually remixing/editing.
Creativity is natural: The general idea is that creativity and sharing are inherent in humanity (and life/evolution).
Media Declarations
While most metadata is invisible, this is about making licensing visible on or around works. The way this would be done is by creating bumpers for cc content by taking different media and create basic guides and media that authors could attach to their files/media to alert others that they are using C-licensed work.
Two Types of Declaration
Visible
This would be up front forms of putting license declarations/attribution around or on media.
Invisible
This would be metadata and forms of watermarking license declarations/attribution into media.
Ways to Accomplish
Basic Guides for Placing Declarations
This would entail making basic howtos for making visible and invisible declarations of content.
There are already guides for some of this.
Along with this would be providing media in the major content areas of CC to support license declaration. Example include video bumpers, pdf/eps files for print, audio announcements for audio tracks, etc.
Software to Place Declarations
This would entail making software to place declarations for both visible and invisible declarations.
There are already software for some of this.

