Announced this week was the news that the BSI in the UK, in partnership with The Content Group, are to develop a Publicly Available Specification (PAS) for ECM.
Now I do try not to be negative about such initiatives as it can be too easy to sit and write a blog to criticise others, we should be making positive contributions to the information on such subjects. However I do question the objective of this initiative. At the end of the link above the following statement is made:
“The manifold benefits of an industry-wide code of practice for ECM include helping organisations and individuals to understand ‘What it is’, ‘What it can do’, and ‘How to measure the quality level of any project against a formally recognised specification’. The PAS is intended to be the first step moving towards an internationally agreed standard for ECM.”
So what are we going to get:
– a definition of ECM. Okay, not a bad start. Everyone has a view on this presently so this will be another one to throw in the mix. Will it be treated as definitive?
– a statement of what ECM can do. Mmm, again not bad. I wonder what level of detail this will go into, full requirements specifications including Use Case style approaches. I suspect this will be more leaning towards what I would consider the Logical Architecture for ECM; again there are plenty of other works in this area.
– how to measure the success of an implementation against a specification; the PAS specification I suspect. This is where I start to get a bit twitchy. The biggest challenge I would put to BSI and The Content Group is how does this differentiate from the MOREQ work which has produced a full specification and will shortly produce version 2? MOREQ is now relatively mature and the new version will include a framework for testing, sounds similar. If this is to go beyond MOREQ and include the full scope of Enterprise Content Management, i.e. including the likes of Digital Asset Management, Web Content Management, and so on then it will add value. This will be interesting to keep an eye on.
I’m sure the likes of James will be amused by efforts like this, I am convinced these are not the types of standards he has been commenting on in recent months. It seems to me that we do have a number of standards in ECM including MOREQ, iECM(well…), JSR170 and now this. We need to be moving towards something which can be used as a blueprint towards a true SOA of ECM and having some idea of the service interfaces which would support this. If ECM is truly going to move towards a SaaS model then this would be a huge beneficial step.