The ID suffix was added because I use external tools to add notes to my vault so I needed a means to ensure there would never be a collision. For example, Alfred. If I accidentally typed the name of a note that already exists into it I didn’t want it to accidentally overwrite an existing note,

Challenges There was little success in attracting dues-based members. There was some interest in using the BRIDGE ID and its associated data as an open data resource, by not for pay. Beyond the original partners, we found few organizations and companies that wanted to use the BRIDGE ID for data interoperability to keep databases synchronized and current. It was hard to penetrate the market for unique organizational identifiers among established and well-funded vendors such as LEI, DUNNS, and a large number of country-based identification systems world-wide. The level of manual effort necessary to curate and deduplicate country-based organizational data internationally far exceed our funding expectations and challenged our sustainability.

Th part of an URI after the # is called "fragment" and is by definition only available/processed on client side (see https://en.wikipedia.org/wiki/Fragment_identifier).

The main problem is that the browser won't even send a request with a fragment part. The fragment part is resolved right there in the browser. So it's reachable through JavaScript.

The simple problem that I see with fragment identifiers is that their existence and functionality relies completely on the developer rather than the browser. Yes, the browser needs to read and interpret the identifier and identify the matching fragment. But if the developer doesn’t include any id attributes in the HTML of the page, then there will be no identifiable fragments. Do you see why this is a problem? Whether the developer has coded identifiers into the HTML has nothing to do with whether or not the page actually has fragments. Virtually every web page has fragments. In fact, sectioning content as defined in the HTML5 spec implies as much. Every element on the page that can contain content can theoretically be categorized as a “fragment”.

This means that, regardless of what the developer has done behind the scenes in the HTML, all HTML fragments on that page should be identifiable by external referrers.

There is a fundamental weakness in the name attribute, which the id attribute addresses: the name attribute is not required to be unique. This is OK for forms where you can have multiple elements with the same name, but unsuitable for the rest of the document where you are trying to uniquely identify an element.

HTML fragment identifiers, as defined in the registration for the text/html media type [RFC2854] operate on id attributes and (now less frequently) the name attribute of the a, applet, frame, iframe, img and map elements.

global web identifiers of legislation

Available at: https://cioms.ch/wp-content/uploads/2017/01/WEB-CIOMS-EthicalGuidelines.pdf.

OPP1151904

ISBN

Why do organisation identifiers matter? Lessons from the healthcare sector