Service Oriented Architecture is the starting point and Web Services is sort of a ‘best practices’ wrapping around that.

Definition of web service - “…a broad based agreement for exposing programmatic behavior over a network and a set of core technologies that enable that capacity” – Noel Bergman

WS-I leads the effort around putting the ‘must’ into place for the standards. The other standards have too many ‘should’ and ‘could’ WS-I and puts the stuff in place to make sure the interop works.

Hot areas in WS

1)    Interoperability

2)    User Experience

3)    Management

4)    Choreography and Transactions

5)    Reliable

6)    Security

Portals are the UI web-services is the back end parts.

WS-Remote Protocol – look more into this

WS Foundations

1)    XML Parser

2)    JAXP

3)    JDOM

4)    JSR 109 – the programming model around web services

5)    ebXML

Long list of other standards that relate to the WS space.

SOAP with attachments.

JAX-RPC – newest version allows JAXB to be plugged into the data-binding space.

Many of the specs are geared toward the vendors so that we as developers can count on the implementation being conformant.

Lots of security stuff is going into the SOAP headers.

First half of the talk is the long, long list of specs that make up ‘Web Services’. To much info.

BPEL is in the work flow space. – need to study this more, looks very interesting

Web Services For Remote Portlets WSRP 1.0 is Approved through OASIS.

It is bad to use XML as the communication tech between micro-layers. How many times have we seen app servers fall on their butt because of this?

WS-I process defines use cases, builds usage scenarios, sample applications and runs the through the profiles, then adds tests. The output then helps them make the inter-op piece work better.

WS-I value add – turn all the ‘may’ or ‘should’ to ‘must’ or ‘must not’, providing guidance or best practice on standards implementation, provide concrete examples and testing stuff.

Profile is the list of standards and versions and then the list of ‘must’ and ‘must not’. The profile will restrict things and choose a single mechanism among many etc. So the profile provides a way for applications to be written so that they can run on different implementations.

Basic Profile is the ‘holding space’ as other profiles mature they will be moved into the Basic Profile. In the mean time they are called ‘extension profiles’. There will be consideration for both, maturity of the extension profile and the widely adopted nature of the extension profile.

WS-I Basic Profile 1.1 is beginning to make headway because SOAP w/ attachments is starting to settle down.