1 / 8

Challenges of Information Collaboration Roles, Methods, Responsibilities and Context

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. Challenges of Information Collaboration. Does Web 2.0 leapfrog Internet constraints? Roles Methods

lee-sears
Download Presentation

Challenges of Information Collaboration Roles, Methods, Responsibilities and Context

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. Example interface: Amazon.com AWS 1) XML delivers: Catalogue Prices Stock / Supplier 2) HTML “look” rendered dynamically via XSLT • 3) Delivered entirely • via XML / REST and • Amazon AWS • 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

  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. Delivery Methods • Synchronous (near real time) – REST/SOAP/ebXML • Asynchronous (interaction model) – ebXML/ SMTP • Push / Pull methods – RSS / SMTP • Security / Scalability trade-offs

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

More Related