Article suggestions?

I think a great article for people would be an introduction with a small sample of what SO(A) is really all about.

I've looked into it a little bit to try and understand it, but the documentation out there seemed quite nebulous. I've got a sneaking suspicion Im not alone on this.

I like the 'SOA 1on1' (man you don't want to know what this would translate too in Dutch!) idea too.

Not some fuzzy talk (like we don't expect from you ;) ), but examples of why serialized objects vs documents+service-requests are different. The pro's & con's.

And the way it helps us to go into the future without knowing it upfront.

I think there is too many unclear undesrtanding of relations between background Web Service technologies. I mean WSDL, XSD and SOAP.

It is great to state clear what is internal structure of each. And precisely define relations and containments: where is it one-to-one, one-to-many etc.

There is powerful idea to "define contracts" first, but too many of us don't even sure of contract's "official language".

May be you are familiar with all that XML and WS technoogies so much, but why don't make they a little bit clearer for programmers en mass?

Actually, how about taking it a step further and laying out a blueprint for BPEML and SOA

I think a walkthrough of implementing a service completely without XML serialized types(the "Ewaldian" void foo(msgIn, msgOut) ). But the WSDL needs to have operations that import types defined in external schemas (in an XSD file or files). The service ought to be able to use schema validation (inbound messages only :) ).

AND -- here's the twist -- the WSDL needs to be structured such that XSD.EXE and/or VS web references can generate working client-side proxy classes (down to the node value level) for callers who wish to do so. Lots of people don't know how to structure schemas that are usable as type definitions for XSD.EXE (complexType) vs. validation (element decls).

Tim Ewalds MDSN article from a couple of years ago described such a service, but the article was point about directly accessing the ASMX SOAP streams.

How to use ARRAYLISTS in a web Services, as parameters and returns.