W3C home > Mailing lists > Public > semantic-web@w3.org > March 2005

RE: true/false in RDF?

From: Joshua Allen <joshuaa@microsoft.com>
Date: Sun, 13 Mar 2005 21:48:42 -0800
Message-ID: <0E36FD96D96FCA4AA8E8F2D199320E52047E4FA1@RED-MSG-43.redmond.corp.microsoft.com>
To: "Jeremy Wong" <jeremy@miko.hk>, <semantic-web@w3.org>
Yeah, that's what I intended to express with my first example - if you
use a literal, the literal is absolutely meaningless without type


Why not just use URIs which mean "true" and "false" and do away with
typing?  The only advantages I can see for typing are imaginary (compile
time/run-time checks?!?!) and the disadvantage is real.



From: Jeremy Wong [mailto:jeremy@miko.hk] 
Sent: Sunday, March 13, 2005 9:35 PM
To: Joshua Allen; semantic-web@w3.org
Subject: Re: true/false in RDF?


I am not too familar with N3 notation about datatype, therefore I
provide my example in RDF/XML


<rdf:Description rdf:about="http://foobar/page.html"




We have typed literal already. Why do you still consider object value?




	----- Original Message ----- 

	From: Joshua Allen <mailto:joshuaa@microsoft.com>  

	To: semantic-web@w3.org 

	Sent: Monday, March 14, 2005 12:16 PM

	Subject: true/false in RDF?


	I've decided that I want to use URI object values for my Boolean
triples, rather than the literals "true/false".  In other words, instead


	http://foobar/page.html  urn:myterms:isCached   "true"


	I want to use:


	http://foobar/page.html  urn:myterms:isCached


	I can find zero examples of the latter; only the former.  But I
think the latter is right.  Why am I wrong?
Received on Monday, 14 March 2005 05:48:41 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:44:52 UTC