- From: Giles Hogben <giles.hogben@jrc.it>
- Date: Wed, 10 Jul 2002 10:22:21 +0200
- To: "Joshua Allen" <joshuaa@microsoft.com>, "Jonathan Borden" <jonathan@openhealth.org>, <www-rdf-logic@w3.org>
How about: A. The author of this document says "There are aliens in my house" B. The author of this document says "I don't have a house" If RDF model implies all triples are asserted and does not specify an author in this implicit assertion, unless we assume it is the author of the document, then if I want to use a triple to say that another is not true, I am having to say something like that. > So what is the meaning of assertion in RDF? If triples are, as you say, > unasserted, what is the meaning of > "This document describes a model theory for RDF(S) which treats the > language as simple assertional language, in which each triple makes a > distinct assertion and the meaning of any triple is not changed by adding > other triples" Hold on. Just because someone makes an assertion does not mean that you believe it. How wonderful it would be if I could just drop one simple RDF triple onto the Internet (joshuaa@microsoft.com isThe kingOfWorld) and have that become true. Any legitimate system is going to have to decide which triples to trust and which to distrust (and in some cases, place on a continuum of trustworthiness). Using triples to assert trustworthiness (or veracity) of other triples does not at all change the meaning of the original triple. It simply gives you additional information for choosing which triples to believe. Example: A. Joe says "There are aliens in my house" B. John says "Joe doesn't have a house" The *meaning* of statement "A" is clear. Statement "B" does not in any way affect the meaning of statement "A". In fact, it doesn't even affect the truth of statement A. The listener is left to make a judgment call about which assertion he accepts and which he rejects. Rejecting a triple is not the same as changing its meaning.
Received on Wednesday, 10 July 2002 04:17:48 UTC