 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| • |
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.
|
|
