>From RFC 4395: 2.2. Syntactic Compatibility
RFC 3986 [5] defines the generic syntax for all URI schemes, along with the syntax of common URI components that are used by many URI schemes to define hierarchical identifiers. All URI scheme specifications MUST define their own syntax such that all strings matching their scheme-specific syntax will also match the <absolute-URI> grammar described in Section 4.3 of RFC 3986. New URI schemes SHOULD reuse the common URI components of RFC 3986 for the definition of hierarchical naming schemes. However, if there is a strong reason for a URI scheme not to use the hierarchical syntax, then the new scheme definition SHOULD follow the syntax of previously registered schemes. URI schemes that are not intended for use with relative URIs SHOULD avoid use of the forward slash "/" character, which is used for hierarchical delimiters, and the complete path segments "." and ".." (dot-segments). Question closed in my view. I don't see any point in responding to further comments that simply repeat the original statement. There is a clear requirement that URI schemes are required to meet stated in the URI standards documents. The rules were developed from long experience and are designed to encourage interoperability. I don't see any reason to second guess that reasoning on the basis of the vague and unsubstantiated concerns you have raised. On Mon, Oct 3, 2011 at 1:23 PM, Paul Hoffman <[email protected]> wrote: > On Oct 3, 2011, at 10:12 AM, Phillip Hallam-Baker wrote: > >> On Mon, Oct 3, 2011 at 1:05 PM, Paul Hoffman <[email protected]> wrote: >>> On Oct 3, 2011, at 9:22 AM, Phillip Hallam-Baker wrote: >>> >>>> URLs are used in cases where hierarchy is assumed. >>> >>> I didn't see such use cases in your draft, nor in Stephen's. Maybe you'll >>> put them in your next proposal. >> >> As Julian correctly pointed out, a generic URI will be used in >> situations where the application will (correctly) assume that anything >> in URI syntax that has a slash character in it will be hierarchical. > > Did Julian say that? The one thing that I saw him say was "Also keep in mind > that if you use "/" for a different purpose than hierarchy, surprising things > will happen when relative references are resolved. It's good to avoid them in > this case." > > I don't see how the digest URL you propose has either "relative references" > nor "resolved". More detail in your next draft would be valuable. > > --Paul Hoffman > > -- Website: http://hallambaker.com/ _______________________________________________ websec mailing list [email protected] https://www.ietf.org/mailman/listinfo/websec
