<div dir="ltr"><div>Thanks for the reply. Yes, iCal4j does provide support for extensions.<br><br></div>Regards,<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 26, 2015 at 5:57 PM, Cyrus Daboo <span dir="ltr"><<a href="mailto:cdaboo@apple.com" target="_blank">cdaboo@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Gaurav,<span class=""><br>
<br>
--On August 26, 2015 at 3:29:50 PM -0700 Gaurav Jain <<a href="mailto:monkeyfdude@gmail.com" target="_blank">monkeyfdude@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am getting EMAIL as an Attendee parameter with DCS 6.0. But ical specs<br>
say otherwise as mentioned below.<br>
<br>
Due to which the parsing is failing for ical4j.<br>
<br>
Why is EMAIL an attendee parameter?<br>
<br>
<br>
The ical specs for attendees is<br>
<br>
/*<br>
* ; the following are optional, ; but MUST NOT occur more than once<br>
(";" cutypeparam) / (";"memberparam) / (";"<br>
* roleparam) / (";" partstatparam) / (";" rsvpparam) / (";"<br>
deltoparam) / (";" delfromparam) / (";"<br>
* sentbyparam) / (";"cnparam) / (";" dirparam) / (";" languageparam) /<br>
*/<br>
</blockquote>
<br></span>
iCalendar allows for the addition of new properties and parameters if you look at the syntax you will see "iana-token" items used as a place holder for future standard protocol elements). The EMAIL parameter is defined in a draft specification which the IETF is working on: <<a href="https://tools.ietf.org/html/draft-ietf-calext-extensions-00#section-6.2" rel="noreferrer" target="_blank">https://tools.ietf.org/html/draft-ietf-calext-extensions-00#section-6.2</a>>.<br>
<br>
ical4j should not be so strict as to refuse to accept new standard properties. As you can see in that draft, there are a whole bunch of new ones being worked on.<br>
<br>
That said, please check to see if you have the latest version of ical4j, because it may already support the new protocol elements, or provide a more relaxed mode so that it does not fail when something new comes along that it does not recognize.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Cyrus Daboo<br>
<br>
</font></span></blockquote></div><br></div>