link/@type and content negotiation

[Erik Wilde <dret@xxxxxxxxxxxx>]

hello.

in the context of some work we're doing that is attempting to describe 
RESTful services, one important problem is how to deal with media types. 
for HTTP URIs, servers can return various media types and this may 
happen via HTTP content negotiation. Atom's link/@type links to a URI 
and specifies a media type, but this mechanism supports only one type 
that can be specified. does anybody have any opinion or experience or 
best practice what to do in scenarios where that URI is actually 
supporting content negotiation?

thanks and kind regards,

erik wilde   tel:+1-510-6432253 - fax:+1-510-6425814
       dret@xxxxxxxxxxxx  -  http://dret.net/netdret
       UC Berkeley - School of Information (ISchool)