Doug Royer | 4 Sep 2005 04:19

iCalendar Source Forge Project - new


I have created a new http://SourceForge.net project - iCalendar

	https://sourceforge.net/projects/icalendar

I released the XSLT files that transform an xCal object into
an iCalendar object.

I want to open this SourceForge project open to any iCalendar
open source work.

--

-- 

Doug Royer                     | http://INET-Consulting.com
-------------------------------|-----------------------------

               We Do Standards - You Need Standards

Attachment (Doug.vcf): text/x-vcard, 332 bytes
Attachment (smime.p7s): application/x-pkcs7-signature, 4696 bytes
_______________________________________________
Ietf-calsify mailing list
Ietf-calsify <at> osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
Joe Hildebrand | 21 Sep 2005 08:26
Picon
Gravatar

Re: xCal - resubmitted.

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
(Continue reading)


Gmane