W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2010

[Bug 9035] Interfaces for URL manipulation: concept of "hierarchical"

From: <bugzilla@wiggum.w3.org>
Date: Tue, 23 Feb 2010 13:30:07 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Njupz-0006px-FR@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9035





--- Comment #5 from Julian Reschke <julian.reschke@gmx.de>  2010-02-23 13:30:06 ---
(In reply to comment #3)
> It _did_ depend on the scheme. As far as I can tell, implementations still
> think it depends on the scheme, and thus RFC3986 is incorrect. I think the
> right solution here might be to refer to the previous versions of the RFCs
> (specifically 2396) for the definition of "hierarchical".

- If HTML5 makes it depend on the property of being "hierarchical", it either
needs to define that term, or reference the definition somewhere else.
Currently it doesn't, and that's why I raised the bug.

- The definition can not hard-wire specific scheme names, because that would
make it impossible to deploy new schemes; so it needs to be sufficient to
inspect the given base URI, given the fact that the scheme may be unknown.

- That being said, the example given above (IE8 parsing data URIs) seems to
indicate that implementations do not uniformly special-case non-hierarchical
URIs; thus it should be considered to drop the distinction here.


-- 
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, 23 February 2010 13:30:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:11 UTC