Discussion: Ideas on OpenLit v0.3
A WIKI page has been created for this topic, please go there. The WIKI page has public edit active. Otherwise, please read on and post comments below, thanks!
Part 1 Basics about OpenLit
What is OpenLit?
"All writers are readers, and many readers are writers. By enabling community sharing and responding, Oort-Cloud catalyzes interactivity and engagement between writers and readers. This is how readers become better readers, and how writers become better writers."–Paul B. Hartzog of www.oort-cloud.org
I'm trying to expand a definition a little more, any ideas?
What is the OpenLit history?
On September 2, 2006, Paul B. Hartzog wrote an article entitled Social Publishing for the Corante Many-to-Many blog. From that article, the idea for www.oort-cloud.org was born, and presumably, the idea of OpenLit evolved from the practical application of Social Publishing. (please expand)
How is OpenLit structured?
Write - Share - Read - Respond
- Write-First, writers write.
- Share-Second, writers share with others what they have written.
- Read-Third, readers read what is available.
- Respond-Fourth, readers respond to what they have read.
–Paul B. Hartzog, Richard Adler of www.oort-cloud.org
How does copy-law fit into OpenLit?
Considering the OpenLit collaborative interpretation, the copy licensing of choice would be a CreativeCommons , Copyleft , and/or PublicDomain designation, although a CopyRight is not prohibited. A breakdown of CreativeCommons licenses, CopyLeft ShareAlike, PublicDomain, and CopyRight is coming soon.
Why use an OpenLit structure?
With the increasing dissemination of information, and the increasing amount of online users, it has become apparent the benefits of collaborative processes when dealing with content. Content could be anything from music, video, knowledge, news, art, writing, research, data archival, etc. Idealistically, any possible topic or interest could be formed into a collaborative structure for content generation. So in the spirit of a great social experiment, we at Oort-cloud are attempting to apply the idea of group collaboration with science fiction writing.
Why use Science Fiction?
Historically, the Science Fiction genre is known as being cutting edge. Science Fiction is an artistic writing style that theorizes what may be (has been, is, add other time/dimension tense here) possible and presents it in a form that is accessible to anyone. Additionally, SF is deeply rooted in the technology and science subculture, so it stands to reason that SF is imbued with many characteristics of modern, real world theory and innovation. Therefore, I think it is appropriate that SF should be the crucible for this experiment.
Part 2 Ideas on OpenLit Theory
I tend to think of OpenLit ideally working in a cyclical form. Meaning that feedback loops are created amongst readers, writers, editors, and publishers. Now, I believe different types of feedback loops could be created, some of which I will discuss below.
- Provider/Subscriber Serial (PSS)-this is the type of SF commonly seen on oort-cloud.org currently. Provider posts content to the main blog, then subscribers read it, and makes comments. The provider observes and interacts with subscribers via comments, and makes adjustments to the content accordingly.
- Multi-Provider/Subscriber Serial (MPS)-this type of cycle involves a group of providers working in collaboration on content. Theoretically, the number of providers could be very large, but the question of practicality arises. An example:
- Joe creates a story; he denotes it with a tag like: MPS. Mark reads Joes work, likes it, and responds, saying he would like to contribute content. Joe establishes a number of content providers he would like to include in his MPS cycle. In this case, let’s say 2. Joe and Mark take turns writing the story,while observing comments from subscribers. Thus the story is ping-ponged between the two, with each making their own contributions.
- Subscriber Serial-this type of cycle is truly an open cycle. The initial provider posts a general plot, then it is open for subscriber to add and remove their ideas. Ideally there would be some Digg, Slashdot, or Reddit style ranking system for the most popular ideas to rise to the top of the list. This cycle is ideal for large amounts of people. The initial provider would be responsible for the actual writing of the story.
In theory, every member of an OpenLit community belongs to a specific group(s) or subgroup(s).
Obviously there could be combinations of these types, as well as other types I haven’t thought of. Examples could include:
- Copy Provider- a content provider who only posts content under copyright and observes/uses subscriber comments
- Open Provider- a content provider who posts content under CopyLeft/CC and observes/uses subscriber comments
- Provider/Subscriber- a user who provides content and posts comments as a subscriber to other provider’s works.
- Editor- a user who has skills in English who is trying to use editorial skills.
- Subscriber- a user who reads and comments on other peoples works
- Soft Subscriber- a user who reads other works, does not take an participatory role in community. (thanks Lenny Zero)
- Publisher- a user who has experience in the publishing industry.
Part 3 Possible OpenLit Social Software
The OpenLit concept has direct applications for software. Examples:
- A comment ranking system. This would be used to rank plot comments in a subscriber serial, thus moving the popular plot changes the “masses” want to see to the fore front, while moving the less popular ones away. Examples: DIGG, REDITT, etc.
- A WYSIWYG editor with specific application for multi-provider editing.Features could include:
- a comment organizer to keep track of comments and the ability to arrange them in certain ways (date,most replies, most starred - if comments were rated) this would be useful as a way to have all subscriber input in one place during a re-write, as opposed to many different nodes/locations.
- multiple user function. Say you and I wanted to do a serial together. We would have a place were we could upload work between us, make edits in real time, and discuss direction without having to use a public blog or email platform. Theoretically you could do this with multiple (>2) people, although I imagine that could get confusing. However, a system could be arranged for a massive multi-provider serial...which would be really cool if it worked correctly.
Come on oort-cloud, lets see what ya' got! -thanks