- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 09 Aug 2005 16:29:07 +0200
- To: Dan Connolly <connolly@w3.org>
- CC: Doug Royer <Doug@royer.com>, xcal-dev@inet-consulting.com, Calsify <ietf-calsify@osafoundation.org>, CalDAV DevList <ietf-caldav@osafoundation.org>, www-rdf-calendar@w3.org, "ietf-calendar@imc.org" <ietf-calendar@imc.org>
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
Received on Tuesday, 9 August 2005 14:29:32 UTC