| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions. Connect your Gmail, DriveDropbox, and Slack accounts and in less than 2 minutes, Dokkio will automatically organize all your file attachments. Learn more and claim your free account.

View
 

PIM Open Standard WG

Page history last edited by Mike Diamond 10 years ago

I'm pretty fed up with PIM and the sheer lack of interoperability in this space.  Only closed systems get it right, and they get so many other things wrong.  I'm thinking it's time to start a PIM Open Standard Working Group to come up with an RFC for PIM interop, and feel a good place to start is to start chronicling the issues.

 

Exported State Persistence

 

Calendar events lack a unique identifier or other hook, so that when exported from one system to another, certain attributes are preserved, such as: if you're the owner of the meeting request, you should remain the owner once exported

 

Reminder API

 

I've run into situations where reminders could not be snoozed or ignored when reading remote calendars.  I believe this is due to a lack of or problem with a network language for calandaring

 

Export/Import format

 

Some calendar application only support CSV, and recurrences aren't preserved.  A standard export/import format should be conceived that supports all the necessary calendaring attributes

 

Name

 

We should call the networking language spimp, for Simple Personal Information Management Protocol.  "Universal" also works in place of "Simple", but the "pimp" is required.

 

There's much more to address, but this is a good start.

Comments (0)

You don't have permission to comment on this page.