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

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 19 Jan 2016 23:25:31 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29381-523-hm5eYpx1aH@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29381

Liam R E Quin <liam@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |liam@w3.org

--- Comment #2 from Liam R E Quin <liam@w3.org> ---
Personal response...

The URI spec is specific that only / is used for hierarchical processing.
https://tools.ietf.org/html/rfc3986#section-1.2.3 [[
  All URI references are parsed by generic syntax parsers when used.
   However, because hierarchical processing has no effect on an absolute
   URI used in a reference unless it contains one or more dot-segments
   (complete path segments of "." or "..", as described in Section 3.3),
   URI scheme specifications can define opaque identifiers by
   disallowing use of slash characters, question mark characters, and
   the URIs "scheme:." and "scheme:..".
]]

(so no, you can't split a URN at a colon).

The URN spec is specific that it avoids the use of /.

https://tools.ietf.org/html/rfc2141 [[
 RFC 1630 [2] reserves the characters "/", "?", and "#" for particular
   purposes. The URN-WG has not yet debated the applicability and
   precise semantics of those purposes as applied to URNs. Therefore,
   these characters are RESERVED for future developments.  Namespace
   developers SHOULD NOT use these characters in unencoded form, but
   rather use the appropriate %-encoding for each character.
]]


Therefore, there's no such thing as a partial URI reference for a URN.

Hope this helps.

Liam

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 19 January 2016 23:25:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:57 UTC