[Ietf-caldav] iCal to XML Schema mapping proposal

"Zbarcea, Hadrian" <hzbarcea@iona.com> Mon, 12 December 2005 15:57 UTC

Return-Path: <hadrian.zbarcea@iona.com>
X-Original-To: ietf-caldav@osafoundation.org
Delivered-To: ietf-caldav@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 7444D7F593 for <ietf-caldav@osafoundation.org>; Mon, 12 Dec 2005 07:57:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 5D2361422D5 for <ietf-caldav@osafoundation.org>; Mon, 12 Dec 2005 07:57:17 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26345-07 for <ietf-caldav@osafoundation.org>; Mon, 12 Dec 2005 07:57:17 -0800 (PST)
Received: from amereast-smg2.iona.com (amereast-smg2.iona.com [63.65.132.112]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id A65381422D6 for <ietf-caldav@osafoundation.org>; Mon, 12 Dec 2005 07:57:16 -0800 (PST)
Received: from amereast-ems2.IONAGLOBAL.COM ([10.65.6.84]) by amereast-smg2.iona.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id jBCFvFJu018612 for <ietf-caldav@osafoundation.org>; Mon, 12 Dec 2005 10:57:15 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C5FF34.B87ED731"
Date: Mon, 12 Dec 2005 10:57:14 -0500
Message-ID: <13AC4E67178F4D4EA31BB1BA64530313E79CEF@amereast-ems2.IONAGLOBAL.COM>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: iCal to XML Schema mapping proposal
Thread-Index: AcX/MutWT94zIjfFQ5aMHmZ319Hr4AAAZbFg
From: "Zbarcea, Hadrian" <hzbarcea@iona.com>
To: ietf-caldav@osafoundation.org
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=
X-Spam-Level:
Subject: [Ietf-caldav] iCal to XML Schema mapping proposal
X-BeenThere: ietf-caldav@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions on Calendar Access protocol based on WebDAV <ietf-caldav.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-caldav>, <mailto:ietf-caldav-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-caldav>
List-Post: <mailto:ietf-caldav@osafoundation.org>
List-Help: <mailto:ietf-caldav-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-caldav>, <mailto:ietf-caldav-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2005 15:57:17 -0000

Hi,

I would like to propose an XML Schema Mapping for the iCalendar format
(RFC2445).

Calendars and scheduling information are an extremely important aspect
of any business process.  The need for business process automation is
increasing.  SOA based architectures are increasingly popular and
already provide measurable benefits to many companies around the world.
There is a wide range of use cases involving automated decision making
that would benefit from calendaring information of resources or people
participating to a business process being available.

While RFC2445 is the de facto standard for calendaring data interchange
it is not well suited for use in SOA and Web Services (WS) which are
based on XML technologies.  Previous attempts were made to provide such
mappings (such as xCal -
http://www.ietf.org/internet-drafts/draft-royer-calsch-xcal-03.txt) but
they are not sufficient for use in WS (which depend on WSDL and XML
Schema).  The CalDAV effort is also approaching calendaring data
interchange from a different perspective from what I could gather.

A standard mapping of iCalandar to XML is needed and long overdue.
Based on my research there is nothing to fill the gap.  Please find
attached an (incomplete) draft of an XML Schema.  

There are 2 types that need to be mapped: VTimeZoneType and VAlarmType.
I will finish them in the coming days.  There are probably other details
to be sorted out and I am looking forward to any feedback you might
have.

Please let me know if your group has an interest in incorporating this
schema or if you have any suggestion about how it could be used.

Thank you,

Hadrian Zbarcea
Senior Engineer
IONA Technologies
200 West St, #400
Waltham, MA 02451
(781) 902-8322