- From: <bugzilla@jessica.w3.org>
- Date: Tue, 02 Aug 2011 06:56:00 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13370
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |FIXED
--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-02 06:56:00 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: Partially Accepted
Change Description: see diff given below
Rationale: You're misunderstanding the requirement. This is not a
computer-checkable conformance requirement in the absence of information about
the vocabulary. A string that happens to be interpretable as a URL isn't
necessarily a URL. A sequence of numbers and dashes that happens to be
interpretable as a date isn't necessarily a date.
The requirement is intended to be used in conjunction with a vocabulary. If you
know a particular property takes a URL, then it has to be in a URL element.
I've added some prose to try to help explain this better.
--
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, 2 August 2011 06:56:06 UTC