1. Silverstein Group Presenter Moshe Silverstein A Content Assembly Mechanism Technology Overview Context & Integration A Content Assembly Mechanism Technology Overview

2. Agenda Introduction to CAM Anatomy of CAM templates Summary and Opportunities

3. What are we trying to achieve? Agile Interoperability - scalability without exponential complexity and prohibitive on- boarding costs (the limiter of traditional EDI) Graceful Implementation - reliable pre-built vertical solution templates Easy Management - linked business processes, partner collaborations, and transaction exchanges.

4. What enablers do we need? Open business integration rules so partners can readily confirm their usage Handling local context drivers and providing content flexibility and agility Validating and processing content with semantics

5. eGov Conceptual Scenario and Interaction Roles Government Partners XML Structure Rules XML Structure Rules Transport ebMS server Transport ebMS server Oracle database Oracle database Central ebXML Registry Central ebXML Registry CPA check CPA check CAM data validator CAM data validator Partner Management Web forms Partner Management Web forms (Persistent Storage) CPA instances CPA instances CPA instances CPA instances System Administrators Manage Partner Interactions Local Applicant Company Applicant Authority Proxy Submission Service Provider Messages 22 11 33 44 55 e-Service authority system (passport / visa) Messages

6. Example Deployment Use Cases Application Integration handler Application Integration handler XML Structure Rules XML Structure Rules Hub ebMS server Hub ebMS server SQL database SQL database ebXML Registry ebXML Registry CPA check CPA check Messages Partner ebMS server Partner ebMS server CPA instances CPA instances Partner Management Web forms Partner Management Web forms Admin Services Admin Services Audit and Control Web forms Audit and Control Web forms Existing Web-based Registration Interface Existing Web-based Registration Interface Existing backend Application(s) Existing backend Application(s) Application handler (partner) Application handler (partner) App Server Content Validation Using CAM tools Content Validation Using CAM tools 22 Content Assembly Using CAM Content Assembly Using CAM11 Content Purposing Using CAM Content Purposing Using CAM 33

7. Sample CAM Validation flow

8. Drilldown into jCAM validation details

9. How does this fit together? Where / Who ActionEvent Information Rule What Why HowWhen ActionEvent Information Rule What Why HowWhen ActionEvent Information Rule What Why HowWhen

10. CAM services Provide payload structure and content definition Production content validation and error handling Local pre-deployment transaction checking (on-boarding) Industry Conformance and Compliance testing Automated error handling and responding Structure re-formatting and re-purposing output Business Context Rules implementation Simple business analyst friendly syntax and predicates Data validation services

11. CAM Structural Overview –Header set context –Assembly XML layout(s) of instances –BusinessUseContext Content Rules Structure variances –ContentReference Dictionary Crosswalk –DataValidations Application rules –ExternalMapping Application data mapping Output formatting sections

12. Demonstration - jCAM validation Overview of jCAM functionality Example of jCAM rules for example transactions jCAM in action –valid transaction processing –Invalid transaction processing Integration with registry as validation service On-line Testing On-line Testing Message Reporting Message Reporting Simple Template Simple Template View Input XML View Input XML Extended Template Extended Template Output Formatting Output Formatting

13. Silverstein Group Theory and implementation of CAM approach XML templates for validation via jCAM Management of automatic response messages Demonstration of on-line transaction testing service Summary

14. Silverstein Group www.freebXML.org www.ebxml.org www.oasis-open.org www.ebxmlbook.com/interop www.ebxmlbook.com/benefits

15. How does CAM augment schema? Can have multiple structure instances selected by context Can include structure from sub-assembly of components Enhanced element semantics beyond simply datatyping Full code lists functionality beyond NMTOKEN Ability to leverage semantics at attribute level consistently with elements Ability to version content model components Link to industry dictionaries / registries Link to web service components for external checks Ability to assemble transaction instances Neutral approach - can handle non-XML / XSD formats

16. Technology Foundation Simple XML V1.0 XPath Neutral approach to structure content Assertion predicates excludeAttribute() excludeElement() excludeTree() makeOptional(), makeMandatory() makeRepeatable(), setLimit() setRequired() setChoice(), useChoice() setId() setLength() setMask() setValue() restrictValues() restrictValuesByUID() useAttribute() useElement() useTree() useAttributeByID() useChoiceByID() useElementByID() useTreeByID() lookup() startBlock(), endBlock()

17. Summary of steps required Pick a target XML transaction instance –select typical real example in common use Insert sample XML structure instance into the CAM template Build structure control predicate statements for use in Business Context control section Build content reference statements for each unique element within the XML transaction Optionally add data validation rules Complete template by testing against sample