Hash and Slash in URI

There is URI using slash(/) for specific resources.

http://purl.org/dc/elements/1.1/title

There is URI using hash(#) for specific resources.

http://www.w3.org/1999/02/22-rdf-syntax-ns#type

The TAG resolution takes the pragmatic view that both are OK. Then, what's the difference between those expressions?

While you are calling URI with slash for a specific resource like "http://purl.org/dc/elememts/1.1/title", it will be redirected from the URI for the thing to the URI for the document about it.

With hash, the information is easy to publish using an editor for RDF files and since the client looking up the URI just strips of the right part and get access to the document about it (http://www.w3.org/1999/02/22-rdf-syntax-ns), the speed of processing time is an advantage.

The difference between hash and slash in URI