Diff for Design for implementing 12015
Wed, 2008-07-09 06:34 by imagiczhang | Wed, 2008-07-09 07:01 by imagiczhang | ||
---|---|---|---|
next diff > | |||
Changes to Body | |||
Line 10 | Line 10 | ||
technical design for the change</span></em></strong>
| technical design for the change</span></em></strong>
| ||
</p>
| </p>
| ||
- | <br />
| + | <p>
|
- | + | Design assumption:
| |
+ | </p>
| ||
+ | <p>
| ||
+ | The following design assumption are used to track the technical constraints of current implementation. If later, the containts are broken, we might change the design and implementation.
| ||
+ | </p>
| ||
+ | <ol>
| ||
+ | <li>XSLT cannot generate multiple outputs in a single transformation<br />
| ||
+ | Note: conref push is in the reverse direction to solve @conref. When resolving normal @conref, we need to read from multiple input and put the content in one output. So in conref push, we need to read single input and push it to differenct outputs. XSLT 1.0 we are using now does not support generate to multiple outputs and XSLT 2.0 standard support that. If later, XSLT 2.0 is adopted, we might need to refactor design and implementation to new ways.</li>
| ||
+ | </ol>
| ||
+ | <p>
| ||
+ |
| ||
+ | </p>
| ||
+ | <p>
| ||
+ |
| ||
+ | </p>
| ||
+ | <p>
| ||
+ |
| ||
+ | </p>
| ||
+ | <p>
| ||
+ |
| ||
+ | </p>
| ||
+ | <p>
| ||
+ |
| ||
+ | </p>
| ||
+ | <p>
| ||
+ |
| ||
+ | </p>
| ||
<h3><strong><em><span>What sections of the toolkit will be impacted by the
| <h3><strong><em><span>What sections of the toolkit will be impacted by the
| ||
change?</span></em></strong><em><span> </span></em></h3>
| change?</span></em></strong><em><span> </span></em></h3>
|
Revision of Wed, 2008-07-09 07:01:
Design for implementing 12015
Design for implementing "push conref " in the DITA Open Toolkit
What user need will be met by this feature?
Users can use conaction pairs combined with @conref to push the content to a specific location.
What is the technical design for the change
Design assumption:
The following design assumption are used to track the technical constraints of current implementation. If later, the containts are broken, we might change the design and implementation.
- XSLT cannot generate multiple outputs in a single transformation
Note: conref push is in the reverse direction to solve @conref. When resolving normal @conref, we need to read from multiple input and put the content in one output. So in conref push, we need to read single input and push it to differenct outputs. XSLT 1.0 we are using now does not support generate to multiple outputs and XSLT 2.0 standard support that. If later, XSLT 2.0 is adopted, we might need to refactor design and implementation to new ways.
What sections of the toolkit will be impacted by the change?
See also
none