X.commerce Open Commerce Language (XOCL)
2 likes•1,472 views
This document introduces X.commerce Open Commerce Language (XOCL), a standard for defining commerce processes and integrating merchant systems. XOCL defines global choreographies using commerce semantics and generates artifacts to implement local orchestrations. Merchants can access new capabilities through a service bus that coordinates distributed transactions between merchant systems and service providers implementing individual roles defined by XOCL contracts. XOCL aims to standardize processes over documents to provide context and address issues like lack of aggregate behavior definitions that plague traditional EDI integration.
X.commerce Open Commerce Language (XOCL)
- 1. X.commerce Open Commerce Language Anand Gangadharan, Product Management Jack Greenfield, Distinguished Architect
- 2. Outline • The Merchant Dilemma • Solution Architecture – Use best of breed components – Integrate them with a simple service bus – Standardize processes not documents • X.commerce platform – Define global choreographies using XOCL – Generate wire encodings, documentation, runtime metadata – Services implement local orchestrations – Service bus coordinates distributed transactions • A lap around XOCL • Current status 6/13/2012 2
- 4. Consumer Behavior is Changing Commerce Promotions & Location-based coupons services Mobile Self-scanning & commerce self-checkout Payments Mobile shopping lists In-store Social commerce research Loyalty 6/13/2012 4
- 5. Blurring Online and Offline Today Tomorrow Mobile Local Online 6% Web- influenced Commerce Global Social Offline offline 37% Digital Service & delivery 6/13/2012 5
- 7. Solutions Must Integrate Multiple Technologies Marketing channels Sales channels Fulfillment channels, Back office
- 8. Using a Service Bus Ad Hoc Integration Service Bus Merchant Service Merchant Service Systems Providers Systems Providers Merchant benefit: Access to new capabilities, lower switching costs Developer benefit: Exposure to new merchants, better cost amortization 6/13/2012 8
- 9. Communication Architecture ????? Commerce semantics JSON Payload encoding REST/HTTP State transfer TCP/IP End to end connection 6/13/2012 9
- 11. The Great Thing About Standards
- 12. The Problem With Documents
- 13. The Problem With Documents Lack of context • Different • Less than 3% of participants have document different • Aggregate behavior undefined • (n**2 – n)/2 requirements implementations for • Must be encoded n participants into unused Overloaded document fields Point to point properties agreements
- 14. Standardizing Processes Context specific Business signals • Define messages • Shared identity individual and • Just enough and lifecycle • Two phase aggregate data to commit behavior synchronize • Demonstrate state intent Global Private entity choreographies structure
- 15. Choreography and Orchestration Send 1 Receive 5 A D Receive 2 Send 6 Receive 1 B C Receive 3 Send 2 Send 4 Send 3 Send 5 Receive 4 • Global choreography can Receive 6 be audited • Local orchestrations can be automated with workflow engines 6/13/2012 15
- 16. UN/CEFACT Modeling Methodology • No signals • Signal receipt • Response • Request is a query • Signal validation indicates success • Response is or failure results • May contain data Inform Notify Response Query
- 19. X.commerce Open Commerce Language (XOCL) XOCL Commerce semantics JSON Payload encoding REST/HTTP State transfer TCP/IP End to end connection 6/13/2012 19
- 20. X.commerce Open Commerce Language (XOCL) Specifications generate development • Parser artifacts • Serializer • Message Schemas • Editor • Metadata • Documentation • Mock Services Textual DSL based on XText 6/13/2012 20
- 21. Processes Package Process Role Workflow • A process defines a set of roles and is implemented by one or more workflows. 6/13/2012 Footnote information goes here 21
- 22. Transactions Package Calls Workflow Transaction Calls Role Sender Receiver Binds Topic • A workflow can call other workflows and/or transactions. • A transaction is an atomic exchange of Message messages between a sender role and a receiver role. 6/13/2012 Footnote information goes here 22
- 23. Types Package Type Has Message • A message has a type, and types may contain instances of other types. • Types defined in XOCL map 1 for 1 onto AVDL equivalents. 6/13/2012 Footnote information goes here 23
- 24. Contracts Package Capability Bundle Contract • A contract is a named set of roles. • A capability must implement all of the roles in a contract. • A bundle is a set of capabilities that Roles implements a set of contracts to enact one or more business processes. 6/13/2012 Footnote information goes here 24
- 25. Discovery Package X.com Process Role • Navigate package hierarchy • Search process, role and transaction descriptions Workflow 6/13/2012 Footnote information goes here 25
- 26. What Roles Do I Play? Package X.com Contract • Capability developers choose contracts when they onboard. • Determines the topics they can publish and subscribe to. Role 6/13/2012 Footnote information goes here 26
- 27. Implementing XOCL X.commerce Capabilities X.commerce Frameworks XOCL X.commerce Fabric
- 28. Multi-tenant commerce aware service bus Topic based broadcast/unicast publish/subscribe AVRO/JSON wire encoding Interprets XOCL metadata during execution Logs and enforces commerce processes X.commerce Fabric Audits SLAs and reports exceptions Automates timeouts and coordinates commit
- 30. X.commerce Capabilities • Product Information Management • Inventory Management • Customer Management • Order Management • Marketplace • Web Store • Email marketing
- 31. A LAP AROUND XOCL
- 32. NEXT STEPS
- 34. Get involved • Start here http://x.com/xocl • See you at GitHub https://github.com/xcommerce/XOCL – Go ahead, fork!
Editor's Notes
- #6: Convergence!