[urn] Re: URN Namespace Assignment

[Ted Hardie <[e-mail]>]

Hi Q,

I would suggest making the registration when the standards work on the
syntax is functionally complete.  That way the review can validate the
syntax and proposed resolution methods prior to any large scale
implementation or deployment.  Given the request is coming from an SDO, I
think it pretty likely that the namespace will eventually be approved, but
it is important that the group validate the syntax and the other aspects of
the registration.  So I recommend registering prior to things being set in
stone, but late enough  that there is a clear proposal.

best regards,

Ted Hardie


On Thu, Sep 17, 2026 at 9:57 AM Q Misell <[e-mail]> wrote:

> Hi,
>
> We're still in the process of writing the standard; as such, it doesn't
> really exist yet. Would it be better to progress on the assumption that
> such a URN namespace could be registered when we're done, and resubmit when
> we have published the final standard?
>
> Mit freundlichen Grüßen,
> Q Misell (sie/ihr - she/her)
>
> 🌲 Please consider the environment before using AI to process this email.
> --
> Max-Planck Institut für Informatik
> Fon [phone] <+49%20681%2093253547>
> Forschungsgruppe Internet Architecture (INET)
> Campus E1.4 514, 66123 Saarbrücken
>
> Am 17.09.2026 um 10:04 schrieb Ted Hardie <[e-mail]>:
>
> Hi Q,
>
> Are you requesting registration under the procedures documented in Section
> 6.3 or RFC 8141, given that this is for CEN-CENELEC? If so, please update
> this to point to the document where the NID will be defined.
>
> As it stands, this registration does not define the syntax to be used, and
> it can't really progress without that.
>
> regards,
>
> Ted Hardie
>
> On Thu, Sep 17, 2026 at 8:11 AM Q Misell <qmisell=
> [e-mail]> wrote:
>
>> Hello,
>>
>> I'm involved in the Barcoded Ticketing for Public Transport (
>> https://bt4pt.eu) project at CEN-CENELEC, and would like to request the
>> preliminary registration of a URN namespace for our purpose in the
>> standard. Please see below the registration template.
>>
>> Namespace Identifier:  bt4pt
>>
>> Version:  1
>>
>> Date:  2026-09-17
>>
>> Registrant:  CEN-CENELEC [e-mail]
>>
>> Purpose:
>> URNs under this namespace will be assigned to entities such as transport
>> organisations, stops, routes, lines, etc. They will be used for
>> interoperability across public transport in Europe, processed by ticket
>> issuing machines and ticket validation devices. The Open Sales and
>> Distribution Model (https://osdm.io) already makes use of URNs in its
>> APIs under the urn:uic: namespace, thus a URN for BT4PT purposes will
>> compliment the UIC's namespace and allow interoperability.
>>
>> Syntax:
>> The exact syntax is as yet undefined, and will be written as part of the
>> in-progress CEN-CENELEC standard.
>>
>> Assignment:
>> Assignment will be managed by the CEN-CENELEC, in the process of
>> publishing standards documents defining sub-ranges of this URN namespace. A
>> sub-range may, in turn, be delegated to some other registration authority,
>> or reference a code-list maintained by another authority, such as the
>> European Union Agency for Railways.
>>
>> Security and Privacy:
>> All identifiers will be assigned for publicly available information only,
>> there will be no possibility for leakage of private information nor any
>> danger for directory harvesting.
>>
>> Interoperability:
>> There are no foreseen interoperability issues.
>>
>> Resolution:
>> A resolution service does not yet exist, but will be defined as part of
>> the in-progress CEN-CENELEC standard.
>>
>> Documentation:
>> Use of this namespace will be documented as part of the in-progress
>> CEN-CENELEC standard.
>>
>> Mit freundlichen Grüßen,
>> Q Misell (sie/ihr - she/her)
>>
>> 🌲 Please consider the environment before using AI to process this email.
>> --
>> Max-Planck Institut für Informatik
>> Fon [phone] <+49%20681%2093253547>
>> Forschungsgruppe Internet Architecture (INET)
>> Campus E1.4 514, 66123 Saarbrücken
>>
>> _______________________________________________
>> urn mailing list -- [e-mail]
>> To unsubscribe send an email to [e-mail]
>>
>
>