Content and Metadata storage/export standards?
By Raoul on Mar 26, 2008
Here's a brief posting that I have to start by stating once again for the record that I'm speaking only for myself and certainly not for the company or OCS or my boss or (probably) any of my colleagues.
How about we standardize our content and metadata storage so that people could buy a standards compatible system and then if they didn't like it, they could export all their "stuff", import it into the new system and carry on.
I realize this may be blasphemy coming from someone who is part of a services organization that runs migration projects, but bear with me. (By the way, I'm very clear I'm not coming up with something new - many others have raised the idea, but I don't see those standards going anywhere - if I'm wrong, please educate me).
I finally came to this conclusion that standards are a good idea after meeting with an industry analyst and discussing BPEL workflow portability with him. Those follow a standard and we still do a good job selling BPEL Manager and integration. Standards work well in many other areas of the enterprise and I would argue that they drive acceptance of technology and innovation rather than constrain it. For instance, many records management products are DoD 5015.2 certified so they all have the same features - we compete on ease of use, integration with our other products, and all the other aspects of the software (resilience, performance, scalability, etc.)
I think our products are good enough that we could propose a metadata and content export standard and use that as a positive in the selection process. We are confident you will use our product stack and we don't feel the need to lock you into a proprietary storage format.
Am I crazy? What else would be in that standard? Should we start with the CMU export bundle formats and structure? Can anyone point me to some previously proposed standards that we can start with? I'm aware of the JSR standards and it sems that most of the the other proposals out there are ISO-type process standards rather than technical specs for data portability. StratML has been positioned in this context, but maybe I'm missing something, because I don't see it filling that role.
Feedback welcome (actually, requested) - firstname.lastname@example.org