[OSLC] resource: storage vs representation--specifying variations in the form of the return from a GET

[Steve K Speicher]

ajberner at us.ibm.com wrote on 01/17/2010 06:03:20 PM:

>> This raises a question about the spec:  Have we been specifying ways of
> GETting alternate representations of the same resource?  I'm wondering 
if
> there shouldn't be a somewhat standardized way to do this, although the
> specifics will be resource dependent.

In the CM 1.0 spec, we followed what is commonly referred to as "HTTP 
content negotiation".
See section titled "Requesting Formats" 
http://open-services.net/bin/view/Main/CmRestApiV1#Requesting_Formats

We identified for each type of CM resource, what media types are supported 
http://open-services.net/bin/view/Main/CmRestApiV1#Media_Types_Used

For example, for a change request resource you can request 3 different 
representations for it based on the CM 1.0 spec: HTML, JSON and XML.

Thanks,
Steve Speicher | IBM Rational Software | (919) 254-0645


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100117/0ca3fcde/attachment-0003.html>