W3C home > Mailing lists > Public > public-owl-wg@w3.org > November 2007

Re: unnamed datatypes in RDF/XML

From: Alan Ruttenberg <alanruttenberg@gmail.com>
Date: Wed, 21 Nov 2007 01:46:58 -0500
To: Bijan Parsia <bparsia@cs.man.ac.uk>
Message-Id: <AE7BB2D1-26E2-4A97-AAAB-E091CF8BC47A@gmail.com>
Cc: public-owl-wg Group WG <public-owl-wg@w3.org>
When  you initially described what you were doing, I thought you were  
saying that something happened during some interval, as in "walks  
from door to table" during (all) the time  between, e.g., t=2.7  
seconds to t=8.9seconds.

I am reading what you write below as you saying the events you are  
annotating are instantaneous, and you are using the datatypes to  
represent your uncertainty about when they exactly happened.

Do I have that right?

-Alan

On Nov 20, 2007, at 4:19 AM, Bijan Parsia wrote:

>> BTW, Bijan, why would you create a different data type for each  
>> time interval you annotate, rather than defining a single  
>> "interval" datatype and then using a bunch of values from it?
>
> Because I want to say
>
> 	event1: occursAt some (=>2 and <=5).
> 	event2: occursAt some (=>4 and <=6).
> 	event3: occursAt some (=>7 and <=10).
> ...
>
> (Assume occursAt is functional.)
>
> I.e., I know events occur within certain intervals, i.e., I know  
> the boundaries of the intervals. There is no single datatype I can  
> instantiate. Even if I had lists, I wouldn't have the right semantics.
>
> Btw, I can infer that there must be at least two distinct events  
> from the above. I can do this even if I change the third line to:
> 	
> 	event3: occursAt some (=>6 and <=10).
>
> (Since event2 can be = event 1 *or* event3, but not both.)
>
> (If you have different sensors and some event detector, you might  
> have them reporting the "same" events with somewhat different  
> intervals.)
>
> Cheers,
> Bijan.
>
Received on Wednesday, 21 November 2007 06:47:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:13:27 GMT