CAP Editoral: Acronyms in Section 1

[Bruce_Kahn@xxxxxxxxxxxxxxxx]

In showing CAP to someone they started
to read Section 1 Introduction and were somewhat confused by the yet undefined
acronyms it used:

This document specifies how a Calendar CUA interacts
with a CS to manage calendar information. In particular, it specifies how
to query, create, modify, and delete iCalendar components (e.g., events,
to-dos, or daily journal entries). It further specifies how to search for
available busy time information. Synchronization with CUAs is not covered.


CAP is specified as a [BEEP] "profile".
As such, many aspects of the protocol (e.g., authentication and privacy)
are provided within [BEEP]. The protocol data units leverage the standard
iCalendar format [iCAL] to convey calendar related information. 

CAP can also be used to store and fetch [iTIP] objects
and when those objects are used in this memo, they mean exactly the same
as defined in [iTIP]. When iCalendar objects are transfered between the
CUA and a CS, some additional properties and parameters may be added and
the CUA is responsible for correctly generating iCalendar objects to non
CAP processes. 

The terms CS and CUA are not defined
until Section 1.3 so could we please expand them to "Calendar Server"
and Calendar User Agent until we define them later in the text?  Plus
a "Calendar CUA" is a bit of a verbose redundancy...

Bruce
===========================================================================
Bruce Kahn                  
             INet: Bruce_Kahn@xxxxxxxxxxxxxxxx
Messaging & Collaboration            
    Phone: 978.399.6496
IBM Software Group                
        FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law...