Re: context of dc:identifier

Pete Johnston wrote:
> Reto said:
>
>   
>> if the datatype is the context, and given that two literals 
>> with different datatypes cannot be equals (not sure if this 
>> is true for custom datatypes) dc:identifiers is an 
>> owl:inverseFunctionalProperty, right?
>>     
>
> I'm not sure that's the case. I think DCMI is pretty vague about what it means by "context" here ;-)
>
> But generally I think
>
> doc:x dc:identifier "12345" .
>
> and
>
> doc:y dc:identifier "12345" .
>
> is not - in the global "context" - sufficient to conclude that doc:x and doc:y are the same resource, and that holds even with a typed literal as object.
>
> That's always been my assumption, anyway.
>   
If the context is the datatype as Bruce has been suggested on the DCMI
list then I think the part "within a given context" of the definition of
dc:identifier[1] is meaningless in the context of RDF. Otherwise, if
there are Contexts in RDF I would like to know more about them, if there
aren't it dc:identifier should probably not be used in RDF especially
not in an RDF primer.

reto


1."Identifier: An unambiguous reference to the resource within a given
context." quoted on http://www.w3.org/TR/rdf-primer/


-- 
Reto Bachmann-Gmür
Talis Information Limited

Book your free place now at Talis Insight 2007 www.talis.com/insight
Find out more about Talis at www.talis.com
Shared InovationTM
 
Any views or personal opinions expressed within this email may not be those of Talis Information Ltd.

Received on Wednesday, 5 September 2007 16:27:50 UTC