RE: The type attribute and HTTP content negotiation.

["Danny Ayers" <danny666@xxxxxxxxxxx>]

> <link rel="alternate" type="text/html" href="http://www.example.com/"; />
> <link rel="alternate" type="application/xhtml+xml"
> href="http://www.example.com/"; />
>
> That is: the same href in both, the same @rel, but different @types.
>
> In a perfect world the type attribute would be passed to whatever is being
> asked to retrieve the resource, and it would specify that type in
> it's http
> request as to what type of resource it wants back (ie. content
> negotiation).
>
> As to which <link> is selected ... that's the same problem if they were
> different @hrefs with application/pdf and image/jpeg ... except having the
> same @href for different types is a hint that content negotiation could
> occur.

This makes sense, but we are using part of the HTML spec here, so I don't
think we could just change type to mean type of the <content>...