Web Service 'IPersist' Interface?

We've been designing our app with a series of web methods that expose our
object graph as 'documents'. We like this because we want to exchange
XML 'data messages' between systems and not expose fine-grained RPC-like
behaviour. We're finding that we get coupling/version issues unless we use
a 'data centric' doc msg approach. Learn to 'first walk and then run' type
approach, I guess.

If this was 5 years ago I would be reaching for 'IPeristStreamInit' with
its Load/Save. I know that HTTP intrinsically has its GET/POST verbs but
we're looking for slightly more, i.e. Create, Load, Save, Update, Remove,
List, y'know the usual suspects. We also have business logic web methods
that we may wish to run over and above this basic CRUD interface.

Does anyone have any experience or pointers that they could pass on before
we publish our 'Yet Another Custom WSDL Interface'. I'm kind of wishing for
a WC3, WS spec for Data Providers / DAV etc. I see good stuff like WS-Coord
and WS-Tran start to emerge but its all more than I need at the moment.

Is it just me or did I miss something (that's not rhetorical BTW :)?

Thanks,
David

* I may have mis-posted this to DOTNET-WEB (when it's not really specific
to DOTNET). Apologies for the duplication and please reply here.

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.