MISMO Architecture - PowerPoint PPT Presentation

1 / 10
About This Presentation
Title:

MISMO Architecture

Description:

Version 3.x Justification. Assumption Quality Standards Product enhances Adoptability. ... Version 3.x Justification. W3C XML Schema is XML. Automated ... – PowerPoint PPT presentation

Number of Views:61
Avg rating:3.0/5.0
Slides: 11
Provided by: gregory150
Category:

less

Transcript and Presenter's Notes

Title: MISMO Architecture


1
MISMO Architecture
  • It is all about Adoption
  • Greg Alvord
  • Gallagher Financial Systems

2
Looking Back and Forward
  • Version 1.x -- One structure for all.
  • Version 2.x -- Structure for each built from
    common pool of fields ( attributes)
  • Version 3.x Pull what is shared together.

3
Version 2.x Product Process
  • Process Group
  • Selects fields from common pool.
  • Submits new fields to Core Data
  • Creates Structure DTD by hand (Usually)
  • Creates LDD by hand (Enter fields into MISMO
    Tool)
  • Core data reviews and approves (No inspection
    tools)
  • Architecture reviews and approves (No tools)

4
Version 3.x Justification
  • Assumption Quality Standards Product enhances
    Adoptability.
  • Escape the limitations of DTD
  • Reuse by cut and paste (error prone publications)
  • No formal link between LDD and DTD ( error prone
    publications)

5
Version 3.x Justification
  • W3C XML Schema is XML
  • Automated processes
  • Better tools available
  • Manipulated with XML tools.
  • XSD?XSLT?LDD HTML
  • Links Publication of structure and content

6
Version 3.x Justification
  • Better Extensibility
  • V 2.x Extensions Complex and therefore are under
    adopted

7
Schema Myths
  • Schema is complex (Wrong in our case!)
  • Our structures are simple
  • Now represented by DTD
  • Schema to represent these structures are simple.
  • Schema

8
Schema Myths
  • XML Files will get bigger (Wrong!)
  • DTD and XSD both describe the same thing.
  • Version 2 Schema and DTD both validate the SAME
    XML.

9
Version 3.x Steps
  • Make a schema representation for each LDD entry
    (Done)
  • Assign each LDD Entry a data type (Done,
    reviewing)
  • Pull Common fields together into Attribute
    Groups (In process)
  • Pull Common Structure together (In Process)
  • Construct 2.x transactions from these pieces.

10
Version 3.x Barriers to Adoption
  • Desire to do too much
  • Over use data types
  • Good data type use Date Formats
  • Bad data type use Punctuation, Field Length
  • Change attribute names
  • Smaller files
  • Huge implementation problem for 2.x and 3.x
    peaceful coexistence
Write a Comment
User Comments (0)
About PowerShow.com