Re: RDF Calendar todo list

Good to see so many people looking at the issues!

I am working on the following as we speak:

>
>* find a permanent home for the namespaces themselves
>
I was thinking that we could use some kind of purl address.  But first, 
we need
a good name.  HybridCal seems a bit temporary.

What about RisNiCal?  (RisNiCal is not ICal)

I'm no naming genius.  Anybody else want to take a stab?

>
>3. Documentation and examples
>
>* write up the reasoning behind the choices we made in the RDF schema
>
Yes, this is going to be essential.   Is  it even possible to do this 
before we are satisfied with the schema?  i.e. I think there are still 
open issues, yes?  And I mean besides simple data-types.  Just off the 
top of my head:

- Is a VCalendar an rdf:Resource or an rdf:Bag?  I think it should be a 
bag (with events, etc) in it.  That's how I have set-up my version of 
the schema, but it seems to be different from Libby's.
- The "*-CHOICE" issue (for example CLASSIFICATION-CHOICE): I'm not 
satisfied witht he way it is now.  It seems like a kludge, and it makes 
writing code for it difficult.  

I think we need a white-board to write these "little" issues down and 
really hash through them.  Perhaps a sourceforge account is needed?

>
>* write some implementations
>
Ok, so this is the front I'm working on.  At present, I have written up 
a small (<1000 lines) pre-alpha quality java library (using 
http://hake.stanford.edu/~melnik/rdf/api.html ) to translate between 
iCalendar and HybridCal.  I intend to release the source code once I'm 
happy with it (but feel free to ask me if you want an advanced peek).

Additionally, I'm starting work on a patch to GnomeCalendar that will 
make it
store it's data in HybridCal.  

-Michael Arick

Received on Monday, 2 July 2001 18:38:56 UTC