Closed ajeanmahoney closed 4 months ago
@cabo because he started the ball rolling with #1067
A note on the FYI subseries -- this subseries was concluded with RFC 6360 and is not expected to be revived.
The RPC believes this feature request is fully specified and can move forward. The FYI subseries is included so that all subseries will be treated consistently by the tools.
The target
attribute for referencegroup
is optional.
What is the expected output when target
is not present?
See examples for new presentations at https://github.com/ietf-tools/xml2rfc/pull/1102#issue-2133697366
The target attribute for referencegroup is optional. What is the expected output when target is not present?
For RFC references, xml2rfc currently provides a URL in the output if the target attribute is empty. Can the same be done here? (Although I hope that authors use xi:includes for subseries references to reduce errors).
@ajeanmahoney, https://github.com/ietf-tools/xml2rfc/pull/1102/commits/205c09c84fb4f204d727ae64c56dab70d61fe768 adds this feature.
Examples: | Format | Example |
---|---|---|
XML | draft-foobar-00.xml | |
Text | draft-foobar-00.txt | |
HTML | draft-foobar-00.html | |
draft-foobar-00.pdf |
Description
Please add introductory text to the subseries reference that captures the "name" of the subseries: "Internet Standard NN", "Best Current Practice NN", or "For Your Information NN", and provide a link to the subseries info page. Add the text "At the time of writing, this [STD|BCP|FYI] comprises the following:" as a lead-in to the list of RFCs within the subseries.
For the RFCs listed within the subseries, please provide each RFC's DOI and info URL as is currently done for individual RFC references.
An example of a single-RFC subseries reference in this requested format:
An example of a multiple-RFC subseries reference in this requested format:
Requested intro for a BCP:
Requested intro for an FYI:
Code of Conduct