W3C home > Mailing lists > Public > www-rdf-calendar@w3.org > December 2002

RE: iCalendar recurring schedules

From: Graham Klyne <GK@ninebynine.org>
Date: Sun, 15 Dec 2002 11:00:32 +0000
Message-Id: <>
To: Rahul Singh <kingtiny@cs.cmu.edu>
Cc: "'www-rdf-calendar'" <www-rdf-calendar@w3.org>

Hi Rahul,

I think we mostly concur.  One follow-up point (from memory, so apologies 
if I get some details wrong)...

At 04:07 PM 12/13/02 -0500, Rahul Singh wrote:

>Your comments definitely got me thinking. Here are some caveats ...
> > 1.  Use of ical:DATE as a property (on VCALENDAR object);  I
> > believe it's
> > declared as a class.
>I assume the ical:DATE you refer to is under the ical:UNTIL property
>that gives the limit of the recurrence of the schedule. Looking at the
>ontology, the Domain of #UNTIL (property under RECUR) is #RECUR and the
>range is of type class #TimeEntry. And DATE is a subclass of TimeEntry.
>Now this seems valid according to the intology but im not sure if I
>should have a property under DATE which actually holds the value rather
>than put the value under in the DATE tags themselves as follows...
>The comment in the Ontology mentions using the above format or the
>XMLSchema datatypes. Maybe what I'm confused about is whether leaf nodes
>of an RDF graph should always be properties (intuitively this seems to
>be the way to go, but Im not sure).

I think an extra property should be inserted somewhere (e.g. like the 
VEVENT and VEVENT-PROP pattern).  The *leaf* nodes should be nodes, not 
properties.  When using a literal, the element *content* is the node.  When 
using a typed-node, the entire element is the node; e.g.



       <ex:Date-value rdf:about="ex://example.org/date/20020502">

See also:



Graham Klyne
Received on Sunday, 15 December 2002 05:55:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:14:11 UTC