- From: Jonathan Borden <jonathan@openhealth.org>
- Date: Mon, 28 Oct 2002 10:02:12 -0500
- To: <www-rdf-comments@w3.org>
- Cc: <www-rdf-logic@w3.org>
A slight correction to my message
http://lists.w3.org/Archives/Public/www-rdf-comments/2002JulSep/0064.html
[[
Reading http://lists.w3.org/Archives/Public/www-rdf-logic/2002Jul/0094.html,
I see that "Prefer A to be yes" is listed as "none".
Apparently I wasn't clear enough.
I don't think the question is properly worded/constructed BUT if I have to
choose an answer:
A MUST BE YES.
]]
I don't mean to imply that the question itself isn't properly constructed,
it is. What I mean is that I don't agree that the choices MUST BE either/or.
and a small correction to below at the end:
[[
That is IF the answers to each part of A MUST BE the same AND
"
Test A:
<Jenny> <ageInYears> "10" .
<John> <ageInYears> "10" .
"
THEN the ageInYears("Jenny") === ageInYears("John") === "10" by any
reasonable interpretation of this test. If there is any one thing that might
be interpreted by RDF datatypes _at least_ this must be interpreted.
]]
<Jenny> <ageInYears> "10" .
<John> <ageInYears> "10" .
=>
ageInYears("Jenny") = ageInYears("John")
but they don't both necessarily equal the string "10" by any reasonable
interpretation. That is to say I am not (at all) opposed to RDF datatyping,
but I would be opposed to not having this most simple comparison be EQUAL.
This is perhaps the only sort of equality that I would expect to be true
_regardless_ of which datatyping solution is chosen --- it is also true in
the present situation, i.e. under RDF as it is today!
Jonathan
Received on Sunday, 28 July 2002 10:17:42 UTC