I wanted to collect some ideas on how people structure their namespaces in their flexwiki implementations, with a view to providing information for people setting up a flexwiki WikiFederation to help them structure their wiki,

Our flexwiki federation is relatively immature but growing all the time, and I think it's time to refactor the namespaces: I want a schema that's easy to use but also extensible - currently I have everything as flat namespaces, with everything linked to from a page on the default namespace, and I don't feel this is going to scale very well.

We are mainly using this for a few projects to write up system/business documentation on, and for teams to share ideas with each other, and information with their users.

So currently it looks like this:

• Wiki (the default TopicNamespace)
• Plato (a project)
• MarketRisk (another project)
• SDR (yet another project)
• Teams.Architecture (a team - here I'm playing around with using multiple 'layers'(?) in the namespace)

I've just discovered the ImportSetting in the ContentBaseDefinition file, and have imported all the other namespaces into the default 'Wiki' namespace. This is good, because poeople can now hook an RSSReader up to the default namespace and see everything that's going on, however it's also had the unfortunate effect of meaning that some people's WikiSignature come up as a drop-down within the default 'Wiki' namespace, because they have had to put a WikiHomePage in each namespace...

Some thoughts...

• Should I create a 'People' namespace, and put everyone's WikiHomePage in there? (so that WikiSignatures would be of the form 'People.MattWynne')

• Should I try to keep all namespaces hierarchical, e.g...
• MyCo.Projects.WidgetFactory
• MyCo.Projects.ThingyEngine
• MyCo.Teams.Miners
• MyCo.People
• ... or skip the common 'upper' tier, e.g....
• Projects.WidgetFactory
• Projects.ThingyEngine
• Teams.Miners
• Poeple

• how can the importing work best for us? should we keep it hierarchical and allways import child namespaces?

I would really like to hear other people's stories about how they've implemented their namespace structures, before I embark on my refactoring mission. Thanks in advance peeps! -- MattWynne

For my bliki (HomePage) I use a namespace called Derek as the default namespace and one called Articles for the Articles.HomePage section. I also have a 'normal' FlexWiki that is intended to be the documentation for some components that is intended to reflect the namespace structure of the component and it's related classes, but I tried to import from the generated XML and it hasn't quite worked the way I wanted and I haven't had time to rebuild it -- DerekLakin