Different RESTful representations of the same resource

Question

My application has a resource at /foo. Normally, it is represented by an HTTP response payload like this:

{\"a\": \"some text\", \"b\": \"some t         


        

Answer 1

you could use a second vendor media-type in the request header application/vnd.com.mycompany.resource.rep2, you can't bookmark this however, query-parameters are not cacheable (/foo?sections=a,b,c) you could take a look at matrix-parameters however regarding this question they should be cacheable URL matrix parameters vs. request parameters