Let's talk about how URI syntax works. There is a scheme name such as HTTP, followed by a colon then scheme specific part. The semantics of the part are determined by the specifications that govern each of the schemes. The URI forces the scheme to adhere to a generic syntax which reserves certain characters for special purposes without saying always what they are. It also forces restrictions to the scheme specific part to provide a degree of consistency when it has a hierarchical structure. Both URI and URL have a shared history. There have been many refinements over the years to each.
There are also other definitions that go along with a URI and one of them points to URI reference. This is another string that represents a URI and is identified as such. URI is also used to identify mechanisms used to access the resource, the specific name of the resource and the computer that it is housed in. The address is divided into parts separated by a slash and a period. The first part is the protocol, the second is the computer where it is stored, and the third part indicates exact location of the document. The last part is the name of the document.
So you can see how URI would be used in an RSS feed. When you put in the information that the RSS feed will use, here is an example of how it would be used. HTTP: - which is Hyper Text Transfer Protocol, then the www, which means the World Wide Web. The next part is exactly where the document is stored which would be revision-technology.com for example. The last part is the document itself which would be website-support.html. While this is an indicator of a URL or uniform resource in the computer world, part of this is indeed a URI.
