OASIS CAM – Technology Introduction

1. OASIS CAM – Technology Introduction Business Rules Exchange Workgroup Call October 30th, 2007

2. OASIS CAM – Technology Introduction David Webber Chair OASIS CAM TC October, 2007 drrwebber@acm.org

3. Agenda • Today’s information integration needs • CAM technology approach • Demonstration • Illustrative examples • Summary / Next Steps

4. Agenda • Today’s information integration needs • CAM technology approach • Demonstration • Illustrative examples • Summary / Next Steps

5. Defining Information Services 1 XML Share Results XML Create Samples Publish Structure + Vocabulary Samples 4 2 Detail Use Rules Structure Rules Context Vocabulary Templates Analyst Rules Develop Rules + Context Templates html Enabling Agile Information Exchanges Test Rules on Samples 3 Rules Editor Results Verify Verify Template Outcomes html

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

7. What makes something Agile? • Re-usable methods that can be applied to many areas • Based on open standards and approach; not proprietary • Context and role driven and aware • This allows tailoring to specific profiles and use pattern templates dynamically • Self-adaptive • When requirements change can be adjusted on-the-fly in real time • Fault tolerant and not brittle • Ability to ignore non-critical interchange items and especially not to fail for trivial reasons or slight version nuances • Leveraging XML capabilities to make self-describing transactions possible rather than static fixed legacy exchanges • Able to support new uses without extensive re-programming • Usage patterns set via external configuration allowing broad but controlled uses

8. Facilitation Needs • For business communities: • Ability to create sharable templates for communities of practice that need consistent XML transaction handling definitions that are open and public. • For business data analysts: • Printable rule documentation support and features. • Example domain templates within communities of practice • Genericode codelists implementation. • For programmers: • XML content manipulation support and rules ( xslt, XPath …) • Web services and SOA support

9. Select your technology set • Many technologies are available, including application servers, distributed objects, and integration servers. Agile use of XML a prerequisite. • The choice of technology will likely be a mix of components that together meet your SOA needs. • Avoid vendor lock-in • Prefer Open Standards and Open Source solutions • Ensure proper use of layers to separate and manage complexity • Select simple components that integrate easily

10. Summary - Solution 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?

11. Agenda • Today’s information integration needs • CAM technology approach • Demonstration • Illustrative examples • Summary / Next Steps

12. History and Status of CAM work OASIS technical committee Five years of combined development in UN/CEFACT and OASIS OASIS v1.1 public standard and specification jCAM open source implementation in Java Creating simple XML-scripted open standard mechanisms for XML transaction assembly and processing Re-use: leverages XPath and xslt, and extends schematron approach Developing templates for common industry formats

13. 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 Generating valid sparse transaction layout is tough Documentation diagrams hard to read Excessive use of namespaces make for fragile XML transaction handling How to create simple re-usable templates?

14. XSD – PESC model example EVERYTHING is optional! So what do I REALLY send to you?

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

16. 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?

17. CAM Process Architecture XML Parser / DOM CAM XPath handler XML-aware Built-in Functions EXTENSIONS Rule Engine Post- Processing / Errors SQL persistence Terms Registry

18. jCAM Functional Components xerces XML Parser / DOM jaxen CAM XPath handler cam XML-aware Built-in Functions EXTENSIONS Rule Engine Post- Processing / Errors SQL persistence Terms Registry X planned using AJAX / ebXML e.g. JRules, Others… Saxon - xslt XML Data Mapping

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

20. Agenda • MISMO information integration needs • CAM technology approach • Demonstration • Illustrative examples • Summary / Next Steps

21. How does CAM 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

22. Eclipse CAM Editor Available structures 1 Rule Details 3 4 Validation Process 2 Structure Rule Viewer 5 Results Viewer

23. 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 1 Simple XML instance 2 Build Simple Template 3 Extending Template 4 Verify Results 5 Document Rule Details

24. Summary of CAM template features Ability to use <as:include> to modularize complex content Use of XPath references enables agile rule handling Full contextual support including variables, rules and context sections Code lists can be externally built and then referenced Extensions section provides customization options Integration with xslt provides extended results handling and error reporting capabilities Template representation model and XML enables extended post-processing and documentation options

25. CAM Functions Summary <as:BusinessUseContext> <as:Rules> <as:default> <as:context> <as:constraint action="makeRepeatable(//Items/Item)"/> <as:constraint action="makeOptional(//Item/comment)"/> <as:constraint action="setLength(//shipTo/state,2)"/> <as:constraint action="setDateMask(//PurchaseOrder/shipDate,YYYY-MM-DD)"/> <as:constraint action="makeOptional(//PurchaseOrder/comment)"/> <as:constraint action="restrictValues(//shipTo/@type,'US'| 'CA'| 'MX', 'US')"/> <as:constraint action="setDateMask(//PurchaseOrder/@orderDate,YYYY-MM-DD)"/> <as:constraint action="setNumberMask(//Item/@pno,###-###)"/> <as:constraint action="setNumberMask(//Item/quantity,###)"/> <as:constraint action="setNumberMask(//Item/price,####.##)"/> <as:constraint condition="//Item/@pno = 123-678“ action="restrictValues(//shipTo/state,'WA')"><as:annotation> <as:documentation type="documentation">Can only ship item 123-678 to Washington State </as:documentation></as:annotation> </as:constraint> <as:constraint condition="$QuickBooks = true“ action="excludeElement(//Item/comment)" /> </as:context> </as:default> </as:Rules> </as:BusinessUseContext> Example of Rules Use

26. Interactive Documentation (iDoc) CAM Template XSLT iDoc wiki HTML

27. Agenda • MISMO information integration needs • CAM technology approach • Demonstration • Illustrative examples • Summary / Next Steps

28. Conceptual View of MISMO transactions 1 XML Transaction Share Details Publish Common Details 4 Case Data Asset Rules Structure Rules Context 2 Templates Interviewer 3 Context Loan Product Use Rules Reports Purpose html Content Rules Terms html Lookup Values Transaction Borrower Versioning

29. MISMOCAMEclipseEditorSample

30. Illustrative MISMO requirements • When Loan Amount > 700,000 • Require LTV <= 90 • When Loan Amount > 1,000,000 • Require LTV <= 80 • AND CLTV <= 90 • When Documentation Type = Full AND Loan Purpose = Purchase AND Occupancy = Primary Residence • Require LTV <= 95 • AND CLTV <= 95 • Require Property State = CA

31. CAM rules syntax <as:BusinessUseContext> <as:Rules> <as:default> <as:context> <as:constraint condition="//Loan/Amount > 700000 and( //Loan/LTV > 90)" action="restrictValues(//Loan/LTV, ‘LTV must be less than or equal 90 for 700,000 loans') "/> <as:constraint action="restrictValues(//Property/State, 'CA')"/> </as:context> </as:default> </as:Rules> </as:BusinessUseContext>

32. Lookup Rule Tables (example #1)

33. Lookup Rule Tables (example #2)

34. Other Domain Examples UBL schema and CCTS Fannie Mae EDI-esque XML OASIS EML Grants.gov form based schema DOJ NIEM/LEX PESC Dictionary and schema • -Transactions replacing EDI • Overloaded reuse of structure components • Financial reporting data • Financial transaction data • Extended use of code sets to label transaction content / purpose -Developed by BAH and NG for form-based application submissions -Translate previous paper form into multiple schema sections -Massive schema with extended namespaces • Universal Business Language (UBL) • OASIS standard • Uses UML models and CCTS approach • Derived from xCBL and simplEDI approach • Supply chain schema with joint initiative EU / Asia / US -Developed by GTRI for DOJ community -Vocabulary based -LEXS schema built using NIEM vocabulary -Law enforcement and court applications • -Developed for Education Department • -form-style XML • -Older XSD techniques for simple flat schema model • No re-use of common structures • Student loans and transcripts • -Set of functional transactions and configuration templates for managing and processing elections • Common set of components and vocabulary • Widely differing use patterns and items by country localization

35. Agenda • MISMO information integration needs • CAM technology approach • Demonstration • Illustrative examples • Summary / Next Steps

36. 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

37. What’s Next / Call to Action Develop template sets for your 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

38. Questions?

39. www.jcam.org.ukcamprocessor.sourceforge.netwww.drools.org (JRules)www.oasis-open.org/committees/camdocs.oasis-open.org/cam Resources:

40. A special mention for our contributors to the CAM and jCAM work:UK - Martin Roberts and team from BTplcUS - Sidhartha Nagolu from AC-Tech / NIH Credits: