r22 - 07 Feb 2006 - 17:55:49 - LisaDusseaultYou are here: OSAF >  Journal Web  >  ProductManagement > ChandlerEcosystem20030808

The Chandler Ecosystem

Goals The goal of this study is to help map out who the important external parties are and what they can offer to Chandler users and Chandler adoption. By understanding existing and future alternatives in the marketplace, we can better allocate resources by focusing on markets where Chandler is clearly differentiated.

(Note: For the purposes of this project, we are only concerned with external parties -- organizations, products or technologies -- that impact Chandler users and user adoption.)

Thus, this study should have direct input to developing the following key tasks:

  1. Partnership strategy leading to policies and template for external relationships
  2. Feature prioritization based on TargetUseCases
  3. Competitive Intelligence gathering
    • What differentiates Chandler?
    • What should Chandler not do (well-served by existing solutions)?
  4. How can Chandler create new opportunities and support third parties

Currently (Aug'03), we are focused on the top 3 goals. Studies leading to the fourth goal is more beneficially done closer to Chandler 1.0 release timeframe.

Taxonomy

Now Future
Symbiotic Partners 1,2,3,4,5, 6,7,8,9,13,14
Alternatives 10,11,12 13,14

Partner categories:

  1. Platform
    • Devices (Phones, PDAs)
    • OS (MS, Apple, Linux) [out of scope]
  2. Open Source Organizations (Open Office. Open Groupware, Jabber)
  3. Standards Committees (IETF e.g. CAP, XMPP)
  4. Higher Education (uPortal, Shibboleth, OKI, UW IMAP, MIT Kerberos)
  5. Other Chandler Interoperability Partners (e.g. Cyrus, MiraPoint?, Courier)
  6. Funders (Intel, IBM, Borland, DARPA)
  7. Distribution (e.g. Red Hat, Dell)
  8. System Integrators (Seybold, Accenture)
  9. User aggregators: ASPs (Earthlink), VARS [@@@ need to come up with a better for entities that will use Chandler as a platform to create commercial services]

Alternatives:
10. All-in-1 competitors (Exchange, Notes)
11 Vertical competitors (Eudora, Mulberry, Meeting Maker)
12 Open Source alternatives (PINE, Mailman)

Future:
13. Emerging Technologies
14. Emerging Markets

Study Areas

Base on the taxonomy of the eco system above, we have divided this project into the following study areas that we should focus on currently (Owners linked):
  1. PDAs and Syncing (Palm, CE, RIM) PieterHartsook
  2. Groupware Market (Kroupware, Open Groupware, Notes, Groove, Sun iPlanet) KevinTsurutome
  3. Exchange/Outlook Interoperability Study KevinTsurutome; additional information on ExchangeInteroperability?
  4. Higher Ed (Shibboleth, OKI, Lionshare, Kerberos) ChaoLam
  5. External Documents and File Formats (RDF, XML, Media (JPG, MP3, GIF), Office (XLS, DOC))
    • Need to understand digital rights management
  6. InstantMessaging
  7. Calendar Ecosystem including CAP and Jungle.WebDAV

StudyAreaTemplate

Dropped as lower priority:

  1. Web-client interoperability and alternatives (uPortal, Convea) ChaoLam
  2. ThirdPartyServerInteroperability (Cyrus, MiraPoint?) DuckySherwood
  3. PIM client alternatives ChaoLam

Random Notes

-- ChaoLam - 08 Aug 2003


Link to competitive analysis... KDS

toggleopenShow attachmentstogglecloseHide attachments
Topic attachments
I Attachment Action Size Date Who Comment
docdoc OutlookInteroperability-0.21.doc manage 178.0 K 14 Aug 2003 - 13:17 KaitlinDuckSherwood Exchange Interoperability Study
Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r22 < r21 < r20 < r19 < r18 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.