RE: Standard list of WCMS features

> Therefore I am
> looking 
> for a detailed list of features to use as a benchmark.

I think it'd make more sense to get a detailed list of client needs and use
that as the benchmark.

I'm certainly no expert, but I've found features lists to be rather
meaningless for a couple of reasons:

1) rarely does one need/use all the features 
   to meet their business goals

2) there is no consistent definition of a 
   particular feature

3) the existence of a feature doesn't say 
   anything about the quality/usability of 
   said feature

I guess I'm saying that benchmarking software products based on the writing
on the package is just usually a waste of time and only reflects the merits
of the vendor's marketing department. 

(Was that post too cynical? ;o)

-Darrel