SUO: Re: Standard Upper Ontology Procedure Topics
o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o
SUOPT. Note 5
o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o
SUOPT Outline. http://suo.ieee.org/email/thrd1.html#11635
CA = Chris Angus
JA = Jon Awbrey
In reference to:
SUOPT 04. http://suo.ieee.org/email/msg11708.html
CA replied:
JA: I think I explained what I would be trying to do before I started,
and I've been trying to give ongoing explanations along the way,
but I will try to provide a more compact account at this point.
CA: Maybe you did, but quite frankly it becomes difficult
to keep track of what it is you are doing given such a
plethora of messages, particularly given the propensity
for the SUO list server to delay, replicate, and amend
the delivery order and also given the volume of messages
from other sources that many of us get. What is it that
tells me how to deal with:
JA: SUOPT :> Defect 01. http://suo.ieee.org/email/msg11711.html
In substance:
JA: What is a defect?
Yes, I understand the frustration with current technology.
It is every bit as tedious for me to follow this discipline
in my writing -- not to mention having to develop it as I go! --
as it must be for you to follow it in your reading. But we
are bound to work with the tools that we have, very often
self-applied, in order to build the tools that we'd like.
It is the 20th of November in the year 2003. I attended my
first seminars on the hot new topic of "Groupware" in 1985-86,
when I was passing through Ann Arbor as a grad student in math,
and the Business, CogSci, and CompSci units had just put together
a new consortium and broke ground on a brand new building dedicated
to R&D on collaboratory environments, among other things, and software
to help people truly collaborate on a global basis was one of the main
project foci and application themes.
And still we have to work this way. Well, at least it's better than it was.
There are all sorts of bright prospects on the horizon. I mentioned Croquet:
http://www.opencroquet.org/
Probably some people, who know more than I do
about the pre-reqs of it all, could help by
looking into this and other such systems.
But we at IEEE SUO are hard on our toys and our tools alike,
and the bales that we have conduced it to tote have already
broken down the poor old Flutterby several times, so it may
be a while loop or two or three before a prospect pans down
the pike that is sufficiently robustic for our daily grinds.
I am going for shorter notes if I can,
so I will break this one off here and
pick up the rest of your points later.
Jon Awbrey
o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o