Data model

• While defining the new Mail schema, I ran into this situation:
  • Kind "AccountBase" has a "port" attribute
  • Kinds "SMTPAccount" and "IMAPAccount" subclass AccountBase^?
  • For SMTPAccount, port should have an initialValue of 25, while for IMAPAccount, initialValue should be 143.
• I ended up defining new attributes named "port" for the two subKinds (SMTPAccount and IMAPAccount) each with the appropriate initialValues. So now even though we probably want "port" to be inherited from AccountBase^?, since we want custom initialValues, we can't inherit.

• I also thought it might be nice if //Schema/Core/Item had a default cloud defined for it (empty, with no endpoints), just so any item whatsoever would be a member of its own cloud even if the schema author hadn't defined a cloud for the item's kind.

Email content model

• While hashing out the email content model with Brian today, an issue came up about how to handle imap and smtp accounts: When the smtp layer goes to send an email message, which smtp account does it use? Is there an app-wide default? I like the Apple Mail.app approach where there is a default smtp account for each imap account. When the user composes a new message, they choose an imap account to send the message "from"; then the smtp layer simply chooses to use the smtp account that was specified for that imap account. Input from Chao and Mimi are needed, and Brian will ask.

-- MorgenSagen - 12 Aug 2004