[www-rdf-calendar] <none>

Jonas,

I'm trying to encapsulate the way you represented the iCalendar parts of
SKIcal in

http://lists.w3.org/Archives/Public/www-rdf-interest/2000Aug/0109.html

using the iCalendar examples.

I wondered if you had a few minutes to look at the page of examples

http://ilrt.org/discovery/2001/06/schemas/skical/examples/

and tell me what you think? I've put a few questions that came up at the
bottom of the page, namely:

Should Organizer and Attendee be made into objects, like SKICal
person? (because an Organizer and Attendee may have roles, rsvp etc
attatched to them).

Should mailto be a uri? what about uuid? how about making uuid
the rdf:ID of the calendar component?

Should dates be like Price, say, because they may have time
zone information attatched to them, much like Price might have currency
information attatched to it? If so, should they always be structured
like this, even if they haven't got a time zone property?

How should time zones be tackled, particularly the separation
of standard and daylight parts? (see example 2)

What about Integers, Text etc. Should these be like Price or
just literals? (Integers should ideally be typed somehow, maybe using
XML schemas?) Text objects in iCalendar can have things attatched to them, and
 therefore might be better seen as objects with an rdf:value.
         
Any thoughts about Vfreebusy objects? (example 6) I'm not sure
if there should be three or maybe four (one containing three), or
something else. 

I'd be very grateful for your opinions Jonas.

Any comments from anyone would be very welcome. I'm starting to compare
different approaches to modelling events using the iCalendar examples to
start with at

http://ilrt.org/discovery/2001/06/schemas/ical-full/examples/

all the best,

libby

Received on Friday, 15 June 2001 09:32:33 UTC