Designing an Information Set for Single-Sourcing  

The single source in a robust single source system is not any one of the outputs that may be created from that source. The single source is an information set from which many outputs may be created. Designing an information set is different from designing a document. Greater structure is required, and that structure must be available to the process that creates information products as output, not simply to the reader. A good information set design involves creating a data model, mapping information relationships, and defining patterns of change.

Baker, Mark. STC Proceedings (1999). Design>Content Management>Single Sourcing

Structured Content: What's in it for Writers?

Everyone has heard (or experienced) stories of CMS or knowledge management initiatives that did not work because content contributors refused to use the tools deployed or were unwilling or unable to supply content in the format required. The conclusion often reached is that writers cannot give up their WYSIWYG tools and that any attempt to make them do so is doomed to failure. On the other hand there are always those who will reply with stories of systems where writers have successfully adapted to the use of XML or SGML, and the CMS is working well. All that is required to duplicate this success, they maintain, is that writers must be forced and/or trained to use the new tools.

Baker, Mark. CMSwatch (2002). Articles>Content Management>Single Sourcing>Writing