W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2010

[Bug 7475] Semantics of rel=first and rel=index breaks specs and implementations

From: <bugzilla@wiggum.w3.org>
Date: Mon, 04 Jan 2010 09:18:20 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NRj4u-0006kn-UA@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7475


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX




--- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-01-04 09:18:20 ---
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: 

Thank you for this research. It is consistent with the results I had found
myself when studying this several years ago.

While I agree with you that the few client implementations that support these
values have indeed been considering these as separate meanings, that in itself
is not a convincing argument. It is clear that as designed so far, the feature
has been a failure (virtually nobody uses it). The main way to increase the
likelihood that something like this will be used is to simplify it, which is
part of what HTML5 does.

In actual use, I would guess that WordPress is amongst the biggest users of
this feature. According to your table, if I'm not misreading it, WordPress uses
"index" (and "start") as defined in HTML5. It doesn't have separate index and
toc pages. Indeed none of the other CMSes you list use "index" at all. Plone
and DotClear use "contents", but it's not clear if the distinction they make is
especially good from a usability perspective.

I do agree that the definitions in HTML5 rock the boat. However, given the
utter mess we are starting with, and given the rarity of these features, I
think it is a worthwhile cost. The alternative, IMHO, quite apart from making
the feature more complicated by having more keywords, would be to just drop the
whole thing altogether.

(Note that the word "index" here is not used in the printed-book sense, but in
the sense of "index.html", the default page on Apache.)


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 4 January 2010 09:18:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:08 UTC