> > That's different to a value that *is* a URI. The example given is for
> > dc:source. The example is saying that the source is the
> resource identified
> denoted
> > by the URI, not that the source IS the URI.
>
>
> Aaaahhhh! The dust settles down.
>
> You actually want to model a different situation!
>
> When i understand correctly you
> want to use http://purl.org/dc/terms/URI
> as an encoding scheme for literal values.
>
> That is what you point to with use of rdf:value
> (poor mans structured values).
> When that model matches your case...
Not quite. Use of dcterms:URI would be something I would agree with, as
would using the URI as a literal value in the construction
<dc:identifier>http://www.example.com/</dc:identifier>, or as a literal
value in the construction <dc:identifier
rdf:value="http://www.example.com"/>. However such use isn't what I'm
getting at.
I'm objecting to the use of the URI like the Example in 2.3.8.1. I do not
believe that the fact that RDF makes use of URIs in itself makes that use
directly equivalent to the use of URIs as an allowed value of Dublin Cores
Identifier. I think the example above, and subsequent examples, are
suffering from "level-confusion" and confuse the use of URIs in RDF with the
use of URIs in Dublin Core. Contrast the following:
<rdf:Description rdf:about="http://www.example.com/">
<dc:identifier>http://www.example.com/</dc:identifier>
</rdf:Description>
<rdf:Description rdf:about="http://www.example.com/">
<dc:identifier rdf:resource="http://www.example.com/"/>
</rdf:Description>
The first has a graph
(http://www.w3.org/RDF/Validator/ARPServlet.tmp/servlet_10239.png should
have this graph for the next 24 hours) with an ellipse labelled
http://www.example.com/ with an arrow marked
http://purl.org/dc/elements/1.1/identifier going to a rectangle labelled
http://www.example.com/. In other words "the resource identified by
'http://www.example.com/' is identified by the string
'http://www.example.com/'". Tautology!
The second has a graph
(http://www.w3.org/RDF/Validator/ARPServlet.tmp/servlet_10241.png should
have this graph for the next 24 hours) with an ellipse labelled
http://www.example.com/ with an arrow going from it and back to itself. In
other words "the resource identified by 'http://www.example.com/' is
identified by the resource identified by 'http://www.example.com/'". Pretty
unlikely!
> The rdf:Alt example is about a context, where
> one wants to express the meaning carried nicely by rdf:Alt .
How does the rdf:Alt act as an identifier?
|