It might be helpful to think about this in terms of specific scenarios:
+ Blue sends out an invite for the Company picnic:
+ Everyone "updates" the event with their attendance: I'm coming, I
might come, I won't be coming.
+ You say how many people you'll be bringing.
+ Maybe it's a potluck, and in the "comments" section of the event,
you write down what you're going to bring: soda, chips, cake,
volleyball.
Looking at the e-vite model: it might be nice if instead of having to
click on an URL to go to the evite on some server, you could just
interact with the evite/event right in your email client?
In other words, the mental model is that the invitation information
is simply meta-data attached to the event...all located conveniently
together so that when you go look at the event on your calendar, you
can see attendance information and comments all in one place.
=====
That being said, you are not the first person to draw a hard line
between invitations and the events they refer to.
Could you explain a little more about why that is? In what ways does
conflating invitations and events get in the way of things you want
to do? ie. I can't file them as separate items. I want to be able to
send out several different/separate invitations for any given event.
etc..
In this world, you could imagine modeling events and invitations as a
cluster or thread of items. Or a thread of different "versions" of
the same event...each a separate invitation.
Mimi
On Jan 25, 2006, at 4:23 PM, Alec Flett wrote:
Mimi Yin wrote:
If I stamp-as-email, address, then send to invite people to an
event,
how does inviting more people later work? I edit the existing
email and
hit send again? That's really different than what I'm used to,
but I
guess that could work. I suppose uninviting people could work
the same
way...
Think of it as Edit and Update?
I think this has both technical and user-level issues.. but I think
the user-level issues dominate. Personally I think edit-and-update
is not a model that makes sense for invitations. This is also why I
don't think stamping as a way of inviting makes any sense.
When I have a party, I send out invitations - be it via e-vite,
paper cards, or whatever. and people reply to tell me they are
coming, But the invitation is an entity unto itself - its sometimes
a physical thing but ultimately it is an idea, a desire for someone
to attend an event. I don't think of that as a modification to my
party, or really even a modification to my original invitation. An
invitation is just that: something that invites someone to an
event. Its not the event itself. An invitation is something you
send - it isn't a collaboration between the inviter and the
invitee. I think that looking at it like stamping makes it sound
like "I'm having a party in which one property is your attendance.
If this isn't the correct definition of my party, please modify the
event."
Anyway, that's my stamping-invitation 2 cents:)
Alec
** Probably out-of-scope for 0.7 **
(but I'll mention them briefly, anyway)
- Delegation (Esther organizes and/or schedules a meeting for
Mitch).
This is part of iTIP, SWAG: 5 days
- Countering a meeting invitation with an alternate time (and
accepting
or declining counters). Part of iTIP. The message body for
this is
easy, getting the UI right might be hard. SWAG: 10 days
Well ideally, this would all be worked out in the item
conversation, rather than all going back to the meeting organizer.
- Cancelling meetings. Again, part of iTIP, easy, good UI isn't
necessary, although of course it would be nice to highlight
cancellations somehow, which might take more effort. SWAG: 1 day
- Jabber transport for invitations (I really want to play with this,
maybe in my self-directed time), SWAG: Large
- "home time" free/busy vs. "work time". For instance, if I go on
vacation for a week, I want family and friends to see a different
free/busy than coworkers. I think figuring out how to do this would
probably be hard.
If you've gotten this far, that means you actually read the whole
message. Congratulations, and thanks. :)
Have a nice night,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
