[Cosmo-dev] Understanding the Cosmo server side target users

[Priscilla Chung]

PPD is trying to understand more about the server side target users  
and I'd like to stir some discussion on the list before we proceed  
with a design session next week.

Based on the Cosmo Server wish-list specified by BCM (also listed  
below):
http://wiki.osafoundation.org/bin/view/Projects/ 
SprintNotesCosmoVisionBrainstorming#ServerWishLi

Could someone go though and explain in layman's terms what each  
feature means and who would find it useful?

-Priscilla

---
     +  External directory integration (LDAP, Kerberos (Apple has these)
           + Auth only, profile in Cosmo
           + Profile in the directory
     + Integration with single sign-on/digital ID
           + Shibboleth/SAML/Library
           + OpenID?
     + The 2 item above imply some kind of framework in place to do this

     + ACL based security (Apple has this)
           + Would also need a UI for managing these
           + WEBDAV ACL extensions
           + A UI which is part of Cosmo
           + WEBDAV principle support - Kervin - use Cosmo as a poor  
man's address book
           + Handling groups - implies existence of group calendars
     + CardDAV?
     + XMPP support
     + Import existing data
     + Run Cosmo/Snarf as a windows service
     + Portlet/portal integration
     + Drag and drop microformat data onto the Cosmo UI
     + Live clipboard/microformat
     + More MyData?.org integration
     + Google calendar support
     + GData/Atom Pub support (BCM thinks this is more important than  
most items on the list)
     + Federated Free/Busy - early stage
     + Storage layer research
     + Integrating admin interface and file system browser into now  
Cosmo UI - AJAXy
     + Remote calendar subscription
     + "Virtual Cosmo" - partitioning a single instance
     + WEBDAV DASL
     + More efficient synching - diffs, less HTTP transactions
     + EIM/morse code