User Tools

Site Tools


design:finalizer

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
design:finalizer [2015/05/14 10:29]
paul Add DOI
design:finalizer [2015/05/22 15:07]
paul Added warning that the page is out of date.
Line 1: Line 1:
 +**THIS PAGE IS NO LONGER IN USE AND IS OUT-OF-DATE.**
 +
 +**PLEASE SEE draft-hoffman-rfcv3-preptool INSTEAD**
 +
 ===v3 prep tool usage scenarios=== ===v3 prep tool usage scenarios===
  
Line 14: Line 18:
 ==Internet-Draft submission== ==Internet-Draft submission==
  
-When the IETF draft submission tool accepts v3 XML as an input format, the submission tool runs the submitted file through the prep tool. If the tool finds no errors, it keeps two XML files: the submitted file and the prepped file. The prepped file is used by the IETF formatters to create outputs such as HTML, PDF, and text (or the tools act in a way indistinguishable from this). The message sent out by the draft submission tool includes a link to the original XML as well as the other outputs, including the prepped XML.  +When the IETF draft submission tool accepts v3 XML as an input format, the submission tool runs the submitted file through the prep tool. If the tool finds no errors, it keeps two XML files: the submitted file and the prepped file
 +This prepped file represents a self-contained record of what any external references resolved to at the time of submission. The prepped file is used by the IETF formatters to create outputs such as HTML, PDF, and text (or the tools act in a way indistinguishable from this). The message sent out by the draft submission tool includes a link to the original XML as well as the other outputs, including the prepped XML.  
  
-The prepped XML can be used by tools not yet developed to output new formats that have as similar output as possible to the current IETF formatters.  For example, if we create a .mobi output renderer later, we can run that renderer on all of the prepped XML that we have saved, ensuring that all of the part numbers and boilerplate we be the same as produced by the previous IETF formatters at the time the document was first uploaded.+The prepped XML can be used by tools not yet developed to output new formats that have as similar output as possible to the current IETF formatters.  For example, if we create a .mobi output renderer later, we can run that renderer on all of the prepped XML that we have saved, ensuring that the content of included external references and all of the part numbers and boilerplate will be the same as what was produced by the previous IETF formatters at the time the document was first uploaded.
  
 ==Canonical RFC preparation== ==Canonical RFC preparation==
design/finalizer.txt · Last modified: 2015/05/22 15:07 by paul