Add chair info and fix markup

Author: anermina

sources/cc-0402-ioptest-results/document.adoc

@@ -77,20 +77,20 @@ http://www.calconnect.org/documents/disclaimerpublic.pdf.
 | 4.3.12 Time | `MUST NOT` | The `TZID` property parameter `MUST NOT` be applied to `TIME` properties whose time values are specified in UTC | Y | Y
 | 4.3.14 UTC Offset | `MUST` | The `PLUS SIGN` character `MUST` be specified for positive UTC offsets (i.e., ahead of UTC). | Y | Y
 | 4.4 iCalendar Object | `MUST` | The first line and last line of the iCalendar object `MUST` contain a pair of iCalendar object delimiter strings | Y | Y
-| 4.6 Calendar Components | `MUST` | An iCalendar object `MUST` include the "PRODID" and "VERSION" calendar properties. | Y | Y
-| 4.6 Calendar Components | `MUST NOT` | 'calscale' and 'method' are optional, but `MUST NOT` occur more than once | Y | Y
+| 4.6 Calendar Components | `MUST` | An iCalendar object `MUST` include the "`PRODID`" and "`VERSION`" calendar properties. | Y | Y
+| 4.6 Calendar Components | `MUST NOT` | '`calscale`' and '`method`' are optional, but `MUST NOT` occur more than once | Y | Y
 | 4.6 Calendar Components | `MUST` | An iCalendar object `MUST` include at least one calendar component. | Y | Y?
-| 4.6.1 Event Component | `MUST NOT` | the following are optional, but `MUST NOT` occur more than once class / created / description / dtstart / geo / last-mod / location / organizer / priority / dtstamp / seq / status / summary / transp / uid / url / recurid | Y | Y
-| 4.6.1 Event Component | `MUST NOT` | either 'dtend' or 'duration' may appear in a 'eventprop', but 'dtend' and 'duration' `MUST NOT` occur in the same 'eventprop | Y | Y
-| 4.6.1 Event Component | `MAY` | the following are optional, and `MAY` occur more than once: attach / attendee / categories / comment / contact / exdate / exrule / rstatus / related / resources / rdate / rrule / x-pro | Y | Y
-| 4.6.2 To-do Component | `MUST NOT` | the following are optional, but `MUST NOT` occur more than once: class / completed / created / description / dtstamp / dtstart / geo / last-mod / location / organizer / percent / priority / recurid / seq / status / summary / uid / ur | Y | Y
+| 4.6.1 Event Component | `MUST NOT` | the following are optional, but `MUST NOT` occur more than once: `class` / `created` / `description` / `dtstart` / `geo` / `last-mod` / `location` / `organizer` / `priority` / `dtstamp` / `seq` / `status` / `summary` / `transp` / `uid` / `url` / `recurid` | Y | Y
+| 4.6.1 Event Component | `MUST NOT` | either '`dtend`' or '`duration`' may appear in a '`eventprop`', but '`dtend`' and '`duration`' `MUST NOT` occur in the same '`eventprop`' | Y | Y
+| 4.6.1 Event Component | `MAY` | the following are optional, and `MAY` occur more than once: `attach` / `attendee` / `categories` / `comment` / `contact` / `exdate` / `exrule` / `rstatus` / `related` / `resources` / `rdate` / `rrule` / `x-pro` | Y | Y
+| 4.6.2 To-do Component | `MUST NOT` | the following are optional, but `MUST NOT` occur more than once: `class` / `completed` / `created` / `description` / `dtstamp` / `dtstart` / `geo` / `last-mod` / `location` / `organizer` / `percent` / `priority` / `recurid` / `seq` / `status` / `summary` / `uid` / `ur` | Y | Y
 | 4.6.2 To-do Component | `MUST NOT` | either 'due' or 'duration' may appear in a 'todoprop', but 'due' and 'duration' `MUST NOT` occur in the same 'todoprop' | Y | Y
-| 4.6.2 To-do Component | `MAY` | the following are optional, and `MAY` occur more than once: attach / attendee / categories / comment / contact / exdate / exrule / rstatus / related / resources / rdate / rrule / x-pro | Y | Y
-| 4.6.3 Journal Component | `MUST NOT` | the following are optional, but `MUST NOT` occur more than once: class / created / description / dtstart / dtstamp / last-mod / organizer / recurid / seq / status / summary / uid / url | N | N
-| 4.6.3 Journal Component | `MAY` | the following are optional, and `MAY` occur more than once: attach / attendee / categories / comment / contact / exdate / exrule / related / rdate / rrule / rstatus / x-pro | N | N
-| 4.6.3 Journal Component | `MUST NOT` | The "VJOURNAL" calendar component cannot be nested within another calendar component | N | N
-| 4.6.4 Free/Busy Component | `MUST NOT` | the following are optional, but `MUST NOT` occur more than once: contact / dtstart / dtend / duration / dtstamp / organizer / uid / url / | N | Y
-| 4.6.4 Free/Busy Component | `MAY` | the following are optional, and `MAY` occur more than once: attendee / comment / freebusy / rstatus / x-prop | N | Y
+| 4.6.2 To-do Component | `MAY` | the following are optional, and `MAY` occur more than once: `attach` / `attendee` / `categories` / `comment` / `contact` / `exdate` / `exrule` / `rstatus` / `related` / `resources` / `rdate` / `rrule` / `x-pro` | Y | Y
+| 4.6.3 Journal Component | `MUST NOT` | the following are optional, but `MUST NOT` occur more than once: `class` / `created` / `description` / `dtstart` / `dtstamp` / `last-mod` / `organizer` / `recurid` / `seq` / `status` / `summary` / `uid` / `url` | N | N
+| 4.6.3 Journal Component | `MAY` | the following are optional, and `MAY` occur more than once: `attach` / `attendee` / `categories` / `comment` / `contact` / `exdate` / `exrule` / `related` / `rdate` / `rrule` / `rstatus` / `x-pro` | N | N
+| 4.6.3 Journal Component | `MUST NOT` | The "`VJOURNAL`" calendar component cannot be nested within another calendar component | N | N
+| 4.6.4 Free/Busy Component | `MUST NOT` | the following are optional, but `MUST NOT` occur more than once: `contact` / `dtstart` / `dtend` / `duration` / `dtstamp` / `organizer` / `uid` / `url` | N | Y
+| 4.6.4 Free/Busy Component | `MAY` | the following are optional, and `MAY` occur more than once: `attendee` / `comment` / `freebusy` / `rstatus` / `x-prop` | N | Y
 | 4.6.4 Free/Busy Component | `MUST NOT` | The recurrence properties ("`RRULE`", "`EXRULE`", "`RDATE`", "`EXDATE`") are not permitted within a "`VFREEBUSY`" calendar component. Any recurring events are resolved into their individual busy time periods using the "`FREEBUSY`" property | N | Y
 | 4.6.5 Time Zone Component | `MUST NOT` | 'tzid' is required, but `MUST NOT` occur more than once | Y | Y
 | 4.6.5 Time Zone Component | `MUST NOT` | 'last-mod' and 'tzurl' are optional, but `MUST NOT` occur more than once | Y | Y
@@ -110,14 +110,14 @@ http://www.calconnect.org/documents/disclaimerpublic.pdf.
 | 4.6.6 Alarm Component | `MUST NOT` | 'duration' and 'repeat' are both optional, and `MUST NOT` occur more than once each, but if one occurs, so `MUST` the other | N | N
 | 4.6.6 Alarm Component | `MUST` NOT|  the following is optional, but `MUST NOT` occur more than once: attach | N | N
 | 4.6.6 Alarm Component | `MAY` | the following is optional, and `MAY` occur more than once: x-prop | N | N
-| 4.6.6 Alarm Component | `REQUIRED` | the following are all `REQUIRED`, but `MUST NOT` occur more than once: action / description / trigger / | N | N
+| 4.6.6 Alarm Component | `REQUIRED` | the following are all `REQUIRED`, but `MUST NOT` occur more than once: `action` / `description` / `trigger` | N | N
 | 4.6.6 Alarm Component | `MUST NOT` | 'duration' and 'repeat' are both optional, and `MUST NOT` occur more than once each, but if one occurs, so `MUST` the other | N | N
 | 4.6.6 Alarm Component | `MAY` | the following is optional, and `MAY` occur more than once: x-prop | N | N
-| 4.6.6 Alarm Component | `REQUIRED` | the following are all `REQUIRED`, but `MUST NOT` occur more than once: action / description / trigger / summary  | N | N
+| 4.6.6 Alarm Component | `REQUIRED` | the following are all `REQUIRED`, but `MUST NOT` occur more than once: `action` / `description` / `trigger` / `summary` | N | N
 | 4.6.6 Alarm Component | `REQUIRED` | the following is `REQUIRED`, and `MAY` occur more than once: attendee | N | N
 | 4.6.6 Alarm Component | `MUST NOT` | 'duration' and 'repeat' are both optional, and `MUST NOT` occur more than once each, but if one occurs, so `MUST` the other | N | N
-| 4.6.6 Alarm Component | `MAY` | the following are optional, and `MAY` occur more than once: attach / x-prop | N | N
-| 4.6.6 Alarm Component | `REQUIRED` | the following are all `REQUIRED`, but `MUST NOT` occur more than once: action / attach / trigger / | N | N
+| 4.6.6 Alarm Component | `MAY` | the following are optional, and `MAY` occur more than once: `attach` / `x-prop` | N | N
+| 4.6.6 Alarm Component | `REQUIRED` | the following are all `REQUIRED`, but `MUST NOT` occur more than once: `action` / `attach` / `trigger` | N | N
 | 4.6.6 Alarm Component | `MUST NOT` | 'duration' and 'repeat' are both optional, and `MUST NOT` occur more than once each, but if one occurs, so `MUST` the other | N | N
 | 4.6.6 Alarm Component | `MUST NOT` | 'description' is optional, and `MUST NOT` occur more than once | N | N
 | 4.6.6 Alarm Component | `MAY` | the following is optional, and `MAY` occur more than once: x-prop | N | N

sources/cc-0506-report-ioptest/document.adoc

@@ -172,8 +172,8 @@ calendar components `MUST` be included. For detail on the usage of the "`VTIMEZO
 component, see the "`VTIMEZONE`" calendar component definition. About local time - the date with
 local time form is simply a date-time value that does not contain the UTC designator nor does it
 reference a time zone.
-* CalDAV: If-None-Match and if-match precondition bugs. This is a bug on a caldav server where
-`if-none-match=*` was not handled properly and a bug on a caldav client where `if-none-mach=*` was set
+* CalDAV: If-None-Match and if-match precondition bugs. This is a bug on a CalDAV server where
+`if-none-match=*` was not handled properly and a bug on a CalDAV client where `if-none-mach=*` was set
 when modifying an event.
 * CalDAV: Interop problems with one vendor's WebDAV interface making it unable to create events
 on "strict" CalDAV servers. Their WebDAV interface does a lot of things when creating a file, the

sources/cc-0508-pres-overview/document.adoc

@@ -20,6 +20,10 @@ and Disclaimer of Warranty for External (Public) Documents as located at
 
 http://www.calconnect.org/documents/disclaimerpublic.pdf.
 
+Permission is granted to existing and potential members of the Consortium to reproduce and distribute this
+presentation within their organizations so long as the presentation is not altered in any way and the Consortium
+is acknowledged as the originator.
+
 == What is CalConnect?
 
 . A Partnership

sources/cc-0601-miniop-usecases-1.0/document.adoc

@@ -165,7 +165,7 @@ attendee.
 
 === Publish
 
-Make known publicly calendar information such as freebusy times.
+Make known publicly calendar information such as `freebusy` times.
 
 === Recurring
 

sources/cc-0601-miniop-usecases-v1.1/document.adoc

@@ -163,7 +163,7 @@ attendee.
 
 === Publish
 
-Make known publicly calendar information such as freebusy times.
+Make known publicly calendar information such as `freebusy` times.
 
 === Recurring
 

sources/cc-0603-report-ioptest/document.adoc

@@ -206,7 +206,7 @@ the Calsify efforts to handle them. Xprops are what need to be enhanced/fixed/re
 
 For the next interop, items to add to interop testing include:
 
-* how many people use the language property on icalendar objects
+* how many people use the language property on iCalendar objects
 * how many can support daily savings time changes that will happen in 2007
 * Free busy testing within CALDAV
 * Tasks testing

sources/cc-0604-ical-recurrence-problems/document.adoc

@@ -189,14 +189,14 @@ The instance needs to be dropped as specified in <<rfc2445,page=44>>.
 === How do we create a rule that excludes weekends and holidays?
 
 ==== {blank}
-Use `BYDAY` without specifying Saturday and Sunday and use `EXDATEs` to remove holidays.
+Use `BYDAY` without specifying Saturday and Sunday and use ``EXDATE``s to remove holidays.
 
 === Implementations without `RRULE` support
 
 ==== {blank}
 A new iTIP response could be created indicating to a sender that the
-recipient does not support `RRULEs`, the sender could then decide to
-"explode" the calendar object into `RDATEs` and send that `RRULE`-less
+recipient does not support ``RRULE``s, the sender could then decide to
+"explode" the calendar object into ``RDATE``s and send that `RRULE`-less
 calendar object. A link to `RRULE` processing reference table and `FREQ`
 example streams can be found at the end of this document.
 
@@ -222,7 +222,7 @@ use cases they were made for:
 
 ===== {blank}
 `EXRULE` -- This recurrence property is cumbersome to use and the
-equivalent can be generated with a list of `EXDATEs`. This property
+equivalent can be generated with a list of ``EXDATE``s. This property
 could be removed for better interoperability.
 
 ===== {blank}
@@ -239,18 +239,18 @@ might have pushed the time into the next hour or day.
 ===== {blank}
 `BYSETPOS` - This `RRULE` property is useful in that it has the
 "payday" use case, ie. last workday of the month, but can be
-complicated to implement. The sender could use `RDATEs` as well but
+complicated to implement. The sender could use ``RDATE``s as well but
 could be a lengthy list if this goes on yearly, etc. It is better to send a
-list of `RDATEs` with exceptions already taken into account, and
+list of ``RDATE``s with exceptions already taken into account, and
 refresh this at appropriate intervals to extend the set. If that is
 recommended in the RFC, then this property could be removed.
 Recommend going to the `CALSIFY` list to see if this is deemed a
 workable solution.
 
 ===== {blank}
-Multiple `EXRULEs` and `RRULEs` -- These properties combined are
+Multiple ``EXRULE``s and ``RRULE``s -- These properties combined are
 complicated to implement, are not supported by many implementers,
-so support for multiple `EXRULEs` and `RRULEs` should be removed
+so support for multiple ``EXRULE``s and ``RRULE``s should be removed
 from the iCalendar RFC and related memos.
 
 == Best Practices
@@ -362,7 +362,7 @@ product, and would be deemed require functionality to the end user. Additional
 modifications that could be discussed for the new drafts are:
 
 . Are multiple ``RRULE``s and ``EXRULE``s really useful, could we do without them?
-. Are `EXRULEs` really useful, could we do without them?
+. Are ``EXRULE``s really useful, could we do without them?
 . Removal of `THISANDPRIOR`, since `THISANDPRIOR` always refers to a finite
 number of occurrences it could be done with exceptions.
 

sources/cc-0605-omads-briefing/document.adoc

@@ -1,4 +1,5 @@
 = OMA-DS CalConnect Liaison Briefing
+:title-main-en: OMA DS - CalConnect Primer
 :docnumber: 0605
 :copyright-year: 2006
 :language: en
@@ -20,6 +21,12 @@ and Disclaimer of Warranty for External (Public) Documents as located at
 
 http://www.calconnect.org/documents/disclaimerpublic.pdf.
 
+Permission is granted to existing and potential members of the Consortium to reproduce and distribute this
+presentation within their organizations so long as the presentation is not altered in any way and the Consortium is
+acknowledged as the originator
+
+OMA DS Face-to-Face location:: Vancouver, British Colombia
+
 == What is CalConnect?
 
 === What is the Consortium

sources/cc-0607-report-ioptest/document.adoc

@@ -117,8 +117,8 @@ didn't work on Vendor1 with the way their server serializes them. Vendor 1 will
 that. It was noted while testing their version that sub collections are not supported by Vendor1
 and Vendor 3. Therefore, they had to do some work on read write capabilities. By the next
 Interop they will do current user privilege sets. This is needed for Access Control. Generally
-speaking, freebusy works. Vendor 2 suggests that next time we should test infinite depth, or
-"rollup", freebusy reports, if anybody other than Vendor 2 supports them.
+speaking, `freebusy` works. Vendor 2 suggests that next time we should test infinite depth, or
+"rollup", `freebusy` reports, if anybody other than Vendor 2 supports them.
 
 == Summary
 

sources/cc-0608-pres-fb-demo/document.adoc

@@ -26,6 +26,8 @@ and Disclaimer of Warranty for External (Public) Documents as located at
 
 http://www.calconnect.org/documents/disclaimerpublic.pdf.
 
+The Open Group Quarterly Meeting location: Coral Gables, Florida
+
 == Why We are here
 
 "Increasingly in business, there is a need to