This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12490 - potential conflict between Link: and <link> semantics
Summary: potential conflict between Link: and <link> semantics
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 blocker
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/spec/Overview...
Whiteboard:
Keywords: WGDecision
Depends on:
Blocks:
 
Reported: 2011-04-14 08:39 UTC by Julian Reschke
Modified: 2012-01-31 23:06 UTC (History)
7 users (show)

See Also:


Attachments

Description Julian Reschke 2011-04-14 08:39:03 UTC
The decision on ISSUE-27 has resulted in a state where the semantics of link relations may depend on where they appear in (Link: HTTP header vs HTML content).

Minimally, the spec should clarify that there's potential for conflict, and explain that the semantics of link relations appearing in the HTTP Link header field are defined by RFC 5988 and the IANA link relations registry, not the Microformats Wiki.
Comment 1 Anne 2011-06-22 22:14:29 UTC
I doubt that is how it would end up being implemented in a user agent that implements both. At least in Opera the code is partially shared.
Comment 2 Julian Reschke 2011-06-23 07:55:03 UTC
In which case you should open a bug requesting the spec to define *that*.
Comment 3 Michael[tm] Smith 2011-08-04 05:13:15 UTC
mass-move component to LC1
Comment 4 Ian 'Hixie' Hickson 2011-08-13 02:35:08 UTC
What does this have to do with HTML?
Comment 5 Julian Reschke 2011-08-20 12:36:36 UTC
(In reply to comment #4)
> What does this have to do with HTML?

The spec tries to define UA behavior for many things which are not "HTML". It already *does* talk about processing Link headers and cites RFC 5988. So just clarify this, please.
Comment 6 Ian 'Hixie' Hickson 2011-08-29 07:26:55 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: This has nothing to do with HTML. The semantics of Link: headers apply just as much when there is no HTML document at all and all that is being viewed is a pure SVG or even pure arbitrary-XML document. It is completely out of scope for HTML to define this.
Comment 7 Sam Ruby 2011-08-29 17:14:05 UTC
From the EDITOR'S RESPONSE "please add the TrackerRequest keyword to this bug,
and suggest title and text for the tracker issue; or you may create a tracker
issue yourself, if you are able to do so"

Does anybody want to propose title and text for the tracker issue?  Or to
create the tracker issue themselves?
Comment 8 Sam Ruby 2011-08-31 11:38:47 UTC
http://www.w3.org/html/wg/tracker/issues/174
Comment 10 Ian 'Hixie' Hickson 2011-12-09 20:26:38 UTC
The decision is to replace this paragraph:

"HTTP Link: headers, if supported, must be assumed to come before any 
links in the document, in the order that they were given in the HTTP 
entity header. (URLs in these headers are to be processed and resolved 
according to the rules given in the relevant specification; the rules of 
this specification don't apply.) [HTTP] [WEBLINK]"

By these two paragraphs:

"HTTP Link: header fields, if supported, must be assumed to come before 
any links in the document, in the order that they were given in the HTTP 
message. These header fields are to be processed according to the rules 
given in the relevant specifications. [HTTP] [WEBLINK]

Note: registration of relation types in HTTP Link: header fields is 
distinct from HTML5 link types, and thus their semantics can be 
different from same-named HTML5 types."

with "HTML5 link types" being a cross-reference.

In the WHATWG copy the wording of the second paragraph will have to be slightly different, obviously.
Comment 11 Julian Reschke 2011-12-09 22:44:43 UTC
(In reply to comment #10)
> ...
> In the WHATWG copy the wording of the second paragraph will have to be slightly
> different, obviously.

Not obvious to me. Please elaborate.
Comment 12 Edward O'Connor 2011-12-12 18:32:22 UTC
I imagine Ian simply means that the WHATWG spec would s/HTML5/HTML/ in the last paragraph.
Comment 13 Julian Reschke 2011-12-12 18:55:00 UTC
(In reply to comment #12)
> I imagine Ian simply means that the WHATWG spec would s/HTML5/HTML/ in the last
> paragraph.

Ah. Well, that can be the same in both specs.
Comment 14 Ian 'Hixie' Hickson 2012-01-10 01:14:47 UTC
Can the chairs confirm that it's ok to s/HTML5/HTML/ in this text?
Comment 15 Sam Ruby 2012-01-10 01:42:49 UTC
(In reply to comment #14)
> Can the chairs confirm that it's ok to s/HTML5/HTML/ in this text?

The chairs will not intercede unless there is an objection by a WG member.  This does not look likely here.
Comment 16 Ian 'Hixie' Hickson 2012-01-31 23:05:02 UTC
Done.
Comment 17 contributor 2012-01-31 23:06:28 UTC
Checked in as WHATWG revision r6956.
Check-in comment: Tweak the wording per chair decision.
http://html5.org/tools/web-apps-tracker?from=6955&to=6956