Subject: cap-10 section 8. comments

From: [email-masked]
Date: Wed, 2 Apr 2003 18:33:40 -0800 (PST)

(same format as previous similar msgs)

----------------------------------------
[61;3379]

   Conformance: This property can be specified in "VAGENDA" and
                              ---MUST
   "VCALSTORE" component.

   Description: This property is used to indicate whether components may
   conflict.  That is, if their expanded instances may share the same
   time or overlap the same time periods.  If it has a value of TRUE,
   then conflicts are allowed.  If FALSE, the no two components may
                                             ^n
   conflict.
----------------------------------------
[62;3433]

   attcounter   = "ATT-COUNTER" other-params ":" cal-address CRLF
   **********
[
this rule does not seem to be specified in any components abnf...
it would only appear (optionally) in the VCALENDAR component?
]
----------------------------------------
[62;3451]

   Conformance: This property can be specified in the "VAGENDA"
                              ---MUST
   component.

   Description: This property is used to specify a fully qualified
   calid.

   Formal Definition: The property is defined by the following notation:

   CALID   = "CALID" other-params ":" calid CRLF
   -----calid                         *****
[
this is not defined (formally) anywhere,
except for possibly here...

also, there seems to be a mix of using ``CALID'' and ``CalID'' in the draft
(when not speaking of the "CALID" property proper).
]
----------------------------------------
[63;3488]

   Conformance: The property can be specified in a "VCALSTORE"
                             ---MUST
   component.

   Description: The parameter value SHOULD BE a MAILTO URI as defined in
   [URL].  It MUST BE a contact URI such as a MAILTO URI and not a home
                                                         **************
   page or file URI that describes how to contact the calmasters.
   *************************************************************
[
there is some ambiguity in parsing this.
the first time I read it I thought it meant it could not be a file URI
(I now assume that it can be).
maybe if the or-clause was moved before the and-clause?
]

   Formal Definition: The property is defined by the following notation:

   calmaster = "CALMASTER" other-params ":" uri CRLF

   uri = ; IANA registered uri as defined in [iCAL]
         ******************************************
[
if I'm running a CS I need to register my email addr?
]
----------------------------------------
[63;3521]

   Conformance: This property is specified in the "VREPLY" component
                              --MUST be
   that is sent in response to a "GET-CAPABILITY" command.
----------------------------------------
[65;3599]

   Conformance: The property can be specified in a "VREPLY" component
                             ---MUST
   that is sent in response to a "GET-CAPABILITY" command.
----------------------------------------
[65;3602]

   Description: The value is one from a list of "CAR-NONE", "CAR-MIN",
   or "CAR-FULL-1".  If "CAR-FULL-1" is supplied then "CAR-MIN" is also
   available.  A "CAR-MIN" implementation only supported the "DEFAULT-
   VCARS" property values listed in the "VCALSTORE" component and a
   "CAR-MIN" implementation does not support the creation or
   modification of "VCAR" components from the CUA.
   ********************************************************************
[
what does CAR-NONE mean?
]

   Formal Definition: The property is defined by the following notation:

   car-level        = "CAR-LEVEL" ":" other-params : car-level-values
                                  XXXX

   car-level-values = ( "CAR-NONE" / "CAR-MIN" / "CAR-FULL-1"
                        / other-levels )

   other-levels     = ; Any name published in an RFC for a "CAR-LEVEL"
                      ; property value.
   *******************************************************************
[
is this different from the usual iana-token?
]
----------------------------------------
[66;3647]

   Conformance: The property can be specified in a "VREPLY" component in
                             ---MUST
   response to a "GET-CAPABILITY" command.
----------------------------------------
[66;3665]

                  ; All of the following MUST BE supplied in any order.
                  ;
   comp-list-req  = "VCALSTORE" "," "VCALENDAR" "," "VTIMEZONE" ","
                      "VREPLY", "VAGENDA", "STANDARD", "DAYLIGHT"
                              - ","      - ","       - ","

                  ; At least one MUST BE supplied. The same value
                  ; MUST NOT occur more than once.
                  ;
   comp-list-min  = ( "," "VEVENT") / ( "," "VTODO") / ( "," "VJOURNAL" )

                  ; The same value MUST NOT occur
                  ; more than once.
                  ;
   comp-list-opt  = ( "," "VFREEBUSY" ) / ( "," "VALARM" )
                    ( "," "VCAR" )      / ( "," "VQUERY" )
                    ( "," x-comp )      / ( "," iana-comp )
                            ----name                 ----name

   comp-list        = comp-list-req 1*3comp-list-min *comp-list-opt

                      *("," comp-list-names) comp-name
                      ********************************
[
this is spurious text?
]
----------------------------------------
[67;3718]

   Conformance: The property can be specified in a "VCALSTORE"
                             ---MUST
   component.
----------------------------------------
[68;3771]

   Description: This property is used in the "VCAR" component to specify
   whether the component is decreed or not.  If the "DECREED" property
   value is "true" then the CUA will be unable to change the contents of
             ----TRUE
   the "VCAR" component and any attempt will fail with an error.
----------------------------------------
[68;3800]

   Conformance: This property can be specified in "VAGENDA" and
                              ---MUST
   "VCALSTORE" calendar component.
----------------------------------------
[69;3812]

   indicate the charset of calendar.  If not specified, the default is
                                      ****************
[
according to 9.1 it is required
or does it mean if the property value is null?
and if a (text) value can be null,
does it mean much for an object to be required?
]
   the first value in the "VCALSTORE" components "DEFAULT-CHARSET"
                                               ^'
   property value list.  The value MUST BE an IANA registered character
   set as defined in [CHARREG].

   In a "VCALSTORE" component it is a comma separated list of charsets
   supported by the CS.  The first entry is the default entry for all
                         ********************************************
   newly created "VAGENDA" components.  The "UTF-8" value MUST BE in the
   **********************************
[
if previous comment is true, then this is extraneous?
or can one be created through iTIP w/o an explicit VAGENDA?
]
   "VCALSTORE" component "DEFAULT-CHARSET" property list.  All compliant
   CAP implementations (CS and CUA) MUST support the "UTF-8" charset.
----------------------------------------
[69;3853]
   Conformance: This property can be specified in "VAGENDA" and
                              ---MUST
   "VCALSTORE" components.

   Description: In a "VAGENDA" component, the "DEFAULT-LOCALE" property
   is used to indicate the locale of the calendar.  The full locale
   SHOULD be used.  The default and minimum locale is POSIX (aka the 'C'
                        ***********
[
similar comments about required/default.
and would not the default be from the VCALSTORE DEFAULT-LOCALE?
]
   locale).
----------------------------------------
[70;3868]

   In a "VCALSTORE" component it is a comma separated list of locales
   supported by the CS.  The first value in the list is the default for
                         **********************************************
   all newly created VAGENDAs.  "POSIX" MUST BE in the list.
   *****************************
[
similar comments about required/default.
]
----------------------------------------
[70;3900]

   Conformance: This property may be specified once in a "VAGENDA" and
                              ---MUST
   "VCALSTORE" components.

   Description: A multi valued property that lists the known time zones.
   The first is the default.  Where "TZID" property values are the same
   as the "TZID" property as defined in [iCAL].

   If in a "VCALSTORE" component it is a comma separated list of TZIDs
   known to the CS.  The entry is used as the default TZID list for all
                     **************************************************
   newly created calendars.  The list MUST contain at least "UTC".  A
   ************************
[
similar comments about required/default.
]
   "VCALSTORE" components MUST have one "VTIMEZONE" component contained
   in it for each value in the "DEFAULT-TZID" property value.
----------------------------------------
[71;3944]

   DEFAULT-TZID:US/Eastern,UTC
                ***
[
is this valid given that ``/'' is tzidprefix?
]
----------------------------------------
[71;3948]

8.14 DEFAULT-VCARS Property
                 *
[
how come this is the only one of this group whose name is pluralized?
]
----------------------------------------
[71;3960]

   Conformance: This property MUST BE specified in "VCALSTORE" calendar
   component and MUST at least specify the following values:
   "READBUSYTIMEINFO", "REQUESTONLY", "UPDATEPARTSTATUS", and
   "DEFAULTOWNER".
   ********************************************************************
[
given this is CAR-MIN (correct?), is this correct?
(going back to what does CAR-NONE mean)
]

   Description: This property is used in the "VCALSTORE" component to
   specify the "CARID" value of the "VCAR" components that MUST BE
                            ^s
   copied into now "VAGENDA" components at creation time by the CS.  All
                -e
   "DEFAULT-VCAR" values must have "VCARS" components stored in the
                ^S                      X
   "VCALSTORE".
----------------------------------------
[72;3980]

   def-vcars      = "DEFAULT-VCARS" other-params ":" text
      ^ault
                    *( "," text ) CRLF

   Example: The following is an example of this property:

   DEFAULT-VCARS:READBUSYTIMEINFO,REQUESTONLY,
   UPDATEPARTSTATUS,DEFAULTOWNER
   ^<space>
[
and in general these are often missing in the folded lines
(I assume the writers care about it since it is correct in other places and
 in the [2445] examples).
]
----------------------------------------
[73;4057]

   expand     = "EXPAND" other-params ":" ("TRUE" / "FALSE") CRLF
                                          ------------------boolean
----------------------------------------
[74;4120]

   Conformance: This property is specified in the "VREPLY" component
                              --MUST be
   that is sent in response to a "GET-CAPABILITY" command.
----------------------------------------
[75;4160]

   Conformance: This property is specified in the "VREPLY" component
                              --MUST be
   that is sent in response to a "GET-CAPABILITY" command.
----------------------------------------
[75;4194]

   Conformance: The property can be specified in the "VCALSTORE"
                             ---MUST                 ***********
   component.
   *********
[
can/MUST this be in the VCALSTORE component?
replace or augment text with:
	 and in the "VREPLY" component that is sent in response to
	a "GET-CAPABILITY" command.
]
----------------------------------------
[76;4231]

   Conformance: The property can be specified in the "VCALSTORE"
                             ---MUST                 ***********
   component.
   *********
[
can/MUST this be in the VCALSTORE component?
replace or augment text with:
	 and in the "VREPLY" component that is sent in response to
	a "GET-CAPABILITY" command.
]
----------------------------------------
[77;4272]

   Conformance: This property can be specified in a component.
                                                  ***********
[
replace with:
	the "VREPLY" component that is sent in response to
	a "GET-CAPABILITY" command.
]

   Description: This property is used in the in the "GET-CAPABILITY"
   command reply to indicated the MIME multipart types supported.  A CS
   and CUA SHOULD support all registered MIME multipart types.

   Formal Definition: The property is defined by the following notation:

   name = "MULTIPART" other-params ":" text *( "," text) CRLF
   ----multipart
----------------------------------------
[77;4300]

   Property Parameters: Non-standard property parameters can be
                                    ^ and language
   specified on this property.

   Conformance: This property can be specified in a component.

   Description: This property is used in the in component to specify a
   localizable display name.  If more than one "NAME" properties are in
   a component, then they MUST have unique "LANG" parameters.  If the
                                                ^UAGE
----------------------------------------
[78;4316]

   "LANG" parameter is not supplied, then it defaults to the "VAGENDA"
        ^UAGE
   default if the component is in a "VAGENDA", or the "VCALSTORE"
   default if the component is stored at the "VCALSTORE" level.
----------------------------------------
[78;4345]

   Property Parameters: Non-standard, alternate text representation and
                                    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
   language property parameters can be specified on this property.
   XXXXXXXX
----------------------------------------
[79;4389]

   Conformance: This property can be specified in "VRIGHT" components.
                              ---MUST
----------------------------------------
[81;4491]

   This description is a revision of the "REQUEST-STATUS" property for
   VCALENDAR version 2.0.  The 'statdesc' is optional and the 'extdata'
   may be included when 'statdesc' is not provided.

[
Property Paremters: and Conformances: (at the least) statements?
]

   rstatus  = "REQUEST-STATUS" rstatparam ":"
   	  statcode ";" *(statdesc ) ";" *(extdata)
                                 X
          ****************************************
[
this seems to say there will always be two semicolons in the value.
if statdesc and extdata have no format,
is there any meaning to them being repeatable?
i.e. is there any difference between the above and:
   	  statcode ";" [statdesc] ";" [extdata]
?
]

   rstatparam  = other-params [";" languageparm] other-params
                                              ^a
----------------------------------------
[82;4544]

   REQUEST-STATUS:2.8; Success\, repeating VEVENT ignored. Scheduled
   as a single VEVENT.;RRULE:FREQ=WEEKLY;INTERVAL=2
   ^<space>

   REQUEST-STATUS:4.1;Time conflict. Date/time is busy.

   REQUEST-STATUS:3.7;Invalid calendar user;ATTENDEE:
   MAILTO:[email-masked]
   ^<space>
----------------------------------------
[82;4569]

   Conformance: The property can be specified in the "VREPLY" component
                             ---MUST
   in response to a "GET-CAPABILITY" command.
----------------------------------------
[83;4608]

   Conformance: The property can be specified in the "VREPLY" component
                             ---MUST
   in response to a "GET-CAPABILITY" command.
----------------------------------------
[83;4640]

   Conformance: The property can be specified in the "VREPLY" component
                             ---MUST
   in response to a "GET-CAPABILITY" command.
----------------------------------------
[84;4683]

   Conformance: The property can be specified in the "VREPLY" component
                             ---MUST
   in response to a "GET-CAPABILITY" command.
----------------------------------------
[85;4748]

   RESTRICTION:SELECT * FROM VEVENT WHERE
   SELF() IN ORGANIZER
   ^<space>

   RESTRICTION:SELECT * FROM VEVENT WHERE 'BUSINESS' IN
   CATEGORIES
   ^<space>
----------------------------------------
[86;4806]
   Conformance: This property can be specified in a "VREPLY" component
                              ---MUST
   in response to a "GET-CAPABILITY" command.
----------------------------------------
[87;4853]
   Conformance: This property can be specified in a command component.
                                                    XXXXXXX
----------------------------------------
[88;4889]

   Purpose: This property defines whether an component is transparent or
                                           X
   not to busy time searches.  This is a modification to [iCAL] "TRANSP"
   property in that it adds some values.

   Value Type: TEXT

   Property Parameters: Non-standard property parameters can be
   specified on this property.

   Conformance: This property can be specified in a component.
                                                   ^ VEVENT
----------------------------------------