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 8450 - Case insensitivity of @rel vs case sensitivity of URIs
Summary: Case insensitivity of @rel vs case sensitivity of URIs
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML Microdata (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NE
Depends on:
Reported: 2009-12-07 13:57 UTC by Toby Inkster
Modified: 2010-10-05 13:03 UTC (History)
6 users (show)

See Also:


Description Toby Inkster 2009-12-07 13:57:22 UTC
Under the RDF extraction procedure <> any tokens in @rel are converted to lower-case. This includes instances where URIs have been used as tokens. Many RDF properties include some upper-case characters, including the commonly used property.

Possible solutions include:

* Require (or at least permit) extractors to consider tokens containing colons case-sensitively; or

* Document the limitation.
Comment 1 Ian 'Hixie' Hickson 2010-01-07 06:58:12 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:

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.
Comment 2 contributor 2010-01-07 06:59:11 UTC
Checked in as WHATWG revision r4533.
Check-in comment: Make rel='' values that contain a colon be case-sensitive URLs, leaving the others as case-insensitive keywords.