Sergey Beryozkin-5 wrote > >>> 4) Knowledge of the media type being returned to the client. One >>> resource can (and often does) support multiple media types, and each >>> media >>> type is going to come with different link relations. >>> >> >> Can you educate me a bit please and explain why different media types >> can affect the link relations ? > > I guess it's to do with media types used as contributors to the > versioning/etc strategies... Either way, the media type being returned > to the client will be available at the provider level... >
I am thinking here of major media type variations, not just application/xml vs application/json. The documentation for a media type should explicitly document the link relations that are available. For example, a model/vrml representation is not going to provide edit links, or imagine a media type like application/vnd.normalized+xml that provides a read-only, scaled back, normalized version of a model that doesn't provide editing or versioning links. You are right that, in any event, the provider has that information, and now that I am thinking on it further, perhaps it isn't that common after all. -- View this message in context: http://cxf.547215.n5.nabble.com/Good-way-to-add-link-relations-to-REST-responses-tp5461580p5466541.html Sent from the cxf-user mailing list archive at Nabble.com.
