Good evening Rest List!;

I'm looking to build a REST middleware to unify a bunch of disjoint
systems, and I've settled on a lot of my design.

I'm still looking for a clean XML object serialization format to unify
how objects are represented. I've looked at XStreams, xmlBlaster, wddx,
xbind and xmlbeans to unify my design, but havent really been stirred by
anything (except the sheer simplicity of XStreams). I dont particularly
care what the native implementation is in, so long as the standard is
well defined enough and "simple" enough to be rebuilt.

In my quest for object serialization, I'm hoping REST List might provide
some feedback, and perhaps some good pointers into the RESTWiki (which
I've plumbed but found little info in).

REST is about resources, but how do we represent these resources? I'm
sure I'm about to cross an electric fense, but resources in modern
computing are often representable as objects; collections of other
objects.




I realize that to define this as a standard would go above the very
nature of REST as a principle rather than a standard, but all good
principles have standards underlying them. Paul Prescod has a good
article on "why not" I've linked below, but somewhere behind why not
lies a coder trying to make a choice:
http://www.prescod.net/rest/encoding/

I'm hoping this is not too off topic, I knew of no better place to turn
to in this conundrum.

Many thanks,
Myren