The results might be wrong or write depending on what your understanding of CMS is.
There is no common understanding of the the term CMS and even not for the derived term ECMS.
CMS means Content Management System. Based on this definition it is a application (system) to manage content. Thats trivial but what does content really means? Content is all and everything. Most of the content can be managed within IT systems as well.
General categories of content maintained by IT applications:
- Structured content
Content maintained and structured as a collection of data (order or offer data). Content in this context means a collection of records with given structure
Those type of data are typical maintained with applications called ERP or other kind of systems of this type (e.g. ALM systems).
- Unstructured content
Content maintained within documents. The content within the document is not addressable outside the application the document was created with (the semantic makes only sense in one specific usage scenario).
Those type of data are typical maintained with applications called DMS or Web-CMS (maintaining HTML) systems.
- Semi-structured content
Content used to create documents (information products) of some kind. The content within the document is addressable outside the application the document was created with.
Content maintained as system independent instance of data (e.g. order or offer data).
In both cases XML is the common format today.
The corresponding consultants knowing the mentioned issue and trying to create domain specific names for specific usage of systems
Main goal is to maintain relational data and used by dedicated applications on top.
Main goal is to maintain documents
Main goal is to maintain intranet / extranet / internet sites
Main goal is to provide enterprise ready workflow and records management on top of DMS feature set
Main goal is to maintain content stored in XML for single-source publishing
anything i missed, of course there are plenty of buzzwords / domains out there describing mixed-scenario usage.
- a C-CMS vendor might support xml usage and publishing very well but does not scale if enterprise workflow or records management is required.
- a ECMS vendor has enterprise BPM support build in but lacks of sophisticated xml semantic and functions.
- a Web-CMS makes creating your Internet presence easy but lacks the usage of the same content for printed documents
This reflects the current state of content management. I expect in the next few years that new and maybe existing systems will move into the semi-structured content area and some of them might succeed. They might reach the final goal that content can be create, maintain, re-purpose and publish based on different user communities from one single source.
Until that stage is reached....coming back to initial "Microsoft SharePoint: The CMS Killer" statement. Ask the author what kind of content use-case he has in mind and you can validate the statement.