1. The Dublin Core metadata specification. http://dublincore.org/
2. Workflow modeling with BPML. http://www.bpmi.org
3. JSR 170. http://www.jcp.org/en/jsr/detail?id=170
While I don't think this answers your question directly, if your client is in a position to make some decisions such as "The CMS I choose must support the Dublin Core metadata specification", that would make the tender very clear.
I'd be interested to hear if anyone is working with these specifications, as well.
Richard
Red Hat, Inc.
James Robertson wrote:
Hi all, I was talking with a client yesterday who is starting out on a big project to select a big CMS.Now, he is looking at the best way of specifying "information model" details, to be included in the CMS tender. By information model, he is referring to details such as: * Information architecture (site design, etc) * Metadata requirements * Content types * Workflows * Enterprise information repositories * Single-source publishing and content reuse requirements * User information (identities, security, etc) The idea is to provide vendors with sufficient information to understand what the specific business requirements are. The challenge is to collate and present this in some sort of meaningful way. I had to confess to this customer that I had not seen much in the way of "best practice" in this area. Does anyone have some thoughts/examples/ best practice ideas about how to best specify this information, and how much should be covered? Thanks in advance, James ------------------------- James Robertson Step Two Designs Pty Ltd Knowledge Management Consultancy, SGML & XML Content Management Requirements Toolkit 112 CMS requirements, ready to cut-and-paste http://www.steptwo.com.au/ [EMAIL PROTECTED] -- http://cms-list.org/ more signal, less noise.
-- http://cms-list.org/ more signal, less noise.
