Re: Standard list of WCMS features

Ilkka Huotari wrote:

>>I am just speaking in terms of
>>
>>- usability
>>- ease of use
>>- ease of building usable solutions for differing users
>>- integrating with the rest of infrastructures
>>    
>>
>
>Of course it's a bit hard to find out all the aspects of a software by a web
>demo. The integration APIs are quite well hidden from that demo.
>
>What was lacking in the ease of use and usability section though, in Netdoc?
>
>(is this still public list material?)
>
>Ilkka
>
>  
>
I would start with

1. some examples of flexible authentication sourcing. You can pull from 
Active directory and Oracle for authenticate a user for example. 
Remember API is not good enough. Anything in this area whether PHP, 
python or Java tends to be cumbersome. You need to think through.
2. some ways to bundle data and code together. If data survives and code 
does not, what good is it?
3. can you speak different protocols; FTP, HTTP, DAV, XML under the same 
authentication
4. much of code has weathered real-world usages

This is a good place to start. If you come out on top, you should have a 
shot at Enterprise CMS.


-- 
Chalu Kim                 “Digital cooperative”
eGenius Inc, 20 Jay Street, 1002, Brooklyn, New York 11201
(718) 858-0142, (718) 858-2434 (fax)