Patrick,
I updated the VJOURNAL profile as per RFC, but still missing the following
fields :
attach, attendee, comments, contacts, exdate, exrule, rdate, rstatus.
These fields also missed in existing TODO profile. Are they really required in
journal profile ?
I even updated the 'journal-plain' datatype to support v1.0 and v1.1 as you
suggested.
Can you please review the commit, if any further changes required :
https://meego.gitorious.org/meego-middleware/syncevolution/commit/fd046b1e2bb8b1c37ba448d031eaf4dc1fd90643
Thanks & Regards,
Amarnath
>-----Original Message-----
>From: Patrick Ohly [mailto:[email protected]]
>Sent: Wednesday, July 27, 2011 5:40 PM
>To: Valluri, Amarnath
>Cc: SyncEvolution
>Subject: RE: Bug #11251 - notes synchronization
>
>On Mi, 2011-07-27 at 15:22 +0100, Valluri, Amarnath wrote:
>>
>> >In the new VJOURNAL sub-profile your list VALARM. According to
>> >http://www.ietf.org/rfc/rfc2445.txt "4.6.3 Journal Component", a
>> >VJOURNAL must not contain VALARMs.
>> [Amarnath] Do you mean 'AALARM' and 'DALARM' properties in VJOURNAL
>sub-profile?
>
>Yes. It looks like a cut-and-paste from some other sub-profile. That's a
>good start, but we need to double-check which of these properties really
>can occur in a VJOURNAL.
>
>--
>Best Regards, Patrick Ohly
>
>The content of this message is my personal opinion only and although
>I am an employee of Intel, the statements I make here in no way
>represent Intel's position on the issue, nor am I authorized to speak
>on behalf of Intel on this matter.
>
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
