[urn] Re: URN namespace update IALA

Thanks, Dale. This all looks good to me.

On 9/27/24 3:31 PM, Dale R. Worley wrote:
> Peter Saint-Andre <[email protected]> writes:
>> [...] A quick glance indicates that not much has changed, but I have
>> not performed a line-by-line comparison between v1 and v2. [...]
> 
> I've put the IANA copy of v1 and Minsu Jeon's v2 through a "word by
> word" difference tool.  The changes look fine to me.  Following is the
> output of the tool, with long stretches of unchanged words removed.  The
> changes are between { and }, with my explanations inserted.  You can
> compare with the v1 at https://www.iana.org/assignments/urn-formal/mrn.
> 
> Dale
> 
> ----------------------------------------------------------------------
> 
>   { Namespace ID:
> 
> "mrn" Requested of IANA
> 
> Version:
> 
> 2
> 
> Date:
> 
> 2024-08-26
> 
> Registrant:
>    
> Name: Minsu Jeon
> E-mail: [email protected], contact&iala-aism.org International
> Organization of Marine Aids to Navigation } (IALA)
> 10 rue des Gaudines,78100,St Germain en Laye,France
> 
> { The International Organization of Marine Aids to Navigation(IALA)
> is a leading intergovernmental organization specializing in Marine
> Aids to Navigation.
> 
> Established in 1957, IALA unites Marine Aids to Navigation
> authorities, manufacturers, consultants, and scientific and training
> institutions worldwide. Its mission is to harmonize Marine Aids to
> Navigation globally, ensuring safe, efficient, and cost-effective
> vessel movements while safeguarding the marine environment. On 22
> August, 2024, IALA officially transitioned from a non-governmental
> organization (NGO) to an intergovernmental organization (IGO } ).
> 
> [DRW:  The above change is a revision of the description of the organization. ]
> 
> Purpose:
> 
> ...
> 
> If adopting existing non-URN based identifier systems that includes
> characters not allowed by the URN syntax as specified in
> [RFC8141]. The representation of these characters should be handled by
> percent-encoding the character as specified in Section 2.1 of the URI
> specification [RFC3986].
> 
> { For the efficient use of the namespace, “mrn”, IALA has established
> a guideline G1143 on unique identifiers for maritime resources.
> 
> Rules for Lexical Equivalence:
> 
> In addition to the URN equivalence } rules defined in Section 2.1 of
> the URN specification [RFC8141]. Case normalization must be applied to
> both the OID and OSNID part before determining lexical equivalence.
> 
> [DRW:  Essentially, the above change is adding the paragraph "For the
> efficient ...".]
> 
> ...
> 
> Assignment:
>    
> Assignment of Organization IDs is done by filling out and sending in
> the registration template, as detailed on {
> https://www.iala-aism.org/technical/data-modelling-mrn/. IALA will
> ensure the uniqueness of organization } IDs by ensuring that an ID can
> only be assigned once.  Records of all successful registrations will
> be maintained in a public version control repository as detailed on
> the website.
> 
> [DRW:  The above change is essentially changing the URL.]
> 
> The assignment procedures for MRN strings under a particular
> Organization-specific namespace ID are the responsibility of the
> maintaining organization. The considerations provided by {
> https://www.iala-aism.org/technical/data-modelling-mrn } / as well as
> Section 6.4.3 of the URN specification [RFC8141] must be taken into
> account when defining the actual assignment procedure.  { The detailed
> procedures are defined in the IALA publication G1164 on the Management
> of Maritime Resource Name Organisation Identifiers } .
> 
> [DRW:  The above change is changing the URL and adds the sentence
> about IALA publication G1164.]
> 
> ...
> 
> Documentation:
> 
> For further documentation see {
> https://www.iala-aism.org/technical/data-modelling-mrn/ }
> 
> [DRW:  The above change is changing the URL.]
> 
> ----------------------------------------------------------------------

_______________________________________________
urn mailing list -- [email protected]
To unsubscribe send an email to [email protected]