Re: [urn] Feedback on draft-ietf-urnbis-rfc2141bis-urn-16

[Julian Reschke <[e-mail]>]

Reviewing my own feedback from 7 months ago and reposting those parts 
that still seem to apply...:

On 2016-04-27 20:11, Julian Reschke wrote:
>
>       rq-components =  ( "?="  q-component
>                           [ "?+" r-component ] ) /
>                        ( "?+" r-component
>                           [ "?="  q-component ] )
>       q-component   = pchar *( pchar / "/" / "?" )
>       r-component   = pchar *( pchar / "/" / "?" )
>       f-component   = fragment
>
> These come as a surprise to anybody not already familiar to what led to
> the spec.
>
> Either introduce them later, or insert some prose explaining where they
> come from.
 >
> Also, it would be good if there was a discussion about compatibility
> with existing use of queries, as these essentially reserve certain
> variants of queries for generic use.

> ...
>    For the sake of consistency with RFC 3986, neither the general syntax
>    nor the semantics of q-components are defined by, or dependent on,
>    the namespace of the URN.  In parallel with RFC 3896, specifics of
>    syntax and semantics, e.g., which keywords or terms are meaningful,
>    of course may depend on a particular namespace or even a particular
>    resource.
>
> I agree that this is the right thing to do, but I'm not sure what this
> has to do with 3986.  3986 allows a scheme to mandate a specific syntax,
> no?
> ...

> ...
>    For the sake of consistency with RFC 3986, neither the general syntax
>    nor the semantics of f-components are defined by, or dependent on,
>    the namespace of the URN.  In parallel with RFC 3896, specifics of
>    syntax and semantics, e.g., which keywords or terms are meaningful,
>    of course may depend on a particular namespace or even a particular
>    resource.
>
> s/3896/3986/
>
>    Section 5.2 of [RFC3986] describes an algorithm for converting a URI
>    reference that might be relative to a given base URI into "parsed
>    components" of the target of that reference, which can then be
>    recomposed per RFC 3986 Section 5.3 into a target URI.  This
>
> s/RFC3986//
> ...


Best regards, Julian