|
Typical site operations A wiki is an editable website that does not require users to know HTML. Most have a system to record changes so that at any time, a page can be reverted to any of its previous states. A wiki system may also include various tools, designed to provide users with an easy way to monitor the constantly changing state of the wiki as well as a place to discuss and resolve the many inevitable issues, namely, the inherent disagreement over wiki content. Wiki content can sometimes be misleading, as users may accidentally or intentionally add incorrect information to the wiki. Many public wikis will allow completely unrestricted access so that people are able to contribute to the site without necessarily having to undergo a process of 'registration', as had usually been required by various other types of interactive websites such as Internet forums or chat sites. Many users find this an attractive surprise. Key characteristics A wiki enables documents to be written collectively in a simple markup language using a web browser. A single page in a wiki is referred to as a "wiki page", while the entire body of pages, which are usually highly interconnected via hyperlinks, is "the wiki"; in effect, a wiki is actually a very simple, easy-to-use user-maintained database for searching or even creating information. A defining characteristic of wiki technology is the ease with which pages can be created and updated. Generally, there is no review before modifications are accepted. Most wikis are open to the general public without the need to register any user account. Sometimes session log-in is requested to acquire a "wiki-signature" cookie for autosigning edits. Many edits, however, can be made in real-time, and appear almost instantaneously online. This can lead to abuse of the system. Private wiki servers require user authentication to edit, sometimes even to read pages. Pages and editing The source format, sometimes known as "wikitext", is augmented with a simplified markup language to indicate various structural and visual conventions. An often used example of one such convention is to start a line of text with an asterisk in order to mark it as an item in a bulleted list. Style and syntax can vary a great deal among implementations, some of which also allow HTML tags. The reasoning behind this design is that HTML, with its many cryptic tags, is not especially human-readable. Making typical HTML source visible makes the actual text content very hard to read and edit for most users. It is therefore better to promote plain-text editing with a few simple conventions for structure and style. It is somewhat beneficial that users cannot directly use all the capabilities of HTML, such as JavaScript and Cascading Style Sheets. Consistency in look and feel is also achieved: In many wiki implementations, an active hyperlink is exactly as it is shown, unlike in HTML where the invisible hyperlink can have an arbitrary visible anchor text. This goes along with some extra safety for the user: Permitting users to write in HTML might allow harmful or annoying code (for example, JavaScript code that prevents the reader from marking part of the text). (Quotation above from Foundation by Isaac Asimov) Some recent wiki engines use a different method: they allow "WYSIWYG" editing, usually by means of JavaScript or an ActiveX control that translates graphically entered formatting instructions, such as "bold" and "italics", into the corresponding HTML tags. In those implementations, the markup of a newly-edited HTML version of the page is generated and submitted to the server transparently, and the user is shielded from this technical detail. Users who do not have the necessary plugin can generally edit the page, usually by directly editing the raw HTML code. More recently, wiki engines are generating wiki syntax instead of HTML. This way, users who are comfortable editing in wiki syntax can carry on. Although for years the de facto standard was the syntax of the original WikiWikiWeb, currently the formatting instructions vary depending on the wiki engine. Simple wikis allow only basic text formatting, whereas more complex ones have support for tables, images, formulas, or even interactive elements such as polls and games. At present there is no standard for wiki markup. Linking and creating pages Wikis are a hypertext medium, with non-linear navigational structures. Each page typically contains a large number of links to other pages. Hierarchical navigation pages often exist in larger wikis, often a consequence of the original page creation process, but they do not have to be used. Links are created using a specific syntax, the so-called "link pattern". Originally, most wikis used CamelCase when naming program identifiers, produced by capitalizing words in a phrase and removing the spaces between them (the word "CamelCase" is itself an example). While CamelCase makes linking very easy, it also leads to links which are written in a form that deviates from the standard spelling. CamelCase-based wikis are instantly recognizable because they have many links with names such as "TableOfContents" and "BeginnerQuestions". Note that it is possible for a wiki to render the visible anchor for such links "pretty" by reinserting spaces, and possibly also reverting to lower case. However, this reprocessing of the link to improve the readability of the anchor is limited by the loss of capitalization information caused by CamelCase reversal. For example, "RichardWagner" should be rendered as "Richard Wagner", whereas "PopularMusic" should be rendered as "popular music". There is no easy way to determine which capital letters should remain capitalized. As a result, many wikis now have "free linking" using brackets, and some disable CamelCase by default. Searching Most wikis offer at least a title search, and sometimes a full-text search. The scalability of the search depends on whether the wiki engine uses a database; indexed database access is necessary for high speed searches on large wikis. Server-side versus client-side wiki By far, the most common wiki systems are server-side. In essence, the edit, display and control functions are provided on the server through the wikiengine that renders the content into an HTML-based page for display in a web browser. A client-side wiki system requires only that the server "serve" wiki files in much the same way that a web server allows HTML files to be retrieved using HTTP. In this type of wiki system, all the execution required to convert the underlying wiki text into an onscreen formatted display page resides in the client browser. Likewise, the editing tools and functionality reside in the browser. The client-side wiki system parallels HTML in that the page becomes a rendering instruction for the browser to interpret. Client-side wiki systems may be little more than a code plugin to a more traditional web browser. Web-based versus peer-to-peer Most wikis are based on a web server. The server can be open to everybody on the Internet, or part of a private LAN, with limited access. There is also a version of wiki that can be shared between peers, with no need for a web server. Such Peer-to-peer wiki system is integrated with a P2P version-control system that takes care of versioning and distribution of pages. Controlling changes Wikis are generally designed with the philosophy of making it easy to correct mistakes, rather than making it difficult to make them. Thus while wikis are very open, they provide a means to verify the validity of recent additions to the body of pages. The most prominent, on almost every wiki, is the "Recent Changes" page—a specific list numbering recent edits, or a list of all the edits made within a given timeframe. Some wikis can filter the list to remove minor edits and edits made by automatic importing scripts ("bots"). From the change log, other functions are accessible in most wikis: the Revision History showing previous page versions; and the diff feature, highlighting the changes between two revisions. Using the Revision History, an editor can view and restore a previous version of the article. The diff feature can be used to decide whether or not this is necessary. A regular wiki user can view the diff of an edit listed on the "Recent Changes" page and, if it is an unacceptable edit, consult the history, restoring a previous revision; this process is more or less streamlined, depending on the wiki software used. In case unacceptable edits are missed on the "Recent Changes" page, some wiki engines provide additional content control. It can be monitored to ensure that a page, or a set of pages, keeps its quality. A person willing to maintain pages will be warned of modifications to the pages, allowing him or her to verify the validity of new editions quickly. Vandalism The open philosophy of most wikis—of allowing anyone to edit content—does not ensure that editors are well intentioned. Wiki vandalism is a problem for wikis. The approach of making damage easy to undo rather than attempting to prevent damage has been characterized as soft security. Many editors of wiki sites tend to have good intentions, although on larger wiki sites, vandalism can go unnoticed for a period of time. Another bothering feature in wikis is trolling. Wiki communities Many wiki communities are private, particularly within enterprises as collaborative software. They are often used as internal documentation for in-house systems and applications. The democratic, all-encompassing nature of Wikipedia is a significant factor in its growth, while many other wikis are highly specialized. Today, the English-language Wikipedia is, by far, the world's largest wiki; the German-language Wikipedia is the second-largest, while the other Wikipedias fill many of the remaining upper slots. Other large wikis include the WikiWikiWeb, Memory Alpha, Wikitravel, World66 and Susning.nu, a Swedish-language knowledge base. The largest wikis on July 3, 2004 were listed at Meatball: Biggest wikis). Many public wikis are listed at WikiIndex - a wiki of wiki. There exist WikiNodes — pages on wikis describing related wikis. They are usually organized as neighbors and delegates. A neighbor wiki is simply a wiki that may discuss similar content or may otherwise be of interest. A delegate wiki is a wiki that agrees to have certain content delegated to that wiki. One way of finding a wiki on a specific subject is to follow the wiki-node network from wiki to wiki; another is to take a Wiki bus tour, for example: . Domain names containing "wiki" are growing in popularity to support specific niches. For those interested in creating their own wiki, there are many publicly available "wiki farms", some of which can also make private, password-protected wikis. PeanutButterWiki, Socialtext, Wetpaint, and Wikia are popular examples of such services; more at List of wiki farms. Wikis and content management systems Wikis have shared, and encouraged, several features with generalized content management systems (CMS) which are used by enterprises and communities-of-practice. Those looking to compare a CMS with an enterprise wiki should consider these basic features: None of these are particular to a wiki, and some have developed independently. Still the concept of a wiki unequivocally refers to this core set of features. Taken together, they fit the generative nature of the Internet (as scholar Jonathan Zittrain has labeled it), in encouraging each user to help build it. It is yet to be studied whether an enterprise wiki encourages more usage, or leads to more knowledgeable community members, than other content management systems. Sometimes, when an online translator is used to translate the language of the text in a Wiki, and somebody edits it, it can erroneously change the language of the text*. However, using an online translator can be a good tool for translating to the language used for other language editions of Wikipedia. See also Notes | |||||||||
|
| ||||||||||
 |
|
| |