Professional Documents
Culture Documents
1.1
What is a Wiki?
Imagine you are surfing the Internet, and you stop at a site where
you could and would like to add or modify something. For instance,
you have a literary reference or link to add. Or you’ve noticed
a typing error. Perhaps you even have a lengthy article that you’d
like to display on a separate page. So, you just click on the “edit”
button, change everything you wish, add a couple of ideas, confirm
it, and the new page is online immediately! In a history, a listing of
the saved, older versions of the page, you can view previous changes
to the page as well as reverse your entries. If it all was a simple and
transparent experience, you were dealing with a wiki. Wiki technol-
ogy enables virtually anyone to completely edit pages without diffi-
culty. Yet that’s not all – anyone can contribute significantly to the
structure of the site, simply by creating new links and adding new
pages. This openness is the innovative and amazing aspect of wikis.
The title of a book on wikis by Bo Leuf and Ward Cunningham puts
it in a nutshell: The Wiki Way. Quick Collaboration on the Web.
Wikis are downright fascinating tools. It has never been so easy Tools
to become a “correspondent” on the Internet, because the technical
hurdles have been reduced to a minimum. People who hear about or
use wikis for the first time often experience a bit of culture shock.
“Anybody can come along and change my text!” is a popular reac-
tion. The opportunities and consequences of free cooperation in the
context of the typical work organization of our society inevitably
lead to irritation, because we assume that a contribution from “oth-
ers” will destroy our own work. We are simply not used to handing
over control and responsibility – and to strangers at that. The Swed-
ish data systems specialist Lars Aronsson writes:
“Most people, when they first learn about the wiki concept, assume
that a website that can be edited by anybody would soon be rendered
Excursion You can’t quite imagine it yet? Then let’s take a short excursion, and
try out whether or not it is really as easy and free as it sounds. Get on
the Internet and go to the site http://www.wiki-tools.de. Click on
Sandbox. In this sandbox, you are free to experiment at will. Click
on edit. Now, write over the existing text in the middle by typing
your name or whatever else comes to mind. Then click on Save
page below the text field. Congratulations! You have just made your
first entry in a wiki.
Definition A wiki is web-based software that allows all viewers of a page to
change the content by editing the page online in a browser. This
makes wiki a simple and easy-to-use platform for cooperative work
on texts and hypertexts.
Origin The first wiki, with the name WikiWikiWeb, was developed in 1995
by Ward Cunningham.2 The software developer from Portland, Ore-
gon is considered to be a pioneer in the development of new meth-
ods, such as object-oriented programming, design patterns or ex-
treme programming. Because he was dissatisfied with conventional
word processing programs, Cunningham searched for a new docu-
mentation system that would better suit the needs of programmers.
His goal was a relatively simple software that would enable collec-
tive work on software codes that could be published immediately.
The new program would automatically document all editing steps to
make changes easier to trace (document history). Ultimately, the
first wiki server went online and has been in operation ever since.3
Connotation “Wikiwiki” is a Hawaiian word that means “quick” or “hurry”.
The name stands for the programming characteristic of wiki soft-
ware in which content can be made available in a quick and uncom-
1
Aronsson 2002.
2
Leuf/Cunningham 2004.
3
http://c2.com/cgi/wiki
The use of wikis is dependent upon the goals of the community, Functions
organization or company that utilizes it. Although they were first
intended for software development, they are now used in a variety of
areas. Due to the further development of the wiki concept via various
wiki clones,4 wikis can integrate an increasing amount of functions.
Generally, we differentiate between two application options with Areas of
wikis: They can be used as tools in a closed work group, or they can Application
be directed at potentially everybody over the WWW. Wikis serve as
knowledge management tools in planning and documentation. They
can also be utilized as an open, web-based content management
system (CMS) for the editing and management of a web presence or
Fig. 1.1
4
See Chap. 4 for wiki clones.
12
This means that, in contrast to comparable systems, wiki technology does
not differentiate between “back end” and “front end”.
13
The relationship between project and community varies. For example, at
Wikipedia, a community has developed around a free encyclopedia project.
On the other hand, the MeatballWiki is only a community without a central
project.
1.2
The Technology of Wikis
Readers Wiki-Software is installed as a script on a server. The server pro-
duces small documents, so-called wiki pages or articles, that can be
accessed via a browser. The content of the wiki page itself is written
as simple text and then stored in a file or database. When a wiki-
based Internet page is accessed, the browser first sends a query to
the server that administers the data sets containing the wiki software.
This data, which is in the form of simple text, must now be format-
ted for display in the browser.
Fig. 1.2
To do this, the wiki script translates the file text (wiki code) or data
set into HTML and embeds it in the web page (template) to be sent
back to the browser. For example, the wiki script can be a PHP
script that reads the raw page data from a MySQL database. This
raw data is checked line for line, and the specific format commands
contained in it are replaced by the corresponding HTML codes.14
14
In this step, all URLs are then clickable, and in place of all URLs that end
in gif, .jpg or .png, in other words those displaying images, the corresponding
image tags are set (the images themselves are subsequently loaded by the
browser).
Fig. 1.3
Web admins Yet even a wiki cannot exist without some technology. On this level,
the web admin is in charge of software installations, maintenance
and updates. In contrast to the other groups mentioned, web admins
have direct access to files without needing to detour through the wiki
interface.
Fig. 1.5
Level model The categories mentioned up to now indicate a model which divides
the access of participants into levels that differ technically in type
and depth. We add to these the lowest level, which includes the in-
frastructure, the server and operating system, as well as the neces-
sary software, web server and database. They are maintained by
a system administrator.
Thus, while the system and web administrators have direct access
to the server and must not necessarily be integrated into the wiki
community, wiki administrators, authors and readers navigate the
web-based interface of the wiki.
Using the idea of the level model, we can also clearly see that, in
contrast to a normal HTML page, the interface with which content
can be created is found in the client realm. This means that, from
a technical standpoint, conditions have been established in which
1.3
Characteristic Wiki Functions
Regardless of the wiki script used, all wikis offer a few technical
core functions, which we will only mention briefly here and later in
more detail.
Links. Each article can be linked to other articles and thus form
a new network structure.
Note: Links can be created in most wikis using a WikiWord: Words WikiWord/
are capitalized and written together without a space (so-called CamelCase
CamelCase, which in itself is an example of such a WikiWord).
CamelCase makes linking easy, but can also cause problems in some
applications. That is why, in other wikis, links are generated by simply
placing the title in square brackets. Regardless of which procedure is
chosen, a link is thus generated that appears in the normal view.
15
Many wikis are listed under: http://c2.com/cgi/wiki?WikiEngines.
16
An assumption not shared by the authors of this book ☺.
The Perl-based TWiki, with its many plug-ins and features, is, in
addition to TikiWiki, the most comprehensive wiki clone. TWiki
implements wiki technology more consistently than bitweaver, be-
cause additional functions can also be realized with this technology
to a large extent. TWiki, which was conceived to be utilized as
a company intranet, is being used increasingly for commercial pur-
poses, due to its high level of development.
Wetpaint is a special example for a free wiki offering. With it, you
can write your own wiki pages on a public domain. However, the
wiki software itself is not freely accessible. Several similar commer-
cial wiki clones, such as Confluence or Socialtext, were developed
in the past.
Selection criteria In the appendix, you will find a small tabular overview of important
wiki systems. It cites a few criteria you should look for when select-
ing a wiki. Section V also contains further tips on selecting the right
wiki.
1.5
The Wiki Phenomenon
Brecht’s Bertolt Brecht, in his so-called “Radio Theory”, written in 1930,
Radio Theory wrote that radio has one side when it should actually have two. “It is
purely a distributive apparatus; it just rations out.”17 His now infa-
mous proposal was to convert broadcasting from a distributive appa-
17
Brecht 1930/1967, 129.
1.5.1
Creativity Through Group Processes
Yet beyond the question of the emancipatory potential of wikis is Wiki effect
perhaps the question as to why the “wiki effect” even occurs at all.
What we mean by “wiki effect” is primarily the self-organization
processes that can be observed in well-known and successful wiki
projects. It is astounding that people will independently research,
organize, write and publish to provide the general public with a free
service. For instance, communities have not only formed around the
large Internet lexica that largely do without central control models.
Their self-organized projects have, in the meanwhile, exhibited con-
siderable successes.
In such cases, it is often evident that the communication of large Cathedral
groups is much more effective and thus can react more flexibly to and bazaar
change than when using hierarchical organizational models. Such
wiki projects are not the exception to the rule: Similar experiences
were previously made with the “subversive” development of open
source software (e.g. Linux). Eric Raymond, a well-known author
and programmer in the hacker and open source scene, hit the nail on
the head when he metaphorically differentiated the various man-
agement methods using the principle of the cathedral and the ba-
zaar:19 While conventional software development assumed that im-
18
See: Ebersbach/Glaser 2004.
19
Raymond 1999.
Playful creation. “Why Wiki works? It’s cool”, is the brazen com-
ment at Ward’s Wiki. A loose, playful atmosphere and fun at work
are important conditions for self-organized processes, because one’s
creative, social and practical skills can best be unfolded in such an
environment. It is motivating when one can make his or her own
designs or contribute an article for a large-scale project. Less attrac-
tive “obligatory” tasks do not necessarily fall by the wayside if their
necessity is recognized.
20
Especially at open space conferences. See Petri 2000, Maleh 2000.
Simple system, simple rules. The decision to sit down and join in
is the greatest obstacle for self-organization processes. Successful
self-organized group processes are often founded on very simple
basic systems, because favorable – if complex – decision-making
and modification processes depend only on a rough overall concept,
access to all relevant information and clear basic conditions. Thus,
the conference model Open Space functions with just a handful of
rules.
Wiki technology, with its low technical access hurdles, is ideal
for web-based group processes. Several wiki communities have
implemented simple codes of conduct.
Open access. Free will and open access are vital conditions for mo-
tivation in self-organization processes. The success of the bazaar
principle as well as the wiki philosophy is based on the fact that
discussions are removed from alleged expert and specialist circles,
right from the start. This creates transparency and incentive.
21
Of course it makes a difference whether a goal is self-set or stipulated, or
whether external goals have been taken on as one’s own.
22
As in the case of many other Internet projects, we must mention the limiting
factor that we expect the circle of active wiki users to continue to be limited to
certain social groups for the present (keyword: digital divide).
The forms broadly discussed here are naturally not pure, but rather
overlap each other and evolve. Due to the interplay between the
individual practices and goals, the overall relationship is continually
restructured as a process. The members of a community have just as
much of an effect on the individual through their actions as the indi-
vidual does when contributing to the daily design of form and con-
tent of the community. All of these behaviors, including those that
are passive and, in a broader sense, “destructive”, are necessary to
a dynamic community. However, the community can also be de-
stroyed by them at any time. Knowledge of specific and general
23
Even in companies in which hierarchies are being disassembled, this does
not necessarily translate into a higher degree of transparency of company
structures.
31
Aronsson, 2002.
1.6
Wiki Pages
Pictures are worth a thousand words. That is why we would like to
present a few sample wiki pages on the following pages. We used no
special criteria in selecting these examples; moreover, we wish to
convey an impression of the diversity of wiki software.