In Chandler, we've tried to simply the application in a number of ways, one is to boil down domain-specific notions of item grouping, status and communications into 3 simple models.

• Item groupings in PIMS today: Local folders, IMAP folders, Public folders, Newsletter folders, Saved Searches, Mail filters, Task lists, Calendars, Notes lists, Projects
• Item groupings in Chandler: Collections

• Status in PIMS today: Not flagged, Flagged / Different flavors of Flags / Done flag, Todo / Done, Present, Past and Future events
• Status in Chandler: Now, Later, Done

• Communications today:
  • Different channels of communications for conversing with one v. many: IM v. IRC
  • Different channels of communications for single items: Email, Item sharing
  • Different channels of communications for subscriptions to groupings of items: Mailing lists, Newsgroups, RSS subscriptions, Calendars, Public folders, etc...
  • Each of these channels has their own notification systems: Pull v. push
  • Different domain specific forms of addressing: From, To, CC, BCC, Reply-to, Sent-by, Requestor, Requestee, Organizer, Participants / Attendees, etc...
• Communications in Chandler:
  • Conversing with one or many
  • Sending / Receiving a single item
  • Sending / Subscribing to a grouping of items irrespective of how it's done (ie. server-centric sharing,
  • Single Capital-N v. small-n notifications scheme across all kinds of communications
  • Unified addressing: From, To, CC, Reply-to, Sent-by. No need for domain-specific notions of From and To.