Re: CAP-12-e: Alarms and SEQUENCE

[email protected] wrote:
> 
> Ok, I thought I asked about this before but maybe not.  In CAP we
> added the SEQUENCE property to VALARMs:

So you say you do not understand, yet you quote text from CAP that
answers your questions. Then in the next question you address the
issue you just raised.

I renew my belief that you are doing you best to stall CAP
from being released. Your selective reading of CAP causes
your underinformed or misinformed posts to cause debates that
are not needed. Just searching for the word SEQUENCE I found
several hits, including:


   A CUA may add the "LOCAL" parameter to the "SEQUENCE" property before
   booking the component. If the "LOCAL" parameter is set to "TRUE",
   then the alarm MUST NOT be forwarded to any other calender. If set to
   "FALSE", or if the "LOCAL" parameter is not in the "SEQUENCE"
   property, the alarm is global.

and

   In addition a problem exists with the control of "VALARM" components
   and their "TRIGGER" properties. A CU may wish to set their own alarm
   (local alarms) on components. These local alarms are not to be
   forwarded to other CUs, CUAs, or CSs as are the "SEQUENCE" property
   and the "ENABLE" parameter. So for the protocol between a CUA and a
   CS, the following changes apply to the CAP protocol from [iCAL]
   section 4.6.6 page 67:

and

   The CUA adds a "SEQUENCE" property to each "VALARM" component as it
   books the component. This property along with the "LOCAL" and
   "ENABLE" parameters allow the CUA to uniquely identify any VALARM in
   any component. The CUA should remove those before forwarding to non
   CAP aware CUAs.

and

   SEQUENCE -  When the "SEQUENCE" property is used in a "VALARM"
   component it uniquely identifies the instances of the "VALARM"
   within that component.

and

   The old-values is a component and the contents of that component are
   going to change and may contain information that helps uniquely
   identify the original component (SEQUENCE in the example below). If
   the CS can not find a component that matches the QUERY and does not
   have at least all of the OLD-VALUES, then a 6.1 error is returned.

and

   Because "SEQUENCE" property is used to locate the "VALARM" component
   in this example,  both the old-values and the new-values contain the
   "SEQUENCE" property with a value of "3" and if the "SEQUENCE"
   property were to be left out of new-values, it would have been
   deleted.

and

   2.  If a contained component is changed inside of a selected
       component, and that contained component has multiple instances,
       then old-values MUST contain information that uniquely identifies
       the instance or instances that are changing. It is valid to
       change more than one. As all contained components that match
       old-values will be modified. In the first modify example above,
       if "SEQUENCE" properties were to be deleted from both the
       old-values and new-values, then all "TRIGGER" properties that
       matched the old-values in all "VALARM" components in the selected
       "VEVENT" components would be disabled.