1. Challenges of Information Collaboration Roles, Methods, Responsibilities and Context David RR Webber SOA Architect IntegrityOne Partners Ph: (703) 581-6500 E-mail: david.webber@ionep.com

2. slide 2 Challenges of Information Collaboration Does Web 2.0 leapfrog Internet constraints? Roles Methods Responsibilities Context Scalability / Level of Service

3. slide 3 Example interface: Amazon.com AWS 3) Delivered entirely via XML / REST and Amazon AWS 2) HTML “look” rendered dynamically via XSLT QUESTIONS? Who controls content? What role is information playing? Who controls access/ service? Who manages changes? ROLES? Virtual Merchant Competitor Comparison service Shopper Search agent Alerter 1) XML delivers: Catalogue Prices Stock / Supplier

4. slide 4 Example Web 2.0 application Mash-up Amazon AWS with Mapping Service Show who has particular products geographically Challenges – finding consistent geographic information in AWS catalogue data Encouraging AWS suppliers to provide more geographic markers Amazon could “game” your application by manipulating the sequence information is provided in – for preferred merchants

5. slide 5 Delivery Methods Synchronous (near real time) – REST/SOAP/ebXML Asynchronous (interaction model) – ebXML/ SMTP Push / Pull methods – RSS / SMTP Security / Scalability trade-offs Functionality RESTSOAPebXMLSMTPRSS Access Control Rapid Setup and Delivery Error Handling and Recovery Audit Control and Tracking Partner Profiles Action / Business Process Integration Schema driven Rich Internet tools access (JavaScript) Reliable Delivery SSL and Port security methods Scalability Distributable? Limited Yes Weak Limited No Partial Yes No SSL No Partial Weak Partial WSDL Partial Yes No Yes Partial Yes No Partial Yes Partial Yes No Partial Yes No Limited Yes Weak Yes No Partial Port No

6. slide 6 Responsibilities MoU / MoA setup / enforcement Role clarification and determination Short term and long term commitments / implications Sustainable business model Technology stewardship / control Notification of changes Enabling agent technologies Fair play and neutral information

7. slide 7 Context Enabling context is challenge for next generation information collaboration Core components approach founded on need to understand and use context Context in legacy systems is hidden inside static code and not exposed Ability to use open public standards to expose rules and context in consistent way – OASIS CAM work

8. slide 8 Summary Early adopter applications are finessing most of these questions with very limited use models, and constrained roles Human interpretation of information presentation avoids difficulties with machine handling of diverse sources (BPM “above the line” human workflow) Business Process Integration will be increasingly the challenge (BPM “below the line” human workflow control / machine tasking – enterprise application integration)