design:finalizer
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
design:finalizer [2015/05/13 12:18] paul Added rfc/@scripts |
design:finalizer [2015/05/22 15:07] (current) 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. | + | 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. |
| ==Canonical RFC preparation== | ==Canonical RFC preparation== | ||
| Line 34: | Line 39: | ||
| * Fill in document publish date | * Fill in document publish date | ||
| * Fill in expires date, if in I-D mode | * Fill in expires date, if in I-D mode | ||
| - | * Fill in " | ||
| * Fill in any default values for attributes on elements, except t/ | * Fill in any default values for attributes on elements, except t/ | ||
| * If the ''< | * If the ''< | ||
| Line 46: | Line 50: | ||
| * figure: '' | * figure: '' | ||
| * (abstract, note, t, aside, blockquote, li, dt, artwork, sourcecode, references): | * (abstract, note, t, aside, blockquote, li, dt, artwork, sourcecode, references): | ||
| - | * add start attribute to every ''< | + | * Add start attribute to every ''< |
| - | * sort refs, if desired | + | * Sort the references, if desired |
| * Resolve all ''< | * Resolve all ''< | ||
| * Ensure the target is valid | * Ensure the target is valid | ||
| Line 56: | Line 60: | ||
| * Check SVG schema against our TinySVG profile | * Check SVG schema against our TinySVG profile | ||
| * else if '' | * else if '' | ||
| - | * Add '' | + | * Add finalizedTime to attribute to '' |
| + | * Add a ''< | ||
| + | * Determine all the characters used in the document and fill in " | ||
| + | * Ensure that the output has the " | ||
| * Pretty-format the XML output. | * Pretty-format the XML output. | ||
| * This step might be controversial | * This step might be controversial | ||
| * Ensure full compliance to v3 schema, without any deprecated elements or attributes, and error if any issues are found | * Ensure full compliance to v3 schema, without any deprecated elements or attributes, and error if any issues are found | ||
| - | * Ensures that the output has the " | ||
design/finalizer.1431544731.txt.gz · Last modified: 2015/05/13 12:18 by paul
Page Tools
