My take is this:
Ontologies represent information on our systems (systems being general,
inclusive of but not exclusive to I.T. systems). These are systems like
information, process, rules, and services. A primary use case for defining
such systems is to collaborate with others – so that our processes,
services and information work together. We can only collaborate based on what
we understand. We can only understand what we can see, what is “published”.
The paradigm of “email publishing” is insufficient – we want
to be able to connect and link systems globally, so we need a global publishing
and reference system. An ontology that is an island may be interesting, but
make it part of these global systems and it is of immense value. We need the
infrastructure for these published and linked ontologies of our interconnected
There are certainly other use cases, but
that is mine and that of a few of my friends.
Behalf Of Cameron Ross
Sent: Tuesday, April 06, 2010
To: [sio-dev] discussion
Subject: Re: [sio-dev] Fwd: [ontolog-forum] Sharing and IntegratingOntologies
I'm also very interested in understanding how online ontology
repositories will be used. The OOR use-cases I've seen have been limited
to repository management. What are the application specific use cases?
I mean, why would an ontologist, software developer and/or software agent
use an online ontology repository?
On Tue, Apr 6, 2010 at 8:45 AM, Ron Wheeler <rwheeler@xxxxxxxxxxxxxxxxxxxxx>
Does anyone have a written use case for what an ontologist would want
What are the problems he/she should be trying to solve when they
contemplate selecting one of our artifacts?
How will our artifacts interface with the rest of the solutions set?
Are we in a position to write the introductory chapter of the user
Do we have a place on the wiki where these ideas can be developed?