Transcript Proposal Briefing

maXML Pilot Project
Ljubljana, Slovenia, June 9, 2003
Since we last met…

Major Revisions to the Schema
–
–
–
–

Developed Alpha version of maXML Workbench
–
–
–

Developed functional Runtime front end
Integrated Design Time (XAware) with Runtime
Developed integration/platform plans
Developed mappings for IMSMA data
–
–
–
–
–

Removed reference to name spaces
Consolidated to 1 file for easier use
Added Technical Survey Artifact
Many small changes based on mappings
Accidents/Incidents
Mined Areas (Minefield, Mined Area, Dangerous Area)
Victims/Casualties
Technical Survey
Impact Survey
Developed Initial Mappings for BHMAC
–
–
–
–
Minefields
Clearance Areas
Victims
Incidents
Design Time

Technology:
–
–
–
–
–
XAware (http://www.xaware.com)
Windows or J2EE technology
Works on the “web”
Uses SQL and direct database connection to select data to export
Combines easy SQL with easy to use transformation scripts
(Javascript)

Users: DBA or system administrator

Purpose: Create a set of transformation rules to generate
maXML
Design Time Process
Design Time

Terminology:
– BizDocument: A set of rules for creating an XML document from
a database (based on Artifacts)
– BizComponent: A rule (in a BizDocument) that specifies
mappings and/or transformations of specific data elements
– BizDriver: A connection to a relational database.
– Data Transformation Rule (DXR): A business logic rule that
transforms data from original format to maXML


e.g. VictimGender: M to <Gender>Male</Gender>
Demo
– Using IMSMA 3.0 database and sample data
Design Time Benefits

What you’ve got:
– Data transformation mapping,
– Published to a server,
– That when called, populates an XML document with data

Benefits:
– BizDocuments, BizComponents, DXRs are HIGHLY reusable


“compounding” benefit
Users start with BizDocuments, BizComponents, and DXRs.
– Users have a drag/drop interface + SQL.
– Managers get easy to use interface.
– Components can be stored on a server/website and shared.
Run Time

Technology:
– JSP/Cocoon
– Open source
– Works on the “web”

Users: DBA or MAC Info Manager

Purpose:
– Create an maXML document from database
– Validate document
– Select a “View” for document

Process:
–
–
–
–
User starts with the BizDocument created in Design Time
Supplies a few parameters via GUI
Creates/validates document
Selects desired “view” and views document
Run Time
Run Time Benefits

Benefits of this approach
–
–
–
–
–
–
–
One front end ties everything together
Can select any BizDocument to start
Can supply pre-cooked or on-the-fly parameters to filter data
Can view data before sending it out.
Can select from any views (or roll your own)
Managers get easy to use interface.
Components (views, etc) can be stored on a server/website and
shared.
– Deployment is cheap and can go on nearly any
server/workstaion
Plans

Focus on 3 major artifacts
–
–
–
–

Accident
Victim
Mine Action Area
Less important: Survey, Gazetteer
Views
– Will begin developing views soon (July)
– Will need input from this group

Schedule:
–
–
–
–
–
Complete Workbench Beta version – May
Complete draft mappings – June
Review mappings with managers – July
Revise – August
Begin Deployment – September/October