This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
design:xml-tags [2014/01/24 14:34] paul [Document Metadata] |
design:xml-tags [2014/03/17 08:57] (current) paul Removed most of the content from the page, and backed it up at id=design:old-xml-tags |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | The following are proposed changes to the xml2rfc v2 vocabulary to make v3 of the vocabulary. The new vocabulary will be used for the canonical versions of RFCs. Discussion of these proposed changes are happening on [[rfc-interest@rfc-editor.org]]. | + | **This page, which mostly was used to mark closed issues, is no longer active. If you have questions, |
- | + | ||
- | ===== Archival Considerations ===== | + | |
- | + | ||
- | All auto-generated text that appears in the other formats needs to also exist in the canonical XML file as well. That text needs its own markup. The auto-generated text includes: | + | |
- | + | ||
- | | + | |
- | | + | |
- | * Table numbers | + | |
- | * IPR boilerplate | + | |
- | + | ||
- | + | ||
- | ===== Document Metadata ===== | + | |
- | + | ||
- | 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// | + | |
- | + | ||
- | Include feedback information so that generated documents can provide usable feedback links. | + | |
- | + | ||
- | 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.// | + | |
- | + | ||
- | ===== Contact Information ===== | + | |
- | + | ||
- | Add a mechanism for a ASCII fallback for non-ASCII names and addresses. Both forms should be searchable. | + | |
- | + | ||
- | Get rid of the restrictions in < | + | |
- | + | ||
- | ===== Figures ===== | + | |
- | + | ||
- | Clean up the set of overlapping attributes between < | + | |
- | + | ||
- | Remove anything that has to do with horizontal or vertical whitespace. | + | |
- | + | ||
- | Extend < | + | |
- | + | ||
- | ===== Floating Figures ===== | + | |
- | + | ||
- | Suggestion that we allow figures to have text wrapped around them. //General dislike for this, or thinking that we don't need it, on rfc-interest.// | + | |
- | + | ||
- | ===== Linking ===== | + | |
- | + | ||
- | Extend < | + | |
- | + | ||
- | Remove the " | + | |
- | + | ||
- | ===== Lists ===== | + | |
- | + | ||
- | Allow multiple paragraphs in a list item; eliminate the need to use < | + | |
- | + | ||
- | Create a new list style for dictionaries. //General agreement on rfc-interest.// | + | |
- | + | ||
- | ===== References to Lists ===== | + | |
- | + | ||
- | Items that need to be discussed. //Under discussion on rfc-interest starting 2014-01-09// | + | |
- | + | ||
- | - Ordered List ItemShould the reference value reflect the style, and in that case what is the correct reference value to use for each of the styles. | + | |
- | - 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 the default string be something other than Paragraph XXXXX | + | |
- | There have been a number of times where I have had a style=" | + | |
- | + | ||
- | ===== References ===== | + | |
- | + | ||
- | Allow overriding the " | + | |
- | + | ||
- | Add a way to add prose to a reference that avoids abuse of < | + | |
- | + | ||
- | Allow < | + | |
- | + | ||
- | Deprecate or remove the < | + | |
- | + | ||
- | ===== Remove from v2 Vocabulary ===== | + | |
- | + | ||
- | 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 ===== | + | |
- | + | ||
- | The < | + | |
- | + | ||
- | ===== Tables ===== | + | |
- | + | ||
- | Maybe allow for xrefs to be used in the < | + |