Componentising topics into sub-objects that could have different types

It occurred to me that exploration of WikiPedia's multiple tabs (Summary, Discuss) etc could usefully solve some of TWiki's issues, including MultipleFormsPerTopic

Suggestion:

• interject a topic-component level beneath page. Subjugate existing topic content into a default component.
• allow different page layouts to express the different components differently.

The schematic below shows the different components as tabs.

______________
|  Summary   |  Discuss |  Form1 | TableA | TableB |
|            --------------------------------------  

To transition, all existing content would be moved onto Summary. Topic references without content would default to summary. Tables and forms would get moved to different components.

In the RCS stores the different components would get stored in different files.

We'd need an extension to topic naming, e.g. Web/SubWeb.TopicComponents:Summary#anchor

-- MartinCleaver - 23 Oct 2005

This is related to TopicObjectModel

-- RafaelAlvarez - 23 Oct 2005

The user interface can be done with NavBarAddOn.

-- ArthurClemens - 24 Oct 2005