Profiling with a Subject Scheme Map

A subject scheme map allows you to create custom profiling values and to manage the profiling attribute values used in the DITA topics without having to write a DITA specialization.

Subject scheme maps use key definitions to define a collection of profiling values. A map that uses the set of profiling values must reference at its highest level the subject scheme map in which the profiling values are defined, for example:
<topicref href="test.ditamap" format="ditamap" type="subjectScheme"/>

A profiled value should be a short and readable keyword that identifies a metadata attribute. For example, the audience metadata attribute may take a value that identifies the user group associated with a particular content unit. Typical user values for a medical-equipment product line might include therapist, oncologist, physicist, radiologist, surgeon, and so on. A subject scheme map can define a list of these audience values.

The following is an example of content from a subject scheme:

  <!-- Pull in a scheme that defines audience user values -->
  <subjectdef keys="users">
    <subjectdef keys="therapist"/>
    <subjectdef keys="oncologist"/>
    <subjectdef keys="physicist"/>
    <subjectdef keys="radiologist"/>
    <subjectdef keys="surgeon">
      <subjectdef keys="neuro-surgeon">
        <subjectdef keys="plastic-surgeon"/>
  <!-- Define an enumeration of the audience attribute, equal to
       each value in the users subject. This makes the following values
       valid for the audience attribute: therapist, oncologist, physicist, radiologist -->
    <attributedef name="audience"/>
    <subjectdef keyref="users"/>

When you edit a DITA topic in the Text or Author mode, Oxygen XML Author plugin collects all the profiling values from the Subject Scheme Map that is referenced in the map that is currently opened in the DITA Maps Manager. The values of profiling attribute defined in a Subject Scheme Map are available in the Edit Profiling Attribute dialog regardless of their mapping the Conditional Text preferences page.

In the example above, the values therapist, oncologist, physicist, and so on, are displayed in the content completion window as values for the audience attribute.

Now let us consider we have the following fragment in a topic:

<p audience="neuro-surgeon">Some text.. </p>

When you define a DITAVAL filter, you can, for instance, exclude anything that is profiled as surgeon:

     <prop action="exclude" att="audience" val="surgeon"/>

If you then transform the main DITA Map specifying the DITAVAL filter file in the transformation scenario, the p element should be excluded from the output. Thus, excluding the surgeon audience also excludes neuro-surgeon and plastic-surgeon from the output. More details about how hierarchical filtering and Subject Scheme Maps should work are found in the following specification: