Consider the following 3 individual markers:

 _003758FBD8D74BC9986772C568D4484C

 _0282C07E5EED4639B3CABAF87D3CAA91

 _139C77A9036C47948B1D1E88DD3BF0E3

_003758FBD8D74BC9986772C568D4484C,
        _0282C07E5EED4639B3CABAF87D3CAA91,
		        _139C77A9036C47948B1D1E88DD3BF0E3
				

Now lets say that in a WWW oriented interpretation,

these markers denote HTTP URIs:

 let _003758FBD8D74BC9986772C568D4484C denote http://person.com/JohnBlack
 
 let _0282C07E5EED4639B3CABAF87D3CAA91 denote http://properties.com/ssn

 let _139C77A9036C47948B1D1E88DD3BF0E3 denote http://ssnvalues.com/123456789

In another IRS oriented interpretation,

let these markers denote objects of the real world:

 let _003758FBD8D74BC9986772C568D4484C denote John Black

 let _0282C07E5EED4639B3CABAF87D3CAA91 denote US gov social security account #

 let _139C77A9036C47948B1D1E88DD3BF0E3 denote 123456789

Now it seems to me that the expected power of applied RDF is just this
metaphorical relationship. The UUID has two separate denotations under two
different interpretations. And this similarity is what gives relevance for
the web interpretation. What we want is for all our statements about
_003758FBD8D74BC9986772C568D4484C to be true under both interpretations.

Of course, in RDF HTTP URIs are used as UUIDs. But while they are used that
way, they are no longer HTTP URIs, but just unique, opaque identity markers. I still
think that in that case, we are using these HTTP URIs as UUIDs to denote the HTTP URIs
used as HTTP URIs. I mean in a WWW oriented interpretation:

 let "http://person.com/JohnBlack" denote http://person.com/JohnBlack
 
 let "http://properties.com/ssn" denote http://properties.com/ssn

 let "http://ssnvalues.com/123456789" denote http://ssnvalues.com/123456789

So even in this case, it seems that the triple with the UUID URI gets its relevance
in the WWW world, by being true in parallel with the interpretation at IRS. The UUIDs
denote two different things: a set of HTTP URIs in the web world and a Person, id #,
and digit string value in the IRS world.

So having two meanings is a good thing about URIs in RDF.