User Tools

Site Tools


xml2rfc_examples

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
xml2rfc_examples [2020/10/27 16:37]
arusso
xml2rfc_examples [2020/10/28 15:14] (current)
arusso
Line 1: Line 1:
 ===== xml2rfc examples ===== ===== xml2rfc examples =====
 +
 +When considering "Is there a better way to do this?"
  
 ==== Summary ==== ==== Summary ====
   - xref to a section in another RFC and the authors want to include the section title   - xref to a section in another RFC and the authors want to include the section title
-  - xref to a section in another RFC when it's not desired to have the RFC number immediately afterwards. 
   - xref with format="title" doesn't work as expected   - xref with format="title" doesn't work as expected
   - <contact> inside <t> when providing more information than fullname    - <contact> inside <t> when providing more information than fullname 
Line 10: Line 11:
 ==== Details ==== ==== Details ====
  
-=== 1) xref to a section in another RFC and the authors want to include the section title ===+==== 1) xref to a section in another RFC and the authors want to include the section title ====
  
 It requires 2 xrefs to get the desired output (using sectionFormat="bare" for the first one). It requires 2 xrefs to get the desired output (using sectionFormat="bare" for the first one).
  
-See two examples at end of page+Note: As discussed with Henrik Nov. 2019.
  
-=== 2) xref to a section in another RFC when it's not desired to have the RFC number immediately afterwards===+Example A (from rfc8658.notprepped.xml)
  
-workaroundrephrase to avoid using sectionFormat="bare"+XML: 
 +<code> 
 +described in Section <xref target="RFC3575" section="2"  
 +sectionFormat="bare">IANA Considerations</xref> of <xref target="RFC3575"/> 
 +</code>
  
 +TEXT output:
 +<code>
 +described in Section 2 (IANA Considerations) of [RFC3575]
 +</code>
  
 +HTML output:
 +<html>
 +<p>defined in Section <a href="https://www.rfc-editor.org/rfc/rfc3575#section-2">2</a> (<a href="https://www.rfc-editor.org/rfc/rfc3575#section-2">IANA Considerations</a>) of [<a href="#RFC3575">RFC3575</a>]</p>
 +</html>
  
-=== 3) xref with format="title" doesn't work as expected === +-------------- 
 +Example B (from rfc8731.notprepped.xml) 
 + 
 +XML: 
 +<code> 
 +defined in Section <xref target="RFC5656" section="7.1"  
 +sectionFormat="bare">ECDH Message Numbers</xref> of <xref target="RFC5656"/> 
 +</code> 
 + 
 +TEXT output: 
 +<code> 
 +defined in Section 7.1 (ECDH Message Numbers) of [RFC5656] 
 +</code> 
 + 
 +HTML output: 
 +<html> 
 +<p>defined in Section <a href="https://www.rfc-editor.org/rfc/rfc5656#section-7.1">7.1</a> (<a href="https://www.rfc-editor.org/rfc/rfc5656#section-7.1">ECDH Message Numbers</a>) of [<a href="#RFC5656">RFC5656</a>]</p> 
 +</html> 
 + 
 + 
 +==== 2) xref with format="title" doesn't work as expected ====
  
 bc it includes square brackets around the title in the text file bc it includes square brackets around the title in the text file
Line 38: Line 71:
 <code> <code>
    This document obsoletes "["Dissemination of Flow Specification    This document obsoletes "["Dissemination of Flow Specification
-   Rules"]" [RFC5575] (see Appendix B for the differences).+   Rules"]" [RFC5575]
 </code> </code>
  
Line 46: Line 79:
 <code> <code>
   This document obsoletes ["Dissemination of Flow Specification Rules"]   This document obsoletes ["Dissemination of Flow Specification Rules"]
-   [RFC5575] (see Appendix B for the differences).+   [RFC5575]
 </code> </code>
  
  
-=== 4) use <contact> inside <t> when providing more information than fullname ===+==== 3) use <contact> inside <t> when providing more information than fullname ====
  
-The functionality exists when <contact> is outside <t>  (e.g., a contributor listed in the style of an address block), but when the <contact> is in <t> in a list, it's not possible. So we end up putting data about the individual outside the <contact> element.+It's possible to include more info when <contact> is outside <t> (e.g., a contributor listed in the style of an address block), but when the <contact> is in <t>, it's not possible. So we end up putting the data about the individual outside the <contact> element. 
  
 a) name + org\\ a) name + org\\
-''<t><contact fullname="Fabio Maino"/>, Cisco Systems, Inc.</t>''\\ +XML: ''<t><contact fullname="Fabio Maino"/>, Cisco Systems, Inc.</t>''\\ 
-(file: draft-ietf-lisp-gpe-19.xml - in the queue)+(file: draft-ietf-lisp-gpe-19.xml - in the queue)\\ 
 +Original (in a list): ''    Fabio Maino, Cisco Systems, Inc.''
  
 b) name + email\\ b) name + email\\
-''<t><contact fullname="Ari Keränen"/> &lt;ari.keranen@ericsson.com&gt;</t>''\\ +XML: ''<t><contact fullname="Ari Keränen"/> &lt;ari.keranen@ericsson.com&gt;</t>''\\ 
-(file: rfc8790.notprepped.xml)+(file: rfc8790.notprepped.xml)\\ 
 +Original (in a registration template): ''Author:  Ari Keranen ari.keranen@ericsson.com''
  
 c) name + email + org\\ c) name + email + org\\
-''<t><contact fullname="Jiantao Fu"/> &lt;jianfu@cisco.com&gt; of Cisco Systems''\\ +XML: ''<t><contact fullname="Jiantao Fu"/> &lt;jianfu@cisco.com&gt; of Cisco Systems''\\ 
-(file: rfc8698.notprepped.xml)+(file: rfc8698.notprepped.xml)\\ 
 +Original (in a paragraph in "Contributors"): ''<nowiki> Jiantao Fu <jianfu@cisco.com> of Cisco Systems</nowiki>''
  
 +Thinking aloud: ability to put the data in the contact element and have a decent rendering when in <t> (Currently, if we put additional data in the contact element when it's in <t>, the additional data doesn't appear in the output at all.)
  
-=== 5) get a <dl> with a blank line between <dt> and <dd> ===+==== 4) get a <dl> with a blank line between <dt> and <dd> ====
  
 Mail sent 2020-10-15 with details. Mail sent 2020-10-15 with details.
Line 75: Line 112:
 suggestion from Jean for dl's newline attribute: newline="false|break|space" suggestion from Jean for dl's newline attribute: newline="false|break|space"
  
-file: rfc8940.xml (draft-ietf-emu-eap-session-id-07) in AUTH48 currently+file: published as rfc8940.xml (draft-ietf-emu-eap-session-id-07) 
  
-=== More on #1 === 
  
-=== xref to published RFC with section number and section title === 
  
-Note: As discussed with Henrik Nov. 2019. 
- 
-Example 1 (from rfc8658.notprepped.xml) 
- 
-XML: 
-<code> 
-described in Section <xref target="RFC3575" section="2"  
-sectionFormat="bare">IANA Considerations</xref> of <xref target="RFC3575"/> 
-</code> 
- 
-TEXT output: 
-<code> 
-described in Section 2 (IANA Considerations) of [RFC3575] 
-</code> 
- 
-HTML output: 
-<html> 
-<p>defined in Section <a href="https://www.rfc-editor.org/rfc/rfc3575#section-2">2</a> (<a href="https://www.rfc-editor.org/rfc/rfc3575#section-2">IANA Considerations</a>) of [<a href="#RFC3575">RFC3575</a>]</p> 
-</html> 
- 
-Example 2 (from rfc8731.notprepped.xml) 
- 
-XML: 
-<code> 
-defined in Section <xref target="RFC5656" section="7.1"  
-sectionFormat="bare">ECDH Message Numbers</xref> of <xref target="RFC5656"/> 
-</code> 
- 
-TEXT output: 
-<code> 
-defined in Section 7.1 (ECDH Message Numbers) of [RFC5656] 
-</code> 
- 
-HTML output: 
-<html> 
-<p>defined in Section <a href="https://www.rfc-editor.org/rfc/rfc5656#section-7.1">7.1</a> (<a href="https://www.rfc-editor.org/rfc/rfc5656#section-7.1">ECDH Message Numbers</a>) of [<a href="#RFC5656">RFC5656</a>]</p> 
-</html> 
xml2rfc_examples.1603841876.txt.gz · Last modified: 2020/10/27 16:37 by arusso