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 13478 - Problems related to the current definition of rel values
Summary: Problems related to the current definition of rel values
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-30 20:28 UTC by Jirka Kosek
Modified: 2011-08-04 05:04 UTC (History)
4 users (show)

See Also:


Attachments

Description Jirka Kosek 2011-07-30 20:28:48 UTC
In section 4.2.4 The link element the spec prohibits usage of additional keywords in rel attribute.

At the same time it is not possible to create document which will be conforming over the period of time, because list of allowed keywords is not listed in the spec but it is available only on external uF site.

Spec should allow arbitrary keywords to allow for extensibility, or at least create special conformance class for documents using such additional keywords.

Also keywords registered at uF site at the certain date should be copied as an appendix of the HTML spec to have snapshots against document can be made conforming.

It's unacceptable if document conformance is relying on external registry, which can change over the time. A lot of organizations is required by law to publish conforming documents, but they don't expect that conformance can change overnight.
Comment 1 Aryeh Gregor 2011-08-02 16:07:01 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: HTML relies on many other specifications and registries, and the practice is well accepted in the standards world.  For instance, HTML requires that lang attribute values be valid according to BCP47, which in turn defers to an IANA registry.  It is not practical to include all registries in HTML proper.

If poorly-written regulations require organizations to conform to particular versions of standards, without allowance for revisions to those standards over time, that's something that has to be fixed in the regulations.  We are not responsible for people who use our standards in ways they aren't intended to be used.  Authoring conformance requirements are designed to inform authors of possible errors and encourage them to voluntarily fix their pages -- they aren't meant to be mandatory.
Comment 2 Michael[tm] Smith 2011-08-04 05:04:07 UTC
mass-moved component to LC1