Links:
InterWiki http://interwiki.wiki.taoriver.net/
Talks about coordinating multiple wiki sites. (01)
Your own transClusion talks about inter-site referencing.
http://purplewiki.blueoxen.net/cgi-bin/wiki.pl?TransClusion (02)
Bill Seitz site is full of good comment re: collaboration:
http://webseitz.fluxent.com/wiki/GroupDiscussion (03)
What I'm basically talking about here is if you have a class, WikiWord,
page, subject called EricKim, it should be unique. And anyone who would
use this name in a wiki, blog, or webpage would automatically get there
via its #id. All it would take is a next generation dictionary project
- maybe WordNet will morph into this. These words are becoming
commodities, MicroSoft, MikeRoweSoft - did you see that blurb :). (04)
Ayway, you maintain EricKim (whatever site/wiki). When I want to
reference it, instead of doing a google search for EricKim, getting
your page, finding the purplenumber, copy and paste it into my new
members page, what I would like to do is make EricKim on my wiki, save,
have the question mark next to the name as it waits for me to create a
new page, then when I click the question mark, before it makes a
(redundant) new page it goes to 'the master ID dictionary' and checks
if there is already a purple number (ID). In this way I don't have to
make a new page for EricKim, it will automatically be a link to your
EricKim page (or maybe I'll have the option of transcluding it; cool,
today's new word!). If EricKim doesn't exist, I make the new page
which is then the page (class - ID) called EricKim. (05)
Forgive me for leaving out the devil details (and my terrible writing).
And also forgive me for not being able to program it. :). (06)
Back to Ontology. Ontology is the organization of this dictionary. A
media arts ontology is a subset of this dictionary. (07)
The way to make a digital arts ontology is the subject of the DAO site.
It is a sister of other ontology project sites, and a subclass of
OntologyProjects. (08)
Re: the integration of the forum and wiki is something I would very
much like to talk more about! This is what I mean by ontology
harvesting. The list creates a load (hopefully) of discourse - raw
data. It would be so good if email tools could be integrated more into
this process (as email is the main discourse interface). If email were
to become obsolete in favor of short messaging (with persistence), then
one could build wiki features into the messenger. (09)
Ontology and discourse analysis need to come together here. Anyone have
a link to a good text analyzer for OSX. I'm translating a textbook into
Chinese. The index of this book will become the ComputerMusicOntology -
a subclass of DigitalArtOntology. (010)
Ken. (011)
On Feb 2, 2004, at 2:53 AM, Eugene Eric Kim wrote: (012)
> On Sat, Jan 31, 2004 at 09:33:04PM +0800, Kenneth Fields wrote:
>
>> I don't think a Wiki need be tailored toward ontology making - rather
>> there needs to be a wiki discourse harvester. Wikis should cooperate
>> on
>> this level - by making their vocabularies (rules) available when a
>> pull
>> (OntoRequest) is received from an OntoAgent at GoogleOntologyServices
>> :). I'm counting on your guys to tell me this exists already.
>
> I don't think it does, and I wouldn't know how to do this myself. So
> you can help us by explaining:
>
> 1. How we would do this? Do the protocols for doing this already
> exist?
>
> 2. Why we would want to do this? Give me a scenario where something
> like this would be useful to you folks.
>
>> Anyway, I see two goals for the DAO project: one is to harvest digital
>> arts discourse while documenting and organizing it (ontology). A
>> parallel course is to discuss (semi)automation of the process. So we
>> have two paths to take - both are good. While each of those
>> discourses
>> are themselves mine-able discourses. How can we make the forum part of
>> the CWE more mine-able and documentable on the Wiki. The purple
>> numbers
>> help! But its not the total answer. Point me to where this already
>> exists :).
>
> One of our ongoing goals is to unify the underlying architecture of
> our tools. Thanks to PurpleWiki's architecture, we have WikiWord
> support, transclusions, and backlinks in blogs (via plugins) as well
> as PurpleWiki. We want to implement the same with mailing list
> archives. This isn't hard; it just takes time, so if one of you is
> looking for a project, let me know. :-)
>
> -Eugene (013)
Powered by MessageSoft SMG
SPAM, virus-free and secure email
http://www.messagesoft.com (014)
_________________________________________________________________
Message Archives: http://dao.cim3.net/forum/dao-forum/
Subscribe/Unsubscribe/Config: http://dao.cim3.net/mailman/listinfo/dao-forum/
Shared Files: http://dao.cim3.net/file/
Community Wiki: http://dao.cim3.net/wiki/
Community Portal: http://dao.cim3.net/
To Post: mailto:dao-forum@dao.cim3.net (015)
|