|
|
|
|
|
What’s been done/tentatively planned |
|
Dynamic Data Base/Advanced ISR
Management Ontology |
|
Translation to DAML |
|
Potential use in EEE FY 02 Experiment |
|
Discussed ESG Technology Integration
Experiment (TIE) with ONA grand experiment |
|
Opportunity to connect Tactical/Low
level Operational with Strategic/High level Operational focus of ONA. |
|
Need to develop operational thread that
can be pursued. |
|
FY 03 (in some cases start sooner) |
|
COAST Plan of Action evaluation |
|
DRC Lessons Learned and Task List
markup extended to land target markup (near term tie to ESG discussed but not
defined) |
|
Lockheed Martin Fusion |
|
Northeast University Fusion work |
|
BBN creating a DAML ESG mail list to
further explore DAML ESG potential |
|
|
|
Rational Rose model (several .mdl
files) obtained from DDB |
|
Lewis Hart, GRCI, ran the .mdl through
in-house version (soon to be released DUET 0.2). Resulting DAML
ontologies included attributes as DAML datatype properties, but types were
off. Rose types are arbitrary text strings, and DDB had used C++
typedefs rather than primitive types (e.g. Float8 rather than double).
Knowing that, shouldn't be hard to manually massage the .mdl and/or .daml
files. DDB model was a good test case |
|
Assessment indicates it seems focused
on numeric fusion. It has a SIGINTSensor class (which Mike Dean used
CoABS PI Meeting demo), but not many other sensor types. A useful
start, need to extend it significantly for EEE. |
|
Materials available at http://www.daml.org/2001/12/ddb/ |
|
Next logical step: to generate Java
classes or use the DDB DAML ontology from Java/JINI/CoABS Grid |
|
Will propose to use to seed the
developers in ESG at joint ESG Enabling Experiments/Semantic Web for the
Military Users/Grid Military Users Group meeting in March 2002 |
|
|
|
|
Four potential areas were identified: |
|
1.
ONA - incorporate Navy Lessons Learned into the DAML experiment to
retrieve lessons learned based on type of operation, geographic area, and
type of equipment/platform. |
|
2.
COAST - incorporate into ESG threads to support course of action
decisions. Two areas that look ripe
for 1st action are where to deploy sensors and what type of
sensors to deploy. Does it make sense
to incorporate SANDPIPER as an interface between sensors and COAST as a
translator of ontologies? |
|
3.
DAML-ize Sensors - apply DAML to the DDB/AIM work. The first cut is complete, but additional
effort may be required to add information to the data. Also need to extend other sensor
types. Maybe we can do something with
straight ELINT vice SEI. |
|
4.
DAML-ize Navy Lessons Learned - Anteon has done a good job of XML mark
up of NLL. This is about 60% of the
effort required to reach a DAML-ized mark up. Need to complete characterization by geographic area, type of
operation, and type of equipment. |
|
Other areas not discussed that may be
of interest: |
|
1.
The Teknowledge work with Power Point and MS Word. |
|
2.
Tools such as Haircut and RuleML |
|
3.
Capabilities developed for Horus that might be applied to data
retrieval from INTEL data bases to support plan development. |