3 ms·
A URI (indicator) is a unique reference to a resource, of some kind. One type of URI is a URN (name), e.g. doi:10.5281/ZENODO.31780 - a unique name for a resou
by amiga386 3y ago
A URI (indicator) is a unique reference to a resource, of some kind.
One type of URI is a URN (name), e.g. doi:10.5281/ZENODO.31780 - a unique name for a resource, but no instructions on how to obtain it
Another type of URI is a URL (location), e.g. https://doi.org/10.5281/ZENODO.31780 https://doi.org/10.5281/ZENODO.31780 - same resource in this case, but now we know we can obtain it via the HTTPS protocol
Few people call the address in the web browser a "URI" any more, even though technically it is one. Your JDBC URL is a URL, as is "mailto:president@whitehouse.gov" or "tel:+44-118-999-881-999-119-7253"
- hot_gril 3y agoI get what they were going for here, but ehhh, the only useful designation is URL. And even acknowledging that URIs exist, it's overly broad to refer to http:// http://... as one. I remember seeing "URI" a lot some ObjC libraries to refer to URLs, it was just confusing.
- yencabulator 3y ago> the only useful designation is URL Yup, URNs were part of the "semantic web" craze, so you could e.g. record facts about a book with isbn: scheme URNs. Nothing much consequential ever came from all that committee busywork, but people got to pontificate and sound smart talking about reification and so on. I still wonder who paid for all of it. https://en.wikipedia.org/wiki/Resource_Description_Framework https://en.wikipedia.org/wiki/Resource_Description_Framework
- hot_gril 3y agoSeems like URNs fit into the XML/XMPP/SOAP genre, old bloated stuff. For some reason there had to be a whole fad for people to realize you can just shove data into JSON and it's good enough.