Return-Path: 
 <dev-return-49276-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 76930 invoked from network); 13 Oct 2003 07:36:49 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 13 Oct 2003 07:36:49 -0000
Received: (qmail 28884 invoked by uid 500); 13 Oct 2003 07:36:22 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 28697 invoked by uid 500); 13 Oct 2003 07:36:21 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 28684 invoked from network); 13 Oct 2003 07:36:21 -0000
Received: from unknown (HELO confixx.bestiole.ch) (66.111.0.243)
  by daedalus.apache.org with SMTP; 13 Oct 2003 07:36:21 -0000
Received: from apache.org (lsb-catv-6-p105.vtxnet.ch [212.147.121.105])
	by confixx.bestiole.ch (8.11.6/8.11.6) with ESMTP id h9D7aWP15334
	for <dev@cocoon.apache.org>; Mon, 13 Oct 2003 09:36:32 +0200
Date: Mon, 13 Oct 2003 09:36:41 +0200
Subject: Re: [RT] Improved navigation of learning objects
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Bertrand Delacretaz <bdelacretaz@apache.org>
To: dev@cocoon.apache.org
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <92E63D74-FCCC-11D7-B7DA-000393D2CB02@apache.org>
Message-Id: <FC8FEF1A-FD4F-11D7-AD04-000393CFE402@apache.org>
X-Mailer: Apple Mail (2.552)
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Le Dimanche, 12 oct 2003, =E0 17:55 Europe/Zurich, Stefano Mazzocchi a=20=

=E9crit :
> On Sunday, Oct 12, 2003, at 16:13 Europe/Rome, Alan Gutierrez wrote:
>> ....Has anyone discussed how to impose an outline on a Wiki?
>
> yes. there are some proposals on the table, ranging from simple to=20
> futuristic....

I think we should concentrate on the simple one for now, maybe by=20
creating an experimental block to work on a prototype?
We could copy the existing docs there, assign unique IDs to them and=20
start playing with trails.
Having permanent IDs leaves room for the futuristic stuff to emerge.

> ...[note: this is getting closer to what topic maps are about! see=20
> topicmaps.org, even if, IMO, it wouldn't make sense to use topic maps=20=

> for this because they are much more complex]

Some form of topic map would be useful to build "what's related" info=20
though, which helps navigation and discovery a lot.

<snip very-interesting-futuristic-stuff>
Thanks for sharing this!

-Bertrand