XML-Based Neutral Language for Data Display Systems

1. XML-Based Neutral Language for Data Display Systems John Hamilton Ron Fernandes Knowledge Based Systems, Inc. 112th RCC Telemetry Group Conference California, MD August 24th, 2005

2. Agenda • Background • Motivation • Data Display Markup Language (DDML) • Data Display Model Repository and Translator Framework (DDTF) • Applications • Conclusions

3. Background • Work based on a Phase I and II SBIR sponsored by Edwards Air Force Base • Technical POC: Dr. Charles Jones • Work with • China Lake / Lockheed Martin, Ridgecrest • NAWS, Pt. Mugu • Pax River Test Range Center • PM Utility Helicopter, U.S. Army • Sherrill-Lubinski Corp • Symvionics Corp. • Bruce Lipe, EAFB • Jon Morgan, EAFB • Project ends Nov 2006

4. Why Neutral Language? • Data display setup is a lengthy procedure • Diverse data display systems • Test and Evaluation (T&E) performed at different locations • Need reuse of displays for joint service T&E missions • Joint Strike Fighter (JSF) • Joint Air-to-Surface Standoff Missile (JASSM)

5. Vendor 6 Vendor 5 Vendor 1 Vendor 4 Vendor 2 Vendor 3 Why Neutral Language? • Currently, displays are created manually • Develop translators without neutral language

6. Vendor 5 Vendor 6 Vendor 1 Vendor 4 DDML Document Vendor 2 Vendor 3 Why Neutral Language? • Develop translators with neutral language

7. Data Display Markup Language • Based on eXtensible Markup Language (XML) • Four logical layers: graphics resources, dynamics, variables and data sources • Includes most T&E display objects • plotters, meters, strip charts, etc. • Primitive graphics resources based on Scalable Vector Graphics (SVG) • rectangles, lines, etc. • Generic to support nonstandard objects

8. Typical Software Layer (e.g., Model-View Architecture) DDML Layers Graphics Resources (position, color, etc.) Graphics Resources (controls, color, etc.) User Interfaces (rendering, display, etc.) Dynamics Information Management (objects, variables, etc.) Data variables and derived data Persistence (load, save, etc.) Data Sources Data Display Markup Language • Layers similar to typical software architecture

9. DDML Design • DDML is generic enough to support multiple data display systems, despite • Nomenclature differences across tools • Different functionality and focus for each system • Architectural differences and fuzzy specification of architectural layers • Nonstandard, tool-specific concepts

10. DDML Design artifacts • Data dictionary – Excel-based • Maps vendor objects to DDML elements and attributes • IDEF1X data model • Special mapping rules file • XMLSpy model • DTD and XML Schemas

11. DDML Data Dictionary • Dictionary of DDML terms and description • Includes corresponding terms in SL, IADS, DataViews, RangeView, GRIDS, etc. • Logically, each term is of the following four types • Element (document type definition [DTD] element) • Attribute (DTD attribute) • User-defined parameter • <param name=“xxx” value=“yy” type=“string”> • User-defined object type • <object name=“MySC” type=“Mike’s Meter”>

12. DDML Details • <model> contains all display objects on a given screen. • Standard display objects including • <stripchart> • <barchart> • <piechart> • <dial> • <slider> • Non-Standard/Custom objects • <object>

13. DDML Structure

14. DDML Support for Derived Data • Example 1: 3x2 - 2(sin y)2 <exp <exp coef=“3” power=“2” var_ref=“x” /> <exp coef=“-2” power=“2” oper=SIN var_ref=“y” /> </exp> • Example 2: 4x2 - 5(sin (y2 +z2) ) <exp <exp coef=“4” power=“2” var_ref=“x” /> <exp coef=“-5” power=“0.5” oper=SIN> <exp coef=“1” power=“2” var_ref=“y” /> <exp coef=“1” power=“2” var_ref=“y” /> </exp> </exp>

15. Symvionics’ IADS ILIAD / SL-GML DDML GE DataViews C / OpenGL RangeView GRIDS Example of using DDML • DDML serves as the interlingua

16. DDML Documentation • Translator development methodology is documented • Internal and external translators; • What’s common to both types • To be presented at ITC 2005 • DDML website maintenance • http://www.kbsi.com/DDML/DDML.htm

17. Mapping DDML to a new Target • Each tool/system must map its concept to that of DDML • Add display objects to data dictionary • Map objects to DDML objects • Define extra/special rules for mapping • Catalog non-standard display objects • Translator must encode these rules to read/write DDML • Internal Vs. External Translator

18. Data Display Translator Framework • DDML Model Repository with Translators

19. Data Display Translator Framework • Phase II: DDML Browser

20. Data Display Translator Framework • Phase II: DDML Query Tool

21. DDML Benefits • Supports interoperability of display systems • Same look and feel across environments and test centers • Vendor-independent way of cataloging display information • Can be used in various environments • T&E missions • Industrial process control • Cockpit and automobile dashboards • Health monitoring: man and machine

22. Conclusions • DDML is a generic XML-based neutral language for data display applications • DDML has been tested to support at least three vendor-specific formats • DDTF provided integrated framework for future translators • DDML and DDTF have applications beyond T&E

23. Points of Contact • Dr. Charles Jones, AFFTC, EAFB • charles.jones@edwards.af.mil • Mike Graul, KBSI • Mgraul@kbsi.com • John Hamilton, KBSI • JLHamilton@kbsi.com • Ronald Fernandes, KBSI • Rfernandes@kbsi.com