- From: Peter F. Patel-Schneider <pfps@research.bell-labs.com>
- Date: 2003年2月05日 10:55:22 -0500 (EST)
- To: www-rdf-comments@w3.org
- Message-Id: <20030205.105522.12923177.pfps@research.bell-labs.com>
The RDF primer, in Section 2.2, states Using URIrefs as subjects, predicates, and objects in RDF statements allows us to begin to develop and use a shared vocabulary on the Web, reflecting (and creating) a shared understanding of the concepts we talk about. For example, in the triple ex:index.html dc:creator exstaff:85740 . the predicate dc:creator, when fully expanded as a URIref, is an unambiguous reference to the "creator" attribute in the Dublin Core metadata attribute set (discussed further in Section 6.1, a widely-used set of attributes (properties) for describing information of all kinds. The writer of this triple is effectively saying that the relationship between the Web page (identified by http://www.example.org/index.html) and the creator of the page (a distinct person, identified by http://www.example.org/staffid/85740) is exactly the concept identified by http://purl.org/dc/elements/1.1/creator. Moreover, anyone else, or any program, that understands http://purl.org/dc/elements/1.1/creator will know exactly what is meant by this relationship. This appears to me to state that the meaning of tokens in RDF *is* their commonly agreed on meaning, regardless of how that meaning is specified. If so, this means that RDF reasoners are responsible for implementing this meaning. Is this actually the case? If so, how can RDF reasoners be implemented? If not, please explain what the above quote means.
Received on Wednesday, 5 February 2003 10:55:32 UTC