Cool Features - Was: (Re: Examples Are Somewhat Confusing)

["Peter O'Leary" <poleary@xxxxxxxxxxxxx>]

> If the objects were contacts, and I was writing a piece of contact
> management software, I'd provide my users with a way to sort the
> contacts by last name or first name or switch between them.  I'd also
> want them to be able to search based on the company I worked at.  For
> example, I want to see everyone where "CN" = "Frank" and "Company" =
> "IBM".

Frank, Alec, et. al.

I understand the utility of applying type parameters to properties in
general. But, are we talking about doing this soley for the purpose of
being able to do the sorting and searching that Alec is referring to? If
so, I would like to point out that this is just one feature (granted, a
very cool one) among *many* that might be useful for Calendaring and
Scheduling. However, IMNSHO, it is not in the top 10 important features
that we *need* to have.

If I remember correctly, you were charged by the group with resolving
your differences so that we might arrive at a useful format for sharing
Calendaring and Scheduling information. If this is the only, or perhaps
the largest, issue that needs to be resolved between you, then my vote
would be to drop this *feature* altogether. We need consensus on this
important piece of work *way* more than just about anything else. There
will be time enough in the future to add features.

Pete.