I few items I'd offer from our archives with background issues to consider. Feel free to add more!

Thoughts on design information from Erik Hennum

Objectives are design information.

It makes sense to link from the content to the design information.

This could be done by specializing <topicref> in the map, and having specialized topicrefs that point to the objectives associated with a topic.

This is analogous to the approach taken in the case of the taxonomy structure. For taxonomy, pointing to a topic in the taxonomy asserts "I am about this subject that I am pointing to." For design information, pointing to an element of the design asserts "I contribute to what this part of the design is calling for."

So pointing from content to an objective asserts "this content is in support of that objective".

Notice that this is a general theme that we can promote in DITA. We use topics to define design, and then use relationships from content to those topics to assert a formal relationship between the content and the design.

Doing this for design information for training is similar to what is done with the taxonomy specialization: the design information may not flow directly to the user, but it helps in authoring, to explain what content is about, and could be used as a basis for metadata or other information that does affect the user experience.


When Topic2 is a definitional topic, a hyperlink from Topic1 to Topic2 can be interpreted to assert a relationship, that Topic1 is "about" Topic2.


The specialization could be of <topicref>, <link>, and <xref>.

Related information

LearningContent/Structure/MapIssues (last edited 2009-08-12 18:03:13 by localhost)