Re: Don't specific media types introduce coupling?

On Thu, Oct 18, 2012 at 2:11 PM, Ruben Verborgh <[email protected]> wrote:
> Hi Jan,
>
> Thanks for the very detailed answer, that clears up a lot of the questions I had concerning coupling.
>
>> If you do not do that (write specific media types) but instead use generic ones (application/xml, application/json) you absolutely, 100%, need some out of band coupling somewhere if you want your client to do more than 'parse as xml' or 'parse as json'. And you will, immediately, end up with a non RESTful architecture where out of band contract is owned and changed by the server.
>
> I’m not sure about the latter.
> I agree if this out-of-band coupling (say, a description document, maybe machine-processable) is static and has to be precompiled. However, if such a description document can be obtained and interpreted at runtime [1], I’d argue that a RESTful interaction is taking place.
>
> Best,
>
> Ruben

Then you don't need to call it a "description document" since it's
just another resource with links that is part of your application.

Cheers,
M


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/rest-discuss/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/rest-discuss/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/