Editing Content Wiki

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
''Is this the same as the [[Signal Wiki]]?  If not, why not?  What must be done to the data before it affects the [[Consumerium buying signal]]?  And when?''
''This page is not for actual [[features|content]] (i.e. do not attempt to classify [[CIV]] or [[Gus Kouwenhoven]] or what they are doing on this page) but for developing the syntax and governance of the Content Wiki so we can set one up.''
''It also is not about opinions, (ie. [[Campaign]]s and split articles on aspects where [[faction]]s do not agree), which go to [[Research Wiki]] aka [[Opinion Wiki]] where further research is performed.  Whatever it is called, this consists of [[Consumerium:intermediate page]]s which are often debated.''
==What is the Content Wiki?==
==What is the Content Wiki?==


Content Wiki is where '''facts''' on [[product]]s and [[companies]] and such will be stored when it gets built. Facts require more discipline than [[opinion wiki]] comments.  When we say "fact" we mean [[instructional capital]] that all [[faction]]s accept as "true" at least to the degree it is allowed to alter the [[Consumerium buying signal]].  ''Another proposed name for this is the [[Signal Wiki]], which makes this relationship very clear.''
Content Wiki is where '''facts''' on [[product]]s and [[companies]] and such will be stored when it gets built.


It will be a [[large public wiki]] with the special problems of that type of communication.
'''Opinions''' (ie. [[Campaign]]s and split articles) go to [[The Consumerium Exchange]] when it gets built.
 
The [[Consumerium Governance Organization]] and its delegated [[sysop]]s will have to decide on what grounds each type of information is input, audited, linked, shared, duplicated, edited, contested, vetoed and removed and by whom.  


This page is not for actual [[features|content]] but for developing the syntax and governance of the Content Wiki so we can set one up.
----
----
==Wiki software for handling research ==
==Wiki software==
To [[fork]] or not to fork that is the question.   Which of the [[wiki code]] alternatives to use?  It is natural to presume that the wiki software will be either:
To fork or not to fork that is the question. It is natural to presume that the wiki softare will be either:
 
#[[MediaWiki]] unmodified
#'''[[MediaWiki modifications|MediaWiki modified]]'''
#[[GetWiki|A fork of MediaWiki, such as GetWiki]]
#[[TikiWiki]] unmodified
#TikiWiki modified
#A fork of TikiWiki
#[[MoinMoinWiki]] extended
#something else supporting [[ConsuML]]


Which one of these alternatives makes sense is an open question.  A [[Wikitext standard]] would help.  [http://www.metaweb.com/wiki/wiki.phtml?title=wikitext_standard  Metaweb is already on it].
#MediaWiki unmodified
#MediaWiki modified
#A fork of MediaWiki
#Something else?


Which one of these alternatives makes sense is an open question
----
----
==The relationship between Wiki and [[ConsuML]] information==
===The relationship between Wiki and [[ConsuML]] information===
*Data stored as [[ConsuML]] documents could be used to generate stubs into the wiki '''on-demand'''
*Data stored as [[ConsuML]] documents could be used to generate stubs into the wiki '''on-demand'''
*The parsing process goes the following way ConsuML data will be parsed to Wiki code in the appropriate natural language for each wiki, which then in turn will be parsed to HTML for the Consumer
*The parsing process goes the following way ConsuML data will be parsed to Wiki code in the appropriate natural language for each wiki, which then in turn will be parsed to HTML for the Consumer
Line 41: Line 29:
If a modified version will be used it makes sense to use many more namespaces to make the wiki more manageable, but on the other hand using standard MediaWiki has many advantages. Using unmodified MediaWiki would just require stricter syntax within the articles
If a modified version will be used it makes sense to use many more namespaces to make the wiki more manageable, but on the other hand using standard MediaWiki has many advantages. Using unmodified MediaWiki would just require stricter syntax within the articles


According to MediaWiki developers adding numerous namespaces is easy so here is a brief and uncomplete list of likely namespaces. Using '''pseudo-namespaces''' might also be applicable:
According to MediaWiki developers adding numerous namespaces is easy so here is a brief and uncomplete list of likely namespaces:
*[[Company]]:
*[[Company]]:
*[[Product]]:
*[[Product]]:
*[[Product Group]]:
*[[Product Group]]:
*[[WorkDescription]]
We need to start forming syntax for [[Consumerium:Intermediate pages|Intermediate pages]] to advance the launch of the Content Wiki
----
==Article Structure==
The [[Wiki]] approach and the [[features|original vision]] can be brought closer by using strictly named subarticles that are then collated into a viewable document on-demand for the [[consumer]] based on her/his [[preferences]]
Advantages include:
*Consumer can specify what information s/he wishes to view and in what order in each case
*Good for internationalization since translation can progress subarticle-by-subarticle
*Finer grained version control and approvance (signatures)
*Performance gains over monolithic articles (?)
*Good for maintaining historical information
*Editors know where to find the portions they have most knowledge of
*Useful for efficiently mixing autogenerated portions with manually edited ones
*Less Wiki Veteran Annoyance due to quicker comprehension of small separate syntax guides instead of one big lump of do's and dont's
Depending on the type of article there are varying needs of:
*Mandatory subarticles
*Optional subarticles
When thinking about companies an outline of subarticle structure is discussed in [[Article structure]]
* ...


We need to start forming templates to advance the launch of the Content Wiki:
*[[Company template]]
*[[Product template]]
*[[ProductGroup template]]
----
----
==Governance==
==Governance==
We need a summarum of the currently existing [[Wiki Governance Practices]] here and study each one and the resulting model that we will use will likely be a synthesis of numerous existing models.  Probably best to discuss at [http://www.metaweb.com/wiki/wiki.phtml?title=Metaweb:governance_ideas Metaweb where big geeks are].
We need a summarum of the currently existing Wiki Governace Practices here and study each one and the resulting model that we will use will likely be a synthesis of numerous existing models
Also track [http://meta.wikipedia.org/wiki/power_structure Meta's power structure debates].
 
Writing explicit [[retail price]] information is not allowed in The Content Wiki. What is allowed is to make remarks that [[Company X]]'s (say some retail-chain in some country) pricing policy for [[product group]]s differs from market averages in one direction or the other.
 
'''See:'''
*[[Talk:Wiki Management]]
*[[Consensus decision-making]]
----
----


Line 96: Line 54:
===How to handle the internationalization?===
===How to handle the internationalization?===
Should all language versions strive to contain the same information or how should we go about this?
Should all language versions strive to contain the same information or how should we go about this?
===Subarticles or a single article?===
There are good sides to both approaches. When thinking about companies an outline of multiple articles might be something like
* [[Company X]] - containing basic identification, [[product group]]s, [[brand]]s, [[product]]s etc.
* [[Company X/economy]]
* [[Company X/history]]
* [[Company X/affiliated businesses]]
* [[Company X/executives]]
* [[Company X/advertising]]
* [[Company X/labor practices]]
* [[Company X/workplace upgrade requests by the workers]]
If the document structure is standaridised it makes for easier navigation and faster downloads. On the other hand it might be considered to limit the creativity of the editors


===How to handle a situation where the target of the article changes===
===How to handle a situation where the target of the article changes===
Please note that all contributions to Consumerium development wiki are considered to be released under the GNU Free Documentation License 1.3 or later (see Consumerium:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)
Retrieved from "https://develop.consumerium.org/wiki/Content_Wiki"