> If it is the same group that determines the use cases as subsequently
> identifies the relevant standards, there could be a danger of only
> coming up with use cases that can be addressed by 'known' specs, i.e.,
> if you have FOAF in the back of your mind as a good bet for a
> relevant piece of the blueprint, you may only come up with use cases
> that FOAF can solve.
In my opinion, use cases are use cases. They have to be independent.
Then, once use cases are outlined, you have to check what can do what,
and how you can extend technologies to meet the need of use cases.
Don't htink about use cases on a technology standpoint, think about it
on a user standpoint; otherwise the exercise is useless.
Take care,
Fred