The complexity arises if someone other than OCLC (?) asserts something about a VIAF URI.
So, for example (and, please note, I’ve used a different URI, because, well, the one your provided is problematic for my purpose here), what if /I/ asserted:
http://viaf.org/viaf/64055977/ skos:note “He smelled very badly, all the time.”
On the surface it looks like VIAF/OCLC said Raphael smelled badly, all the time because, provenance-wise, the domain tracks back to OCLC. In reality, I said it, but you cannot tell.
If we use global URIs, and additional statements are made against those, then something like this could happen.
From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Smith-Yoshimura,Karen
Sent: Thursday, July 10, 2014 1:40 PM
To: [log in to unmask]
Subject: Re: [BIBFRAME] Bibframe and Linked Data (Authorities)
>There's been lots of talk about provenance and the like in a global graph of data, but I feel most of those discussions rely on fairly technical mechanisms, the complexity of >which outweigh the simplicity of minting one's own URI. (Also, the provenance statements will need their own URIs!)
Doesn’t http://viaf.org/viaf/54202464 show the provenance is VIAF? What’s complex about this?