February 2012 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
 |  |  |
[[wiki-net_chat?]]
[[wiki-net_ting?]]
 |  |  | |  |
 |  |  |  |  |
 |  |  |  |  |
 |  |  |  |  |
 |  |  |  |  |
|  |  | |  |
 |  |  |  |  |
 |  |  |  |  |
 |  |  |  |  |
 |  |  | |  |
 |  |  |  |  |
 |  |  |  |  |
 |  |  | |  |
 |  |  |  |  |
 |  |  |  |  |
recent 3 changes
No items found in http://oddwiki.org/odd/OddWikiCenter?action=rss.
recent 3 Mµs #OddWikiCenterEn
No items found in http://www.twingly.com/search.rss?q=%23OddWikiCenterEn&sort=published&content=microblog&excludesite=twitter.com.
No items found in http://search.twitter.com/search.rss?q=+%23OddWikiCenterEn.
Read all Mµs #OddWikiCenterEn.
clean linking
You find some small case and dashes on this wiki: Here is why.
Clean linking is the only way to be sure that a person writing on a wiki running on whatever wiki-engine is really free to choose what a link shall look like.
This is an essential requirement for finding a global agreement on a common syntax to name wiki-pages.
By their internal syntax the engines predefine. Not much, just a little. and every engine a little different in a different corner. For example
On Mediawiki a link turn Clean linking, first letter upper case.
On demo-wiki a link turns clean_linking, fist letter lower case.
And more … how ever you do it: There’s always an engine that you can not do it right on.
The syntaxes of all wiki-engine are incompatible to each other. To enable an agreement on a new common syntax, yes to even enable the growth of a common link language we have to look for the smallest common multiplier - and that’s clean linking.
The diversity of wiki-engines is a treasure, just like the diversity of natural languages is. They mean different ways of thinking. We have to preserve this diversity. We should rather look how to make it easier to work on the level of the free choice for all.
CamelCase doesn’t create PatternLanguage. If you see
CleanLinking is a way of CleanLinking.
clean linking is a way of clean linking.
Both create link language, repetition of patterns does. CamelCase additionally creates bad readability.
On dashes
English is the internet language. The major part of users do not speak English as their mothertongue. For many people it’s in fact very difficult.
To understand what a wiki-node is you need to know what a wiki is and what a node is. When I say frontpage I spare out important information for a non-English speaker. For this person it might be fron tpage or frontp age just as well. When I say front-page I make myself easier understandable. Kind of global politeness.
On lower case
Nouns are smallcase in English, like meat, ball or community. Names, like Mark Dilley or Berlin are upper case. German nouns are upper case (tests show that it augments readability actually), for example Gründer - founder. One exception: wiki is smallcase, always. Thus I propose for a global link language to use
- community-wiki
- meat-ball-wiki
- Gründer-wiki
Ok, meatball and oddwiki might be discussable 
The name of a wiki has to contain the word wiki, else it’s attached at the end. Thus oddmuse-zen-garden-wiki
page names go like this
name of the wiki: name of the page
community-wiki: wiki-node
keep in mind that these are links and that they have a different color, the upper case as an information of importance is not neccessary. The rules where made for handwriting and printing in books where different text color is a hell of a deal. On computer-monitors it’s all easy. This new situation is not reflected in our ortographics yet. We have to strip the text from information overload - upper case often is doubling information that is already there.
Clean linking becomes especially interesting in combination with deep linking.
Using dashes in the english words is simply incorrect ortography. English has a large number of words that are actually spelled with a dash in them. How to link to them? Using three dashes (clean—linking) is surely an option, but looks (and feels when typing) wierd. Maybe using some other easily-typed (on common keyboards) character would be better (clean.linking, clean\linking, clean+linking). No matter what option is choosen, it has some drawbacks at least in some languages/use-cases. I think it’s good when a wiki is just configured so that it is best suited for whatever purpose that particular wiki was created. No need to have a complete, elaborate common wiki-syntax. – RadomirDopieralski
A friend of mine recently stumbled across an idea that led him to start creating a PHP wiki engine that includes clean linking built in to the syntax. It also includes a form of NearLinks, which he is arranging as “lateral” or “hierarchical”. He only created this a few days ago, and he’s still not incorporated things like RecentChanges. I thought it was interesting because it is the first instance of a wiki engine with clean linking built in that I know of. See: http://fortress.shacknet.nu/phliki3/main.php?p=main – SamRose
MattisManzel: Very interesting, Sam, thanks. “No need for a globally organized air-traffic control” Wilbour Wright said, probably, dunno, but if he was surely wrong. It might not seem urgent to have a complete elaborate common wiki-syntax now but it might be of a real big advantage later to think a little about it already now. One big soup - the imagination of five big soups not being able to communicate properly among each others is horryfying.
