Well, not *that* portable. I don't think HTTP should be talking about
the syntactic details of specific media types. Delegating this to
media type definitions would be the most sensible long-term thing to
do, although some sort of advice would be needed in the meantime...
On 28/02/2009, at 10:39 PM, Vincent Murphy wrote:
> The id attribute value (if one exists) of the <a> anchor element used
> to initiate the HTTP request in the user agent would be used as a
> fragment identifier in the referer URI. This is in exactly the same
> way as fragment identifiers is used to identify a destination anchor
> in current practice.
>
> I think this mechanism is portable across media types.
>
> 2009/2/26 Mark Nottingham <mnot@mnot.net>:
>> Yes - part of that discussion needs to be exactly what is included
>> in the
>> referer URI.
>
--
Mark Nottingham http://www.mnot.net/