design:xml-tags
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
design:xml-tags [2014/01/24 13:27] paul [Remove from v2 Vocabulary] |
design:xml-tags [2014/03/15 20:12] paul Updated for -03 |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| ===== Document Metadata ===== | ===== Document Metadata ===== | ||
| - | Extend the concept of language tagging to at least examples and contact information to address potential CJK font confusion. //Under discussion on rfc-interest | + | Extend the concept of language tagging to at least examples and contact information to address potential CJK font confusion. //No objections to this for v3 from rfc-interest. -00// |
| - | Provide a way to indicate the intended level on the standards track while a document is still an Internet-Draft. //Under discussion on rfc-interest | + | Include feedback information so that generated documents can provide usable feedback links. //Wondering how this is supposed to work: is it only for metadata, or is a processor supposed to turn it into text. If the latter, where in the RFC does the text appear? Need to take back to rfc-interest.// |
| - | Include feedback information so that generated documents can provide usable feedback links. //Under discussion on rfc-interest | + | Make the < |
| - | Make the < | + | There should be a way to mark a section as something that will not appear in the published RFC. //No objections to this for v3 from rfc-interest. -00// |
| - | + | ||
| - | There should be a way to mark a section as something that will not appear in the published RFC. //Under discussion on rfc-interest | + | |
| ===== Contact Information ===== | ===== Contact Information ===== | ||
| - | Add a mechanism for a ASCII fallback for non-ASCII names and addresses. Both forms should be searchable. | + | Add a mechanism for a ASCII fallback for non-ASCII names and addresses. Both forms should be searchable. |
| - | Get rid of the restrictions in < | + | Get rid of the restrictions in < |
| ===== Figures ===== | ===== Figures ===== | ||
| Line 35: | Line 33: | ||
| Remove anything that has to do with horizontal or vertical whitespace. | Remove anything that has to do with horizontal or vertical whitespace. | ||
| - | Extend < | + | Extend < |
| ===== Floating Figures ===== | ===== Floating Figures ===== | ||
| Line 49: | Line 47: | ||
| ===== Lists ===== | ===== Lists ===== | ||
| - | Allow multiple paragraphs in a list item; eliminate the need to use < | + | Allow multiple paragraphs in a list item; eliminate the need to use < |
| - | Create a new list style for dictionaries. //General agreement on rfc-interest.// | + | Create a new list style for dictionaries. //General agreement on rfc-interest. |
| ===== References to Lists ===== | ===== References to Lists ===== | ||
| - | Items that need to be discussed. //Under discussion on rfc-interest starting 2014-01-09// | + | Items that need to be discussed. //Short discussion on rfc-interest starting 2014-01-09, no conclusion// |
| - | - Ordered List ItemShould | + | - Should |
| - Should the reference value be built from the chain of list elements? | - Should the reference value be built from the chain of list elements? | ||
| - Should it be possible to generate a reference that is a partial list of the chain of elements | - Should it be possible to generate a reference that is a partial list of the chain of elements | ||
| - Should the default string be something other than Paragraph XXXXX | - Should the default string be something other than Paragraph XXXXX | ||
| There have been a number of times where I have had a style=" | There have been a number of times where I have had a style=" | ||
| + | |||
| ===== References ===== | ===== References ===== | ||
| - | Allow overriding the " | + | Allow overriding the " |
| Add a way to add prose to a reference that avoids abuse of < | Add a way to add prose to a reference that avoids abuse of < | ||
| - | Allow < | + | Allow < |
| Deprecate or remove the < | Deprecate or remove the < | ||
| Line 76: | Line 75: | ||
| In v2, there are a few elements that require their sub-elements to be in a certain order even though that order isn't really needed by the XML processor. For example, < | In v2, there are a few elements that require their sub-elements to be in a certain order even though that order isn't really needed by the XML processor. For example, < | ||
| - | < | + | < |
| ===== Sections Without Numbers ===== | ===== Sections Without Numbers ===== | ||
| Line 85: | Line 84: | ||
| Maybe allow for xrefs to be used in the < | Maybe allow for xrefs to be used in the < | ||
| + | |||
| + | ===== New Formatting ===== | ||
| + | |||
| + | Add a < | ||
design/xml-tags.txt · Last modified: 2014/03/17 08:57 by paul
Page Tools
