challenges of information collaboration roles, methods, responsibilities and context david rr webber...

8
Challenges of Information Collaboration Roles, Methods, Responsibilities and Context David RR Webber SOA Architect IntegrityOne Partners Ph: (703) 581-6500 E-mail: [email protected]

Upload: lisa-small

Post on 04-Jan-2016

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Challenges of Information Collaboration Roles, Methods, Responsibilities and Context David RR Webber SOA Architect IntegrityOne Partners Ph: (703) 581-6500

Challenges of Information Collaboration

Roles, Methods, Responsibilities and Context

David RR WebberSOA ArchitectIntegrityOne PartnersPh: (703) 581-6500E-mail: [email protected]

Page 2: Challenges of Information Collaboration Roles, Methods, Responsibilities and Context David RR Webber SOA Architect IntegrityOne Partners Ph: (703) 581-6500

slide 2

Challenges of Information Collaboration

Does Web 2.0 leapfrog Internet constraints?

Roles Methods Responsibilities Context Scalability / Level of Service

Page 3: Challenges of Information Collaboration Roles, Methods, Responsibilities and Context David RR Webber SOA Architect IntegrityOne Partners Ph: (703) 581-6500

slide 3

Example interface: Amazon.com AWS

3) Delivered entirelyvia XML / REST andAmazon 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

Page 4: Challenges of Information Collaboration Roles, Methods, Responsibilities and Context David RR Webber SOA Architect IntegrityOne Partners Ph: (703) 581-6500

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

Page 5: Challenges of Information Collaboration Roles, Methods, Responsibilities and Context David RR Webber SOA Architect IntegrityOne Partners Ph: (703) 581-6500

slide 5

Delivery Methods Synchronous (near real time) –

REST/SOAP/ebXML Asynchronous (interaction model) – ebXML/

SMTP Push / Pull methods – RSS / SMTP Security / Scalability trade-offsFunctionality REST SOAP ebXML SMTP RSS

Access ControlRapid Setup and DeliveryError Handling and RecoveryAudit Control and TrackingPartner ProfilesAction / Business Process IntegrationSchema drivenRich Internet tools access (JavaScript)Reliable DeliverySSL and Port security methodsScalability Distributable?

LimitedYesWeakLimitedNoNoPartialYesNoSSLNo

PartialPartialWeakPartialWSDLWSDLWSDLPartialPartialYesNo

YesPartialYesYesYesYesNoPartialYesYesYes

YesYesPartialYesNoNoNoPartialPartialYesNo

LimitedYesWeakYesNoNoNoPartialPartialPortNo

Page 6: Challenges of Information Collaboration Roles, Methods, Responsibilities and Context David RR Webber SOA Architect IntegrityOne Partners Ph: (703) 581-6500

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

Page 7: Challenges of Information Collaboration Roles, Methods, Responsibilities and Context David RR Webber SOA Architect IntegrityOne Partners Ph: (703) 581-6500

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

Page 8: Challenges of Information Collaboration Roles, Methods, Responsibilities and Context David RR Webber SOA Architect IntegrityOne Partners Ph: (703) 581-6500

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)