Once again I find myself debating the difference between a name and an identifier. I know each when I see it, but there are grey areas. For example, is 'Tungsten' a name or an ID for element 74?
16
18
it's the usual "it depends" storyline. i think names are mostly a social and loose construct, whereas identifiers often are a technical and much more constrained one.
1
2
Replying to @dret @philarcher1
+1 to what @dret said. In some context, 'Tungsten' would be a perfectly valid identifier for this (and conversely, in some context 'Element 74' might refer to something completely different...). IRIs, of course, make most of the context explicit in their structure.

Mar 4, 2022 · 8:02 AM UTC

1
1
Replying to @pchampin @philarcher1
you can make any identifier space mildly self-describing if that's what you design for. speaking of URI/IRI, it's a rather simple space because all you have is a scheme and then some scheme-specific stuff. that's a great starting point, but not a lot of context info per se.
1