Return-Path: 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 427BB801FB; Thu, 16 Nov 2006 13:45:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 30D58142279; Thu, 16 Nov 2006 13:45:26 -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 09913-03; Thu, 16 Nov 2006 13:45:24 -0800 (PST) Received: from mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 7304214225A; Thu, 16 Nov 2006 13:45:24 -0800 (PST) Received: from [17.101.32.44] ([17.101.32.44]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id kAGLjIrc008597 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Nov 2006 16:45:20 -0500 Date: Thu, 16 Nov 2006 16:45:13 -0500 From: Cyrus Daboo To: CalDAV DevList Message-ID: X-Mailer: Mulberry/4.0.7b1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=-1.7 tagged_above=-50.0 required=4.0 tests=ALL_TRUSTED, AWL X-Spam-Level: Cc: Ietf-calsify@osafoundation.org Subject: [Ietf-caldav] Calendar availability specification X-BeenThere: ietf-caldav@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on Calendar Access protocol based on WebDAV List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 21:45:26 -0000 Hi folks, I would like to draw your attention to: This draft defines a new iCalendar component whose purpose is to convey user availability time periods. This differs from VFREEBUSY in that the components can specify repeating/recurring periods. So it is useful for defining regular "office hours" etc. In addition to defining the new VAVAILABILITY component and explaining how it affects free-busy determination, the spec also describes how CalDAV can use these in its own free-busy operations. Please note that discussion of this draft should take place on the ietf-caldav mailing list: So please reply there with any comments you might have. This specification comes from work done in the Calendaring & Scheduling Consortium and is being submitted to the IETF for further discussion, review and hopefully on to standardization. This draft does have a dependency on the Calsify 2445bis work (specifically IANA registration of the new component), so it will follow that down standardization path. -- Cyrus Daboo Return-Path: 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 A68E17F636 for ; Tue, 14 Nov 2006 08:17:37 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 982DA142262 for ; Tue, 14 Nov 2006 08:17:37 -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 12643-02 for ; Tue, 14 Nov 2006 08:17:36 -0800 (PST) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 13D91142264 for ; Tue, 14 Nov 2006 08:17:36 -0800 (PST) Received: from 68-112-233-197.dhcp.oxfr.ma.charter.com ([68.112.233.197] helo=hephaistos) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.51) id 1Gk0yX-000Mea-7S; Tue, 14 Nov 2006 11:17:32 -0500 Received: from ndw by hephaistos with local (Exim 4.62) (envelope-from ) id 1Gk0yi-0003fF-LL; Tue, 14 Nov 2006 11:17:40 -0500 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 68.112.233.197 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: nwalsh From: Norman Walsh To: "Zbarcea, Hadrian" Subject: Re: [Ietf-caldav] Re: iCalendar to XML transform References: <0035B85C0AEE7B42AE0CE75E5B730CD6056AAA@amer-ems1.IONAGLOBAL.COM> X-URL: http://www.sun.com/ X-Countdown: T-minus 2 years, 9 weeks, 4 days, 7 hours, 46 minutes, 7 seconds Date: Tue, 14 Nov 2006 11:17:39 -0500 In-Reply-To: <0035B85C0AEE7B42AE0CE75E5B730CD6056AAA@amer-ems1.IONAGLOBAL.COM> (Hadrian Zbarcea's message of "Tue\, 14 Nov 2006 09\:39\:18 -0500") Message-ID: <87d57qt330.fsf@nwalsh.com> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=sha1; protocol="application/pgp-signature" 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=AWL X-Spam-Level: Cc: ietf-caldav@osafoundation.org X-BeenThere: ietf-caldav@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on Calendar Access protocol based on WebDAV List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 16:17:37 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable / "Zbarcea, Hadrian" was heard to say: | As to the RDF point, I fully agree with you. RDF would not really fit | in WS scenarios, and that's how I approached the problem initially. I | believe WS are very valuable and they should interoperate with calendar | servers seamlessly (for this an xml schema and a WSDL mapped CalDAV | would be necessary). Well, a debate about what technologies are useful to implement web services is clearly out-of-scope here. I've been looking at the Google calendar API and it seems fairly interesting. | But RDF is equally interesting and I planned to | try a few things in the near future myself. They don't rule each other | out imho. No indeed. I'd be tempted to send RDF encodings of iCal in my WS message payload, if I could carve out time to work on such a thing. Be seeing you, norm =2D-=20 Norman Walsh XML Standards Architect Sun Microsystems, Inc. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (GNU/Linux) iD8DBQFFWewjOyltUcwYWjsRAtCbAJ472TvGdfmR+7OLe9DjdTtFUGkTlgCgi/PG PxohovJEZ+y3a89OYwUGD4E= =XA9l -----END PGP SIGNATURE----- --=-=-=-- Return-Path: 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 7D8D080807 for ; Tue, 14 Nov 2006 06:41:35 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 6F4B114225E for ; Tue, 14 Nov 2006 06:41:35 -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 31237-01 for ; Tue, 14 Nov 2006 06:41:34 -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 81CDB142258 for ; Tue, 14 Nov 2006 06:41:34 -0800 (PST) Received: from amer-ems1.IONAGLOBAL.COM ([10.65.6.25]) by amereast-smg2.iona.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id kAEESKdm011424; Tue, 14 Nov 2006 09:28:20 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Ietf-caldav] Re: iCalendar to XML transform Date: Tue, 14 Nov 2006 09:39:18 -0500 Message-ID: <0035B85C0AEE7B42AE0CE75E5B730CD6056AAA@amer-ems1.IONAGLOBAL.COM> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Ietf-caldav] Re: iCalendar to XML transform Thread-Index: AccH6zx4AV8bt5+yT0SvuyL8ErsFmgADXQZA From: "Zbarcea, Hadrian" To: "Norman Walsh" 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: X-Mailman-Approved-At: Mon, 20 Nov 2006 08:25:00 -0800 Cc: ietf-caldav@osafoundation.org X-BeenThere: ietf-caldav@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on Calendar Access protocol based on WebDAV List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 14:41:35 -0000 Hi, Well that was trivial indeed :). I am not sure how useful. There are many reasons and we can debate them offline. For instance=20 "DTSTART: 19700405T020000" is now just text in xslt and date functions cannot be applied. I believe one would be severely limited in the kind of xslt transforms she could write. As to the RDF point, I fully agree with you. RDF would not really fit in WS scenarios, and that's how I approached the problem initially. I believe WS are very valuable and they should interoperate with calendar servers seamlessly (for this an xml schema and a WSDL mapped CalDAV would be necessary). But RDF is equally interesting and I planned to try a few things in the near future myself. They don't rule each other out imho. Interesting discussion. I'd like to keep it going :) Hadrian > -----Original Message----- > From: Norman Walsh [mailto:Norman.Walsh@Sun.COM] > Sent: Tuesday, November 14, 2006 7:48 AM > To: Zbarcea, Hadrian > Cc: Kervin L. Pierre; Tim Hare; ietf-caldav@osafoundation.org > Subject: Re: [Ietf-caldav] Re: iCalendar to XML transform >=20 > / "Zbarcea, Hadrian" was heard to say: > | The problem imho is that there is no such thing as trivial XML. >=20 > Well, it sounded to me like parsing the text was a problem Tim had solved, > his question was how to get it into XSLT. For that, XML can indeed be > trivial: >=20 > > BEGIN:VCALENDAR > BEGIN:VTIMEZONE > TZID:/softwarestudio.org/Olson_20011030_5/America/Los_Angeles > BEGIN:DAYLIGHT > DTSTART:19700405T020000 > RRULE:FREQ=3DYEARLY;BYDAY=3D1SU;BYMONTH=3D4 > ... > >=20 > | Royer is not active anymore in these communities as it seems. And that > | was a DTD not an XML schema anyway. RDF is a tricky way to go. >=20 > Yeah, but this is the sort of application where RDF might be the right > answer. It's syntactic structure is fairly shallow, it's semantics are > fairly concise (by which I mean, there are semantic constraints like > start times precede end times, etc.), it's an open format, and one of > the most useful things to do with your calendar data is combine it > with the calendar data of others. RDF is good at those things. >=20 > Be seeing you, > norm >=20 > -- > Norman Walsh > XML Standards Architect > Sun Microsystems, Inc. Return-Path: 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 2B0BE80830 for ; Tue, 14 Nov 2006 04:48:54 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 1D08F1422B2 for ; Tue, 14 Nov 2006 04:48:54 -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 31990-08 for ; Tue, 14 Nov 2006 04:48:52 -0800 (PST) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 881F91422BE for ; Tue, 14 Nov 2006 04:48:52 -0800 (PST) Received: from 68-112-233-197.dhcp.oxfr.ma.charter.com ([68.112.233.197] helo=hephaistos) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.51) id 1Gjxia-0002SQ-IF; Tue, 14 Nov 2006 07:48:48 -0500 Received: from ndw by hephaistos with local (Exim 4.62) (envelope-from ) id 1GjxiB-0004QH-US; Tue, 14 Nov 2006 07:48:24 -0500 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 68.112.233.197 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: nwalsh From: Norman Walsh To: "Zbarcea, Hadrian" Subject: Re: [Ietf-caldav] Re: iCalendar to XML transform References: <0035B85C0AEE7B42AE0CE75E5B730CD6056AA2@amer-ems1.IONAGLOBAL.COM> X-URL: http://www.sun.com/ X-Countdown: T-minus 2 years, 9 weeks, 4 days, 11 hours, 19 minutes, 45 seconds Date: Tue, 14 Nov 2006 07:48:09 -0500 In-Reply-To: <0035B85C0AEE7B42AE0CE75E5B730CD6056AA2@amer-ems1.IONAGLOBAL.COM> (Hadrian Zbarcea's message of "Mon\, 13 Nov 2006 20\:41\:08 -0500") Message-ID: <877ixynqie.fsf@nwalsh.com> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=sha1; protocol="application/pgp-signature" 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=AWL X-Spam-Level: Cc: ietf-caldav@osafoundation.org X-BeenThere: ietf-caldav@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on Calendar Access protocol based on WebDAV List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 12:48:54 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable / "Zbarcea, Hadrian" was heard to say: | The problem imho is that there is no such thing as trivial XML. Well, it sounded to me like parsing the text was a problem Tim had solved, his question was how to get it into XSLT. For that, XML can indeed be trivial: BEGIN:VCALENDAR BEGIN:VTIMEZONE TZID:/softwarestudio.org/Olson_20011030_5/America/Los_Angeles BEGIN:DAYLIGHT DTSTART:19700405T020000 RRULE:FREQ=3DYEARLY;BYDAY=3D1SU;BYMONTH=3D4 ... | Royer is not active anymore in these communities as it seems. And that | was a DTD not an XML schema anyway. RDF is a tricky way to go. Yeah, but this is the sort of application where RDF might be the right answer. It's syntactic structure is fairly shallow, it's semantics are fairly concise (by which I mean, there are semantic constraints like start times precede end times, etc.), it's an open format, and one of the most useful things to do with your calendar data is combine it with the calendar data of others. RDF is good at those things. Be seeing you, norm =2D-=20 Norman Walsh XML Standards Architect Sun Microsystems, Inc. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (GNU/Linux) iD8DBQFFWbsSOyltUcwYWjsRAgFvAKCkx0eGcfjvzE7p+n4XPmkkp76nJQCfXepM lwkvEaFS9LL3amAZOhN3NGc= =c9pL -----END PGP SIGNATURE----- --=-=-=-- Return-Path: 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 E845880CCD for ; Mon, 13 Nov 2006 18:03:34 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id D93E51422A1 for ; Mon, 13 Nov 2006 18:03:34 -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 18635-03 for ; Mon, 13 Nov 2006 18:03:33 -0800 (PST) Received: from web515.biz.mail.mud.yahoo.com (web515.biz.mail.mud.yahoo.com [209.191.86.226]) by laweleka.osafoundation.org (Postfix) with SMTP id ED37314229E for ; Mon, 13 Nov 2006 18:03:32 -0800 (PST) Received: (qmail 24629 invoked by uid 60001); 14 Nov 2006 02:03:32 -0000 Message-ID: <20061114020332.24627.qmail@web515.biz.mail.mud.yahoo.com> Received: from [208.54.69.198] by web515.biz.mail.mud.yahoo.com via HTTP; Mon, 13 Nov 2006 18:03:32 PST Date: Mon, 13 Nov 2006 18:03:32 -0800 (PST) From: "Kervin L. Pierre" Subject: RE: [Ietf-caldav] Re: iCalendar to XML transform To: "Zbarcea, Hadrian" , Norman Walsh , Tim Hare In-Reply-To: <0035B85C0AEE7B42AE0CE75E5B730CD6056AA2@amer-ems1.IONAGLOBAL.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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: Cc: ietf-caldav@osafoundation.org X-BeenThere: ietf-caldav@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on Calendar Access protocol based on WebDAV List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 02:03:35 -0000 Hello, --- "Zbarcea, Hadrian" wrote: > To make a long story short I do have an xml schema > that maps iCal to XML > and started to work on a parser that reads iCal and > emits SAX/StAX. I did one too, a while back, though mine was a trivial DTD->Schema conversion. I would love to see the schema you came up with. > submit it again. I consider it near complete, it is > my work, but it's > public domain, no strings attached. If anybody is > interesting in > helping me with the parsing/web services stuff > that'd be great. I'd be interested in supporting it in my applications if it gains some support. What might be needed right now is a 'grass-roots' effort to get a grammer off the ground and hopefully standardised at some point when there has been enough interest raised. Maybe get a website up, some documentation, and a few projects supporting it as an alternate calendar representation. I can help with some of that if needed. > Adapting existing parsers to produce valid xml > according to this schema > would work too. > I'd love to help with an implementation but it would probably be a Win32 libical modification at this point due to my resource constraints. Best regards, Kervin > Regards, > Hadrian > > > -----Original Message----- > > From: ietf-caldav-bounces@osafoundation.org > [mailto:ietf-caldav- > > bounces@osafoundation.org] On Behalf Of Kervin L. > Pierre > > Sent: Monday, November 13, 2006 11:53 AM > > To: Norman Walsh; Tim Hare > > Cc: ietf-caldav@osafoundation.org > > Subject: Re: [Ietf-caldav] Re: iCalendar to XML > transform > > > > > > --- Norman Walsh wrote: > > > function that could load the file. An easier > > > solution might be to write > > > a simple pre-processor in your favorite > scripting > > > language to turn the > > > .iCal into trivial XML. You could just wrap the > > > > I agree. And as more and more people are going > > to be doing this to leverage the tons of XML > > code/apps/technologies out there standardising > > this iCalendar grammer will become increasingly > > important. > > > > Does this relate to... > > > http://ietfreport.isoc.org/idref/draft-hare-xcalendar/ > > in anyway? > > > > Is anything happening with xCal? > > > http://tools.ietf.org/html/draft-royer-calsch-xcal-03 > > > > http://www.w3.org/TR/2005/NOTE-rdfcal-20050929/ ? > > > > Would be nice if one of those grammers gained some > > some momentum... :) > > > > Best regards, > > Kervin > > _______________________________________________ > > Ietf-caldav mailing list -- > Ietf-caldav@osafoundation.org > > See http://ietf.webdav.org/caldav/ for more CalDAV > resources > > > http://lists.osafoundation.org/mailman/listinfo/ietf-caldav > Return-Path: 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 4B46380D5D for ; Mon, 13 Nov 2006 17:38:13 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 3B80A1422A0 for ; Mon, 13 Nov 2006 17:38:13 -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 16554-01 for ; Mon, 13 Nov 2006 17:38:09 -0800 (PST) Received: from amereast-smg1.iona.com (amereast-smg1.iona.com [65.223.216.181]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 1DDC814229E for ; Mon, 13 Nov 2006 17:38:09 -0800 (PST) Received: from amer-ems1.IONAGLOBAL.COM ([10.65.6.25]) by amereast-smg1.iona.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id kAE1bKEn028124; Mon, 13 Nov 2006 20:37:20 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Ietf-caldav] Re: iCalendar to XML transform Date: Mon, 13 Nov 2006 20:41:08 -0500 Message-ID: <0035B85C0AEE7B42AE0CE75E5B730CD6056AA2@amer-ems1.IONAGLOBAL.COM> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Ietf-caldav] Re: iCalendar to XML transform Thread-Index: AccHRD1S1iGwmNs6SACf14UJR/rF5AARx3OQ From: "Zbarcea, Hadrian" To: "Kervin L. Pierre" , "Norman Walsh" , "Tim Hare" 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: X-Mailman-Approved-At: Mon, 20 Nov 2006 08:24:59 -0800 Cc: ietf-caldav@osafoundation.org X-BeenThere: ietf-caldav@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on Calendar Access protocol based on WebDAV List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 01:38:13 -0000 Hi, I think what you are trying to do is great. I would dare suggest a slightly different approach. I talked to Brian Mosley and Ted Leung a month or so back but didn't have the time to follow up. The problem imho is that there is no such thing as trivial XML. To be really useful and interoperable the semantics needs to be expressed via an xml schema. Unfortunately xCal does not seem to go anywhere, Doug Royer is not active anymore in these communities as it seems. And that was a DTD not an XML schema anyway. RDF is a tricky way to go. I went the same path more than a year ago. I approached the whole thing from the web services perspective. Web Services are defined by WSDL, which mandates schema. I worked with a project that became apache CXF and would like to support an xml based programming model but use CalDAV on the wire (it may not be obvious what I mean, but it's quite simple). To make a long story short I do have an xml schema that maps iCal to XML and started to work on a parser that reads iCal and emits SAX/StAX. It's a java implementation, but antlr supports other languages too. I won't attach the schema (again), but please let me know and I will submit it again. I consider it near complete, it is my work, but it's public domain, no strings attached. If anybody is interesting in helping me with the parsing/web services stuff that'd be great. Adapting existing parsers to produce valid xml according to this schema would work too. Regards, Hadrian > -----Original Message----- > From: ietf-caldav-bounces@osafoundation.org [mailto:ietf-caldav- > bounces@osafoundation.org] On Behalf Of Kervin L. Pierre > Sent: Monday, November 13, 2006 11:53 AM > To: Norman Walsh; Tim Hare > Cc: ietf-caldav@osafoundation.org > Subject: Re: [Ietf-caldav] Re: iCalendar to XML transform >=20 >=20 > --- Norman Walsh wrote: > > function that could load the file. An easier > > solution might be to write > > a simple pre-processor in your favorite scripting > > language to turn the > > .iCal into trivial XML. You could just wrap the >=20 > I agree. And as more and more people are going > to be doing this to leverage the tons of XML > code/apps/technologies out there standardising > this iCalendar grammer will become increasingly > important. >=20 > Does this relate to... > http://ietfreport.isoc.org/idref/draft-hare-xcalendar/ > in anyway? >=20 > Is anything happening with xCal? > http://tools.ietf.org/html/draft-royer-calsch-xcal-03 >=20 > http://www.w3.org/TR/2005/NOTE-rdfcal-20050929/ ? >=20 > Would be nice if one of those grammers gained some > some momentum... :) >=20 > Best regards, > Kervin > _______________________________________________ > Ietf-caldav mailing list -- Ietf-caldav@osafoundation.org > See http://ietf.webdav.org/caldav/ for more CalDAV resources > http://lists.osafoundation.org/mailman/listinfo/ietf-caldav Return-Path: 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 A0BD280CCE for ; Mon, 13 Nov 2006 08:53:17 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 9242014228E for ; Mon, 13 Nov 2006 08:53: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 00870-02 for ; Mon, 13 Nov 2006 08:53:14 -0800 (PST) Received: from web512.biz.mail.mud.yahoo.com (web512.biz.mail.mud.yahoo.com [209.191.86.223]) by laweleka.osafoundation.org (Postfix) with SMTP id F198C14228C for ; Mon, 13 Nov 2006 08:53:13 -0800 (PST) Received: (qmail 48751 invoked by uid 60001); 13 Nov 2006 16:53:13 -0000 Message-ID: <20061113165313.48749.qmail@web512.biz.mail.mud.yahoo.com> Received: from [72.189.140.217] by web512.biz.mail.mud.yahoo.com via HTTP; Mon, 13 Nov 2006 08:53:13 PST Date: Mon, 13 Nov 2006 08:53:13 -0800 (PST) From: "Kervin L. Pierre" Subject: Re: [Ietf-caldav] Re: iCalendar to XML transform To: Norman Walsh , Tim Hare In-Reply-To: <87k61zo66g.fsf@nwalsh.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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: Cc: ietf-caldav@osafoundation.org X-BeenThere: ietf-caldav@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on Calendar Access protocol based on WebDAV List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 16:53:17 -0000 --- Norman Walsh wrote: > function that could load the file. An easier > solution might be to write > a simple pre-processor in your favorite scripting > language to turn the > .iCal into trivial XML. You could just wrap the I agree. And as more and more people are going to be doing this to leverage the tons of XML code/apps/technologies out there standardising this iCalendar grammer will become increasingly important. Does this relate to... http://ietfreport.isoc.org/idref/draft-hare-xcalendar/ in anyway? Is anything happening with xCal? http://tools.ietf.org/html/draft-royer-calsch-xcal-03 http://www.w3.org/TR/2005/NOTE-rdfcal-20050929/ ? Would be nice if one of those grammers gained some some momentum... :) Best regards, Kervin Return-Path: 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 AF09380BCB for ; Mon, 13 Nov 2006 07:02:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id A0236142294 for ; Mon, 13 Nov 2006 07:02:12 -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 20764-03 for ; Mon, 13 Nov 2006 07:02:12 -0800 (PST) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [63.240.77.84]) by laweleka.osafoundation.org (Postfix) with ESMTP id 26CDA142289 for ; Mon, 13 Nov 2006 07:02:12 -0800 (PST) Received: from thare (c-68-84-31-33.hsd1.fl.comcast.net[68.84.31.33]) by comcast.net (sccrmhc14) with SMTP id <2006111315021101400me6u3e>; Mon, 13 Nov 2006 15:02:11 +0000 From: "Tim Hare" To: "'Dan Connolly'" Date: Mon, 13 Nov 2006 10:02:13 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <1163429709.29678.8.camel@dirk> Thread-Index: AccHM+wmk2SPAkGMSrOvrOyxYVRy0QAAEvwQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Message-Id: <20061113150212.26CDA142289@laweleka.osafoundation.org> X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=2.7 tagged_above=-50.0 required=4.0 tests=AWL, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS, MSGID_FROM_MTA_ID X-Spam-Level: ** Cc: ietf-caldav@osafoundation.org, www-rdf-calendar@w3.org Subject: [Ietf-caldav] RE: iCalendar to XML transform X-BeenThere: ietf-caldav@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on Calendar Access protocol based on WebDAV List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 15:02:12 -0000 Simple: I have XT at home, I don't have Python; and I wanted to see if I could do it purely in XSLT. I've done XML-to-iCal in XSLT so this seemed like a logical challenge. Professionally, I'm a mainframe jock, so you're lucky I didn't just write it in COBOL - the new variants contain XML input and output capabilities - parsing, not validating. Tim Hare Interested Bystander, Non-Inc. -----Original Message----- From: www-rdf-calendar-request@w3.org [mailto:www-rdf-calendar-request@w3.org] On Behalf Of Dan Connolly Sent: Monday, November 13, 2006 9:55 AM To: Tim Hare Cc: www-rdf-calendar@w3.org; ietf-caldav@osafoundation.org Subject: Re: iCalendar to XML transform On Sun, 2006-11-12 at 21:11 -0500, Tim Hare wrote: > I've worked out an XSL transform which I believe will convert any > iCalendar file to an XML document that has a node for each component > and property in the input file, with attributes on component elements > which are the parameters on the properites input. > > One issue, remains, however: the only way I could find to bring in the > iCalendar file was as a defined SYSTEM entity in the XSL stylesheet itself. What prompted you to try using XSLT for parsing .ics files? My approach to reading iCalendar has been to use python and build JSON-shaped structures, and then convert to various XML formats using Kid templates. http://www.w3.org/2002/12/cal/icslex.py http://www.w3.org/2002/12/cal/icsxml.py Hmm... not much documentation in those modules. I wrote an couple items on a similar exercise involving quicken data... Getting my Personal Finance data back with hCalendar and hCard Submitted by connolly on Wed, 2006-03-08 http://dig.csail.mit.edu/breadcrumbs/node/96 using JSON and templates to produce microformat data Submitted by connolly on Sun, 2006-03-19 http://dig.csail.mit.edu/breadcrumbs/node/99 -- Dan Connolly, W3C http://www.w3.org/People/Connolly/ D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E Return-Path: 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 430557FFC4 for ; Mon, 13 Nov 2006 06:55:18 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 336AF142294 for ; Mon, 13 Nov 2006 06:55:18 -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 05244-10 for ; Mon, 13 Nov 2006 06:55:15 -0800 (PST) Received: from homer.w3.org (homer.w3.org [128.30.52.30]) by laweleka.osafoundation.org (Postfix) with ESMTP id CD934142289 for ; Mon, 13 Nov 2006 06:55:15 -0800 (PST) Received: from localhost (homer.w3.org [128.30.52.30]) by homer.w3.org (Postfix) with ESMTP id 25BD74EEBE; Mon, 13 Nov 2006 09:55:09 -0500 (EST) From: Dan Connolly To: Tim Hare In-Reply-To: References: Content-Type: text/plain Organization: World Wide Web Consortium (http://www.w3.org/) Date: Mon, 13 Nov 2006 08:55:09 -0600 Message-Id: <1163429709.29678.8.camel@dirk> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=0.5 tagged_above=-50.0 required=4.0 tests=AWL, DNS_FROM_RFC_POST X-Spam-Level: Cc: ietf-caldav@osafoundation.org, www-rdf-calendar@w3.org Subject: [Ietf-caldav] Re: iCalendar to XML transform X-BeenThere: ietf-caldav@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on Calendar Access protocol based on WebDAV List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 14:55:18 -0000 On Sun, 2006-11-12 at 21:11 -0500, Tim Hare wrote: > I've worked out an XSL transform which I believe will convert any iCalendar > file to an XML document that has a node for each component and property in > the input file, with attributes on component elements which are the > parameters on the properites input. > > One issue, remains, however: the only way I could find to bring in the > iCalendar file was as a defined SYSTEM entity in the XSL stylesheet itself. What prompted you to try using XSLT for parsing .ics files? My approach to reading iCalendar has been to use python and build JSON-shaped structures, and then convert to various XML formats using Kid templates. http://www.w3.org/2002/12/cal/icslex.py http://www.w3.org/2002/12/cal/icsxml.py Hmm... not much documentation in those modules. I wrote an couple items on a similar exercise involving quicken data... Getting my Personal Finance data back with hCalendar and hCard Submitted by connolly on Wed, 2006-03-08 http://dig.csail.mit.edu/breadcrumbs/node/96 using JSON and templates to produce microformat data Submitted by connolly on Sun, 2006-03-19 http://dig.csail.mit.edu/breadcrumbs/node/99 -- Dan Connolly, W3C http://www.w3.org/People/Connolly/ D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E Return-Path: 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 1649880CCB for ; Mon, 13 Nov 2006 05:00:03 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 06D2214228C for ; Mon, 13 Nov 2006 05:00:03 -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 24442-10 for ; Mon, 13 Nov 2006 05:00:01 -0800 (PST) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 6443A142287 for ; Mon, 13 Nov 2006 05:00:01 -0800 (PST) Received: from 68-112-233-197.dhcp.oxfr.ma.charter.com ([68.112.233.197] helo=hephaistos) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.51) id 1GjbPp-000Hd5-Ua; Mon, 13 Nov 2006 07:59:59 -0500 Received: from ndw by hephaistos with local (Exim 4.62) (envelope-from ) id 1GjbNV-0004e8-12; Mon, 13 Nov 2006 07:57:33 -0500 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 68.112.233.197 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: nwalsh From: Norman Walsh To: "Tim Hare" References: X-URL: http://www.sun.com/ X-Countdown: T-minus 2 years, 9 weeks, 5 days, 11 hours, 4 minutes, 43 seconds Date: Mon, 13 Nov 2006 07:57:27 -0500 In-Reply-To: (Tim Hare's message of "Sun\, 12 Nov 2006 21\:11\:08 -0500") Message-ID: <87k61zo66g.fsf@nwalsh.com> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=sha1; protocol="application/pgp-signature" 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=AWL X-Spam-Level: X-Mailman-Approved-At: Mon, 13 Nov 2006 08:09:32 -0800 Cc: ietf-caldav@osafoundation.org, www-rdf-calendar@w3.org Subject: [Ietf-caldav] Re: iCalendar to XML transform X-BeenThere: ietf-caldav@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on Calendar Access protocol based on WebDAV List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 13:00:03 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable / "Tim Hare" was heard to say: | One issue, remains, however: the only way I could find to bring in the | iCalendar file was as a defined SYSTEM entity in the XSL stylesheet itsel= f. Right. The iCal format is text, not XML. XSLT 2.0 has an "unparsed-text()" function that could load the file. An easier solution might be to write a simple pre-processor in your favorite scripting language to turn the .iCal into trivial XML. You could just wrap the whole document in a tag or you could try to be more clever. Be seeing you, norm =2D-=20 Norman Walsh XML Standards Architect Sun Microsystems, Inc. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (GNU/Linux) iD8DBQFFWGu7OyltUcwYWjsRAlgOAJ46+0XHQQfz4fpZgD+Pva2WtMWkwQCcDOHw XuBmCVCINZBR8cEeQbqmq/c= =kVwy -----END PGP SIGNATURE----- --=-=-=-- Return-Path: 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 7A81880B27 for ; Sun, 12 Nov 2006 18:11:13 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 6A97A142270 for ; Sun, 12 Nov 2006 18:11:13 -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 05654-06 for ; Sun, 12 Nov 2006 18:11:13 -0800 (PST) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [204.127.200.84]) by laweleka.osafoundation.org (Postfix) with ESMTP id 0713514226F for ; Sun, 12 Nov 2006 18:11:12 -0800 (PST) Received: from thare (c-68-84-31-33.hsd1.fl.comcast.net[68.84.31.33]) by comcast.net (sccrmhc14) with SMTP id <2006111302111101400mh9hfe>; Mon, 13 Nov 2006 02:11:11 +0000 From: "Tim Hare" To: , Date: Sun, 12 Nov 2006 21:11:08 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: Thread-Index: Acb2AF+Kr8NKJHipRyKQHE4stE6ErQQxs4NQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Message-Id: <20061113021112.0713514226F@laweleka.osafoundation.org> X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=2.7 tagged_above=-50.0 required=4.0 tests=AWL, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS, MSGID_FROM_MTA_ID X-Spam-Level: ** Subject: [Ietf-caldav] iCalendar to XML transform X-BeenThere: ietf-caldav@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on Calendar Access protocol based on WebDAV List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 02:11:13 -0000 I've worked out an XSL transform which I believe will convert any iCalendar file to an XML document that has a node for each component and property in the input file, with attributes on component elements which are the parameters on the properites input. One issue, remains, however: the only way I could find to bring in the iCalendar file was as a defined SYSTEM entity in the XSL stylesheet itself. It's not, as near as I can tell in testing, possible to use it as the original document, or to use the document() function because that causes whitespace to be stripped, including the CR-LF sequence needed to determine the end of an iCalendar property line. If anyone has insight into how to process a text file as input in this kind of process, please let me know. I am willing to share the stylesheet if you like. I'm sure there are issues possibly remaining regarding quoted or escaped characters and the like. Tim Hare Interested Bystander, Non-Inc. Return-Path: 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 A83E77F6FA; Thu, 2 Nov 2006 10:29:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 498611422A0; Thu, 2 Nov 2006 10:29:09 -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 04520-03; Thu, 2 Nov 2006 10:29:07 -0800 (PST) Received: from [192.168.1.102] (c-69-181-78-47.hsd1.ca.comcast.net [69.181.78.47]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 278B714226D; Thu, 2 Nov 2006 10:29:07 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v752.2) To: CalDAV DevList , Cosmo Dev Mailing List Message-Id: <9CDC8269-5410-4C96-8481-F4F6B03144EA@osafoundation.org> Content-Type: multipart/alternative; boundary=Apple-Mail-11--498647607 References: <200610260211.k9Q2BDTV029822@nit.isi.edu> From: Lisa Dusseault Date: Thu, 2 Nov 2006 10:29:05 -0800 X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Spam-Status: No, hits=1.9 tagged_above=-50.0 required=4.0 tests=AWL, HTML_MESSAGE, RCVD_IN_SORBS_DUL X-Spam-Level: * Subject: [Ietf-caldav] Fwd: RFC 4709 on Mounting Web Distributed Authoring and Versioning (WebDAV) Servers X-BeenThere: ietf-caldav@osafoundation.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on Calendar Access protocol based on WebDAV List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Nov 2006 18:29:18 -0000 --Apple-Mail-11--498647607 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed FYI -- this could be used to describe how to mount a CalDAV share, as well as a general WebDAV share. Think of it as a way of providing metadata that can't normally go on a link, about how to use that link. Lisa Begin forwarded message: > From: rfc-editor@rfc-editor.org > Date: October 25, 2006 7:11:13 PM PDT > To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org > Cc: rfc-editor@rfc-editor.org > Subject: RFC 4709 on Mounting Web Distributed Authoring and > Versioning (WebDAV) Servers > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 4709 > > Title: Mounting Web Distributed Authoring and > Versioning (WebDAV) Servers > Author: J. Reschke > Status: Informational > Date: October 2006 > Mailbox: julian.reschke@greenbytes.de > Pages: 15 > Characters: 23672 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-reschke-webdav-mount-05.txt > > URL: http://www.rfc-editor.org/rfc/rfc4709.txt > > In current Web browsers, there is no uniform way to specify that a > user clicking on a link will be presented with an editable view of a > Web Distinguished Authoring and Versioning (WebDAV) server. For > example, it is frequently desirable to be able to click on a link and > have this link open a window that can handle drag-and-drop > interaction with the resources of a WebDAV server. > > This document specifies a mechanism and a document format that > enables WebDAV servers to send "mounting" information to a WebDAV > client. The mechanism is designed to work on any platform and with > any combination of browser and WebDAV client, relying solely on the > well-understood dispatch of documents through their MIME type. > This memo > provides information for the Internet community. > > > INFORMATIONAL: This memo provides information for the Internet > community. > It does not specify an Internet standard of any kind. Distribution > of this memo is unlimited. > > This announcement is sent to the IETF list and the RFC-DIST list. > Requests to be added to or deleted from the IETF distribution list > should be sent to IETF-REQUEST@IETF.ORG. Requests to be > added to or deleted from the RFC-DIST distribution list should > be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. > > Details on obtaining RFCs via FTP or EMAIL may be obtained by sending > an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body > > help: ways_to_get_rfcs. For example: > > To: rfc-info@RFC-EDITOR.ORG > Subject: getting rfcs > > help: ways_to_get_rfcs > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. > Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > Submissions for Requests for Comments should be sent to > RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions > to RFC > Authors, for further information. > > > Joyce K. Reynolds and Sandy Ginoza > USC/Information Sciences Institute > > ... > > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce --Apple-Mail-11--498647607 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 FYI -- this could be used to = describe how to mount a CalDAV share, as well as a general WebDAV = share.=A0 Think of it as a way of providing metadata that can't normally = go on a link, about how to use that link.

Lisa

Begin = forwarded message:

Date: October 25, 2006 7:11:13 PM = PDT
Subject: RFC 4709 on Mounting Web Distributed = Authoring and Versioning (WebDAV) Servers


A new Request = for Comments is now available in online RFC libraries.


=A0 =A0 =A0 =A0 RFC = 4709

=A0 =A0 =A0 =A0 = Title:=A0 =A0 =A0 = Mounting Web Distributed Authoring and=A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = Versioning (WebDAV) Servers=A0
=A0 =A0 =A0 =A0 Author: =A0 =A0 J. Reschke
=A0 =A0 =A0 =A0 = Status: =A0 =A0 = Informational
=A0 =A0 =A0 =A0 Date: =A0 =A0 =A0 October = 2006
=A0 =A0 =A0 =A0 Mailbox:=A0 =A0 julian.reschke@greenbytes.de<= /A>


In current Web browsers, there = is no uniform way to specify that a
user clicking = on a link will be presented with an editable view of a
Web Distinguished Authoring and Versioning (WebDAV) = server.=A0 For
example, it is frequently desirable to be able to = click on a link and
have this link open a = window that can handle drag-and-drop
interaction = with the resources of a WebDAV server.

This document = specifies a mechanism and a document format that
enables WebDAV servers to send "mounting" = information to a WebDAV
client.=A0 The mechanism is designed to = work on any platform and with
any = combination of browser and WebDAV client, relying solely on = the
well-understood dispatch of = documents through their MIME type.=A0= This memo=A0
provides information for the Internet = community.


=A0
It does not specify an Internet standard of any = kind. Distribution
of this memo is = unlimited.

This announcement is sent to the IETF list and the = RFC-DIST list.
Requests to be added to or = deleted from the IETF distribution list
should = be sent to IETF-REQUEST@IETF.ORG.=A0 Requests to be
added to or deleted from the RFC-DIST distribution = list should

Details on obtaining RFCs via FTP or EMAIL may be = obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with = the message body=A0

help: = ways_to_get_rfcs. For example:

=A0 =A0 =A0 =A0 To: rfc-info@RFC-EDITOR.ORG
<= DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">=A0 =A0 =A0 =A0 = Subject: getting rfcs

=A0 =A0 =A0 =A0 help: = ways_to_get_rfcs

Requests for special distribution should be = addressed to either the
author of the = RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.= =A0 Unless
specifically noted otherwise on the RFC itself, all = RFCs are for
unlimited = distribution.

Submissions for Requests for Comments should be sent = to
RFC-EDITOR@RFC-EDITOR.ORG.=A0 Please consult RFC 2223, = Instructions to RFC
Authors, for further = information.


Joyce K. = Reynolds and Sandy Ginoza

...



IETF-Announce mailing list
https://www1= .ietf.org/mailman/listinfo/ietf-announce =
= --Apple-Mail-11--498647607--