Re: [Ietf-caldav] xCal - resubmitted.
Joe Hildebrand <hildjj@gmail.com> Wed, 21 September 2005 06:26 UTC
Return-Path: <hildjj@gmail.com>
X-Original-To: ietf-caldav@osafoundation.org
Delivered-To: ietf-caldav@osafoundation.org
Received: from smtp.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 5069D7F536 for <ietf-caldav@osafoundation.org>; Tue, 20 Sep 2005 23:26:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.osafoundation.org (Postfix) with ESMTP id 12F9B142294 for <ietf-caldav@osafoundation.org>; Tue, 20 Sep 2005 23:26:54 -0700 (PDT)
Received: from smtp.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02827-10 for <ietf-caldav@osafoundation.org>; Tue, 20 Sep 2005 23:26:53 -0700 (PDT)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.199]) by smtp.osafoundation.org (Postfix) with ESMTP id 673AE142297 for <ietf-caldav@osafoundation.org>; Tue, 20 Sep 2005 23:26:53 -0700 (PDT)
Received: by zproxy.gmail.com with SMTP id z3so2310639nzf for <ietf-caldav@osafoundation.org>; Tue, 20 Sep 2005 23:26:52 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cdNAfGiMrgLFEuO+4gleWjNFbq6oTUixr+krVBBEmi8P+CQNHnr4Nb03YOMsuzf54PUYC6GnNAVEpKCK2/yOi9gVqQZy4FuJYtRGtOYrfVzl+sbGe8IdfxXUBL/I+9IQ+hJPTKxwsx+KcGA8rIQFeMJqdO4nw+STNarHWK+pND4=
Received: by 10.54.49.17 with SMTP id w17mr2293866wrw; Tue, 20 Sep 2005 23:26:52 -0700 (PDT)
Received: by 10.54.125.4 with HTTP; Tue, 20 Sep 2005 23:26:52 -0700 (PDT)
Message-ID: <82777bea0509202326360835c6@mail.gmail.com>
Date: Wed, 21 Sep 2005 00:26:52 -0600
From: Joe Hildebrand <hildjj@gmail.com>
To: ietf-calsify@osafoundation.org, "ietf-calendar@imc.org" <ietf-calendar@imc.org>, xcal-dev@inet-consulting.com, Doug Royer <Doug@royer.com>, CalDAV DevList <ietf-caldav@osafoundation.org>, www-rdf-calendar@w3.org
Subject: Re: [Ietf-caldav] xCal - resubmitted.
In-Reply-To: <42F8BDB3.5000100@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <42F7C417.3050503@Royer.com> <42F8728F.9070808@gmx.de> <1123597518.18971.922.camel@dirk> <42F8BDB3.5000100@gmx.de>
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=-1.6 tagged_above=-50.0 required=4.0 tests=BAYES_00, RCVD_BY_IP
X-Spam-Level:
X-BeenThere: ietf-caldav@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: hildjj@gmail.com
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: Wed, 21 Sep 2005 06:26:54 -0000
On namespace URIs: We went through this on XMPP. It turned out that URIs of this form were the winner: urn:ietf:params:xml:ns:xmpp-tls urn:ietf:params:xml:ns:xmpp-sasl (See RFC 3920) I also agree that <iCalendar/> needs to be in a namespace. I'm not sure why it needs to be in a different namespace than <vcalendar/>, unless you wanted to be able to put other things inside a calendar. I'd suggest that having two different namespaces would be unnecessary complexity. >From 2.7, xmlns isn't really an attribute. You shouldn't call out how namespaces work. And PLEASE don't imply that prefixes are required, or that they must take on some special value. I want to be able to use a doc like this: <iCalendar xmlns='urn:ietf:params:xml:ns:xcal'> <vcalendar> <version>2.0</version> </vcalendar> </iCalendar> which is semantically identical (assuming that iCalendar moves into the namespace). Writing your examples in this format might make them easier to read, as well. If the language attribute could be mapped (special-case) on to xml:lang, it would be great, since there are some tools that already deal with xml:lang. In 2.9, specifying that invalid XML characters MUST be entity encoded prohibits <![CDATA[ ]]> escapes. You might just refer to standard XML escaping mechanisms. I don't think 2.10 adds value. People using XML should understand [XMLNS] at this point. No need to be remedial. It might be nice to have a section about extensibility. - extend with any XML you want, as long as it's in its own namespace - MUST ignore any extensions you don't understand - MUST NOT expect extensions to survive round-tripping to ical. Once some of the namspace issues are worked out, it looks like you're on the right track. On 8/9/05, Julian Reschke <julian.reschke@gmx.de> wrote: > Dan Connolly wrote: > > On Tue, 2005-08-09 at 11:08 +0200, Julian Reschke wrote: > > [...] > > > >>>Copies of the draft at: > >>> > >>> http://INET-Consulting.com/draft-royer-calsch-xcal-01.txt > >>> http://INET-Consulting.com/draft-royer-calsch-xcal-01.html > >>> http://INET-Consulting.com/draft-royer-calsch-xcal-01.xml > >> > >>Just two quick formal comments...: > >> > >>1) Is it intentional that in the examples, the iCalendar container > >>element is in no namespace? > >> > >>2) I don't think the IETF will let you use something like > >>"http://ietf.org/rfc/rfcXXXX.txt" as namespace name; > > > > > > Right; I gather Best Current Practice is... > > > > [[[ > > If the registrant wishes to > > have a URI assigned, then a URN of the form > > > > urn:ietf:params:xml:<class>:<id> > > > > will be assigned where <class> is the type of the document being > > registered (see below). > > ]]] > > -- http://www.faqs.org/rfcs/rfc3688.html > > One could probably also use: <urn:ietf:rfc:NNNN> (see > <http://ietf.org/rfc/rfc2648>). > > > ... > > Best regards, Julian > _______________________________________________ > 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 > -- Joe Hildebrand
- [Ietf-caldav] Re: xCal - namespace URL Tim Hare
- RE: [Ietf-caldav] Re: xCal - resubmitted - file n… Cameron Stillion
- [Ietf-caldav] xCal - namespace URL Doug Royer
- [Ietf-caldav] Re: xCal - resubmitted - file name … Doug Royer
- Re: [Ietf-calsify] RE: [Ietf-caldav] xCal - resub… Doug Royer
- RE: [Ietf-caldav] xCal - resubmitted. Cameron Stillion
- Re: [Ietf-caldav] xCal - resubmitted. Helge Hess
- RE: [Ietf-caldav] xCal - resubmitted. Cameron Stillion
- Re: [Ietf-caldav] xCal - resubmitted. Julian Reschke
- Re: [Ietf-caldav] xCal - resubmitted. Dan Connolly
- Re: [Ietf-caldav] xCal - resubmitted. Helge Hess
- RE: [Ietf-caldav] xCal - resubmitted. Cameron Stillion
- Re: [Ietf-caldav] xCal - resubmitted. Reinhold Kainhofer
- RE: [Ietf-caldav] xCal - resubmitted. Cameron Stillion
- Re: [Ietf-caldav] xCal - resubmitted. Julian Reschke
- [Ietf-caldav] xCal - resubmitted. Doug Royer
- Re: [Ietf-caldav] xCal - resubmitted. Joe Hildebrand