Matt Taylor wrote:

> 1. Must integrate with a J2EE compliant application Server (Yes)

No.

> 2. Must allow content contributors to provide website content without
> developer intervention by separating content from presentation (XML/XSL)
> (yes)

Yes on the separation, no on the xml/xsl

> 3. Must be able to support mixed production environments (Solaris, HPUX)
> (Yes?)

Yes.

> 4. Must be able to manage content from relational databases and remote file
> systems

Since PHP can, yes.

> 5. Should be able to manage content contained in our E-Com store and product
> catalog

Don't know that product.

> 6. Must follow open standards with no proprietary, platform or vendor
> dependence. (Yes)

Depends on what level you are looking at the system.

> 7. The content database must be accessible outside the scope of the CM
> tools(no proprietary database)

Yes, but the check are not currently enforced when accessed this way.

> 8. Must provide XML/Java APIs for developer use and interaction with the CM
> system (No)

No.

> 9. Must provide for scheduling launch / expiration of content

Rudimentary provisions available, needs scripting to match to needs.

> 10. Should be able to provide e-mail based notifications and approvals
> throughout customizable workflows

Same as 9.

> 11. Must either provide integrated versioning capabilities or be able to
> interface with existing SCM (Source Code Management) systems (i.e. CVS, VSS,
> MKS)

Nadmin can but it's not native to Midgard.

> 13. Should be able to integrate with existing development methodologies and
> procedures

Err... everyones', everywhere? No.

> 14. Should implement roles-based (NT) security

No.

> 15. Should have little or no impact on performance

Subjective.

> 16. Would like to be able to provide a step-by-step list of each task a user
> must complete (Workflow Guide)

Would like to: check! :)

> 17. Style sheet Driven Content Editor

No.

Emile


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to