Re: xCal - resubmitted.

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 -- [email protected]
See http://ietf.webdav.org/caldav/ for more CalDAV resources
http://lists.osafoundation.org/mailman/listinfo/ietf-caldav