Content Wiki: Difference between revisions

    From Consumerium development wiki R&D Wiki
    (Subarticles vs. monolith articles)
    (How to handle a situation where the target of the article changes)
    Line 67: Line 67:


    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
    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===
    Situations like this include:
    *Product upgrades
    *Mergers

    Revision as of 12:21, 5 October 2003

    What is the Content Wiki?

    Content Wiki is where facts on products and companies and such will be stored when it gets built.

    Opinions (ie. Campaigns and split articles) go to The Consumerium Exchange when it gets built.

    This page is not for actual content but for developing the syntax and governance of the Content Wiki so we can set one up.


    Wiki software

    To fork or not to fork that is the question. It is natural to presume that the wiki softare will be either:

    1. MediaWiki unmodified
    2. MediaWiki modified
    3. A fork of MediaWiki
    4. Something else?

    Which one of these alternatives makes sense is an open question


    The relationship between Wiki and ConsuML information

    • 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 autogenerated protions will be enclosed with special tags such as <autogenerated></autogenerated>
    • Messing with the autogenerated portions manually better be justified
    • The ConsuML will act as a glue between The Consumerium Exchange and the Content Wiki. ConsuML will be used to verify what corresponds to what within The Exchange and between The Exchange and The Wiki

    Wiki Syntax

    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:

    We need to start forming templates to advance the launch of the Content Wiki:


    Governance

    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


    Interaction between other wikis containing related content?

    Background: There is already information on companies, brands, labels and such in Wikipedia and Disinfopedia.

    • How to avoid redundant copy-pasting between wikis?
    • How will the recording of information be coordinated to benefit the consumer in her/his search for knowldge on offered products?
    • The obivious thing that comes to mind would be to build an interwiki watchlist type of utility that would enable tracking changes to articles with matching article names across multiple wikis. This would most likely interest the editors of all the involved wikis.

    Other Open Questions

    How to handle the internationalization?

    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

    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

    Situations like this include:

    • Product upgrades
    • Mergers