Revision of What is your DITA Quotient (D.Q.)? from Fri, 2008-04-18 01:06

Wiki page: Submitted by Bob Doyle on Fri, 2008-04-18 01:06. Last updated on Fri, 2008-04-18 16:52.

The idea behind the DITA Quotient is a rough but quantitative numerical estimate of the applicabilty of DITA to your content. You simply answer ten questions and get an estimate of the value of DITA for your organization.

DITA News will publish the average numbers for everyone filling in the questionnaire, so you will be able to compare yourself to others. And we will track the average answers for the ten questions over time, to see how DITA is being adopted and how its various capabilities are being utilized.

Below is the questionnaire content. The questionnaire is anonymous. No information about your organization is collected.

To estimate your D.Q., fill in the online form at DITA News.

You will receive a printable list of your answers, which outline the main DITA


	Is content management important? Do you manage your content using a content management system?
	Yes // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question20Answer96", "radio", "Yes");
	No // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question20Answer97", "radio", "No");

	Is structure important? Do you structure your content? Do you have an information architecture (e.g., a taxonomy)? Do you have a document architecture (e.g., content model)?
	Information architecture and document architecture // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question21Answer99", "radio", "Information architecture and document architecture");
	Information architecture (e.g., taxonomy) // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question21Answer100", "radio", "Information architecture (e.g., taxonomy)");
	Document architecture (content models) // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question21Answer108", "radio", "Document architecture (content models)");
	Unstructured content // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question21Answer109", "radio", "Unstructured content");

	Is content reuse important? How much of your content gets reused in other contexts?
	A lot // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question22Answer101", "radio", "A lot");
	Some // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question22Answer102", "radio", "Some");
	A little // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question22Answer103", "radio", "A little");
	None // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question22Answer104", "radio", "None");

	Is single-sourcing important? Do you publish content to multiple output formats and channels (e.g., web/HTML and print/PDF)?
	Yes // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question24Answer110", "radio", "Yes");
	No // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question24Answer111", "radio", "No");

	Is translation/localization important? Is your content multi-lingual?
	Yes // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question25Answer112", "radio", "Yes");
	No // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question25Answer113", "radio", "No");

	Do you markup your content? Does your content have metadata?
	Semantic, structural, and style tags // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question26Answer114", "radio", "Semantic, structural, and style tags");
	Structural and style tags // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question26Answer115", "radio", "Structural and style tags");
	Style/format/presentation/layout tags only // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question26Answer116", "radio", "Style/format/presentation/layout tags only");

	Is your content modular? Is your content created in small chunks/topics?
	Yes. (content is readable in any order, like help topics) // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question28Answer119", "radio", "Yes. (content is readable in any order, like help topics)");
	No. (content is long linear narrative) // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question28Answer120", "radio", "No. (content is long linear narrative)");

	Is your content conditional? Do you serve different content to different audiences?
	Yes // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question27Answer117", "radio", "Yes");
	No // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question27Answer118", "radio", "No");

	Is your content task-oriented and minimalist? Do you follow these documentation best practices?
	Minimalist and task-oriented // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question23Answer105", "radio", "Minimalist and task-oriented");
	Task-oriented // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question23Answer106", "radio", "Task-oriented");
	Minimalist // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question23Answer107", "radio", "Minimalist");
	Neither // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question23Answer123", "radio", "Neither");

	Is standardization important? Do you want to use practices that are shared in your industry/profession?
	Yes // add this element pair to the array of preview elements aPreviewElement[aPreviewElement.length] = new fPreviewElement("Question29Answer121", "radio", "Yes");
	No.

Login to post comments
12192 reads

Revision of What is your DITA Quotient (D.Q.)? from Fri, 2008-04-18 01:06

Search

Download DITA

Browse

Recent Content

Subscribe

Site info

Who's who

Navigation

Hosted by:

Sponsored by:

Sponsored links: