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

Re: RDF vCard effort related to RDF iCalendar

From: Antoni Mylka <antoni.mylka@dfki.uni-kl.de>
Date: Thu, 03 May 2007 16:48:07 +0200
Message-ID: <4639F627.9040701@dfki.uni-kl.de>
To: Garret Wilson <garret@globalmentor.com>, RDF Calendar mailing list <www-rdf-calendar@w3.org>

Garret Wilson napisaƂ(a):
> 
> Hmmm... There's http://www.w3.org/2002/12/cal/ical.rdf and 
> http://www.w3.org/2002/12/cal/icaltzd.rdf , but I couldn't find any 
> definitive description of the syntax for a UTF-OFFSET, the content of a 
> #Value_RECUR, a description of #List_of_Float, etc.
> 
> I realize I'm coming to this discussion late. I'll go over these schemas 
> more closely.
> 
> Garret
> 
> 

I started working with icaltzd in october 2006 I've written an ical
crawler for the Aperture Framework [1]. Now Aperture has become a part
of the Nepomuk Social Semantic Desktop project [2] (funded by EU).

My work involves creating two ontologies that might be relevant for this
discussion. The first is the Nepomuk Contact Ontology. It's main purpose
is to describe entries in addressbooks. It evolved from vCard, but now
it became more generic. Each Contact has multiple Roles and each Role
can have multiple ContactMedia (PostalAddresses, EmailAddresses etc.).
My goal was that each vCard entry can easily be expressed with NCO, but
an NCO contact can contain much more information that can fit into a VCard.

The second one is NCAL - Nepomuk Calendar Ontology. This one is a
more-or-less direct adaptation of RFC 2445. We didn't use ICALTZD
directly because it's in OWL (while nepomuk uses RDFS-inspired Nepomuk
Representational Language) and because of the problems with ICALTZD.
There are more of them. I've gathered them in section 7.2 of the 
document available from [6] I hope it will help to start a new 
discussion about ICAL RDF.

A new discussion is all the more relevant because RFC 2445 is to become
obsolete within a couple of weeks. See [3], the section about goals an
milestones. The changes in the document are described in detail on the
IETF Calsify status page [4]. See [5] for the exact diff between RFC
2445 and the proposed 2445bis.

The draft of the documentation of the ontology I'm working on can be 
downloaded from [6] Most of this document is probably irrelevant to you. 
You could skim through the 5. section (the one inspired by vCard) but 
the most interesting part is section 7. It contains a detailed account 
of the things I didn't like in ICALTZD and a process I adopted when 
creating NCAL. I guess NCAL might be a starting point for the new ICAL 
ontology.

The Protege files with the ontology itself are available at [7]. 
Remember that this is a work in progress and just about anything may 
change :). They will be officially released to the general public after 
  acceptation by the Nepomuk Consortium.

All comments are welcome.

[1] http://aperture.sourceforge.net
[2] http://nepomuk.semanticdesktop.org
[3] http://www.ietf.org/html.charters/calsify-charter.html
[4] http://tools.ietf.org/wg/calsify/
[5]
<http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/draft-ietf-calsify-rfc2445bis-06.changes.html>
[6] http://www.dfki.uni-kl.de/~mylka/nie.pdf
[7] http://www.dfki.uni-kl.de/~mylka/nie.zip

--
Antoni Mylka
antoni.mylka@dfki.de
Received on Thursday, 3 May 2007 15:55:37 UTC

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