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 7458 - inconsistent definition of "up" relation
Summary: inconsistent definition of "up" relation
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Whiteboard: NE
Keywords: NoReply
Depends on:
Reported: 2009-08-30 10:49 UTC by Julian Reschke
Modified: 2010-10-04 13:59 UTC (History)
3 users (show)

See Also:


Description Julian Reschke 2009-08-30 10:49:36 UTC
Citing: Link type "up"

"The up keyword indicates that the document is part of a hierarchical structure, and that the link is leading to the document that is the parent of the current document."

So "up" always defines a relation to the parent document.

But wait...:

"The up keyword may be repeated within a rel attribute to indicate the hierarchical distance from the current document to the referenced document. Each occurrence of the keyword represents one further level. (...)"

So "up up" does not define a relation to the parent document, after all.

The simplest way to fix this is to remove the exception here; please do not experiment with the link relation system in general unless it's clear that it's needed.
Comment 1 Ian 'Hixie' Hickson 2009-09-18 09:32:07 UTC
I have fixed the contradiction. I haven't removed the feature because it is a neat way of marking up breadcrumb navigation mechanisms.
Comment 2 Maciej Stachowiak 2010-03-14 14:50:23 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, 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:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.