Last updated on 26th October 2007
© 2005-2007 MIP
You
are the visitor number
| Home | History | Organization | Documents | Contact |
Miscellaneous
You are at:
Best viewed at
1024 * 768
|
Configuration Control |
|
CP flow chart. |
|
MIP Glossary |
|
Some definitions.
|
|
Some acronyms.
|
|
Greding |
|
|
Any time that changing or updating a particular MIP document
is required, a CP must be issued, discussed and approved.
Baseline.
Site Map
|
|
|
|
|
|
|
|
 |
|
|
|
Download here |
|
Contact the |
| Webmaster |
MIP is looking for new ideas and XML may be a good one!
This site provides various resources for system and web service developers interested in Extensible Markup Language (XML) implementations of the MIP's Information Exchange Data Model (IEDM).
MIP, as the authoritative source for the C2IEDM and JC3IEDM, has developed reference C2IEDM and JC3IEDM Schema (XSD) and associated tools to assist developers. Design rationale and examples for MIP IEDM reference XML schema are contained in JC3IEDM documentation, Annex O.
This site documents the open source efforts of the MIP XML working party (WP), a continuing activity to develop XML capabilities based on the MIP IEDM.
XML Namespace
and Schema Definition.
XML Use Cases and Schema Requirements.
MIP XML, Open Source
Capabilities.
An XML namespace is a W3C standard for providing uniquely named elements and attributes that express a specific community vocabulary.
Complete interoperability only occurs when communities share a common set of concepts, terms, semantics and business rules. The MIP IEDM captures technical specifications for multinational joint consultation, command and control (JC3) concepts, terms, and semantics. The MIP IEDM can be used to generate XML reference schemas for a MIP namespace. The JC3IEDM Annex O defines some initial useful design patterns and associated XSD for different purposes, e.g. relational database processing and object-oriented web services. Links to the draft MIP IEDM reference schemas are shown below.
Based on the collaborative work of MIP and NDAG, NATO will host and manage an XML namespace for the MIP IEDM.
Multiple alternative MIP IEDM XSDs can be defined based on user/system/service requirements. While these schemas may differ in syntax they must be equivalent in terms of the concepts and semantics they convey. For example, object-oriented and entity-relationship style XSD have been defined to support different XML use cases. The Working Party will develop in the future mediation services to convert instance XML documents from one schema pattern to another.
The following six base types of XML use cases, classified into data exchange and transformation services, are identified in JC3IEDM version 3.0 Annex O:
Data exchange:
Web services/object-oriented (WS/OO)
Relational data base management systems (RDBMS) (exchange with
non-MIP data base)
MIP XML exchange mechanism (XEM XML PDU)
Transformation services:
Tactical Communication Interface mediation services, e.g., TDL, ADatP-3 or USMTF
[mediation means that information is usually
lost]
Mediation between different semantically aligned systems (e.g.,
between versions of the MIP data model
Export to various output/presentation formats, e.g., STANAG
5500-conformant messages or HTML.
The MIP PMG established the MIP XML WP to help accelerate IEDM adoption and use of the MIP IEDM in XML-based services and applications. The XML WP is a voluntary collaborative effort to establish a set of useful shared XML baseline components, to include:
 |
RBMS. (XML download page) |
 8/DEC/06 |
|
|
|
WS/OO. (XML download page) |
8/DEC/06 |
*Download the files and decompress them to access the content.
These resources are beta versions and no assertion as to their completeness or suitability for specific use is currently made. While these resources may not be optimal for any specific national/project implementation it is believed that they will serve an educational purpose and be very useful to system and service implementers. In short it is expected that the XML WP efforts will broaden and quicken awareness and adoption of the MIP IEDM while lowering the cost of implementing capabilities compliant with the MIP solution semantics.
The MIP XML resources referenced by this page are provided under the terms of an open source license agreement.
The following partial list shows potential collaborative future efforts:
Support for communities of interest (COI).
Alternative XSD designs
XML Naming and
Design Rules:
MIP Evaluation of NATO Guidance
Business
Information Entity (business objects) XSD definition
capabilities and examples.
Methods to support business rule specification and checking.
Web Services Capabilities.
Schema driven automatic service generation.
Binary compression capabilities.
Within the MIP community feedback and direct collaboration is encouraged - in support of national interests and in accordance with national priorities.
The XML WP is interested in receiving external feedback from military systems developers, regardless of affiliated COI, interested in achieving semantic alignment with a multinational C2/C3 COI. Direct contributions to the XML WP efforts are encouraged, with the caveats that such contributions may not be proprietary or restricted in their use (i.e., can be distributed under the open source license agreement) and that the MIP will not make any endorsement of third party products.
Feedback should be addressed to: Erik Chaum, erik.chaum@DMSO.mil
Last Updated: 10 January 2007.
MIP is looking for
new ideas and XML may be a good one!
XML Namespace
and Schema Definition.
XML Use Cases and Schema Requirements.
MIP XML, Open Source
Capabilities.
Future
Efforts on XML.
Working Party Participation.
You are at:
Best
viewed at
1024 *
768
| Home | History | Organization | Documents | Contact |
| Miscellaneous |
Last updated on 26th
October 2007
© 2005-2007 MIP
You
are the visitor number