Collaborative editing

From WhyNotWiki

1 Of databases
- 1.1 OpenPrinting Printer Compatibility Database database
  - 1.1.1 About the data
2 Of text documents
- 2.1 Collaborative editing as a negotiation.
- 2.2 Thought Experiment: Collaborative editing as a turn by turn process.
3 Pastebin
4 Spreadsheets
- 4.1 SocialCalc / wikiCalc
5 Collaborative documents: In general

[edit] Of databases

[edit] OpenPrinting Printer Compatibility Database database

http://www.linux-foundation.org/en/OpenPrinting/Database/DatabaseIntro. Retrieved on 2007-05-11 11:18.

The OpenPrinting database contains a wealth of information about specific printers, along with extensive driver information, the drivers themselves, basic specifications, and an associated set of configuration tools.

...

[edit] About the data

This database includes basic specifications for printers and details of how to make them go under normal unices [...].

We have also a web API for printer setup tools to be able to browse the database and to download driver packages. This allows fully automatic installation of detected printers which the local distribution does not support, and also updating drivers if the distribution does not ship an update. We provide enough data, that the tool can ask the user whether he really wants to install this driver: free/non-free, license, from manufacturer/third party, support contact and level, ...

Printers are categorized according to how well they work under Linux and Unix. The ratings do not pertain to whether or not the printer will be auto-recognized or auto-configured, but merely to the highest level of functionality achieved.

...

This is an interactive database; if you know anything useful that isn't represented here, please add your knowledge to the pool -- post anything you know to the forum for your printer or use our add printer form, and one of our editors will incorporate your information into the data. If you printer is already listed, enter your contribution to the "User Notes" section of the existing entry.

This entire database (except the driver packages) is available in an XML format as part of the Foomatic system, which provides configuration tools and filter scripts for a variety of spoolers. All driver packages and the LSB DDK are in this directory.

[edit] Of text documents

collaborative editing / Wikinomics (http://www.socialtext.net/wikinomics/index.cgi?collaborative_editing). Retrieved on 2007-05-11 11:18. [Wiki policies (category)][Wiki philosophy (category)][Wiki conventions (category)]

Collaborative editing, can be defined as "turn-by-turn edits by multiple individuals who have equal control over the text." It is a form of Peer Production for written material, best used for knowledge creation. On a human level, collaborative editing is a mixture of cooperation and competition. It is competitive because on the level of words, phrases and ideas collaborative editing is a Darwinian test of fitness. The page evolves and only the best, or the truth, survives. It is cooperative because editors need each other to review each others contributions and by editing, reveal the true knowledge. As such, the rules of collaborative editing have these general objectives:

to support the survival of the community (by encouraging and sustaining participation)

promote coherence, structure and stability in the documents.

increase the value of the content.

In most public wikis some kind of house rules or terms of use statement is made plain to all participants. These rules (which are often editable in themselves) make for a civilized wiki-based community.

[edit] Collaborative editing as a negotiation.

Collaborative editing is a powerful tool, but is ultimately a form of negotiation. Those who are new to wiki are rightly skeptical about any magical results from collaboration.

"If wiki is so hot at making truth, what would happen if Jerry Falwell and Osama Bin Laden participated in a wiki page about God. "

If two individuals in isolation are not willing to negotiate at all, then no collaborative process (including wiki) will help them produce together anything worth the effort. Notwithstanding the "battle of opposing fundamentalists" scenario (which would usually be a miserable failure) "battles" between two wiki editors is common and in a two person wiki fight - there is no reason to think that wisdom or truth should prevail. In isolation it would be a simple matter of "he who edits last wins."

If however, there is a willing negotiation between those with highly opposed views, it is not hard to imagine that uniquely valuable wisdom can emerge. In a social situation, this becomes more likely. With more than two participants and bystanders, most editors will not want to appear as a bully, or a vandal, and will tend to self-moderate.

[edit] Thought Experiment: Collaborative editing as a turn by turn process.

To best explain the process objectively and show how it adds value to infomation, suppose that:

PROCESS:

there are only two editors (A and B)

turn by turn, each editor can privately view and edit a page.

there is an observer who can see the page at all times.

except for the document itself, no communication exists between the editors.

for the benefit of the observer, every turn the editor classifies all the content in the document

unacceptable content is marked (or highlighted) red.

acceptable content green (acceptable).

every turn each editor changes some or all of the text marked as red.

the observer, on the basis of the individual markings will see all content as being either red, (mutually disagreeable) green (mutually agreeable) or yellow (contested).

RESULT:

Given enough turns, an equilibrium will emerge wherein the editors will find complete agreement over the total content of the page. The Dynamics:

Acceptable: (Green)

These mutually green areas of consensus will remain "stable" and have a long life span.

Unacceptable: (Red)

Statements that are unacceptable (Red) to both players are highly unstable. Since both players edits to make red text green (in their own perspective), mutually unacceptable content has a short life span.

Disputed: (Yellow)

If a section of text is green to one person and red to another this section of overlapping red and green will be edited by whomever sees it as red.

As further rounds are played, the amount of green text should increase - it is in equilibrium as they say. One way to find equilibrium is a fair statement of the "agreement to disagree" - or dissensus.

example: A wiki trying to explain God would include both Jerry Falwell's understanding and al-Sadr's in as objective a way as possible, while acknowledging their differing views. It might read something like, "Although Jerry Falwell explains God as _____, another notable viewpoint is that of Muqtada al-Sadr, who holds that God is ________."

If a player creates wanton destruction they can expect a quick revert. Thus, on a wiki, the only way to win is to negotiate until the one side or the other is content enough to leave it all be. If the last editor standing decides to make a (now unsupervised) culling of all their opponents ideas he would (one presumes) eventually be found out, and the content would be [revert]ed by someone else. While in reality this exchange seldom happens between only two editors, the results hold for larger numbers and "minor conflicts" will tend to wash out more quickly.

In general, the more content a wiki has, the better it can represent, in detail, the full ecosystem of issues and ideas that make up a collective social reality. As Chris Anderson explained wikis, with their unlimited capacity for information, can reflect not only the common consensus (at the top of the page) but also an unlimited length of details and perspectives: the Long Tail) lets the reader with the patience to inquire see many diverse views upon God and other topics, and presumably will be better able to form opinions of their own.

[edit] Pastebin

http://pastebin.com/pastebin.php?help=1. Retrieved on 2007-05-11 11:18.

[edit] What is pastebin?

pastebin is here to help you collaborate on debugging code snippets. If you're not familiar with the idea, most people use it like this:

submit a code fragment to pastebin, getting a url like http://pastebin.com/1234

paste the url into an IRC or IM conversation

someone responds by reading and perhaps submitting a modification of your code

you then view the modification, maybe using the built in diff tool to help locate the changes

[edit] How can I view the differences between two posts?

When you view a post, you have the opportunity of editing the text - this creates a new post, but when you view it, you'll be given a 'diff' link which allows you to compare the changes between the old and the new version.

This is a powerful feature, great for seeing exactly what lines someone changed.

[edit] How can I delete a post?

If you clicked the "remember me" checkbox when posting, you will be able to delete post from the same computer you posted from - simply view the post and click the "delete post" link.

[...]

[edit] And this is all free?

It will always be free, our hosting and maintenance costs are paid for through advertising.

[edit] Can I get the source?

The source code to this site is available under a GPL licence. You can download it here

[edit] Spreadsheets

[edit] SocialCalc / wikiCalc

Homepage:	http://www.wikicalc.org/ https://www.socialtext.net/open/index.cgi?socialcalc_wikicalc
Description:	wikiCalc is a wiki-based spreadsheet developed by Dan Bricklin and released under a GPL license. SocialCalc is co-developed with Dan and Socialtext, released under SPL and is being integrated with Socialtext Open.