On 10/7/2011 1:35 PM, Duane Nickull wrote:
> Sorry to interject, but to me the term "SOA Ontology" means an ontology or
> set of formal abstract constraints that declare the knowledge of "what"
> SOA is (profuse apologies if this is errant). If the ontology work is to
> classify things that are not exclusive to SOA, then it should not be
> called an "SOA ontology" perhaps. Is there a definition of exactly what is
> meant by SOA ontology? (01)
This is the critical question. (02)
In talking about ontologies, we have usually addressed the subject
matter of the applications. For example, an ontology for medical
applications would define things like diseases, drugs, therapies, etc. (03)
If we're talking about the subject matter, the same application
ontology would be used for programs that process documents on
the internet, organize a database for a hospital, or provide
SOA services. (04)
But if we're not talking about application ontologies, we have to
state what kinds of things and processes a SOA ontology is supposed
to define that are different from anything that is required for
other kinds of computer systems. (05)
Before you can begin to define a formal ontology for anything, you
must at least have some informal list of what you need to specify.
Some questions: (06)
1. Does anyone have such a list for SOA? (07)
2. If the things on that list were formally defined, how would those
definitions be used? (08)
3. Would those definitions improve SOA systems? (09)
4. How? (010)
John (011)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J (012)
|