- From: <bugzilla@jessica.w3.org>
- Date: Sun, 01 Dec 2013 02:19:52 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23946 Boris Zbarsky <bzbarsky@mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bzbarsky@mit.edu --- Comment #2 from Boris Zbarsky <bzbarsky@mit.edu> --- > So the forbidding of query parts makes blob: a non-URI in the sense of that RFC. It's not clear to me why. RFC 3986 section 1.1.1 says: As such, the URI syntax is a federated and extensible naming system wherein each scheme's specification may further restrict the syntax and semantics of identifiers using that scheme. so it seems ok to have a scheme that uses the RFC 3986 parser and then says that only URIs which do not have a query section are valid. As a side note, RFC 3986 isn't compatible with how URIs are actually used on the web, so browsers don't actually implement it, and RFC 2396 is much more clear that "the URI syntax does not require that the scheme-specific-part have any general structure or set of semantics which is common among all URI" (RFC 2396, section 3). The argument that there might be use cases for allowing a query here is much more interesting than an argument based on RFC 3986. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 1 December 2013 02:19:53 UTC