Diff for 12017 design
Wed, 2008-05-14 02:16 by imagiczhang | Wed, 2008-05-14 05:44 by imagiczhang | ||
---|---|---|---|
next diff > | |||
Changes to Body | |||
Line 5 | Line 5 | ||
</p>
| </p>
| ||
<h2>Design for <em>item</em></h2>
| <h2>Design for <em>item</em></h2>
| ||
- | <h3>What user need will be met by this feature?</h3>
| + | <h3>What user need will be met by this feature?</h3>Users can use the same metadata structure in ditamap as the one defined in topic/prolog while the old format of metadata is still valid. With the same metadata structure in ditamap and topic, users can easily copy the metadata content from map to topic or vice versa by using conref.
|
- | <p>
| + | |
- |
| + | |
- | </p>
| + | |
- | <p>
| + | |
- | Try to include information about what the user wants to accomplish,
| + | |
- | rather than technical details of how it will be accomplished.
| + | |
- | </p>
| + | |
<h3>What is the technical design for the change?</h3>
| <h3>What is the technical design for the change?</h3>
| ||
<p>
| <p>
|
Revision of Wed, 2008-05-14 05:44:
12017 design
Design for 12017
Design for item
What user need will be met by this feature?
Users can use the same metadata structure in ditamap as the one defined in topic/prolog while the old format of metadata is still valid. With the same metadata structure in ditamap and topic, users can easily copy the metadata content from map to topic or vice versa by using conref.What is the technical design for the change?
Describe enough that developers can understand what changes will be made. If the design is extensive, it may be best to store it in another wiki page.
What sections of the toolkit will be impacted by the change?
This may include program names or sections that users interact with. This information should help in developing functional test cases (as opposed to existing regression test cases).
See also
Link to any external design information, such as a specification document from OASIS or an RFE submitted at SourceForge