Skip to content

Commit

Permalink
small rewording about diff among URI/URL/URN
Browse files Browse the repository at this point in the history
  • Loading branch information
mpsaloha committed Jul 15, 2019
1 parent 7c76603 commit 28a9f29
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/eml-faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -425,7 +425,7 @@ v2.1.0.

**Q:** Explain the difference between an URI and a URL. (context: sample URIs look a lot like a URL. What makes it a URI?)

**A:** The distinctions among URIs (Uniform Resource Identifiers), URLs (Uniform Resource Locators), and URNs (Uniform Resource Names), relate to differentiating the functionalities of *identifying* a Resource, as opposed to *locating* a Resource, or doing both. URLs are all URIs (with some edge case exceptions subject to argument), and URNs are also URIs. In many cases, URIs serve both to name and locate a Resource. Within the vision of the Semantic Web, URIs are ideally unique, persistent URNs identifying some Web Resource, that can also serve to locate and retrieve (dereference) a representation of that Resource (URLs). The formal specification for these terms and what they mean is found in the Internet Engineering Task Force's (IETF's) *Request for Comments* RFC 3986, section 1.1.3 (<https://tools.ietf.org/html/rfc3986#section-1.1.3>). Another acronym one may encounter with increasing frequency is IRI (Internationalized Resource Identifier) that simply extends the concept of a URI to include full Unicode character set, rather than just ASCII in its construction (<https://tools.ietf.org/html/rfc3987>)
**A:** The distinctions among URIs (Uniform Resource Identifiers), URLs (Uniform Resource Locators), and URNs (Uniform Resource Names), relate to differentiating the functionalities of *identifying* a Resource, as opposed to *locating* a Resource, or doing both. URLs are all URIs (with some edge case exceptions subject to argument), and URNs are also URIs. In many cases, URIs serve both to name and locate a Resource. Within the vision of the Semantic Web, URIs are ideally unique, persistent URNs identifying some Web Resource, that can also serve to locate (URL) and retrieve (dereference) a representation of that Resource. The formal specification for these terms and what they mean is found in the Internet Engineering Task Force's (IETF's) *Request for Comments* RFC 3986, section 1.1.3 (<https://tools.ietf.org/html/rfc3986#section-1.1.3>). Another acronym one may encounter with increasing frequency is IRI (Internationalized Resource Identifier) that simply extends the concept of a URI to include full Unicode character set, rather than just ASCII in its construction (<https://tools.ietf.org/html/rfc3987>)


**Q:** oveeview (“When are ID’s required in the EML”) - context: annotations
Expand Down

0 comments on commit 28a9f29

Please sign in to comment.