Copyright OASIS, 2005 / 2007 Scalable PESC transaction handling using OASIS CAM technology David Webber Chair OASIS CAM TC Presentation April 24 th, 2007 Washington DC CAM Technology Introduction

Background  The PESC is defining XSD schema for loan, transcript and more interactions.  Wide scale adoption brings with it challenges of versioning, consistency, rules, codelists, guidelines and contextual use patterns.  How does the OASIS CAM technology augment XSD structure definitions to provide scalable collaborative deployment support and smooth out potential disruptive adoption impacts?  How can a community of practice create a shared resource center to facilitate content interoperability?

Overview  Part 1 – Challenges and Needs (10 mins)  Registry - building a domain lexicon + PESC schema library  Versioning, consistency, rules, codelists, guidelines  Providing local contextual validation services  Relationship to XSD schemas  Deployment / Use Models  Part 2 – XML Technology (10 mins)  Introduction to OASIS CAM  Architecture Overview  Approach for PESC transactions  Part 3 – Demonstration (20 mins)  CAM tool overview  Solving agility – PESC XML examples  Value proposition  Call to action/next steps  Q&A (15 mins) Copyright OASIS, 2005 / 2007

Presentation April 24 th, 2007 Washington DC CHALLENGES AND NEEDS Part 1 Copyright OASIS, 2005 / 2007  Registry - building a domain lexicon + PESC schema library  Versioning, consistency, rules, codelists, guidelines  Providing local contextual validation services  Relationship to XSD schemas  Deployment / Use Models

Copyright OASIS, 2005 / 2007 Common Data Issues –  Secure Reliable Exchanges  Poor and Inconsistent Documentation  Data / Customer / Process Integration  Collaboration and Messaging  System Development Life Cycle  Change Management  Segregation of Duties  User Authentication Exchange & Information Technology

PESC Registry Overview ???????

Registry Core Components ???????

Component Associations ???????

Related Messages ???????

Solution / Problem Metrics  Can I create a standard simple open format to describe my message structures and data content rules?  Can my partners validate their transactions in test BEFORE they send them?  How do people know what I will send them?  I want something that’s simple and standards based – leverages existing XML components  Can I generate HTML documentation that is readable by business analysts? Copyright OASIS, 2005 / 2007

Why not use XSD?  Today’s XML schemas have complex structures with no context awareness + no cross field association rules + no dynamic lookups  The XSD provides a model of ALL possible structure instances – not the particular instance  Excessive use of namespaces make for fragile XML transaction handling  Generating valid sparse transaction layout is tough  Documentation diagrams hard to read  How to create simple re-usable templates? Copyright OASIS, 2005 / 2007

XSD - GPA model example

What about these needs?  Versioning  Content consistency  Use rules  Codelists  Associations (what uses which?)  Guidelines  Providing local contextual validation services

Typical Local Use Pattern Create Samples Rules Editor XML Analyst Templates Samples Develop Verify Structure Rules Context 3 2 Rules html XML Results html Publish 1 Detail Use Rules Test Rules on Samples 4 Share Results

Partner Conformance Test and Certification Validate Templates Report Partner Creates XML Results Test Pass / Fail Templates XML html Structure Rules Context Publish

Presentation April 24 th, 2007 Washington DC TECHNOLOGY Part 2 Copyright OASIS, 2005 / 2007  Introduction to OASIS CAM  Architecture Overview  Approach for PESC transactions

Copyright OASIS, 2005 / 2007 History and Status of CAM  OASIS technical committee  Five years of combined work in UN/CEFACT and OASIS  OASIS v1.1 committee specification  jCAM open source implementation in Java  Creating simple XML-scripted open standard mechanisms for XML transaction assembly and processing  Developing templates for common industry formats

Who is doing this?  Templates for OASIS UBL subset transactions  UK – BTplc – prototyping UBL telephone industry service provisioning  Online transaction validation test-bed  Transaction dictionaries and samples  MetLife - modified templates approach for ACORD  OVS - OASIS EML voting records templates  OASIS BPSS v2.0.4 now supports Context + CAM  Nortel – validate SOAP headers and SAML XML Copyright OASIS, 2005 / 2007

Copyright OASIS, 2005 / 2006 CAM Process Architecture CAMCAM XML Parser / DOM XML Parser / DOM Built-inFunctionsBuilt-inFunctions XPathhandlerXPathhandler SQLpersistenceSQLpersistence TermsRegistryTermsRegistry Rule Engine Post-Processing / Errors Post-Processing XML-awareXML-aware EXTENSIONS

Copyright OASIS, 2005 / 2006 jCAM Functional Components CAMCAM XML Parser / DOM XML Parser / DOM Built-inFunctionsBuilt-inFunctions XPathhandlerXPathhandler SQLpersistenceSQLpersistence TermsRegistryTermsRegistry Rule Engine EXTENSIONS jaxen xerces e.g. DROOLS, Others… Saxon - xslt planned using AJAX / ebXML Post-Processing / Errors Post-Processing XML Data Mapping XML-awareXML-aware cam XX

Deployment Options B2B Web services jCAM engine jCAM engine XML Templates XML Message System XML Java API Receive Process Validate Server Templates Request XML html Response Java API Process Structure Rules Context Standalone EDITOR Template XML html Report

Copyright OASIS, 2005 / 2006 Versioning Challenges  If the schema version changes – how to ensure it does not break our in place validations?  How to rapidly adapt to rule changes in a production environment?  How to develop user context driven deep version control and re-use of sub-components?  Enhance and automate Test release cycle by improving transparency for bug fix process and expose change deltas to speed testing process? Support for regression testing?

Overview of PESC needs Transaction Templates Structure Rules Context 3 2 Use Rules html XML Reports html Publish 1 Common Details Rules 4 Share Details Address Course Contact Student Loan Sponsor Transcript Content Rules Lookup Values Context Versioning

Presentation April 24 th, 2007 Washington DC DEMONSTRATION Part 3 Copyright OASIS, 2005 / 2007  Tools Overview  Solving agility – PESC XML example  Value proposition  Call to action/next steps

Copyright OASIS, 2005 / 2006 How does jCAM work?  CAM uses WYSIWYG approach to XML  Starting with your XML sample – creates structure template from that + default data content model  Next – add your structure use rules – optional / repeatable, date fields, allowed values, lookups  Then make context business rules – cross field use rules, exclude, include, variables  Save template – run against samples  Eclipse editor tool makes this all easy to do!  Deploy to production using jCAM processor

Eclipse CAM Editor Available structures Structure Rule Viewer Rule Details Results Viewer Validation Process

Copyright OASIS, 2005 / 2006 Using jCAM :  Start with sample XML  Use Eclipse template editor  Load XML, generate CAM  Enhance base template  Test, refine and deploy  Generate documentation  Deliver business solution Build Simple Build Simple Template Build Simple Build Simple Template Extending Template Extending Template Verify Results Verify Results Verify Results Verify Results Simple XML instance XML instance Simple XML instance XML instance Document Rule Details Rule Details Document Rule Details Rule Details

CAM Functions Summary excludeAttribute()startBlock()useElementByID()useAttribute() excludeElement()endBlock()useTreeByID()useChoice() excludeTree()checkCondition()setDefault()useElement() makeOptional()makeRecursive()restrictValuesByUID( ) useTree() makeMandatory()setUID()orderChildren()useAttributeByID() makeRepeatable()restrictValues()setRequired()useChoiceByID() setChoice() setId() setLength() setNumberRange() setLimit() setValue() setDateMask() setStringMask() setNumberMask() allowNulls() datatype() or setDataType() <as:constraint = “ action="restrictValues(//shipTo/state,'WA')"> <as:documentation type="documentation">Can only ship item to Washington State <as:constraint condition="$QuickBooks = true“ action="excludeElement(//Item/comment)" /> Example of Rules Use

Copyright OASIS, 2005 / 2006 Value Proposition  Making XML transaction handling simpler and predictable  Extends and clarifies your existing XSD schema structures  Quick and easy rule building from sample XML transaction  Enabling more robust fault tolerant processing + versioning  Providing open sharable templates and documentation  Re-use easier through support for includable components  Ability to integrate to business processes and context  Open source, open public standard toolkit – editor + engine

Copyright OASIS, 2005 / 2006 What’s Next / Call to Action  Develop template sets for PESC business domain  Integrate into your messaging exchanges  OrionSMG supports jCAM  Web service test-bed  Publish to registry to facilitate adoption  Create document templates to generate registry content / guidelines  Use Wiki / SourceForge to facilitate sharing

A Q & Q U E S T I O N S A N S W E R S

Copyright OASIS, 2005 / camprocessor.sourceforge.net Resources:

Copyright OASIS, 2005 / 2007 A special mention for our contributors to the CAM and jCAM work: UK - Martin Roberts with BTplc US - Sidhartha Nagolu from AC-Tech / NIH Credits: