L is locator, I is identifier. URLs are a subset of URIs. Both start with a schema (something:...), but URIs lack the information about the location and way to

L is locator, I is identifier. URLs are a subset of URIs. Both start with a schema (something:...), but URIs lack the information about the location and way to get at a resource. The canonical example for identifier-but-not-location is an ISBN or DOI. That interpretation however requires a very peculiar interpretation of "location", because imho "where can I read about that" can precisely be answered by "ISBN ...". The usual copout "but you don't know where the next library will be" also makes all the traditional URLs non-locations, because you then also don't always know where the next browser is or how to operate it. The rest of the responsible RFC is also not very useful: https://danielmiessler.com/study/difference-between-uri-url/ https://danielmiessler.com/study/difference-between-uri-url/