See ScopeAndPurpose for a definition of the overall scope of the glossary. Based on this, the following details have been determined:

Determining terms to be included

The following process is proposed:

1. We start with a "clean sheet of paper", as it is too hard to rework the existing content.
2. We then focus exclusively on a small number of key glossary items, say 30.
3. These may be determined via a voting process, if required.
4. The initial terms are fully defined, and developed into "gold standard" definitions
5. From there, new terms can only be added to the glossary if there is a consensus they fall within the guidelines identified.

Proposed terms

Definitely in scope:

• content management system
• document management system
• records management system
• digital asset management
• enterprise content management
• dynamic publishing
• batch publishing
• content reuse
• content repurposing
• authoring template
• publishing template
• workflow
• versioning
• version control
• single source publishing
• structured authoring
• web content management

Possibilities:

• asset-based CMS TB: huh?
• centralised authoring
• content aggregation
• content audit
• content migration
• content syndication
• content type
• content element
• content deployment
• content preview
• content virtualization
• Darwin Information Typing Architecture
• decentralised authoring
• dynamic content
• digital rights management
• electronic documents & records management system (EDRMS)
• JSR170
• learning content management system
• learning management system
• metadata
• metrics
• mid-tier CMS TB:I think we should avoid this sort of vendor categorization
• open source CMS
• out-of-the-box CMS
• page-based CMS
• personalisation
• portal
• publishing models
• ROI
• RSS
• staging server
• groups
• roles

Definitely out of scope:

• General IT terminology (eg. API, backup, cascading style sheet, business process, CORBA, object oriented, DHTML, etc)
• Terminology from other fields (eg. change management, community of practice, creative commons, DTD, human computer interface, etc)
• General English terms (eg. annotation, approval, business case, calendar, conversion, etc)
• TB: I would add that terms for specific models (editorial or otherwise) are probably too vernacular for us as well. For example, I would drop "Decentralized authoring"

Questions and comments

JamesR: the terms listed at present are very technology (CMS) focused. Is this a problem, and should this be expanded to encompass a broader CM and business focus? If so, what should be added?

JamesR: please add items directly to the "Possibilities" list!

TonyB We also need to decide if we are going to use Intl English... Less of an issue for CMPros site (let the author decide), but we need to standardi(z/s)e in the Glossary. I'm OK with intl english, so long as someone reviews my labour...;-)

TB: I would turn to the IA people for the definitive statement on metadata and taxonomies

BobD: Starting with a "clean sheet of paper" seems disrespectful of the large amount of work already done, but I am ready to start.

I recommend we review all the existing terms/definitions to help us decide those most in need of new treatment by CM Pros.

I think "gold standard" may be the same hubris that stopped work on benchmarking best practices.

___

Back to Glossary Guidelines