DNI/DoD Joint Data Technical Working Group

1. Dr Glenda Hayes/MITRE PEO-GES Data Services 13 Jul 2010 DNI/DoD Joint Data Technical Working Group

2. Agenda Purpose Background Context Process Criteria and Definitions JDTWG Recommendations  Emergency Triage Next Steps

3. Purpose • Discuss the establishment of a DoD and DNI Joint Data Technical Working Group (JDTWG) responsible for: • Vetting and recommending data standards to the DoD Information Technology Standards Registry (DISR) and Intelligence Community Standards Registry (ICSR) Joint Secretariat for inclusion in the respective registries

4. IT Standards IT Data Standard Standards Hierarchy (Taxonomy) IT Technical Standard Specification Only Abstract Data Standard Specification Technical Data Standard Schema Testable Mechanism Non-IT Standard

5. Background • ITSC Chair Memo, 20 May 2010 • Subject: Data Standards and DISR - Involvement with Joint Data Technical Working Group (JDTWG) • Inbound standards for DISR/ICSR consideration come in a wide array and range of data artifacts • With the advent of new IC data standards requirements, we have taxed the subject matter expertise in the standing DISR/ICSR TWGs • DISR/ICSR Secretariat can draw upon subject matter expertise within the DoD Metadata Working Group and the IC Data Standards Coordination Activity • Final set of data definitions, criteria, and process in an improved revision to the DISR/ICSR Standard Operating Procedures within 30 days

6. DoD Metadata MgmtEngineering-level Processes Namespace Managers & WGs Namespace Managers & WGs DISA Data Services Office Namespace Managers & WGs Governs/Coordinates Within Namespace Operates, Maintains Data Services Environment (nee DoD Metadata Registry) Hosts Participates in Consults, Subscribes to & Submits to/Downloads from Metadata Registry Discusses Participates in DoD Metadata WG DOD Developer • DoD MDR Focus Group • DDMS Focus Group • DNI/DoD Joint Data TWG

7. (Current) Definition • Data Standard • A data standard is an established structured representation for data exchange. It is documented by a specification for an explicit set of requirements and may have associated XML artifacts (e.g., schema, OWL, schematron, stylesheet). Data standards containing one or more associated XML artifacts are designated technical data standards (e.g., JPEG, MPEG, NITF, DDMS, UCORE ). Data standards not containing eXtensible Markup Language (XML) artifacts are designated abstract data standards. • SOURCE: DoD Standard Operating Procedures for the Information Technology Standards Committee (ITSC), Technical Working Groups (TWGs), and Focus Groups (FGs), 28 July 2009 XML artifact = No Data Standard = Yes

8. (Proposed) Definition • Data Standard • a common meaning and representation for a concept or information exchange that has been proposed by an authoritative body, in accordance with procedures established by the ITSC. • A data standard is intended to improve understanding and data interoperability by reducing ambiguity and the necessity for mediation . • An abstract data standard contains a narrative specification. • A technical data standard additionally includes the complementary data engineering components or test criteria that can be used to guide system development and to test conformance. If the exchange will be encoded in XML, conformance may be assessed by the adherence of exchange examples to the rules encoded in an XML schema or schematron document. If the exchange will not be encoded in XML (e.g., JPEG, MPEG), conformance may be assessed by adherence to readily available and/or network test sites.

9. User Initial Decision Process Flow User identifies a Candidate Data Standard Is there an associated XML artifact Is the XML artifact in the MDR Submit citation via CR to DISR Yes Yes A No No Submit citation via CR to DISR Follow MDR’s Registration Process A Submit citation via CR to DISR A

10. Data Standard’s Process Flow Candidate Standard Process Flow A Yes DISR ITSC Org Rep Approve Secretariat Review Process ITSC Org Rep Review Yes No ISOP Approve No Authoritative Body Not Accepted Yes Authoritative Body SDO SSO DSP DoDMWG No No ITSC Approve Yes Is there an associated XML artifact No Yes CR not included in DISR JDTWG Recommend approval No JDTWG Review And Process CR Secretariat Release to JDTWG Yes Is the XML artifact in the MDR No Yes

11. Data Standard’s Process Flow Joint Data TWG Responsibilities A Yes DISR ITSC Org Rep Approve Secretariat Review Process ITSC Org Rep Review Yes No ISOP Approve No Authoritative Body Not Accepted Yes Authoritative Body SDO SSO DSP DoD MWG No No ITSC Approve Yes Is there an associated XML artifact No Yes CR not included in DISR JDTWG Recommend approval No JDTWG Review And Process CR Secretariat Release to JDTWG Yes Is the XML artifact in the MDR No Yes

12. Process • DISR/ICSR Joint Secretariat will continue to oversee Change Request (CR) submission accuracy and compliance • When questions of data standard appropriateness, technical maturity, and CM principles arise, the JDTWG will be asked to engage • DISR/ICSR Joint Secretariat will be the gatekeeper associated with CR accuracy and completeness • JDTWG will be the gatekeeper for review of data standard selection and readiness • Procedures • The JDTWG will meet a minimum of three times per calendar year • Meetings will follow a published agenda prepared and distributed by the DoD and IC co-chairs • The co-chairs or any core member may request additional meetings as appropriate • JDTWG Composition • Members of the DoD Metadata Working Group • Members of the IC Data Coordination Activity • Other interested parties approved by the DISR/ICSR Joint Secretariat

13. Criteria for a Data Specification Inclusion in DISR (1/2) • Must be representative of an implementation convention to define, organize, interpret or exchange data • Must be accompanied by amplifying documentation (e.g. Technical Specification, Profile, Model, Business Rules, etc.) • For consideration as a standard within the DISR, must be submitted as a change request (CR) with a clearly defined applicability statement • Must be produced by an authoritative body • Authoritative Body is a joint body that contains more than one COCOM, Service or Agency as stakeholders, and is a recognized, sustainable organization • Defined governance body (e.g., Technical Management Board, Technical Committee, IT Portfolio Manager, Enterprise Services Engineering Review Group, etc.) • Must be published, non-proprietary, versioned, available and maintained under a mature configuration management process

14. Criteria for a Data Specification Inclusion in DISR (2/2) • Where applicable, complementary visibility in DoD Metadata Registry (MDR) • DoD MDR provides the authoritative process for configuration management (CM) of XML schemas, DB schemas, and other machine-readable data engineering artifacts • Data engineering citations will be published in the DISR • Must be composed as a reusable data artifact. Preference is for artifacts applicable to multiple products, systems, or capabilities, not single-use. • Proposed standard must not create a conflict within the DISR • Any standards proposed that may result in a conflict will be coordinated with the appropriative authoritative bodies for resolution

15. Characteristics of a Well-behaved Authoritative Body (1/2) • Sustainable Organization to meet scope of capability being addressed • Persistent Organization possessing financial resources and budget authority • Persistent Technical and Subject Matter Expertise • Transparent decision making process • Documented and visible charter and voting process (e.g., posted to DKO) • Stakeholders’ voting record and adjudication actions are documented and visible (e.g., wiki or DISRonline voting tool) • Well-defined, rigorous configuration management process • Clearly defined artifacts being managed • Documented process for adding and removing participants

16. Characteristics of a Well-behaved Authoritative Body (2/2) • Activities that are coalition related must process guidance packages for C/S/A vetting in accordance with the Joint Staff J65C process • Need to cite Joint Staff Instruction CJCSI 6010.01D (series), Subject: Coordination of United States Command, Control, Communication, and Computer Systems Positions in International Forums, dated 15 Dec 2007 • A demonstrated culture of supporting peer-to-peer social networking/collaboration on areas of common interest • Active participation in DoD MWG for data related activities

17. JDTWG Recommendations for Current Candidate Standards Emergency Triage Needed

18. Next Steps Review proposed Joint Data TWG terminology and processes Draft the Joint Data TWG charter Draft SOP Introduce at the 13 July DoD MWG Coordinate with ITSC

19. www.disa.mil