Why

• Not big differences in datatypes, but new objects nevertheless
• Versions, modified date, stamps, etc not just motivated by dashboard, general problem that needs to be solved for 0.7

What

• Generic data type? (ie, "stuff we don't know about")
• Stamps:
  • Stamp property access: item.stamps["osaf.pim.calendar.EventStamp"].startTime / convenience methods like EventStamp^?(note).startTime
• Common ancestor for all items:
  • Stay at Note? (we think yes) If we want Item later, we can cross that bridge
  • Open issue: is there a "shared property" for things like "title"? (Travis investigating)
• Topic stuff (service layer):
  • Asynchronous way of handling service calls/ updating events
  • Do we need this for 0.7? What is minimum?
  • Minimum: * Succeed/ failure for create/ update/ delete (?)
• Travis look @ Dojo data
• Thorny issues:
  • Topics:
    • Is loading data an event?
    • Scaling problems?
    • Can we mitigate these w/ repository? Why?
• Conclusions:
  • No repository
  • Three new components:
    • Service layer
      • Called directly by ui
      • Things like save, delete, etc (anything with an "action purpose")
    • Model changes
      • Stamps
    • Topic communication
      • Called by service layer in response to actions
      • Things like "save succeeded," "save failed", etc (events)

-- TravisVachon - 20 Feb 2007