Excellent. I argued in earlier discussions on IBIS that it is often
necessary to be able to interject material into the discussion that doesn't
fit the model. When there is a link to a paper or an entire web site in an
email, for example, the writer is not suggesting that the new material
necessarily supports or opposes any particular point in the discussion, but
only that it provides relevant information.
Those in the discussion who read the material my find a number of arguments
relevant to the discussion, to different points in the discussion, and in
support or opposition.
If there is enough interest in the new material and it is really relevant,
much of it will eventually be absorbed into the discussion, but it can't be
dumped into one of the existing IBIS categories. There needs to be a
"reference" or "related material" mechanism, and a Wiki seems to be an
Garold (Gary) L. Johnson
----- Original Message -----
From: "Jack Park" <email@example.com>
Sent: Friday, August 24, 2001 6:18 PM
Subject: Re: [unrev-II] Re: Maleable Archives
> I am taking one of the Java Wiki implementations and turning it into an
> instance of a <topicMap> where each page can be a <topic> and so forth.
> plan is to add page version control and purple numbers (Murray?) before
> turning it loose. Also want to be able to copy&paste image files in as
> In the end, I envision that when folks get heavy into a heated IBIS
> discussion, they can go over to the Wiki and create a page, write a tome
> whatever, then link it back into their IBIS arguments. That way, the IBIS
> discussion stays on task, discussing issues, not carrying long papers
> for the ride.
> At 04:15 PM 8/24/2001 -0700, you wrote:
> >* Eric Armstrong <firstname.lastname@example.org> [010824 14:28]:
> > > Alexander Shapiro wrote:
> > > > What about a CVS type approach to discussions. Anyone can edit,
> > > > possibly even other peoples messages (what if you see a typo made by
> > > > someone else). The latest changes (diffs) can be seen, and voted on
> > > > by readers. The author can get priority in refusing changes to
> > > > messages. Also, now I am thinking that the author could explicitly
> > > > allow or dissalow others (all or groups) to change their posts.
> > > >
> > > That is basically the idea. But we need granular versioning,
> > > so changing a line revs the paragraph, not the whole document.
> >I am a wiki fan. I have info on Wikis on my open source Groupware page
> >at http://nexist.sourceforge.net/groupware.html.
> >I know that Eugene was working on his modified wiki and Jack was working
> >on something similar for Nexist.
> >-- Grant Bowman <email@example.com>
> Community email addresses:
> Post message: unrev-II@onelist.com
> Subscribe: unrev-IIfirstname.lastname@example.org
> Unsubscribe: unrev-IIemail@example.com
> List owner: unrev-IIfirstname.lastname@example.org
> Shortcut URL to this page:
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Secure your servers with 128-bit SSL encryption! Grab your copy of VeriSign's FREE Guide, "Securing Your Web
site for Business" and learn all about serious security. Get it Now!
Community email addresses:
Post message: unrev-II@onelist.com
List owner: unrev-IIemail@example.com
Shortcut URL to this page:
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
This archive was generated by hypermail 2.0.0 : Sat Aug 25 2001 - 08:54:47 PDT