CIQ Address Levels

1
(No Transcript)
2
(No Transcript)
3
(No Transcript)
4
Address Use Level Defined(US Postal model
example)

• Level 0 handwritten postal address machine
  parsed
• Level 1 last line - city, state, zip (postal
  code) or foreign country
• Level 2 in country simple postal address
  concatenated delivery address line(s)
• Level 3 extended postal address advanced
  features
• 3A Non-address - business volume (bulk)
• 3B delivery address field s (atomic)
• Level 4 Rendering only - external or business
  to business use, e.g., shipping / delivery/bill
  to/marked for/in care of
• Level 5 management advanced features
• 5A internal management
• 5B international management

5
(No Transcript)
6
(No Transcript)
7
(No Transcript)
8
(No Transcript)
9
Building the right pieces

• Need to intelligently use XML get maximum
  benefit, while avoiding potential pitfalls.
• Exploit work that others have done pathfinder
  for OAGIS V8 use of Schema techniques and
  best-practices on XML use
• Align with ebXML architecture to provide syntax
  neutral methods wherever possible

10
Leveraging CIQ

• Need to reflect levels 1 thru 5 of use
• CIQ formal detail underpins 5th level.
• Use XML schema techniques to layer granularity
  above that.
• Each granular layer also has country specific
  models.
• Use ebXML AssemblyDoc to capture context
  structure rules and country models.

11
(No Transcript)
12
(No Transcript)
13
(No Transcript)
14
XML techniques summary

• We can use W3C Schema to show basic typing and
  structural permutations for all address content,
  matching the 5 levels of the business model.
• To provide automation of the business logic
  at-point-of-use requires ebXML and AssemblyDocs
  to supplement the Schema.
• This gives us short-term implementation today,
  with long-term extensibility and improvement of
  business value and information quality.

15
(No Transcript)
16
Postal Address Conclusions

• Support Address Use Levels 1 - 5
• Support Delivery Quality Metrics
• Make use of Schema in near term
• Define Postal Address using both Global
  complexType and Global Element Definitions
• Harmonize USPS ECCMA approach with CIQ (xAL),
  HR-XML, postal address
• Support Dual Resolution (concatenated and detail)
• Align defined detailed elements (include mapping
  to concatenated)
• Establish UID-identified elements to support
  AssemblyDoc mapping to registry
• Define code lists to support rendering
  requirement
• Establish legacy environment compatibility (EDI
  X12 for DOD)

17
(No Transcript)