Joe Pantella

1
DDMS Change Requests

• Joe Pantella
• Architect
• 10-18-2006

2
Agenda

• The New DDMS Home Page
• Description of CRs
• Proposed Solutions
• Report of Technical Exchange Meeting with CR
  Stakeholders.

3
The New DDMS Home Page
4
Change Request 20061

• Problem
• Apache AXIS 1.4 SOAP Stack WSDL2JAVA tool fails
  to generate Java code that creates valid DDMS XML
  instances.
• Specifically the code generated by WSDL2Java
  generates keyword2 and category2 tags in the
  subjectCoverage field which are not defined in
  the DDMS XML Schema.

5
CR 20061 - Issue Example

• Valid DDMS XML
• ltddmsSubjectgt
• ltddmscategory ddmsqualifier"http//metadata.do
  d.mil/mdr/ns/TaxFG/0.75c/Core_Tax_0.75c.owlPoliti
  cal_event " ddmscode"Political_Event"
  ddmslabel"Political Event"/gt
• ltddmskeyword ddmsvalue"President Bush"/gt
• ltddmskeyword ddmsvalue"Prime Minister Khai"/gt
• lt/ddmsSubjectgt
• AXIS generated DDMS XML
• ltddmsSubjectgt
• ltddmscategory ddmsqualifier"http//metadata.do
  d.mil/mdr/ns/TaxFG/0.75c/Core_Tax_0.75c.owlPoliti
  cal_event " ddmscode"Political_Event"
  ddmslabel"Political Event"/gt
• ltddmscategory2 ? INVALID ddmsqualifier"http//m
  etadata.dod.mil/mdr/ns/TaxFG/0.75c/Core_Tax_0.75c.
  owlPolitical_event " ddmscode"Political_Event"
  ddmslabel"Political Event"/gt
• ltddmskeyword2 ddmsvalue"President Bush"/gt ?
  INVALID
• ltddmskeyword2 ddmsvalue"Prime Minister
  Khai"/gt ? INVALID
• lt/ddmsSubjectgt

6
CR 20061 Cause

• Technical Cause of Issue
• WSDL2Java appends numbers to accessor methods in
  element classes where multiple elements of the
  same name may appear.
• The use of Java reflection on the method names to
  determine element names in the XML instances
  sometimes results in inappropriate names for XML
  elements.
• The current model of the subject element in the
  DDMS XML Schema forces this bug to manifest
  itself.

7
CR 20061 Proposed Solution

• Remodel the subject element in such a way to
  preclude this bug from manifesting itself.
• Submit a bug to the Apache AXIS project.
  (Already completed. See http//issues.apache.org/j
  ira/browse/AXIS-2561)
• Document the solution and/or work around in
  additional documentation surrounding the DDMS XML
  Schema.

8
CR 20061 Proposed Solution

• Existing Model
• ltxscomplexType name"SubjectType"gt
• ltxssequencegt
• ltxschoice maxOccurs"unbounded"gt
• ltxselement ref"category"/gt
• ltxselement ref"keyword"/gt
• lt/xschoicegt
• ltxselement ref"category" minOccurs"0"
  maxOccurs"unbounded"/gt
• ltxselement ref"keyword" minOccurs"0"
  maxOccurs"unbounded"/gt
• lt/xssequencegt
• lt/xscomplexTypegt
• Proposed Model
• ltxscomplexType name"SubjectType"gt
• ltxschoice minOccurs1 maxOccurs3"gt ? for
  backwards compatibility
• ltxselement ref"category minOccurs1
  maxOccursunbounded/gt
• ltxselement ref"keyword minOccurs1
  maxOccursunbounded/gt

Addresses WSDL2Java issue.
Also a more elegant solution than the DDMS XML
Schema currently employs.
9
Change Request 20062

• Problem
• The DDMS 1.3 specification includes support for
  the GeospatialCoverage_attributeVocabularyDefinit
  ions.xsd (an ISO TC211 XML Schema for GML).
  This schema uses abstract complex types that are
  standards conformant, but not supported by the
  current MS Visual Studio environment for
  developing and hosting web services in a dotNet
  environment.

10
CR 20061 Proposed Solution

• Redesign the DDMS XML Schema geospatialCoverage
  element to eliminate reliance and use of ISO
  TC211 defined XML Schemas for Geographic Markup.
  
• Document a workaround for this issue until the
  tools are able to mature enough to handle these
  W3C XML Schema features.

OR
11
Report of CR Tech. Exchange Mtg.

• On September 20, 2006 a technical exchange
  meeting was convened with the CR submitters et
  al. to discuss options for dispensing of the CRs.
  
• Identified Core Issue
• Is the DoD prepared to allow the development
  status of open source and non-compliant albeit
  common tools to dictate how it models its data?
• Recommendation that the DDMS Core panel convene
  to discuss how to handle similar issues in the
  future.
• Primary actions
• Provide better documentation surrounding the DDMS
  XML Schema and related design decisions.
• Provide a simple statement of intent for the DDMS
  XML Schema.
• Identify and document options for working around
  current issues until tools can be matured and
  attain compliance with the standards.
• Identify tools that currently support the
  features used in the DDMS XML Schema.
• Minutes available on the DDMS Home Page
• http//metadata.dod.mil/mdr/irs/DDMS under
  Configuration Managment
• Ballots for voting on these CRs will be sent out
  to the DDMS Panel during the last week of
  October.

12
Questions
13
www.disa.mil