[Bug 12677] New: Should drop "The link types that contain no U+003A COLON characters (:), including all those defined in this specification, are ASCII case-insensitive values, and must be compared as such." since it's meaningless (nothing specifies anything about colons h

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

           Summary: Should drop "The link types that contain no U+003A
                    COLON characters (:), including all those defined in
                    this specification, are ASCII case-insensitive values,
                    and must be compared as such." since it's meaningless
                    (nothing specifies anything about colons h
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#lin
                    kTypes
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org,
                    public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#linkTypes

Comment:
Should drop "The link types that contain no U+003A COLON characters (:),
including all those defined in this specification, are ASCII case-insensitive
values, and must be compared as such." since it's meaningless (nothing
specifies anything about colons having any other meaning.)

Posted from: 76.102.14.57 by ian@hixie.ch
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_7) AppleWebKit/534.24
(KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24

-- 
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 Wednesday, 18 May 2011 07:57:46 UTC