atom:content's src and server-driven content negotiation

I don't want to start yet another discussion about violating SHOULD level requirements but I can't think of any better way to handle the following situation (but hopefully you can :-): Suppose the host www.example.com uses HTTP/1.1's server-driven content negotiation for its resource /img

Re: atom:content's src and server-driven content negotiation

Andreas Sewe wrote: I don't want to start yet another discussion about violating SHOULD level requirements but I can't think of any better way to handle the following situation (but hopefully you can :-): Suppose the host www.example.com uses HTTP/1.1's server-driven content negotiation