I'm confused too. As I understand it, as far as RDF is concerned:
http://id.loc.gov/authorities/sh2008115565#concept
and
http://id.loc.gov/authorities/sh2008115565
are _different identifiers_. So either id.loc.gov is using different
identifiers to refer to the same thing; in which case maybe this is
accidental on id.loc.gov's part, or maybe there's a reason for that we
don't understand. (There is in general no prohibition on using different
identifiers to refer to the same thing, but it IS confusing. Using one
identifier to refer to two different things, on the other hand, is
prohibited). OR, those two URIs don't in fact refer to the same thing,
they refer to two different things, but we don't understand what. OR
we're just even more confused.
We should ask Ed maybe? I am also confused. But personally hash URI's
often confuse me.
Jonathan
Karen Coyle wrote:
> Quoting Jonathan Rochkind <rochkind_at_JHU.EDU>:
>
>
>> Yeah, that's a confusing thing. The RDF world seems to like using hash
>> URIs to represent things. As far as RDF is concerned, the URI's
>> uniqueness is determined including the hash. Two URIs identical except
>> that they end in two different hashes are two different identifiers as
>> far as RDF is concerned.
>>
>
> So in the example that Ross gave,
>
> <rdf:Description
> rdf:about="http://id.loc.gov/authorities/sh2008115565#concept">
>
> identifies the same thing as:
>
> <rdf:Description rdf:about="http://id.loc.gov/authorities/sh2008115565">
>
> ?
>
> But
>
> <skos:inScheme rdf:resource="http://id.loc.gov/authorities#conceptScheme"/>
> <skos:inScheme rdf:resource="http://id.loc.gov/authorities#geographicNames"/>
>
> do not either identify the same thing as:
>
> <skos:inScheme rdf:resource="http://id.loc.gov/authorities"/>
>
> ?
>
> If so, then, yes, that is very confusing.
>
Received on Wed Nov 11 2009 - 14:42:21 EST