[Bug 13068] for consistency with RFC 5988, link/@rel should allow extension relation types

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13068

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX

--- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-16 04:51:59 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: Consistency with RFC 5988 isn't goal. Registering types is so
trivial at this point that there's no need for an even easier mechanism. And of
course we don't really want to encourage widespread proprietary values.
(Privately used proprietary values are already possible without registering the
type: just say it's ok and so long as all of you in your community agree, then
it's ok. Same with any other extension to any other standard in the world.)

-- 
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 Tuesday, 16 August 2011 04:52:01 UTC