Domain Model Issues and supporting Use Cases

Meeting goals

• Survey the issues
• Figure out next actions

Plausible Dashboard (0.7)

• User-defined attributes [on-list]
• Bi-directional references between Sidebar collections and Detail view attributes
• For details: ZeroPointSevenDetailView20060201#LabelFieldDiscussion

Chandler's Organizational Paradigm aka Virtuality (back-end goal for 0.7 in preparation for UI in 0.8)

• Hierarchy of Kinds
  • Diagram of how it is today
  • Prefer to change this sooner rather than later
• Hierarchy of Attributes
• Related developer oriented use cases - like mixing in 3rd party kinds with pim kinds

Invitations and Generic "Item Sending"

• Changing Email stamp to a Communications stamp (only a UI-level issue right now)
  • Stamping as an e-mail has problems (like making it hard to resend a message - at least if stamping to MailMessageMixin is the sending trigger, since it's already stamped)
• Per-item read-write privileges (ie. I have read-only access to this share, but I'm invited to this particular event, so I can edit it)
• Per-attribute read-write privileges
  • Addressing: Emailing read-only shared items to others (invitations)
  • Attendance
• UUIDs on items received via emails and reconciling them with updates and shares (0.7)

Sharing and Collaboration

• Knowing and displaying newly added item/edited item for shares (0.8: Dogfood Collaboration)
• Spheres (scheduled for 0.9: Usable Collaboration)
• Revisit what's in the sharing cloud? (0.8: Dogfood Collaboration)
  • Private annotations
  • Private labels versus Shared labels
  • Personal versus Shared triage status
• An attribute for "Who" added/edited an item to a share (0.8 Dogfood Collaboration)

Managing Data Flow

• Input and Outputs per collection. See: DataInOutOfChandler (punt until after 0.7 planning)

Extensibility

• Defining new Kinds and have parcels plug into the right places in the UI (dependent on figuring out Hierarchy of Kinds)
  • Shows up in the App bar
  • Shows up with the right Stamp

Suggestions

• Does anyone mind if change the 'body' attribute from Lob to Text? I don't think we store anything in 'body' that requires a streaming API to access it. It would be more convenient to be able to say item.body = "foo".

Next actions

• Ted to take a walk through the entire Domain model for general cleanup (during planning period)
• Ted to spend some time on Domain model for Contacts (in 0.7 timeframe)
• Discuss shared Labels and user-defined attributes with Morgen
  • MorgenSagen says that we can share the Tag attribute values AND/OR we can define sharing clouds on the fly to include user-defined attributes and tags in shares. [Yes, we can share Tags, but it's not yet clear to me we can define sharing clouds on the fly since that means two Chandlers with different cloud definitions, and that's potentially bad if they try to share with each other. ~morgen]
  • Also with Bryan Stearns <http://lists.osafoundation.org/pipermail/dev/2006-February/005147.html>
• Discuss user-defined attributes with Philippe, Bryan, Alec, John, pje, Andi
• Discuss per item, per attribute read-write privileges with Morgen and Phillip
• Sheila/Mimi talk about UUID issue with Morgen: Is this going to be an issue?
• Talk about Inputs and Outputs issue with Morgen (no UI for 0.7)