Diff for Working with conditional text
Fri, 2006-02-10 21:55 by Bruce Esrig | Thu, 2006-03-16 20:08 by Bruce Esrig | ||
---|---|---|---|
< previous diff | next diff > | ||
Changes to Body | |||
Line 1 | Line 1 | ||
<p>Conditional processing, also known as profiling, is the filtering or flagging of information based on processing-time criteria. The filtering mechanism first matches against the criteria, and then takes a specified action. </p>
| <p>Conditional processing, also known as profiling, is the filtering or flagging of information based on processing-time criteria. The filtering mechanism first matches against the criteria, and then takes a specified action. </p>
| ||
- | <p>DITA provides several built-in attributes to hold the values for filter criteria for an element. These include:</p>
| + | <p>DITA provides several built-in attributes to hold the values for filter criteria for an element. These are:</p>
|
<ul>
| <ul>
| ||
- | <li>audience</li>
| + | <li>audience </li>
|
<li>platform </li>
| <li>platform </li>
| ||
<li>product </li>
| <li>product </li>
|
Conditional processing
Conditional processing, also known as profiling, is the filtering or flagging of information based on processing-time criteria. The filtering mechanism first matches against the criteria, and then takes a specified action.
DITA provides several built-in attributes to hold the values for filter criteria for an element. These are:
- audience
- platform
- product
- otherprops
- rev (for flagging only)
It is possible, for example, to specify the platform or audience that a particular paragraph applies to. The values of these attributes can then be leveraged by any number of processes, including filtering, flagging, search, and indexing.
There is a proposal for DITA 1.1 that will enable specializers to define their own metadata attributes for use in conditionally processing content.
The architectural specification describes conditional processing at