Re: [urn] [Marketing Mail] Re: Request for urn mrn

H Kasper,

Sorry for not coming back to your reply re my comments sooner... Thanks for taking my suggestions into account. I agree with Peter and John that your registration is ready to be completed if you add Peter's suggested references to §§ 3.1 and 6.4.2 of RFC 8141.

Thanks,

Lars

On Tuesday, November 07, 2017 11:22 PM, urn [mailto:urn-bounces@ietf.org] On Behalf Of John C Klensin wrote:

> Concur.
>    john
> 
> 
> --On Tuesday, November 7, 2017 10:27 -0700 Peter Saint-Andre
> <stpeter@stpeter.im> wrote:
> 
> > On 11/7/17 10:11 AM, Kasper Nielsen wrote:
> >> Hi,
> >>
> >> I'm a little unsure about the further registration process.
> >
> > Sorry about that. We're all smoothing out wrinkles in the
> > registration process, so thanks for your patience.
> >
> >> Do we need
> >> to do something on our side?
> >
> > Your textual changes look good to me. I have only two small
> > comments...
> >
> >>        The assignment procedures for MRN strings under a
> >>     particular     Organization-specific namespace ID is
> >>     the responsibility of the
> >
> > That should be "are" (subject-object agreement is annoying!).
> >
> >>        Rules for equality comparisons of the OSNS part must
> >>     be clearly documented
> >>        by the governing organization.
> >
> > It might be slightly better to say this:
> >
> >    Rules for equality comparisons of the OSNS part must be
> > clearly    documented by the governing organization, and be
> > consistent with    Sections 3.1 and 6.4.2 of RFC 8141.
> >
> > That might help guide the governing organizations with regard
> > to any rules they might define; I am thinking especially of
> > the following guidelines in Sections 3.1 and Section 6.4.2
> > respectively:
> >
> >    Such rules MUST always have the effect of eliminating some
> >    of the false negatives obtained by the procedure above and
> > MUST NOT    result in treating two URNs as not "the same" if
> > the procedure here    says they are URN-equivalent.
> >
> > And:
> >
> >    3.  Rules for determining URN-equivalence between two names
> > in the        URN namespace.  Such rules ought to always have
> > the effect of        eliminating false negatives that might
> > otherwise result from        comparison.  If it is appropriate
> > and helpful, reference can be        made to particular
> > equivalence rules defined in the URI        specification
> > [RFC3986] or to Section 3 of this document.        Examples of
> > URN-equivalence rules include equivalence between
> > uppercase and lowercase characters in the NSS, between
> > hyphenated        and non-hyphenated groupings in the name, or
> > between single        quotes and double quotes.  There may
> > also be namespace-specific        special encoding
> > considerations, especially for URNs that contain
> > embedded forms of names from non-URN identifier systems.  (Note
> >        that these are not normative statements for any kind of
> > best        practice related to handling of relationships
> > between characters        in general; such statements are
> > limited to one particular URN        namespace only.)
> >
> > With those minor adjustments, in my opinion your registration
> > is ready to be completed.
> >
> > Peter
> >
> 
> 
> 
> 
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn