Diff for Working with conditional text
Tue, 2007-09-18 23:01 by syeo | Tue, 2007-09-18 23:02 by syeo | ||
---|---|---|---|
Copy of the revision from Mon, 2007-09-17 17:54. | Copy of the revision from Thu, 2006-03-23 13:11. | ||
< previous diff | next diff > | ||
Changes to Body | |||
Line 1 | Line 1 | ||
- | Moved to wiki: http://dita.xml.org/conditional-text
| + | <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 are:</p>
| |
+ | <ul>
| ||
+ | <li>audience </li>
| ||
+ | <li>platform </li>
| ||
+ | <li>product </li>
| ||
+ | <li>otherprops </li>
| ||
+ | <li>rev (for flagging only) </li>
| ||
+ | </ul>
| ||
+ | <p>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.</p>
| ||
+ | <p>There is a proposal for DITA 1.1 that will enable specializers to define their own metadata attributes for use in conditionally processing content.</p>
| ||
+ | <p>The architectural specification describes conditional processing at</p>
| ||
+ | <ul>
| ||
+ | <li><font size="2"><a href="http://docs.oasis-open.org/dita/v1.0/archspec/condproc.html">http://docs.oasis-open.org/dita/v1.0/archspec/condproc.html</a></font> </li>
| ||
+ | </ul>
| ||
+ | <p>Editors for the Architecture area:</p>
| ||
+ | <ul>
| ||
+ | <li><a title="View user profile." href="http://dita.xml.org/user/26"><strong><font color="#ac083e">Bruce Esrig</font></strong></a> </li>
| ||
+ | <li><a title="View user profile." href="http://dita.xml.org/user/25"><strong><font color="#ac083e">Michael Priestley</font></strong></a> </li>
| ||
+ | </ul> |
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
Editors for the Architecture area: