Hint: If you don't know what the terms 'federation', 'namespace', 'TopicNamespace' and 'WikiBase' mean in the context of FlexWiki, see WikiFederationOverview.)

The FederationConfiguration is an XML file that defines most of the important things about your federation (the namespaces in the federation, etc.). You identify your FederationConfiguration file in the web.config file on your server (see WebConfiguration for details).

In the configuration file is information about the federation, including a list of all of the WikiBases in the federation. For example:

<?xml version="1.0" encoding="utf-8"?>

<FederationConfiguration>

<DefaultNamespace>FlexWiki</DefaultNamespace>

<Namespaces>

<Namespace Root=".\wikibases\FlexWiki" Namespace="FlexWiki" />

<Namespace Root=".\wikibases\SecondNamespace" Namespace="SecondNamespace" />

</Namespaces>

<About>This site is the home of FlexWiki, an experimental collaboration tool. Read OneMinuteWiki, VisitorWelcome or PNADocumentation to learn more.

</About>

</FederationConfiguration>

In this example, we define a configuration with a default namespace (FlexWiki), two WikiBases, a mail server configured to send WikiNewsletters and the About setting (see FederationBranding).

• Doesn't appear to be any mail server defined here. There's no SMTP setting. OK, I know, it's in the web.config file but I don't see why it's mentioned here -- [ WayneDawson - 2004-07-19]

In this example, there are two namespaces in the federation and their content is stored in the folders .\wikibases\FlexWiki and .\wikibases\SecondNamespace. These could be absolute file-system paths, but in this case they're relative paths -- relative to the location of the NamespaceMap.xml file itself.

This location is called the WikiBase's RootFolder.

How to add more namespaces

Go to your admin folder and follow the namespace wizard and one will be created for you.

Note

the Root for a namespace in a <Namespace> element will only be considered relative if it starts with .\. This might be surprising if you expect other common forms of relative paths to work; they won't!

Note

when you define a namespace FlexWiki will create a folder for it automatically. -- JustinCollum

Question

How do I go about configuring WikiBases AGMTA and AGTMA.Projects for my FlexWiki implementation? Also, do I need to establish seperate WikiBase folders? Thirdly, how do I reference a topic from the second namespace in a Wiki document in the first?

Question

This seems to be old format, can anybody publish the new format?

Answer

It may not be my place, but I ran into the same problem so here is my stab at it, copying this page and modifying where necessary by looking at the source code: NewFederationConfiguration. Feel free to edit, hack, slash, delete or otherwise modify. JasonWilliams

Configuration Options

The following options can (and sometimes must) appear in the federation configuration file:

<DefaultNamespace>

This defines the namespace whose HomePage will appear when a user visits the front page of your FlexWiki site and hasn't specified a specific page to view.

<About>

This setting lets you control the About text for your site. See FederationBranding for more details.

<NoFollowExternalHyperlinks>

This setting controls whether FlexWiki will generate user-supplied hyperlinks with the appropriate HTML to support the NoFollow anti-spam initiative.

Setting to a 1 will enable NoFollow support. Setting to a 0 will disable this support.

Question

Like this? <NoFollowExternalHyperlinks>1</NoFollowExternalHyperlinks> . For some reason this does not work. Any ideas?

Answer

Yes. Make sure you have a recent InterimBuild. -- DavidOrnstein

<Namespaces> and <Namespace>

The <Namespaces> element contains a series of <Namespace> elements, each of which define a namespace by providing the name of the namespace as well as the location of the "RootFolder" for the namespace. In the example above, there are two namespaces in the federation and their content is stored in the folders .\wikibases\FlexWiki and .\wikibases\SecondNamespace. These could be absolute file-system paths, but in this case they're relative paths -- relative to the location of the FederationConfiguration file itself.

Note

Tthe Root for a namespace in a <Namespace> element will only be considered relative if it starts with .\. This might be surprising if you expect other common forms of relative paths to work; they won't!