14,28d13
< <em>6dec04 Note:</em> See the 205 Milestone 10 version of this file for a quick
< finish to things.  The ideas here need to be merged into the M10 version, or
< vice versa.
< 
< <p>
< Loose items to include where they go:
< <ul>
< <li>
< Date stamp of what the user sees as the application program cannot change when
< the user changes the location of the Cal Tool user directory.  Need to define a
< bit more precisely "what the user sees", but it means the thing with the name
< or icon of the application that the user sees when browsing the file space,
< which can be either a single file (e.g., <tt>.exe</tt>) or a directory tree
< (e.g., <tt>.app</tt>).
< </ul><font color=black>
35c20
< </p><p>
---
> <p>
39,46c24
< administrative users, from seeing private calendar items.  The implementors may
< not elect to exclude private items from the host copy of a calendar, since the
< requirements in
< <a href="admin.html#Central Host Connections">
< Section 2.6.6.1
< </a>
< indicate that upon copying from local calendar to host, the copies of the
< calendar must be identical.
---
> administrative users, cannot see private calendar items.
53,63c31
< </p><p>
< We may want to address certain key performance issues of interest to
< implementors, but not tell them how to do their thing.  Here's a list (only one
< item in the list as of 25ul04):
< <ol type=a>
< <li>
< Whether local-to-host copying is full or incremental is up to the implementors;
< the of the local-to-host copy operation is that the two calendars must be
< identical when the copy operation is complete, and some reasonable performance
< standards must be met, where we need to figure out what "reasonable" is.
< </ol>
---
> 
201a170
> <blockquote>
202a172
> <br>
205a176
> <br>
208a180
> <br>
211a184
> <br>
214a188
> <br>
217a192
> </blockquote>