Why are ids a thing ?

[D-Maxwell]

While conceptualizing Crated, I heavily took inspiration from HTML, and more specifically, from its element classification.
In HTML, an element may be accessed by its tag, id, or class. As I had in mind a somewhat similar system, maybe even one that could be translated somehow, I set my mind into such a system, without really thinking about the id part that much; which lead me to implement it, (wrongly), despite it not being needed at all.

What I mean by wrongly, is that ids are supposed to be unique; in that case, what would be the point of having multiple ids on a single object? Since no cross-reference is possible (i.e. two objects sharing an id), might as well join the two ids into one, or make it a class if it is intended to be used by more than a single element. What even is this obsession with singularities? One is just a number, a value, it doesn't hold much value in this scenario; and for simplicity reasons, as to not over convolute the project, I think I will be dismissing ids entirely, not just their ability to be multiple on a single object. (i.e. storing ids as a list of strings)

In the end, the behaviour of a class can absolutely supersede the use of an id. The only point of ids in HTML is for headers and really just links.
Except, this feature, which is so far the only reason for ids to even exist in the first place, will not be implemented this way into Crated.
I obviously still need quite some time to complete the potential implementation of links and references, as it is still nothing more than an idea in the back of my mind, and a few notes here and there.

TL ; DR – Bye bye ids, long live classes !