W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2016

[Bug 29381] [QT3] resolve-uri-28 expects error FORG0002, but seems valid according to RFC-3986

From: <bugzilla@jessica.w3.org>
Date: Tue, 10 May 2016 09:13:26 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29381-523-PcnAnHmGMb@http.www.w3.org/Bugs/Public/>

--- Comment #5 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
In addition to what already has been said, please mark that RFC-3986 has an
explicit remark on this scenario in the section on the algorithm (5.x). In
5.2.1 it says:

   "Note that only the scheme component is required to be
   present in a base URI; the other components may be empty or


   "A component is undefined if its associated delimiter does
   not appear in the URI reference; the path component is never
   undefined, though it may be empty."

Section 3.3 describes the path segment as being the whole after "urn:" and
before any "#" or "?" for non-hierarchical URIs, called in ABNF

So I think the described scenario is neither an error nor undefined in the

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 10 May 2016 09:15:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 10 May 2016 09:15:25 UTC