Ontology for the Intelligence Community: Difference between revisions

From NCOR Wiki
Jump to navigationJump to search
mNo edit summary
mNo edit summary
Line 28: Line 28:
Ontology and military doctrine  
Ontology and military doctrine  
A repeatable process for creating ontologies
A repeatable process for creating ontologies
Annotations of data headings vs. Annotations of data column content
1. One big chunk of the agenda for the training event, I think, should
be devoted to ontology building, by analogy with our work with Bill in
Buffalo on creating the FacialFeature ontology.
We could choose 2 or 3 similar topics, and work with the people in the
room on building ontologies for each. In this way, they learn what is
involved, and we all end up with more ontology content to work with in
the future.
2. There seemed to be an interest in the topic of ontology
coordination, which we got to at the end of the last training event. I
think we should push this further by working out exactly what ontology
content we need to build, and how a division of labor would work.
3. The idea of ontology views (ontodog, idiosyncratic terms ...) and
of the relation between ontology and data should be pushed further --
(a) to educate the participants, (b) to get clearer about what we need
to do to address their needs. I am still working on a text for the SE
- Methodology document on these matters.
4. BFO, showing especially how BFO can help with item 2.
5. Relations to NIEM, JC3IEDM, (global graph?)
6. MIOF
7. Ontologies of data (-types) vs. ontologies of real world content
survey of video ontologies

Revision as of 16:12, 27 March 2012

Venue: Aberdeen Proving Ground, MD

Date:

Thursday, April 19, 2012
Friday, April 20, 2012

Draft Schedule April 19 9:00 What is ontology and what is it useful for?

Failures and successes of ontology technology
Semantic enhancement as a strategy for integration of military intelligence data

10:30 Break

10:45: Military intelligence: an overview of the domain from a data integration perspective

Types of data
Types of entity to which these data relate
Joint Intelligence Doctrine
The domain of military intelligence ontology

12:15 Lunch

13:00 A strategy to ensure consistency of data across multiple domains A repeatable process for creating ontologies The Semantic Enhancement approach

14:30 Ontology for the intelligence analysts (B. Mandrick) Ontology and military doctrine A repeatable process for creating ontologies

Annotations of data headings vs. Annotations of data column content

1. One big chunk of the agenda for the training event, I think, should be devoted to ontology building, by analogy with our work with Bill in Buffalo on creating the FacialFeature ontology. We could choose 2 or 3 similar topics, and work with the people in the room on building ontologies for each. In this way, they learn what is involved, and we all end up with more ontology content to work with in the future.

2. There seemed to be an interest in the topic of ontology coordination, which we got to at the end of the last training event. I think we should push this further by working out exactly what ontology content we need to build, and how a division of labor would work.

3. The idea of ontology views (ontodog, idiosyncratic terms ...) and of the relation between ontology and data should be pushed further -- (a) to educate the participants, (b) to get clearer about what we need to do to address their needs. I am still working on a text for the SE - Methodology document on these matters.

4. BFO, showing especially how BFO can help with item 2.

5. Relations to NIEM, JC3IEDM, (global graph?) 6. MIOF 7. Ontologies of data (-types) vs. ontologies of real world content survey of video ontologies