Re: CAP - BEEP Profile

> >>Does that fix the issue?
> >
> >i have no idea. the text in the document is so convoluted it should be
> >sent to the 9th circuit court.
> >
>
> Does anyone that knows iCAL and CAP understand what the issue is?

If I understand correctly, I think its OK. BEEP appears to require a
single mime entity per message.  This mime entity may or may not be
multipart, no matter.


iCal has the ability to encode multiple objects in two ways:

- one object per mime entity, encoded as multipart

- multiple objects per mime entity, delimited with VBEGIN/VEND in a single
text/calendar part.


Is the following wording any help?

-------------------------
Multiple iCal objects may be sent in a single BEEP message by either
representing them as seperate MIME text/calendar parts contained within a
MIME multipart/mixed part or by simple concatenation within a single
text/calendar [**] part, seperated by a single blank line.

In either case, all iCal objects transmitted together must have the same
TARGET property.

The sending of multipart MIME entities over BEEP is not permitted for CAP
unless the other endpoint has indicated its ability to accept them via the
appropriate CAPABILITY[*].
-------------------------

[* - I don't know which capability is this, it would be good to name it
explicitly]

regards,

jb