Minor markup fixes

CalConnect · Jan 12, 2025 · 3ed8b1c · 3ed8b1c
1 parent 4631658
commit 3ed8b1c
Show file tree

Hide file tree

Showing 24 changed files with 41 additions and 35 deletions.
diff --git a/sources/cc-0504-report-ioptest/document.adoc b/sources/cc-0504-report-ioptest/document.adoc
@@ -25,7 +25,7 @@ http://www.calconnect.org/documents/disclaimerpublic.pdf.
 
 June 18, 2005
 
-TO: Calconnect Members
+TO: CalConnect Members
 
 Re: June 1-3, 2005 Interop Test Results
 

diff --git a/sources/cc-0505-questionnaire-results-reccurence/document.adoc b/sources/cc-0505-questionnaire-results-reccurence/document.adoc
@@ -45,7 +45,7 @@ This document is generally available to all who responded to the questionnaire i
 evaluating their implementation against others, and to
 all organizations and implementors working with Calendaring and Scheduling
 implementations. The Recurrence Technical
-Committee of Calconnect would appreciate feedback on the value and relevance of this
+Committee of CalConnect would appreciate feedback on the value and relevance of this
 material from those who make use of it.
 Feedback and comments may be sent to the Executive Director of the Consortium via
 [email protected].

diff --git a/sources/cc-0506-report-ioptest/document.adoc b/sources/cc-0506-report-ioptest/document.adoc
@@ -51,7 +51,7 @@ interop testing.
 === CALDAV Testing
 
 Anyone testing CALDAV had a test script to run through. During the pre-testing, some items were
-found in the script that were corrected and put back on the Calconnect web server.
+found in the script that were corrected and put back on the CalConnect web server.
 
 As noted before, the CALDAV script was available for pre-testing as "Homework". Some things that
 were found and fixed were the following:'

diff --git a/sources/cc-0510-questionnaire-results-timezone/document.adoc b/sources/cc-0510-questionnaire-results-timezone/document.adoc
@@ -165,7 +165,7 @@ task of writing a codec for the data structures. Everything I need to know is in
 RFCs. If there was a description of how to implement `VTIMEZONE`, I would have done
 it.
 
-I strongly suggest that the calconnect group go to greater effort to offer
+I strongly suggest that the CalConnect group go to greater effort to offer
 implementation guidance to further interop. This could include pseudo-code processing
 models, warnings about problems and corner cases to look out for, and should
 particularly involve test suites. `RRULE`, for example, would be unimplementable

diff --git a/sources/cc-0511-report-roundtable-2/document.adoc b/sources/cc-0511-report-roundtable-2/document.adoc
@@ -61,15 +61,15 @@ proposal as to how best to move this forward.
 *TC-EVENTPUB* was formed based on work being done at UC Berkeley and elsewhere to
 develop a precise understanding of event publishing and how it differs from general scheduling
 problems, with the goal of attracting efforts being done in several academic institutions and
-elsewhere to combine into a single work project and Technical Committee within Calconnect.
+elsewhere to combine into a single work project and Technical Committee within CalConnect.
 
 *TC-CALSIFY* was re chartered with an expanded scope to support and help drive the CALSIFY
 effort in the IETF via a Working Group to consider the potential revision of RFC 2445.
 
 *Glossary Project*: The work done in the USECASE Technical Committee has shown the need for
 a taxonomy document for common vocabulary and glossary for calendaring and scheduling. Ms.
 Egan volunteered to act as Project Editor to compile a first draft document for circulation by mid-
-February. The Glossary, once complete, will be posted and publicly available on the Calconnect
+February. The Glossary, once complete, will be posted and publicly available on the CalConnect
 website.
 
 *External Communications*: The Consortium has chartered an ad hoc group to develop proposals
@@ -78,7 +78,7 @@ and scheduling, such as an RSS Feed for the C&S space, speaking appearances at t
 conferences and trade shows, and an expanded website presence including links to sites offering
 calendaring functionality.
 
-== Calconnect Interoperability Event
+== CalConnect Interoperability Event
 
 Participants in the CalConnect Interoperability Event included Isamet, Mozilla, Oracle, and the
 University of Washington. The major part of the CalConnect Interoperability Event was CalDAV
@@ -101,7 +101,7 @@ involved in developing this matrix and determining how well the matrix maps to w
 minimum actually is.
 
 The CALDAV Technical Committee will produce scenarios for additional CalDAV testing for the
-next Calconnect Interoperability Event, then turn to assisting CalDAV authors in submitting the
+next CalConnect Interoperability Event, then turn to assisting CalDAV authors in submitting the
 CalDAV draft to the IETF. They expect to use the use cases from the USECASE TC and anticipate
 contributing additional use cases. CALDAV is very interested in being able to conduct virtual
 Interops on a monthly basis and will work with IOP/TEST and the IOP Manager to accomplish

diff --git a/sources/cc-0512-report-roundtable-3/document.adoc b/sources/cc-0512-report-roundtable-3/document.adoc
@@ -76,7 +76,7 @@ areas:
 * Cross domain security and access control
 * Todos for project management
 
-== Calconnect Interoperability Event
+== CalConnect Interoperability Event
 
 Participants in the CalConnect Interoperability Event included Isamet, Mozilla, Novell, Oracle,
 and Rensselaer Politechnic Institute. The CalConnect Interoperability Event was focused on
@@ -86,7 +86,7 @@ the Consortium website and delivered to the IETF.
 
 == Technical Committees
 
-All Calconnect Technical Committees met during the course of the Roundtable to review their
+All CalConnect Technical Committees met during the course of the Roundtable to review their
 status and work to date with the entire set of attendees and to progress their work with the large
 input from the Roundtable. Of particular note:
 

diff --git a/sources/cc-0513-report-roundtable-4/document.adoc b/sources/cc-0513-report-roundtable-4/document.adoc
@@ -69,7 +69,7 @@ issues and determine whether specific work needs to be undertaken in the area.
 *External Communications*: The Consortium will be announcing an RSS feed for Calendaring
 issues and announcements in the next several weeks.
 
-== Calconnect Interoperability Event
+== CalConnect Interoperability Event
 
 Participants in the CalConnect Interoperability Event included EVDB, IBM, Isamet, Mozilla,
 Novell, Oracle, OSAF, RPI (Rensselaer Polytechnic Institute) and Sun Microsystems. Results
@@ -78,7 +78,7 @@ Reports.
 
 == Technical Committees
 
-All Calconnect Technical Committees met during the course of the Roundtable to review their
+All CalConnect Technical Committees met during the course of the Roundtable to review their
 status and work to date with the entire set of attendees and to progress their work with the large
 input from the Roundtable. Of particular note:
 

diff --git a/sources/cc-0601-miniop-usecases-1.0/document.adoc b/sources/cc-0601-miniop-usecases-1.0/document.adoc
@@ -84,7 +84,7 @@ information.
 An application domain that covers systems that allow the
 interchange, access and management of calendar data.
 
-=== Calconnect
+=== CalConnect
 
 The Calendaring and Scheduling Consortium consisting of
 vendors and user groups interested in promoting and improving calendaring and

diff --git a/sources/cc-0601-miniop-usecases-v1.1/document.adoc b/sources/cc-0601-miniop-usecases-v1.1/document.adoc
@@ -83,7 +83,7 @@ An entity (often a human) that accesses calendar information.
 An application domain that covers systems that allow the interchange,
 access and management of calendar data.
 
-=== Calconnect
+=== CalConnect
 
 The Calendaring and Scheduling Consortium consisting of vendors and
 user groups interested in promoting and improving calendaring and scheduling

diff --git a/sources/cc-0611-ical-benefits/document.adoc b/sources/cc-0611-ical-benefits/document.adoc
@@ -150,19 +150,19 @@ types such as 'Calendar User Address' to improve interoperability. iCalendar
 supports a more comprehensive set of property parameters to enable
 delegation of requests, alternative representations of data, and participant
 status. A full list of new property value data types and property value
-parameters is provided in the Appendix.
+parameters is provided in <<appendix-A>>.
 
 iCalendar defines eighteen new properties to support specification of time
 zones, calendaring and scheduling operations such as a canceling a meeting,
 non-Gregorian calendar scales, and other calendar attributes. A full list is
-provided in the Appendix.
+provided in <<appendix-A>>.
 
 iCalendar provides support for meeting requests/group scheduling with the
-new METHOD property. The scheduling protocol is a logical extension of
+new `METHOD` property. The scheduling protocol is a logical extension of
 iCalendar and is defined by RFC 2446 the iCalendar Transport-independent
 Interoperability Protocol (iTIP). There is no equivalent for vCalendar data.
 
-The new RECURRENCE-ID property allows individual calendar instances to
+The new `RECURRENCE-ID` property allows individual calendar instances to
 be linked together and enables powerful recurrence/exception handling.
 
 iCalendar has proper support for time zones and can accurately represent
@@ -190,7 +190,7 @@ The widespread adoption of iCalendar in all application spaces will result in a
 larger range of Calendar content available to consumers over the Internet.
 Further extensions to iCalendar will enable exchange of an even richer set of
 data. The consortium's Event Publication Technical Committee (TCEVENTPUB)
-has developed the VVENUE proposal for representing venue
+has developed the `VVENUE` proposal for representing venue
 related information (e.g. concert listings, museum admission prices, and
 driving directions). iCalendar-based solutions combined with ITIP (RFC 2446)
 will enable full fledged scheduling for consumers.
@@ -273,6 +273,7 @@ iCalendar.
 For more information on the efforts of the Calendaring & Scheduling
 Consortium, please visit http://www.calconnect.org/.
 
+[[appendix-A]]
 [appendix]
 == {blank}
 
@@ -435,6 +436,6 @@ http://www.ietf.org/html.charters/calsify-charter.html.
 * [[[cc-recurrence,CC/R 0604]]]
 
 [bibliography,normative=false]
-=== Calconnect Mobile Calendaring Questionnaire
+=== CalConnect Mobile Calendaring Questionnaire
 
 * [[[cc-mob-calendaring,CC/R 0609]]]
diff --git a/sources/cc-0612-report-ioptest/document.adoc b/sources/cc-0612-report-ioptest/document.adoc
@@ -138,7 +138,7 @@ up correctly the receiving application.
 
 === Second set of comments
 
-Our server team was pleased to participate in this Calconnect IOP. We had the absolute latest version of
+Our server team was pleased to participate in this CalConnect IOP. We had the absolute latest version of
 our CalDAV server available for testing on two machines.
 
 All clients were tested against the server during the course of the event. No major problems were found in

diff --git a/sources/cc-0714-report-vcard-workshop/document.adoc b/sources/cc-0714-report-vcard-workshop/document.adoc
@@ -155,7 +155,7 @@ to verify when they are fixed in the updated specifications.
 The technical committee will produce a recommendations document to the IETF describing
 the suggested fixes and enhancements felt necessary.
 
-The technical committee will work with other Calconnect technical committees to
+The technical committee will work with other CalConnect technical committees to
 accomplish this work (e.g., TC-Mobile, TC-XML (proposed), TC-Eventpub (VVENUE
 overlap), TC-Ioptest (interoperability testing).
 

diff --git a/sources/cc-0802-report-ioptest/document.adoc b/sources/cc-0802-report-ioptest/document.adoc
@@ -402,4 +402,4 @@ applications during our onsite testing events.
 Thank you to all the participants and their willingness to take time out of busy schedules to help
 CalConnect forward the usage of calendaring standards.
 
-Respectfully submitted by Pat Egen, Calconnect Interop Manager.
+Respectfully submitted by Pat Egen, CalConnect Interop Manager.
diff --git a/sources/cc-0803-report-ioptest/document.adoc b/sources/cc-0803-report-ioptest/document.adoc
@@ -30,7 +30,7 @@ http://www.calconnect.org/documents/disclaimerpublic.pdf.
 
 == Introduction
 
-This was the first Mobile Calendar Interoperability testing event held by Calconnect. There was a
+This was the first Mobile Calendar Interoperability testing event held by CalConnect. There was a
 predetermined set of objects to test. It was determined early one that the testing document was quite
 comprehensive and would never be completed in the two days we had for interop testing. Therefore, the
 testing parties elected to choose several items from each testing group for interoperability testing. You

diff --git a/sources/cc-0807-report-ioptest/document.adoc b/sources/cc-0807-report-ioptest/document.adoc
@@ -44,7 +44,7 @@ http://www.calconnect.org/documents/disclaimerpublic.pdf.
 
 == Introduction
 
-The thirteenth Calconnect interoperability event was held at the Yahoo campus at Sunnyvale,
+The thirteenth CalConnect interoperability event was held at the Yahoo campus at Sunnyvale,
 California. Participants of the testing event used predetermined test scenarios. Rather than post
 the full test scenarios in this document, they can be found on the CalConnect website at the
 following URL: http://www.calconnect.org/ioptesting.shtml.

diff --git a/sources/cc-0808-report-ioptest/document.adoc b/sources/cc-0808-report-ioptest/document.adoc
@@ -849,7 +849,7 @@ Therefore, this time we tested only a subset of the scenarios and this proved to
 to do. Participants were able to get through all the scenarios and provide commentary. It was
 found that there were some things tested that appeared to be redundant. Gregory Pekofsky put
 together a document that provides suggestions on how to streamline the limited subset so we can
-better utilize our valuable testing time. His suggested are noted in Appendix B at the end of this
+better utilize our valuable testing time. His suggested are noted in <<appendix-B>> at the end of this
 document.
 
 As usual, participants found that sitting in a room together and doing live testing was extremely

diff --git a/sources/cc-0812-pres-meet-cc/pres-ischedule.adoc b/sources/cc-0812-pres-meet-cc/pres-ischedule.adoc
@@ -33,7 +33,7 @@ All documents included in the zip file for Meet CalConnect 2008 are considered p
 
 * Mattias Amnefelt
 * Infrastructure architect at Stockholm University
-* Member of the iSchedule TC of Calconnect
+* Member of the iSchedule TC of CalConnect
 
 == Introduction
 

diff --git a/sources/cc-0907-miniop-resource-info/document.adoc b/sources/cc-0907-miniop-resource-info/document.adoc
@@ -123,7 +123,7 @@ resources as well as traditional users.
 
 The congruence between vCard and iCalendar, and the loci that provide the possibility on which our
 recommendation is based, are found in the attributes of the `ATTENDEE` iCalendar property (see
-Appendix for the relevant sections of the Calsify and vCard drafts):
+<<appendix-D;and!appendix-E>> for the relevant sections of the Calsify and vCard drafts):
 
 * We observe that an attribute of the `ATTENDEE` property is `DIR`. `DIR` is similar to vCard's
 `SOURCE` attribute in that both store a URI value that points to a directory entry.
@@ -169,6 +169,7 @@ direct mapping allows for increased use of vCard as a structured source for stor
 We propose the `CUTYPE`/`KIND` attributes for "room" classification encapsulate the broader "venue"
 concept, perhaps leveraging work in `VVENUE` as a template for potential schema.
 
+[[appendix-A]]
 [appendix]
 == Attributes in Vendor Implementations
 
@@ -181,6 +182,7 @@ ID436.4%Capacity327.3%Hourly Rate/Cost/Use/Overtime436.4%Hourly
 Rate327.3%Initials327.3%Phone327.3%Working Hours327.3%Cost\Use218.2%External
 Address218.2%Organizational Unit218.2%Overtime Rate218.2%URL218.2%
 
+[[appendix-B]]
 [appendix]
 == Attributes observed in use cases
 
@@ -261,6 +263,7 @@ Address218.2%Organizational Unit218.2%Overtime Rate218.2%URL218.2%
 * test results analyists (per ea: name, location, contact info)
 * timezone
 
+[[appendix-C]]
 [appendix]
 == Attributes in vCard 3.0
 
@@ -295,6 +298,7 @@ Address218.2%Organizational Unit218.2%Overtime Rate218.2%URL218.2%
 * `KEY`
 * `END`
 
+[[appendix-D]]
 [appendix]
 == draft-ietf-calsify-rfc2445bis-08
 
@@ -377,6 +381,7 @@ ATTENDEE;CUTYPE=GROUP:mailto:[email protected]
 ----
 ====
 
+[[appendix-E]]
 [appendix]
 == draft-ietf-vcarddav-vcardrev-03
 

diff --git a/sources/cc-1002-report-ioptest/document.adoc b/sources/cc-1002-report-ioptest/document.adoc
@@ -36,7 +36,7 @@ http://www.calconnect.org/documents/disclaimerpublic.pdf.
 
 The February CalConnect interoperability testing event was held at the UC Irvine campus in Orange
 County, California. Participants of the testing event used predetermined test scenarios. The EMClient
-group participated remotely from the Czech Republic. We utilized our Calconnect Jabber room and Wiki
+group participated remotely from the Czech Republic. We utilized our CalConnect Jabber room and Wiki
 to enable the remote participation.
 
 The documents used in this testing event were the testing matrix for RFC4791 and in addition sync

diff --git a/sources/cc-1305-report-ioptestevent-27/document.adoc b/sources/cc-1305-report-ioptestevent-27/document.adoc
@@ -42,7 +42,7 @@ This document was prepared by Technical Committee _{technical-committee}_.
 
 == Report
 
-The interoperability test event at Calconnect XXVII, hosted by The University of Wisconsin,
+The interoperability test event at CalConnect XXVII, hosted by The University of Wisconsin,
 Madison, Wisconsin took place on Monday June 3rd through Wednesday morning June 5th.
 
 There were 6 organizations participating and 1 observing represented by 13 attendees. Those

diff --git a/sources/cc-1601-report-conference-35/document.adoc b/sources/cc-1601-report-conference-35/document.adoc
@@ -90,7 +90,7 @@ internet draft submissions to the IETF and ultimately be progressed to become RF
 
 === TC API
 
-Work for Calconnect XXXVI includes an overall event object model and a new
+Work for CalConnect XXXVI includes an overall event object model and a new
 "participant" model. Locations and alarms will be reviewed again. The goal is a public
 release of the event model at CalConnect XXXVI.
 

diff --git a/sources/cc-1602-report-ioptestevent-35/document.adoc b/sources/cc-1602-report-ioptestevent-35/document.adoc
@@ -42,7 +42,7 @@ This document was prepared by Technical Committee _{technical-committee}_.
 
 == Report
 
-The Calconnect interoperability event was hosted by AOL at their Palo Alto site on
+The CalConnect interoperability event was hosted by AOL at their Palo Alto site on
 January 11th through the morning of the 13th.
 
 While it was a smaller than usual event much valuable work took place. There was the

diff --git a/sources/cc-1604-report-ioptestevent-36/document.adoc b/sources/cc-1604-report-ioptestevent-36/document.adoc
@@ -42,7 +42,7 @@ This document was prepared by Technical Committee _{technical-committee}_.
 
 == Report
 
-The Calconnect interoperability event was hosted by Ribose and OGCIO at Cyberport in
+The CalConnect interoperability event was hosted by Ribose and OGCIO at Cyberport in
 Hong Kong on April 18 and 19, 2016.
 
 The event at HongKong continued our move to a more forum like approach, combining

diff --git a/sources/cc-1805-report-conference-43/document.adoc b/sources/cc-1805-report-conference-43/document.adoc
@@ -90,7 +90,7 @@ public or private areas.
 
 * The Time Zone Data Distribution Service (TZDIST) Geolocate Extension
 
-== Calconnect Liaisons
+== CalConnect Liaisons
 
 CalConnect has formal reciprocal membership liaisons with M3AAWG and OASIS and a strong working
 relationship with the IETF.
@@ -213,7 +213,7 @@ England.
 * Possible interest by FastMail in hosting CalConnect XLVI in Autumn 2019 in
 Philadelphia.
 
-== Pictures from Calconnect XLIII
+== Pictures from CalConnect XLIII
 
 Pictures courtesy of Thomas Schäfer, 1&1