1 |
An Approach Using MIP Products for the Development of the Coalition Battle Management Language Standard
|
|
|
|
In: DTIC (2013)
|
|
BASE
|
|
Show details
|
|
3 |
KEYNOTE 2 : Rebuilding the Tower of Babel - Better Communication with Standards
|
|
|
|
In: DTIC (2013)
|
|
BASE
|
|
Show details
|
|
4 |
Making Semantic Information Work Effectively for Degraded Environments
|
|
|
|
In: DTIC (2013)
|
|
BASE
|
|
Show details
|
|
6 |
Applying A Formal Language of Command and Control For Interoperability Between Systems
|
|
|
|
In: DTIC (2008)
|
|
BASE
|
|
Show details
|
|
7 |
United States Air Force (USAF) Semantic Interoperability Capabilities Based Assessment and Technology Roadmap
|
|
|
|
In: DTIC (2007)
|
|
BASE
|
|
Show details
|
|
9 |
Toward a Standard Rule Language for Semantic Integration of the DoD Enterprise
|
|
|
|
In: DTIC (2006)
|
|
BASE
|
|
Show details
|
|
10 |
Adding Semantic Support to Existing UDDI Infrastructure
|
|
|
|
In: DTIC AND NTIS (2005)
|
|
BASE
|
|
Show details
|
|
11 |
Towards a Formal Ontology for Military Coalitions Operations
|
|
|
|
In: DTIC (2005)
|
|
BASE
|
|
Show details
|
|
12 |
Safe and Principled Language Interoperation
|
|
|
|
In: DTIC AND NTIS (2005)
|
|
BASE
|
|
Show details
|
|
13 |
Type-Directed Continuation Allocation
|
|
|
|
In: DTIC AND NTIS (2005)
|
|
BASE
|
|
Show details
|
|
14 |
Information Engineering in Support of Multilateral Joint Operational Interoperability
|
|
|
|
In: DTIC (2005)
|
|
Abstract:
In the information age era, there never has been a better time to reflect upon the fact that information in itself is something that has to be engineered. Since command and control is a cognitive process by which the commander gains situation awareness and proceeds to deliberated and co-ordinated action, one has to ask himself how raw data turns into actual information, and eventually knowledge that will trigger human understanding. Furthermore, the question arises as to how C4ISR system of systems can support this transformation process. Of course, this is no magic. Information systems do the only thing they are good at: Working on large amounts of data at incredible speed. This is where the human fails. However, data must be aggregated in such a way that it results in information that conveys operational meaning to the commander. This is where information technologies alone fail, miserably. The resulting information must capture the semantics of the commander's domain of interest, and this must exist prior the automated data transformation process. The exercise of capturing the semantics of a certain business domain (the nouns, verbs, adjectives, etc.) along with its usage guidance (business rules) can be referred to as information engineering or ontology engineering. Conducting information engineering activities comes in support of the definition of ontologies. By definition, an ontology is an explicit formal specification of how to represent the objects, concepts and other entities that are assumed to exist in some area of interest and the relationships that hold among them. Broadly speaking, interoperability can be achieved for systems that sit on top of a single common ontology, or for systems that sit on top of distinct ontologies provided with a means of translation between the crossing domains. ; Presented at the Meeting on Coalition C4ISR Architectures and Information Exchange Capabilities (Les architectures C4ISR et les capacites d'echange d'information en coalition), held in The Hague, The Netherlands, on 27-28 Sep 2004. Published in the Proceedings of the Meeting, p18-1 through 18-8, 2004. Document includes briefing charts in addition to text. See also ADM202135, RTO-MP-IST-042. The original document contains color images.
|
|
Keyword:
*C4ISR(COMMAND-CONTROL-COMMUNICATIONS-INTEL-SURVEIL-RECONN); *ENGINEERING; *INFORMATION SYSTEMS; *INTEROPERABILITY; *JOINT MILITARY ACTIVITIES; CANADA; Command; COMMAND AND CONTROL SYSTEMS; Control and Communications Systems; FOREIGN REPORTS; INFORMATION EXCHANGE; NATO FURNISHED; ONTOLOGY; SITUATIONAL AWARENESS; SYMPOSIA
|
|
URL: http://oai.dtic.mil/oai/oai?&verb=getRecord&metadataPrefix=html&identifier=ADA469717 http://www.dtic.mil/docs/citations/ADA469717
|
|
BASE
|
|
Hide details
|
|
15 |
Integrated DoD/C4ISR Architectures: It's not About the Framework.
|
|
|
|
In: DTIC (2004)
|
|
BASE
|
|
Show details
|
|
16 |
Implications of Multilingual Interoperability of Speech Technology for Military Use (Les implications de l'interoperabilite multilingue des technologies vocales pour applications militaires)
|
|
|
|
In: DTIC AND NTIS (2004)
|
|
BASE
|
|
Show details
|
|
17 |
Implications of Multilingual Interoperability of Speech Technology for Military Use (Les implications de l'interoperabilite multilingue des technologies vocales pour applications militaires) (CD-ROM)
|
|
In: DTIC (2004)
|
|
BASE
|
|
Show details
|
|
18 |
Information Engineering in Support of Multilateral Joint Operational Interoperability
|
|
|
|
In: DTIC (2004)
|
|
BASE
|
|
Show details
|
|
19 |
The Benefit of Ontologies for Interoperability of CCIS. (Easy, Quick and Cheap Solutions are Impossible, if Semantics of CCIS are Affected.)
|
|
|
|
In: DTIC (2003)
|
|
BASE
|
|
Show details
|
|
20 |
Semantic Interoperability in AD Hoc Wireless Networks
|
|
|
|
In: DTIC AND NTIS (2001)
|
|
BASE
|
|
Show details
|
|
|
|