I know the "right" way to do return different representations of a
resource is via content negotiation. Still, in many cases it's
perceived to be easier to use different extensions for different types.
E.g. I could do a GET on
http://example.org/customers/4711 to get the
default representation, say in HTML, and use
http://example.org/
customers/4711.xml to get an XML representation. Whether this is
"good" or "bad" doesn't really matter IMO; it's going to definitely a
common approach. How do we address this?
Stefan
--
Stefan Tilkov, http://www.innoq.com/blog/st/