The canonical use for this is some that everybody who wants to run a FlexWiki doesn't have to start off by copying all of the common files like One Minute Wiki, VisitorWelcome and SuggestedEnhancements. Copying these is evil

This would probably be best implemented by as a kind of AbstractContentBase.

Perhaps I am being a little naive or maybe I don't fully understand the problem, bout couldn't you provide Federation Linking like this:

Define this as for an external wiki:

 @fedFlexWiki=http://www.flexwiki.com/default.aspx/FlexWiki.$$$

Then you can use this:

 One Minute Wiki@fedFlexWiki

To give this One Minute Wiki.

This method works fine at the moment and is the approach I use on my internal FlexWiki to provide access to the standard pages like OneMinuteWiki, etc. Ideally I think there would be a slightly different syntax so that these links can be displayed in a different format making a federation link distinct from a wiki link. -- DerekLakin

• This approach requires you to hand-construct all of these links, topic by topic. It also requires the references to those topics to be written somewhat unnaturally. With a Linkedfederation, that would all come for free. Link the two ContentBases and you're done. -- DavidOrnstein

I think I understand now. So the linking of two ContentBases would behave the same way as importing a namespace in C#, such that you only need to qualify ambiguous topics, i.e. those that appear in both namespaces. -- DerekLakin