"Garold (Gary) L. Johnson" wrote:
>
> I agree that we don't need formal classification systems, but we *do* need
> subject hierarchies and ways to assign multiple subjects to any part of the
> information. This sort of reorganization supports the "Reorganize, Relink,
> Subsume" idea.
>
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. (01)
The discussion may well need to be more limited, however. So the
reorganization would keep factoring out questions and issues,
continually
modifying the malleable layer (while the underlying log of posts remains
inviolate and intact). (02)
> A well designed Purple Wiki + email system *with the other features* you
> describe (outline views, etc.) could well be an excellent start.
>
> This is why I keep pushing for wiki text in email, including
> purple numbers.
>
I agree with your conclusion. The inclusion of links to the archive,
minimal as it is, is already proving to be of value. (03)
> I would settle for enforcing plain text email and seeing only wiki text. > The
> resulting emails could have identifiers constructed and e linked into a
> segment of the wiki. Capturing the threading might be harder, but the
> current email archive does it, so it is apparently possible.
>
Sounds good to me. I've switched back to plain-text editing.
Thanks to this forum, I've learned to make sure my groups all specify
"Deliver plain text", as well. (04)
> There are mechanisms in some Wikis that support construction of an
> outline or at least an ancestor list.
>
Really! That would be an interesting avenue to pursue. (05)
> I find a wiki difficult to deal with since I can see only a single
> note at a time.
>
I'm glad to know it's not just me. I've found that to be a major
limiting factor, as well. (06)
> I have often envisioned an outliner that can access a wiki.
> This can be done locally, but interacting with a true wiki on the
> web is not so easy.
>
The ADM outline browser may well make a difference here. I suspect
that <a type="transclude"> or something of that nature would be
necessary to identify the outline-able material, and maybe ADM's
browser would need a bit of customization, but they have the basic
functionality in place that would make it possible. (07)
Note:
Their goal is to sell browsers, or maybe systems. Last I heard,
they were still working on their business model. I have nothing
whatever against them making a buck, and I don't mind buying a
copy if necessary, as long as the interaction-protocols are
documented, and other browsers could be constructed. Or if a
wiki/browser combination is really successful, maybe they would
sell wiki-systems and give away the browser. Dunno. But a clever
browser that improves usability of a system that *also* works
with standard browsers would be a killer combination. (08)
> If entries were also made into a date structure similar to Blosxom, and
> indexes created based on Topic Maps or even just a simple category list >
>that allowed multiple categories, we are very close to having many of
> the necessary tools in one place.
>
Again, I need more convincing that categorization is really necessary,
as opposed to really nice. (At one point, I know I thought it *was*,
but if there was a compelling use case that motivated it, I've lost
sight of it.) (09)
> If we could then develop a local outlining tool that understood how to
> access the Wiki files as notes, remote editing of a Wiki from something
> other than a browser becomes feasible.
>
> Oh well, it doesn't hurt to dream!
>
I'm liking ADM as a starting point for the browser. But I suspect that
something like NextistWiki will be a good starting point for the Wiki. (010)
--
This message is archived at: (011)
http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=yak&i=3E7660CC.EE6B2A7D@sun.com (012)
|