Darren Kenny wrote: > I think an important must have feature that I've not seen specifically > mentioned, but maybe I've missed it, is the ability to have a at least a some > sort of page hierarchy (like filesystems) mechanism. > > This is a feature I've found very lacking on some Wikis and have generally had > to create pages like SomeTopic_SubPage1 rather than SomeTopic/SubPage1. This > would also allow for each project/community to have their own area - but also > helps avoid some namespace collisions between areas. > > For this reason I have liked Moin Moin wiki over other solutions I've > experienced, but that was only for personal use, I don't know how it scales. > > Thanks, > > Darren. > Good shot.
You are correct that there is currently no requirement regarding page hierarchies. There is, however, a requirement to support namespaces (actually 'namespaces and/or categories'), with a view to facilitating content structuring, which would allow for separate areas. It would also allow pages with the same name to exist in different namespaces, for example, zones.howto and nwam.howto (the nomenclature is just meant to show <space>.<page>). So I think hierarchies would help avoid collisions *within* areas, as namespaces already protect against collisions *between* areas. The area of taxonomy is not well covered, and whatever drops out of the community simplification effort, it is clear that the system has to be flexible to accommodate change - hierarchies would aid flexibility. So, I think page hierarchies is a good requirement to have, but that it is also related to namespaces and content structuring. Perhaps requirement C16 needs updating to reflect this, and possible moving to an essential requirement, as I'm not sure a wiki without the capability of some sort of taxonomy is of any use to us. Maybe the correct thing to do is have namespaces and hierarchies as part of a taxonomy requirement. Chris _______________________________________________ website-discuss mailing list [email protected]
