Barbara: Thumbs up on below. I'm the gov't data model lead for Army Future
Combat System development, and what you describe below is exactly what I want
to do to drive the FCS data model development, given the numerous data models
and message standards we need to integrate/interoperate/mediate to/from. The
CECOM SEC ontology effort are driving to do just that and I hope to
leverage/drive those efforts. (01)
Ken (02)
Ken Lorentzen
PM UA SWI - Strategic Integration
Comm: 732-427-2537
Cell: 908-675-6937 (03)
-----Original Message-----
From: Broome, Barbara (Civ,ARL/CISD) [mailto:bdbroome@xxxxxxxxxxxx]
Sent: Friday, November 19, 2004 10:14 AM
To: cuo-wg@xxxxxxxxxxxxxx
Subject: [cuo-wg] FW: Common Upper Ontology Meeting Notes (04)
Jim, (05)
Nice meeting. (06)
Let me just follow up with a couple of points regarding the issues discussed. (07)
(1) Your point about not repeating the mistakes that the AI community made is
very valid. The AI community overcommitted, and then when they made strides
forward they got very little credit because expections were higher than the
deliverables could support. When we talk about Ontologies supporting
machine-to-machine interoperability, I think we begin to make our goals sound
too big. More humbly, there are two important tasks that these Ontologies
should support in a netcentric computing environment: (a) heterogeneous data
integration; and (b) automatic service discovery. There may be other
tasks...but these two cover a pretty big chunk of the "interoperability"
problem. (08)
(2) I mentioned concerns that there's more payoff with the lower level
Ontologies than with the upper level. When we used an "Upper Ontology" for the
STO, we chose GH-5 (C2IEDM) and converted it to OWL. Now that is a
considerably lower level ontology (i.e., more specific to our problem) than you
are addressing with SUMO, PSYC, and DOLCE. I gather from the discussion that
this would be a "Middle Ontology." Later, when we actually went to integrate 2
data sources, we found the real work was still tied to the data. GH-5 helps
some, but you still have to extend it to get an Ontology than can really be
used to access multiple heterogeneous data sources. Similarly, if we wanted to
do automatic service discovery, we would have to do a lot of work to insure the
right terms are defined well enough to support discovery of the kinds of
services we're interested in. I'm not saying that Upper Ontologies are not
important. I am saying that, within DoD we may want to focus on estab!
lishing several quality Middle Ontologies and figure out how to incorporate
them into our systems. That certainly is difficult enough to sit in the
research arena... but is DoD-specific enough to mean that the general research
community will probably not address it without DoD funding. And this bit of
focus may help us to avoid the AI problem discussed above. (09)
Best regards,
Barbara (010)
-----Original Message-----
From: Schoening, James R CECOM DCSC4I
[mailto:James.Schoening@xxxxxxxxxxx]
Sent: Thu 11/18/2004 2:13 PM
To: Broome, Barbara (Civ,ARL/CISD)
Cc:
Subject: RE: Common Upper Ontology Meeting Notes (011)
Barbara, (012)
Good points. You should post them to the group at
cuo-wg@xxxxxxxxxxxxxxx (013)
Jim (014)
Lorentzen, Kenneth A PM UA NSI.vcf
Description: Binary data
_________________________________________________________________
Message Archives: http://colab.cim3.net/forum/cuo-wg/
Subscribe/Unsubscribe/Config: http://colab.cim3.net/mailman/listinfo/cuo-wg/
To Post: mailto:cuo-wg@xxxxxxxxxxxxxx
Community Portal: http://colab.cim3.net/
Shared Files: http://colab.cim3.net/file/work/SICoP/cuo-wg/
Community Wiki:
http://colab.cim3.net/cgi-bin/wiki.pl?SICoP/CommonUpperOntologyWG (01)
|