Is a tool agnostic content architecture best?
I had a conversation today where I was discussing strategies for content architecture with a Fortune 100 high tech company. The person I was speaking with stated that they wanted to create a strategy where the content was completely independent of the tool set used to create and process it.
I believe his premise was that by making the content tool agnostic, that it enables independence from tools, and allows different parts of the organization to choose different tool sets independently to meet their specific requirements. Provided all the tools can magically inter-operate and just load and save the content in the same model everything will be wonderful.
So my question is. Is this really feasible, or is it just a flight of fancy?
My opinion is that if you are focused on satisfying the actual business requirements of users who are authoring, managing, translating, and publishing that content you cannot practically separate the tools from the content because the requirements themselves are not satisfied by either the content model or the tools, but the combination of both.
This is why you never see this type of separation in other software categories like CRM, Financials, or ERP.
If your organization was looking for a new CRM, would they design an independent data model and strategy around managing client information, then find tools that will use the model? I doubt it.
Instead they would most likely gather their business requirements, which by definition need to be independent of implementation, then go to the market with an RFI or RFP. This enables them to consider all the possible ways and technologies available to solve their problems.
I would love to hear your opinions and feedback on this subject.
Paul Trotter
Founder and CEO
Author-it Software Corporation

