Embed Size (px)
DESCRIPTION
Agenda/Discussion Review/Edit Draft TOR –Revised draft to be presented to next JMSWG Review JMSWG Presentation –Exported TDS contents of 6011, 6016C, and 6017 to XML NATO DLWG Issues –“Provide a position on DLWG adoption of MILSTD 6017 as a NATO Standard” – okay, but US retains CM –US support for DLWG XML Syndicate and NATO Namespace Manager but not for developing XML products (because process for creating products not well defined) Review/Edit Draft TOR –Revised draft to be presented to next JMSWG Review JMSWG Presentation –Exported TDS contents of 6011, 6016C, and 6017 to XML NATO DLWG Issues –“Provide a position on DLWG adoption of MILSTD 6017 as a NATO Standard” – okay, but US retains CM –US support for DLWG XML Syndicate and NATO Namespace Manager but not for developing XML products (because process for creating products not well defined)
Citation preview
1
eXtensible Markup Language Implementation Management Subgroup(XML IMSG)
06-1
24 – 26 January 2006
Michael [email protected]
2
Purpose
The purpose of the XML-IMSG is to explore and advise the JMSWG in the application of XML technology to the TDL message standards. With a growing number of Net Centric and Network Enabled Capability initiatives that rely on XML and similar meta-data technologies, application in the world of TDL standards is inevitable. With the existing investment in TDL technology and the supporting information infrastructure, TDL data repositories (standards, data dictionaries, implementation data bases, etc.) should be leveraged to expand the XML data repositories in order to reach new, unanticipated consumers. The XML-IMSG will manage the development of new XML representations of TDL.
3
06-1 Agenda/Discussion
• Review/Edit Draft TOR– Revised draft to be presented to next JMSWG
• Review JMSWG Presentation– Exported TDS contents of 6011, 6016C, and 6017 to XML
• NATO DLWG Issues– “Provide a position on DLWG adoption of MILSTD 6017 as a NATO
Standard” – okay, but US retains CM– US support for DLWG XML Syndicate and NATO Namespace Manager
but not for developing XML products (because process for creating products not well defined)
4
06-1 Agenda/Discussion (continued)
• XML Prototype Development – DISA developed Java code to export TDS contents to XML– Marine Corps committed to producing VMF XML schemas from DISA’s
TDS XML export• XML Schema Validation – two issues
– Is this schema valid, i.e., comply with W3C content/format rules?– Does this schema accurately reflect the underlying standard?
5
VMF XML Way Ahead
• DISA Plan– Produce 6017 XML Extract from TDS (done)– Develop validation rules, requirements, process (not started)– Validate 6017 schemas (need validation rules) – dry run?– Publish MIL-STD-6017A – 31July 06– Produce, validate, and publish 6017A XML – date unknown
• Army Plan– Complete draft 6017A VID – end of April 06– Use Marine Corps process to generate draft 6017A XML– Distribute draft 6017A VID and non-validated XML - end of April 06
• Caveat– 6017A VID is unofficial draft – use at own risk– 6017A XML is unofficial draft – content and format likely to change; use
at own risk
