DoD XML Registry Status

1
DoD XML RegistryStatus

• Dr. Glenda Hayes, MITRE
• Presentation to Federal CIO XML WG
• 20 Mar 2002

2
Agenda

• Current Status
• DoD XML Registry
• COE XML Guidance Proposed for DoD Adoption
• Next Steps
• Convergence Task Force
• Create Reusable Domain Schemas
• Participate in NIST Registry Proof of Concept

3
DoD XML Registryhttp//diides.ncr.disa.mil/xmlreg

• One Stop Publish Subscribe for Defense
  Metadata
• IOC May 99
• COI Creation Management
• Public Access via WWW plus
• Password protected instance
• SIPRNET instance shortly

Market-driven Approach to XML Mgmt
4
DoD XML Registry Features

• Search/Browse Filters
• Across or within namespaces
• By Substring in Name, Definition, Comment
• On Information Resource Type, Submitter, Status,
  Version, Domain Value, Date Range
• Navigate relationships among resources
• New Information Resource Type Schema Data Type
• On-Line Submission Pkg Verification Submission
• Manifest Schema uses W3C XML Schema
  Recommendation
• Password Protected Areas
• On-Line Registry Administrative Features
• Status changes (finer granularity)
• Status reports for Namespace Mgrs
• General/Overall Services
• Server-side certificate (DoD generated)

5
DoD XML RegistryCommunities of Interest

• Other Proposed
• NBC
• Architecture
• E-Business
• MASINT
• Document
• Training

6
DoD XML Registry Current Inventory

• Documents - 631
• Domain Value - 774
• Submission Packages - 49
• XML Attribute - 981
• XML Element - 14700
• XML Sample - 21
• Schema - 89
• Schema Data Type - 16
• Stylesheets - 4

Current As of 15 Mar
Includes Password-protected portions
7
DoD Data EmporiumCustomer Service Transactions

• 01 Emporium hits approx 24K (100/day)
• XML Registry 50-plus/day
• Other Emporium pages approx 50/day
• Re-use of XML
• Army Intelligence Data Integration
• GCCS-I3 XML Target Folders
• Time Critical Targeting to use Wx and GMI XML
• Database Segment Re-use
• GMIDB for I3 data replication
• Clearinghouse Function
• 25 - 30 QA transactions/mo
• Initial Convergence Task Force
• Logistics/DFAS lead Alcon to agree on Postal
  Address
• Proposed Conventions and Normative Schemas

8
XML Registration Rules

• XML Component Registration
• Consult Registry before creating new components
  and reuse existing XML where practical
• Indicate planned use of XML components by
  formally subscribing to them
• Register additional XML or recommend
  modifications
• Community of Interest Namespace Formation
• Formed as required when someone will agree to
  manage
• Requirements for new Namespaces staffed with
• Existing Namespace Managers
• Senior Service/Agency engineers
• Flag Level Review Board

COE Process proposed for DoD Adoption
9
DoD XML Registration Policy Coordination

• DoD CIO EB Actions
• CRCB directs Chief Engineer to propose COE XML
  process for DoD
• Chief Engineer briefs DoD CIO Executive Board
  (EB) 29 Aug 2000
• CIO EB asks for
• Draft registration Policy memo
• Draft implementation plan
• Resource assessment
• Staff through ASD C3I, USD ATL, etc.
• Implementation Plan
• Version 6f Comments Received and Reviewed
• Version 7 to ASD/C3I 16 Jul 2001
• Version 8 of Implementation Plan, Version 3 of
  Policy being drafted by ASD-C3I Name Change
  Request DOD XML Registry
• Brief to CIO EB for decision (To Be Determined)
• Federal CIO Actions
• Coordination with Federal CIO
• Request to re-brief xml.gov
• Participate in NIST Registry Proof of Concept

10
Analyzing the Build-Time Market

• Emporium support for Market Analysis
• ID of duplicate or overlapping terms, concepts
  etc.
• Metadata Component page visits, downloads and
  subscriptions
• ID and mission of users
• Compliance levels

Lat Long
Data Emporium
ENT
?
Lat Long
Lat Long
Lat Long
Lat Long
Lat Long
AOP
GOP
TAR
GEO
GMI
MET
PER
FIN
Exploit Observed Commonality!
provides technical bases for both to be and
transformations to handle legacy
11
Convergence Task ForceDelivery Address
12
Common Domains

• High probability that developers (or SMEs) will
• Re-invent the domain
• Re-invent the XML representation for the domain
• Need to use the same domain for multiple roles
• Not know the original source for the domain
• Thereby introduce deviations, increasing
  synchronization cost over time
• Re-invent transformations between standards for
  the domain
• Balk at some prescribed element names
• Reference Sets Experience Developers will reuse
  if
• Easy to find
• Easy to use
• Not overly constraining

13
Reusable Data Components Reference Sets
CREATE TABLE COUNTRY (CTRY_CD CHAR(2) NOT
NULL, CTRY_NM VARCHAR(50) NOT NULL PRIMARY
KEY (CY_CD)) CREATE UNIQUE INDEX XPKCOUNTRY
ON COUNTRY ( CTRY_CD ASC)
Ref Data Sets by Functional Area
14
Adoption of Common Data Types

• Data types are domains for data validation
• Range limits
• Enumeration
• Patterns
• Elements provide role/context for a data type
• Elements are reusable, Data types are reusable
• Common data types constrain variability, with
  less impact on programs than common element names
• Explicit Data types are represented in XML
  schemas as simpleType or complexType
• DOD XML Registry for Transform Specifications
• Function/Rule-based (e.g., English-to-Metric)
• Association/Cross Reference (e.g., FIPS-to-ISO)

ltxsdelement nameAllegiance" typeFIPS10-4Count
ryCodeType"gt
15
Composable Interfaces
GMIMIDBAddlAllegianceCodeType
Union of Domains
COEFIPS10-4CountryCodeType
COECOPCountryCodeType
COEExerciseCountryCodeType
COETarget
COEUnitOfMeasureCodeType
GMIDatumType
Target.xml
Legend ? Normative Schema ? Notional
Schema ? Notional Instance
GEOGeospatialLocationType
16
Normative schemas for Some Common Data Types

• simpleType
• Unit of Measure
• Country Code
• FIPS 10-4 (2-character)
• ISO 3166 (2-character, 3-character, 3-number)
• complexType
• Geospatial Location (Latitude, Longitude, Datum)

Candidates for the Enterprise COI
17
FIPS10-4CountryCodeType Domain Source DOD Data
Emporium RefSet
lang tag
documentation
Tie-back version to XML Registry
Data Type, Data Size
XML Elements UpperCamelCase XML Attributes
lowerCamelCase Types UpperCamelCase Type
enumeration meaning
18
Registering Common XML Domains FIPS and ISO
Country Codes

• Both standards exist, neither can be ignored
• Challenge for interoperability
• Transforms needed

FIPS Qty 262
ISO Qty 239
Qty w/Same code 93
US
US
Qty not in FIPS 3
FX
Qty not in ISO 26
GZ
UM
IZ
TP
WE
IQ
Qty w/Different code 143
19
DISA Participation in NIST Registry Proof of
Concept

• DISA Role
• Advertise and link to DoD XML Registry
• Assess ebXML Registry Services
• Develop interoperability modalities among
  registries

ebXML Wrapper
ebXML-compliant Registry
DoD XML Registry
ebXML-compliant Registry
20
SHADE Next Steps

• SIPRNET copy of Registry
• Visibility for classified environment
• Registration Assistance
• Harvest Metadata from Operational Sources
• Convergence
• Identify Preferred Components
• Transform Components
• e.g., FIPS-to-ISO, Metric-to-English
• Registry API
• For Application-level Access to Metadata

21
Emporium Development Planadds progressively more
metadata galleries from various resources
Ontologies
DDA (Models)
Transformations
Other
Standard Data (DDDS)
EDI (X-12)
XML Reg v1
XML Reg v3
XML Reg v2
Emporium Baseline (Ref Sets v1)
DB Segs v0
DB Segs v1
Ref Tabs (Ref Sets v2)
EBXML
ISO 11179
Messages
Symbology
Emporium v0 (Federated Metadata Stores)
Emporium v1 (Common Metadata Store)
Emporium vX
Including valid values and identifiers
required for linking
22
(No Transcript)
23
Phase 3 Requirements

• Generate schema from registered components
• Impact analysis for status change
• De-register mechanism
• Measure use/re-use
• Add user-defined types for registration
• Registry API
• Subscription
• Info Desk with FAQ capability
• Compare/contrast assistance for Convergence
• Registry Replication
• Registry Submission Assistance
• Indent Namespaces within COIs
• Constrain Search (exact vs substring)
• Convert reference sets to domain value documents

24
DOD XML RegistryNext Steps
DOD
?
25
Convergence Task ForceRegistered address
components
26
Proposed COE Conventions

• Preference for W3C XML Schema Recommendation
• Use annotation/documentation for elements,
  attributes, types to provide documentation
• Use UpperCamelCase for elements, lowerCamelCase
  for attributes
• Use annotation/appinfo ltMeaninggt to provide
  meaning for enumeration values
• Use explicit Data Types rather than inline
  constraints
• Use UpperCamelCase for types and append Type to
  differentiate types from elements
• For aggregation tags, append List to element
  name
• Include xmllang tag within schema and xml
  instance where needed.
• Limit the use of generic tags (e.g., no item
  tag)
• Express tie-back to XML Registry