[Pmwiki-users] Why heirarchy?

[John Rankin]

On Wednesday, 20 October 2004 7:27 AM, Patrick R. Michaud <pmichaud at pobox.com> wrote:
>On Tue, Oct 19, 2004 at 10:55:59AM -0700, Fred Chittenden wrote:
>> There's all sorts of applications and uses for hierarchical structure.  
>> For example, I'm fooling around with a soccer club's rec team with about
>> 4000 youth players on several 400 hundred teams.  The most logical
>> structure would seem to be
>> *Rec Soccer
>> **Boys (with ages U7-U18)
>> ***U7
>> ****Schedule and Results
>> ****Team A
>> *****Roster
>> *****Practice schedule
>> *****Team News
>> [...]
>> 
>> SoccerClubBoysU7TeamARoster seems like a rather kludgy long name workaround
>> to having a regular hierarchical structure, particularly when one might
>> have .  When someone views Team A, they'd only have to link to Roster to
>> get Team A's roster, instead of using a long name, which would clearly be
>> subject to all sorts of errors.   
>
>This example is excellent, but I need a response to a clarification.
>Per the example, given that someone is viewing Team A, they'd be
>at a page like SoccerBoysU7TeamA.HomePage, and links to the other
>pages would then be [[Roster]], [[Practice schedule]], [[Team News]],
>etc., exactly as you've described.  In the current one-level system, 
>long names only seem to come into play when linking to another team's 
>roster or page, yes?  Does that happen with enough frequency to be
>a concern?  If so, what would be a typical example of a cross-team/
>cross-group link, and what would you expect the markup to look
>like?
>
>Or does the example here envision that each of the "Roster", 
>"PracticeSchedule", etc. will be groups containing subpages and not
>leaf pages as I've described them here?
>
>Pm
>
Would this be a case where a wiki farm is useful? 

-- 
JR
--
John Rankin