[dispatch] Re: Request for DISPATCH consideration: draft-linkgenetic-linkid-uri

["Martin J. Dürst" <[e-mail]>]

Hello Christian, others,

There was a breakout session about this at W3C TPAC in Kobe in November 
2025, which I attended. See 
https://www.w3.org/calendar/tpac2025/breakout-sessions/ and search for 
LinkID, or see https://github.com/w3c/tpac2025-breakouts/issues/83 
(there was a github issue for each breakout session).

I haven't found any minutes or recordings of that session. As far as I 
remember, there were not too many attendees. At the end, I made two 
comments, more or less along the following lines (as far as I remember):
1) The proposal is from a single company, what are the guarantees that 
it can be implemented by others without problems?
2) (This comment was based on my experience as a W3C Team member) At the 
W3C, Tim Berners-Lee (who designed the Web and who has the most (in 
terms of years) experience with (broken) links) always stressed that 
persistence of links was a social problem, not a technical problem. Put 
in other words, http(s) links can be extremely stable if managed well; 
on the other hand, LinkID links can become unstable if not managed well.

I do not remember any other comments (from myself or others), but that 
doesn't exclude the possibility. Maybe Christian remembers more or has 
some more documentation of that event.

Regards,   Martin.

On 2026-09-28 23:59, Christian Nyffenegger wrote:
> Dear DISPATCH Chairs,
> I would like to request DISPATCH consideration and guidance regarding my Internet-Draft:
> The LinkID URI Scheme and Resolution Model
> draft-linkgenetic-linkid-uri-00
> https://datatracker.ietf.org/doc/draft-linkgenetic-linkid-uri/
> The document specifies the linkid: URI scheme and a resolution model for persistent, location-independent identifiers. The objective is to provide a stable identifier for a resource that remains independent of changes to its current network location and can be resolved to a current actionable URI.
> The linkid URI scheme is already provisionally registered with IANA.
> iana.org/assignments/uri-schemes/prov/linkid<https://www.iana.org/assignments/uri-schemes/prov/linkid>
> Following guidance from Ted Hardie on the URI Review mailing list, I am contacting DISPATCH to seek community guidance on the appropriate IETF path for progressing this work.
> My objective is to mature the specification through the appropriate standards process and, ultimately, to support permanent registration of the linkid URI scheme. I am open to the path that the IETF community considers most appropriate for this work.
> I would therefore appreciate the opportunity to discuss the proposal with DISPATCH and, if appropriate, present the draft at an upcoming DISPATCH meeting.
> I am also happy to revise the Internet-Draft based on community feedback. In particular, I will address the interoperability considerations raised during URI review regarding existing uses of the term “LinkId” within URI constructions.
> Please let me know what you recommend as the next step and whether you would like any additional material from me in advance.
> Best regards,
> Christian Nyffenegger
> Founder & CEO
> ---
> 
> Link Genetic GmbH (CH)
> Christian Nyffenegger
> Leugrueb 21
> 8126 Zumikon
> Switzerland
> Company Phone CH: [phone]
> 
> Link Genetic Inc.(US)
> 26 Broadway
> Suite 934
> New York, NY 10004
> USA
> Company Phone US: [phone]
> 
> E-Mail: [e-mail]<mailto:[e-mail]>
> Internet: www.linkgenetic.com<http://www.linkgenetic.com/>
> Book us: https://calendly.com/linkgenetic
> 
> This message (including any attachments) is confidential, for the exclusive use of the intended recipient and may contain privileged information. If you are not the intended recipient, retention, dissemination, distribution, copying or otherwise making use of this message is strictly prohibited. Please be kind enough to notify the sender immediately by e-mail if you have received this message by mistake, and delete it from your system. Thank you.
> 
> 
> _______________________________________________
> dispatch mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]