Diff for 12017 design

Wed, 2008-05-14 05:44 by imagiczhangWed, 2008-05-14 08:14 by imagiczhang
Changes to Body
Line 8Line 8
 
<h3>What is the technical design for the change?</h3>
 
<h3>What is the technical design for the change?</h3>
 
<p>
 
<p>
-
Describe enough that developers can understand what changes will be
+
The change in DITA standard affects two modules in preprocess, conref resolution and move metadata.
-
made. If the design is extensive, it may be best to store it in another
+
</p>
-
wiki page.
+
<p>
  +
Conref which pull content from map to topic is different from that between topics because it doesn't need to specify topic id. Right now conref.xsl can handle this kind of reference but we still need to make sure that it can work between different specilizations.
  +
</p>
  +
<p>
  +
Move metadata needs to process the new metadata structure in ditamap. Fortunately, the code currently read the metadata from ditamap according to their @class value and doesn't depend on the actual structure of the metadata. Therefore, the code can process the new metadata after the dtd refactor and doesn't need to be updated. However, we still need to make sure the code can work on different specializations.
 
</p>
 
</p>
 
<h3><strong>What sections of the toolkit will be impacted by the change?</strong> </h3>
 
<h3><strong>What sections of the toolkit will be impacted by the change?</strong> </h3>
 
<p>
 
<p>
-
This may include program names or sections that users interact with.
+
Conref resolution and move metadata module in preprocess needs to pass verification test. Right now, they don't need to be updated.
-
This information should help in developing functional test cases (as
+
-
opposed to existing regression test cases).
+
 
</p>
 
</p>
 
<h3>See also</h3>
 
<h3>See also</h3>
 
<p>
 
<p>
-
Link to any external design information, such as a specification document from OASIS or an RFE submitted at SourceForge
+
none<br />
  +
 
</p>
 
</p>
 
 
Revision of Wed, 2008-05-14 08:14:

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?

The change in DITA standard affects two modules in preprocess, conref resolution and move metadata.

Conref which pull content from map to topic is different from that between topics because it doesn't need to specify topic id. Right now conref.xsl can handle this kind of reference but we still need to make sure that it can work between different specilizations.

Move metadata needs to process the new metadata structure in ditamap. Fortunately, the code currently read the metadata from ditamap according to their @class value and doesn't depend on the actual structure of the metadata. Therefore, the code can process the new metadata after the dtd refactor and doesn't need to be updated. However, we still need to make sure the code can work on different specializations.

What sections of the toolkit will be impacted by the change?

Conref resolution and move metadata module in preprocess needs to pass verification test. Right now, they don't need to be updated.

See also

none

XML.org Focus Areas: BPEL | DITA | ebXML | IDtrust | OpenDocument | SAML | UBL | UDDI
OASIS sites: OASIS | Cover Pages | XML.org | AMQP | CGM Open | eGov | Emergency | IDtrust | LegalXML | Open CSA | OSLC | WS-I