W3C home > Mailing lists > Public > www-rdf-calendar@w3.org > May 2001

Re: RDF calendar schemas

From: Geoff Chappell <geoff@sover.net>
Date: Wed, 30 May 2001 04:45:53 +1000
Message-ID: <016001c0e86f$97114840$0400a8c0@GSC866>
To: "Libby Miller" <Libby.Miller@bristol.ac.uk>, "Greg FitzPatrick" <greg.fitzpatrick@metamatrix.se>
Cc: "www-rdf-calendar" <www-rdf-calendar@w3.org>
> sub events
> Finally, I found it very useful in modelling the XMLEurope data to have
> the notion of one event being contained within another. For example,
> a track is a kind of event which might be spread over one or more days
> at a conference, which contains various presentations, also events. Or
> is a track is too broad for you, a session might contain more than one
> event, and may plausibly be considered an event in itself. The
> vaclendar is a container for events as I see it. We'd still need an RDF
> property to indicate somehow that there was more data about the event
> available (maybe rdf:seealso would do?).
> Does this make sense?
> cheers
> Libby

You could accomplish this also if you had the ability to constrain event
start/end times relative to other events start/end times (or to absolute

For example:
    session1 start time: 10:00 am
    session1 end time:  (= session1 start + 8 hours)

    event 1 start time: ( = session1 start)
    event 1 end time: (=event1 start + 1 hr)

    event 2 start time: (= event1 end)
    event 2 end time: (= event2 start + 1 hr)

You can imagine other types of constraints...

    event 7 start time: (= event 6 end time)
    event 7 end time: (>= event 7 start time + 1 hr) and (< session1 end

...that could provide the basis for at least some limited automated

Have constraints of this nature been discussed at all (or are they already
supported in iCal)?


Geoff Chappell
Received on Wednesday, 30 May 2001 18:05:01 UTC

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