Ah. Yes. Totally agree. I see categorization with some
sort of hierarchical taxonomy and/or topic map network
as the next critical step in moving the tool towards a
knowledge-management system. (01)
I emphasize that it is the *second* step, however. Early
on, I thought it was critical to the collaboration problem.
Now, I'm thinking that it isn't. (02)
I see remote collaboration as the first problem that needs
to be solved, so that bigger and better systems can be
evolved, extended, or designed. (03)
"Garold (Gary) L. Johnson" wrote:
>
> Eric Armstrong wrote:
>
> * I'm not sure what you mean here. Do mean the ability to define arbitrary
> > categories (aka classes), and assign them to purplized nodes? If so, I
> > grant that it would be useful, and I'd love to see it. (I think that's
> > what Peter was alluding to when he mentioned reorganizing at a meta
> > level.) But I've reached the conclusion that a well-structured
> > discussion can be carried on without them.
>
> For discussions, I agree, but discussions are not all there is in the world.
>
> I want to be able to use the same system to organize meeting notes,
> documents that I need to study and my notes on them, project analysis,
> software design information, ... and nearly any other sort of information
> that I need to find again.
>
> Subjects (Topic Maps) help for that. I see topic maps as essentially an
> outline on which to hang information. While using outliners with the subject
> / article model, I often find that it would be convenient to have some sort
> of outline separate from the information, and that is what subjects are for
> me.
>
> One feature I always want in an outliner is "cloning", the ability to have
> the same record in more than one place. I see a good Topic Map system as an
> outliner where every node is a pointer, and hence a single node can be in as
> many places at once as is convenient.
>
> In some paper filing systems that work this way, the process is to search
> for a folder by how you remember it, and if you don't find it where you
> think it should be, mark the spot. When you do find the folder, return to
> any marked spots and insert a reference to the correct folder. This scheme
> works within any linked system.
>
> When followed consistently, information tends to be located by the all of
> the "intuitive" paths, much as happens in human memory.
>
> == Wiki Parents ==
>
> All that is done in such systems is to save the node name used to create the
> new entry. This provides a singly linked list of ancestors. Some systems
> then support manipulations of the structure. Along with back links and "see
> also" structures, Wikis become much easier to navigate.
>
> Thanks,
>
> Garold (Gary) L. Johnson
>
> --
> This message is archived at:
>
>
>http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=yak&i=MIEJJJFBHJEBDEKGPHOPMEGHEAAA.dynalt@dynalt.com (04)
--
This message is archived at: (05)
http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=yak&i=3E7BA21B.9D271983@sun.com (06)
|