Return to

Core Web Services

Capability

Purpose

Function

Authentication/access control

Ensure content is received from known sender

messaging

Robust delivery protocol support

Guarantee bytes transmitted are also received exactly as sent

messaging

Delivery failure recovery

Will continue to attempt to re-send, will recover from most recognized delivery system failures

messaging

Packaging control

Sender can instruct the receiver as to the start and end of content, and the sections within the transaction

messaging

Message Structure validation

Agreement between sender and receiver as to physical interchange format required

messaging

Envelope validation

Ensure that the sender is recognized by the receiver and that the sender is authorized to submit that type of content

collaboration agreement

Business process collaboration

Agreement between sender and receiver as to business process engagement and the exchange commitments and quality of service

collaboration agreement

Signature support

Additional security checks to validate sender and also legally endorse the interchange

messaging

Encryption support on envelope

Prevent eavesdropping gaining access to communications details between two parties

messaging

Encryption support on payload

Prevent unauthorized access to content

messaging

Payload structure validation

Agreement between sender and receiver as to physical content required and semantics and meaning of content

business process

Routing support

Allow content to reach the desired recipient based not on just physical addressing, but also deferred delivery via third party, or broadcasting to multiple recipients, or passing to correct backend application(s)

messaging

Receipt confirmation

Transaction number created, as in the EDI 997 ACK message, or with email delivery receipt confirmation.

messaging

Backend application control

If errors occur post-delivery, that these can be communicated accurately from the processing system(s) back to the original sender

business process

Activity tracking

Allow auditing of exact interactions and verification of delivery and payloads interchanged

messaging

Accessibility support ( Section 508)

Support for multiple interface options to information

all components

Define business process flow

Partners agree on their roles and responsiblities and document these so that software can track and implement these automatically

business process

Business process flow execution control

Manage backend application execution processing through management of the individual program components and devices

business process

Content assembly mechanism

Context driven assembly rules for business transaction information - allows coherent information exchanges within a community of interest and between partners

business process

Context sharing mechanism

Externalizes the key knowledge triggers and rules so that each part of the business collaboration can understand the context it is required to act on at that juncture

all components

Storage of templates and metadata

Use of classification system by industry domain to allow discovery and reuse of business knowledge within communities of interest (see OASIS BCM TC work).

registry

Business directory services

Allow a community of interest to build marketplaces and discover products and services between members

registry and directory

Confederated sharing of content meaning and purpose

Allow enterprises within communities of interest to have their own local definitions aligned to industry terminology and templates but be able to share these in a systematic way with other partners

registry

Point description mechanism

Any component of the network can describe its functions, access means and control mechanisms

registry and directory

Copyright 2003, WebServices.Org
[top]