![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 1661 for rfc2629xslt
- Timestamp:
- 02/05/12 15:41:36 (9 years ago)
- Location:
- rfc2629xslt
- Files:
-
- 1 added
- 9 edited
-
gen-w3c-reference.xslt (added)
-
rfc2629-ext.rnc (modified) (18 diffs)
-
rfc2629.xslt (modified) (15 diffs)
-
rfc2629toXHTML.xslt (modified) (15 diffs)
-
rfc2629xslt.html (modified) (41 diffs)
-
rfc2629xslt.pdf (modified) (previous)
-
rfc2629xslt.txt (modified) (28 diffs)
-
rfc2629xslt.xml (modified) (7 diffs)
-
samples/rfc2629.xslt (modified) (15 diffs)
-
testcase.html (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
rfc2629xslt/rfc2629-ext.rnc
r1652 r1661 100 100 | cref 101 101 | spanx 102 | x_anchor-alias)* 103 } 102 | x_anchor-alias* 103 | x_bcp14)* 104 } 104 105 105 106 # Redefine <postamble> to allow our extension elements … … 133 134 attlist.rfc, 134 135 x_link*, 136 x_feedback?, 135 137 x_assign-section-number*, 136 138 front, … … 198 200 attribute x:annotation { ATEXT }? 199 201 200 # Extend attribute set for <c> (see Section 11.2 3)202 # Extend attribute set for <c> (see Section 11.24) 201 203 attlist.c &= 202 204 attribute anchor { xsd:ID }? 203 205 204 # Extend attribute set for <iref> (see Section 11.2 3)206 # Extend attribute set for <iref> (see Section 11.24) 205 207 attlist.iref &= 206 208 attribute x:for-anchor { ATEXT }? 207 209 208 # Extend attribute set for <list> (see Section 11.2 4)210 # Extend attribute set for <list> (see Section 11.25) 209 211 attlist.list &= 210 212 attribute x:indent { ATEXT }? … … 219 221 attribute x:maturity-level { "proposed" | "draft" | "internet" }? 220 222 221 # Extend attribute set for <section> (see Section 11.2 6)223 # Extend attribute set for <section> (see Section 11.27) 222 224 attlist.section &= 223 225 attribute x:fixed-section-number { ATEXT }? … … 235 237 attribute x:annotation { ATEXT }? 236 238 237 # Extend attribute set for <xref> (see Section 11.2 7)239 # Extend attribute set for <xref> (see Section 11.28) 238 240 attlist.xref &= 239 241 attribute x:fmt { "()" | "," | "anchor" | "of" | "number" | "sec" | … … 252 254 element x:anchor-alias { 253 255 attribute value { TEXT }, 256 empty 257 } 258 259 # Supply feedback links (see Section 11.10) 260 x_feedback = 261 element x:feedback { 262 attribute template { TEXT }, 254 263 empty 255 264 } … … 345 354 } 346 355 347 # Heading (see Section 11.1 0)356 # Heading (see Section 11.11) 348 357 x_h = 349 358 element x:h { … … 351 360 } 352 361 353 # Heading (see Section 11.1 1)362 # Heading (see Section 11.12) 354 363 x_highlight = 355 364 element x:highlight { … … 357 366 } 358 367 359 # Length Measurement (see Section 11.1 2)368 # Length Measurement (see Section 11.13) 360 369 x_length-of = 361 370 element x:length-of { … … 365 374 } 366 375 367 # Link (see Section 11.1 3)376 # Link (see Section 11.14) 368 377 x_link = 369 378 element x:link { 370 attribute basename { URI } ,371 attribute href { URI } ,379 attribute basename { URI }?, 380 attribute href { URI }?, 372 381 attribute title { TEXT }?, 373 382 attribute rel { TEXT }, … … 375 384 } 376 385 377 # Extended list item (see Section 11.1 4)386 # Extended list item (see Section 11.15) 378 387 x_lt = 379 388 element x:lt { … … 383 392 } 384 393 385 # Note (see Section 11.1 5)394 # Note (see Section 11.16) 386 395 x_note = 387 396 element x:note { … … 389 398 } 390 399 391 # Signal XML content (see Section 11.1 6)400 # Signal XML content (see Section 11.17) 392 401 x_parse-xml = 393 402 element x:parse-xml { … … 396 405 } 397 406 398 # Inline prose in a reference (see Section 11.1 7)407 # Inline prose in a reference (see Section 11.18) 399 408 x_prose = 400 409 element x:prose { … … 402 411 } 403 412 404 # Inline quote (see Section 11.1 8)413 # Inline quote (see Section 11.19) 405 414 x_q = 406 415 element x:q { … … 408 417 } 409 418 410 # Anchor reference (see Section 11. 19)419 # Anchor reference (see Section 11.20) 411 420 x_ref = 412 421 element x:ref { … … 415 424 } 416 425 417 # source information (see Section 11.2 0)426 # source information (see Section 11.21) 418 427 x_source = 419 428 element x:source { … … 423 432 } 424 433 425 # superscript (see Section 11.2 1)434 # superscript (see Section 11.22) 426 435 x_sup = 427 436 element x:sup { -
rfc2629xslt/rfc2629.xslt
r1652 r1661 31 31 32 32 <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 33 version=" 1.0"33 version="2.0" 34 34 35 35 xmlns:date="http://exslt.org/dates-and-times" … … 662 662 663 663 <xsl:template match="artwork"> 664 <xsl:if test="not(ancestor::ed:del) and $xml2rfc-ext-parse-xml-in-artwork='yes' and function-available('myns:parseXml')" >664 <xsl:if test="not(ancestor::ed:del) and $xml2rfc-ext-parse-xml-in-artwork='yes' and function-available('myns:parseXml')" use-when="function-available('myns:parseXml')"> 665 665 <xsl:if test="contains(.,'<?xml')"> 666 666 <xsl:variable name="body" select="substring-after(substring-after(.,'<?xml'),'?>')" /> … … 3953 3953 <xsl:when test="self::xref"> 3954 3954 <xsl:variable name="target" select="@target"/> 3955 <xsl:comment>workaround for Saxon 9.1 bug; force evalutation of: <xsl:value-of select="$target"/></xsl:comment> 3956 <xsl:variable name="no"><xsl:number level="any" count="xref[@target=$target]"/></xsl:variable> 3955 3957 <xsl:text>#</xsl:text> 3956 3958 <xsl:value-of select="$anchor-prefix"/> 3957 3959 <xsl:text>.xref.</xsl:text> 3958 <xsl:value-of select="@target"/>.<xsl:number level="any" count="xref[@target=$target]"/> 3960 <xsl:value-of select="@target"/> 3961 <xsl:text>.</xsl:text> 3962 <xsl:value-of select="$no"/> 3959 3963 </xsl:when> 3960 3964 <xsl:when test="self::iref"> … … 4198 4202 <xsl:sort select="translate(@subitem,$lcase,$ucase)" /> 4199 4203 4200 <xsl:if test="generate-id(.) = generate-id(key('index-item-subitem',concat(@item,'..',@subitem)) )">4204 <xsl:if test="generate-id(.) = generate-id(key('index-item-subitem',concat(@item,'..',@subitem))[1])"> 4201 4205 4202 4206 <xsl:variable name="in-artwork2" select="key('index-item-subitem',concat(@item,'..',@subitem))[@primary='true' and ancestor::artwork]" /> … … 5295 5299 <xsl:choose> 5296 5300 <xsl:when test="$target"> 5297 <a href="#{$target /@anchor}" class="smpl">5301 <a href="#{$target[1]/@anchor}" class="smpl"> 5298 5302 <xsl:call-template name="copy-anchor"/> 5299 5303 <!-- to be indexed? --> … … 5455 5459 </xsl:if> 5456 5460 <xsl:choose> 5457 <xsl:when test="function-available('myns:parseXml')" >5461 <xsl:when test="function-available('myns:parseXml')" use-when="function-available('myns:parseXml')"> 5458 5462 <xsl:if test="myns:parseXml(concat($cleaned,''))!=''"> 5459 5463 <xsl:call-template name="error"> … … 5462 5466 </xsl:if> 5463 5467 </xsl:when> 5464 <xsl:when test="function-available('saxon:parse')" >5468 <xsl:when test="function-available('saxon:parse')" use-when="function-available('saxon:parse')"> 5465 5469 <xsl:variable name="parsed" select="saxon:parse(concat($cleaned,''))"/> 5466 5470 <xsl:if test="$parsed='foo'"> … … 5468 5472 </xsl:if> 5469 5473 </xsl:when> 5474 <xsl:when test="false()"></xsl:when> 5470 5475 <xsl:otherwise></xsl:otherwise> 5471 5476 </xsl:choose> … … 6533 6538 <xsl:text>http://greenbytes.de/tech/webdav/rfc2629.xslt, </xsl:text> 6534 6539 <!-- when RCS keyword substitution in place, add version info --> 6535 <xsl:if test="contains('$Revision: 1.57 2$',':')">6536 <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.57 2$', 'Revision: '),'$','')),', ')" />6540 <xsl:if test="contains('$Revision: 1.576 $',':')"> 6541 <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.576 $', 'Revision: '),'$','')),', ')" /> 6537 6542 </xsl:if> 6538 <xsl:if test="contains('$Date: 2012-0 3-19 14:26:22$',':')">6539 <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 2012-0 3-19 14:26:22$', 'Date: '),'$','')),', ')" />6543 <xsl:if test="contains('$Date: 2012-05-02 14:26:45 $',':')"> 6544 <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 2012-05-02 14:26:45 $', 'Date: '),'$','')),', ')" /> 6540 6545 </xsl:if> 6541 6546 <xsl:value-of select="concat('XSLT vendor: ',system-property('xsl:vendor'),' ',system-property('xsl:vendor-url'))" /> … … 7032 7037 <!-- diag support --> 7033 7038 <xsl:template name="lineno"> 7034 <xsl:if test="function-available('saxon-old:line-number')" >7039 <xsl:if test="function-available('saxon-old:line-number')" use-when="function-available('saxon-old:line-number')"> 7035 7040 <xsl:if test="saxon-old:line-number() > 0"> 7036 7041 <xsl:text> (at line </xsl:text> … … 7050 7055 </xsl:if> 7051 7056 </xsl:if> 7052 <xsl:if test="function-available('saxon:line-number')" >7057 <xsl:if test="function-available('saxon:line-number')" use-when="function-available('saxon:line-number')"> 7053 7058 <xsl:if test="saxon:line-number() > 0"> 7054 7059 <xsl:text> (at line </xsl:text> … … 7101 7106 <xsl:variable name="current-year"> 7102 7107 <xsl:choose> 7103 <xsl:when test="function-available('date:date-time')" >7108 <xsl:when test="function-available('date:date-time')" use-when="function-available('date:date-time')"> 7104 7109 <xsl:value-of select="substring-before(date:date-time(),'-')"/> 7110 </xsl:when> 7111 <xsl:when test="function-available('current-date')"> 7112 <xsl:value-of select="substring-before(string(current-date()),'-')"/> 7105 7113 </xsl:when> 7106 7114 <xsl:otherwise/> … … 7110 7118 <xsl:variable name="current-month"> 7111 7119 <xsl:choose> 7112 <xsl:when test="function-available('date:date-time')" >7120 <xsl:when test="function-available('date:date-time')" use-when="function-available('date:date-time')"> 7113 7121 <xsl:value-of select="substring-before(substring-after(date:date-time(),'-'),'-')"/> 7122 </xsl:when> 7123 <xsl:when test="function-available('current-date')"> 7124 <xsl:value-of select="substring-before(substring-after(string(current-date()),'-'),'-')"/> 7114 7125 </xsl:when> 7115 7126 <xsl:otherwise/> … … 7119 7130 <xsl:variable name="current-day"> 7120 7131 <xsl:choose> 7121 <xsl:when test="function-available('date:date-time')" >7132 <xsl:when test="function-available('date:date-time')" use-when="function-available('date:date-time')"> 7122 7133 <xsl:value-of select="substring-after(substring-after(substring-before(date:date-time(),'T'),'-'),'-')"/> 7134 </xsl:when> 7135 <xsl:when test="function-available('current-dateTime')"> 7136 <xsl:value-of select="substring-after(substring-after(substring-before(string(current-dateTime()),'T'),'-'),'-')"/> 7123 7137 </xsl:when> 7124 7138 <xsl:otherwise/> … … 7288 7302 </xsl:template> 7289 7303 7304 <xsl:function name="exslt:node-set"> 7305 <xsl:param name="node"/> 7306 <xsl:copy-of select="$node"/> 7307 </xsl:function> 7308 7290 7309 </xsl:transform> -
rfc2629xslt/rfc2629toXHTML.xslt
r1652 r1661 1 1 <?xml version="1.0" encoding="ISO-8859-1"?> 2 2 <!--Auto-generated from rfc2629.xslt through HTMLtoXHTML.xslt--> 3 <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:date="http://exslt.org/dates-and-times" xmlns:ed="http://greenbytes.de/2002/rfcedit" xmlns:exslt="http://exslt.org/common" xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:myns="mailto:julian.reschke@greenbytes.de?subject=rcf2629.xslt" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:saxon="http://saxon.sf.net/" xmlns:saxon-old="http://icl.com/saxon" xmlns:x="http://purl.org/net/xml2rfc/ext" xmlns:xhtml="http://www.w3.org/1999/xhtml" version=" 1.0" exclude-result-prefixes="date ed exslt msxsl myns rdf saxon saxon-old x xhtml">3 <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:date="http://exslt.org/dates-and-times" xmlns:ed="http://greenbytes.de/2002/rfcedit" xmlns:exslt="http://exslt.org/common" xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:myns="mailto:julian.reschke@greenbytes.de?subject=rcf2629.xslt" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:saxon="http://saxon.sf.net/" xmlns:saxon-old="http://icl.com/saxon" xmlns:x="http://purl.org/net/xml2rfc/ext" xmlns:xhtml="http://www.w3.org/1999/xhtml" version="2.0" exclude-result-prefixes="date ed exslt msxsl myns rdf saxon saxon-old x xhtml"> 4 4 5 5 <xsl:strip-space elements="back front list middle rfc section"/> … … 530 530 531 531 <xsl:template match="artwork"> 532 <xsl:if test="not(ancestor::ed:del) and $xml2rfc-ext-parse-xml-in-artwork='yes' and function-available('myns:parseXml')" >532 <xsl:if test="not(ancestor::ed:del) and $xml2rfc-ext-parse-xml-in-artwork='yes' and function-available('myns:parseXml')" use-when="function-available('myns:parseXml')"> 533 533 <xsl:if test="contains(.,'<?xml')"> 534 534 <xsl:variable name="body" select="substring-after(substring-after(.,'<?xml'),'?>')"/> … … 3821 3821 <xsl:when test="self::xref"> 3822 3822 <xsl:variable name="target" select="@target"/> 3823 <xsl:comment>workaround for Saxon 9.1 bug; force evalutation of: <xsl:value-of select="$target"/></xsl:comment> 3824 <xsl:variable name="no"><xsl:number level="any" count="xref[@target=$target]"/></xsl:variable> 3823 3825 <xsl:text>#</xsl:text> 3824 3826 <xsl:value-of select="$anchor-prefix"/> 3825 3827 <xsl:text>.xref.</xsl:text> 3826 <xsl:value-of select="@target"/>.<xsl:number level="any" count="xref[@target=$target]"/> 3828 <xsl:value-of select="@target"/> 3829 <xsl:text>.</xsl:text> 3830 <xsl:value-of select="$no"/> 3827 3831 </xsl:when> 3828 3832 <xsl:when test="self::iref"> … … 4066 4070 <xsl:sort select="translate(@subitem,$lcase,$ucase)"/> 4067 4071 4068 <xsl:if test="generate-id(.) = generate-id(key('index-item-subitem',concat(@item,'..',@subitem)) )">4072 <xsl:if test="generate-id(.) = generate-id(key('index-item-subitem',concat(@item,'..',@subitem))[1])"> 4069 4073 4070 4074 <xsl:variable name="in-artwork2" select="key('index-item-subitem',concat(@item,'..',@subitem))[@primary='true' and ancestor::artwork]"/> … … 5151 5155 <xsl:choose> 5152 5156 <xsl:when test="$target"> 5153 <a xmlns="http://www.w3.org/1999/xhtml" href="#{$target /@anchor}" class="smpl">5157 <a xmlns="http://www.w3.org/1999/xhtml" href="#{$target[1]/@anchor}" class="smpl"> 5154 5158 <xsl:call-template name="copy-anchor"/> 5155 5159 <!-- to be indexed? --> … … 5311 5315 </xsl:if> 5312 5316 <xsl:choose> 5313 <xsl:when test="function-available('myns:parseXml')" >5317 <xsl:when test="function-available('myns:parseXml')" use-when="function-available('myns:parseXml')"> 5314 5318 <xsl:if test="myns:parseXml(concat($cleaned,''))!=''"> 5315 5319 <xsl:call-template name="error"> … … 5318 5322 </xsl:if> 5319 5323 </xsl:when> 5320 <xsl:when test="function-available('saxon:parse')" >5324 <xsl:when test="function-available('saxon:parse')" use-when="function-available('saxon:parse')"> 5321 5325 <xsl:variable name="parsed" select="saxon:parse(concat($cleaned,''))"/> 5322 5326 <xsl:if test="$parsed='foo'"> … … 5324 5328 </xsl:if> 5325 5329 </xsl:when> 5330 <xsl:when test="false()"/> 5326 5331 <xsl:otherwise/> 5327 5332 </xsl:choose> … … 6388 6393 <xsl:text>http://greenbytes.de/tech/webdav/rfc2629.xslt, </xsl:text> 6389 6394 <!-- when RCS keyword substitution in place, add version info --> 6390 <xsl:if test="contains('$Revision: 1.57 2$',':')">6391 <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.57 2$', 'Revision: '),'$','')),', ')"/>6395 <xsl:if test="contains('$Revision: 1.576 $',':')"> 6396 <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.576 $', 'Revision: '),'$','')),', ')"/> 6392 6397 </xsl:if> 6393 <xsl:if test="contains('$Date: 2012-0 3-19 14:26:22$',':')">6394 <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 2012-0 3-19 14:26:22$', 'Date: '),'$','')),', ')"/>6398 <xsl:if test="contains('$Date: 2012-05-02 14:26:45 $',':')"> 6399 <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 2012-05-02 14:26:45 $', 'Date: '),'$','')),', ')"/> 6395 6400 </xsl:if> 6396 6401 <xsl:value-of select="concat('XSLT vendor: ',system-property('xsl:vendor'),' ',system-property('xsl:vendor-url'))"/> … … 6887 6892 <!-- diag support --> 6888 6893 <xsl:template name="lineno"> 6889 <xsl:if test="function-available('saxon-old:line-number')" >6894 <xsl:if test="function-available('saxon-old:line-number')" use-when="function-available('saxon-old:line-number')"> 6890 6895 <xsl:if test="saxon-old:line-number() > 0"> 6891 6896 <xsl:text> (at line </xsl:text> … … 6905 6910 </xsl:if> 6906 6911 </xsl:if> 6907 <xsl:if test="function-available('saxon:line-number')" >6912 <xsl:if test="function-available('saxon:line-number')" use-when="function-available('saxon:line-number')"> 6908 6913 <xsl:if test="saxon:line-number() > 0"> 6909 6914 <xsl:text> (at line </xsl:text> … … 6956 6961 <xsl:variable name="current-year"> 6957 6962 <xsl:choose> 6958 <xsl:when test="function-available('date:date-time')" >6963 <xsl:when test="function-available('date:date-time')" use-when="function-available('date:date-time')"> 6959 6964 <xsl:value-of select="substring-before(date:date-time(),'-')"/> 6965 </xsl:when> 6966 <xsl:when test="function-available('current-date')"> 6967 <xsl:value-of select="substring-before(string(current-date()),'-')"/> 6960 6968 </xsl:when> 6961 6969 <xsl:otherwise/> … … 6965 6973 <xsl:variable name="current-month"> 6966 6974 <xsl:choose> 6967 <xsl:when test="function-available('date:date-time')" >6975 <xsl:when test="function-available('date:date-time')" use-when="function-available('date:date-time')"> 6968 6976 <xsl:value-of select="substring-before(substring-after(date:date-time(),'-'),'-')"/> 6977 </xsl:when> 6978 <xsl:when test="function-available('current-date')"> 6979 <xsl:value-of select="substring-before(substring-after(string(current-date()),'-'),'-')"/> 6969 6980 </xsl:when> 6970 6981 <xsl:otherwise/> … … 6974 6985 <xsl:variable name="current-day"> 6975 6986 <xsl:choose> 6976 <xsl:when test="function-available('date:date-time')" >6987 <xsl:when test="function-available('date:date-time')" use-when="function-available('date:date-time')"> 6977 6988 <xsl:value-of select="substring-after(substring-after(substring-before(date:date-time(),'T'),'-'),'-')"/> 6989 </xsl:when> 6990 <xsl:when test="function-available('current-dateTime')"> 6991 <xsl:value-of select="substring-after(substring-after(substring-before(string(current-dateTime()),'T'),'-'),'-')"/> 6978 6992 </xsl:when> 6979 6993 <xsl:otherwise/> … … 7137 7151 </xsl:template> 7138 7152 7153 <xsl:function name="exslt:node-set"> 7154 <xsl:param name="node"/> 7155 <xsl:copy-of select="$node"/> 7156 </xsl:function> 7157 7139 7158 </xsl:transform> -
rfc2629xslt/rfc2629xslt.html
r1652 r1661 356 356 } 357 357 @top-right { 358 content: " November 2011";358 content: "March 2012"; 359 359 } 360 360 @top-center { … … 383 383 } 384 384 } 385 </style><link rel="Contents" href="#rfc.toc"><link rel="Author" href="#rfc.authors"><link rel="Index" href="#rfc.index"><link rel="Chapter" title="1 Introduction" href="#rfc.section.1"><link rel="Chapter" title="2 Supported RFC2629 elements" href="#rfc.section.2"><link rel="Chapter" title="3 Processing Instructions" href="#rfc.section.3"><link rel="Chapter" title="4 Anchors" href="#rfc.section.4"><link rel="Chapter" title="5 Supported XSLT engines" href="#rfc.section.5"><link rel="Chapter" title="6 Transforming to HTML" href="#rfc.section.6"><link rel="Chapter" title="7 Transforming to XHTML" href="#rfc.section.7"><link rel="Chapter" title="8 Transforming to CHM (Microsoft Compiled Help)" href="#rfc.section.8"><link rel="Chapter" title="9 Transforming to PDF" href="#rfc.section.9"><link rel="Chapter" title="10 Transforming to ePub" href="#rfc.section.10"><link rel="Chapter" title="11 Generic Extensions" href="#rfc.section.11"><link rel="Chapter" title="12 Utilities" href="#rfc.section.12"><link rel="Chapter" href="#rfc.section.13" title="13 Informative References"><link rel="Appendix" title="A RELAX NG Compact Schema" href="#rfc.section.A"><link rel="Appendix" title="B Implementation Notes" href="#rfc.section.B"><link rel="Appendix" title="C Examples" href="#rfc.section.C"><link rel="Appendix" title="D Producing the IETF 'Boilerplate'" href="#rfc.section.D"><link rel="Appendix" title="E License" href="#rfc.section.E"><link rel="Appendix" title="F Change Logs" href="#rfc.section.F"><meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.57 2, 2012-03-19 14:26:22, XSLT vendor: SAXON 6.5.5 from Michael Kay http://saxon.sf.net/"><meta name="keywords" content="RFC2629, xml2rfc, XSLT, hCard, XSL-FO, PDF, GRDDL, epub, Dublin Core"><link rel="schema.dct" href="http://purl.org/dc/terms/"><meta name="dct.creator" content="Reschke, J. F."></head><body><table class="header"><tbody><tr><td class="left">RFC2629 through XSLT</td><td class="right">J. Reschke</td></tr><tr><td class="left"></td><td class="right">greenbytes</td></tr><tr><td class="left"></td><td class="right">November 2011</td></tr></tbody></table><p class="title">Transforming RFC2629-formatted XML through XSLT</p><hr class="noprint"><h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1><ul class="toc"><li>1. <a href="#rfc.section.1">Introduction</a></li><li>2. <a href="#supported.elements">Supported RFC2629 elements</a><ul><li>2.1 <a href="#rfc.section.2.1">Extension elements</a></li></ul></li><li>3. <a href="#processing.instructions">Processing Instructions</a><ul><li>3.1 <a href="#rfc.section.3.1">Supported xml2rfc-compatible PIs</a></li><li>3.2 <a href="#rfc.section.3.2">Unsupported xml2rfc-compatible PIs</a></li><li>3.3 <a href="#rfc.section.3.3">Extension PIs</a></li></ul></li><li>4. <a href="#anchors">Anchors</a></li><li>5. <a href="#xslt.engines">Supported XSLT engines</a><ul><li>5.1 <a href="#rfc.section.5.1">Standalone Engines</a></li><li>5.2 <a href="#xslt.engines.browser">In-Browser Engines</a></li></ul></li><li>6. <a href="#output.html">Transforming to HTML</a><ul><li>6.1 <a href="#rfc.section.6.1">HTML compliance</a></li><li>6.2 <a href="#html.link">Standard HTML LINK elements</a></li><li>6.3 <a href="#rfc.section.6.3">Standard HTML metadata</a></li><li>6.4 <a href="#rfc2731.properties">Dublin Core (RFC2731) metadata</a></li><li>6.5 <a href="#hcard">Experimental hCard support</a></li></ul></li><li>7. <a href="#output.xhtml">Transforming to XHTML</a></li><li>8. <a href="#output.chm">Transforming to CHM (Microsoft Compiled Help)</a></li><li>9. <a href="#output.pdf">Transforming to PDF</a><ul><li>9.1 <a href="#output.pdf.fop">Via XSL-FO</a><ul><li>9.1.1 <a href="#rfc.section.9.1.1">Extension feature matrix</a></li><li>9.1.2 <a href="#rfc.section.9.1.2">Example: producing output for Apache FOP</a></li></ul></li><li>9.2 <a href="#output.pdf.html">Via X(HTML)</a></li></ul></li><li>10. <a href="#output.epub">Transforming to ePub</a></li><li>11. <a href="#extensions">Generic Extensions</a><ul><li>11.1 <a href="#ext.element.abnf-char-sequence"><abnf-char-sequence> element</a></li><li>11.2 <a href="#ext.element.anchor-alias"><anchor-alias> element</a></li><li>11.3 <a href="#ext.element.bcp14"><bcp14> element</a></li><li>11.4 <a href="#ext.element.bb"><bb> element</a></li><li>11.5 <a href="#ext.element.bc"><bc> element</a></li><li>11.6 <a href="#ext.element.blockquote"><blockquote> element</a></li><li>11.7 <a href="#ext.element.boilerplate"><boilerplate> element</a></li><li>11.8 <a href="#ext.element.bt"><bt> element</a></li><li>11.9 <a href="#ext.element.dfn"><dfn> element</a></li><li>11.10 <a href="#ext.element.h"><h> element</a></li><li>11.11 <a href="#ext.element.highlight"><highlight> element</a></li><li>11.12 <a href="#ext.element.length-of"><length-of> element</a></li><li>11.13 <a href="#ext.element.link"><link> element</a></li><li>11.14 <a href="#ext.element.lt"><lt> element</a></li><li>11.15 <a href="#ext.element.note"><note> element</a></li><li>11.16 <a href="#ext.element.parse-xml"><parse-xml> element</a></li><li>11.17 <a href="#ext.element.prose"><prose> element</a></li><li>11.18 <a href="#ext.element.q"><q> element</a></li><li>11.19 <a href="#ext.element.ref"><ref> element</a></li><li>11.20 <a href="#ext.element.source"><source> element</a></li><li>11.21 <a href="#ext.element.sup"><sup> element</a></li><li>11.22 <a href="#ext-rfc2629.artwork">Extensions to Xml2rfc <artwork> element</a></li><li>11.23 <a href="#ext-rfc2629.iref">Extensions to Xml2rfc <iref> element</a></li><li>11.24 <a href="#ext-rfc2629.list">Extensions to Xml2rfc <list> element</a></li><li>11.25 <a href="#ext-rfc2629.rfc">Extensions to Xml2rfc <rfc> element</a></li><li>11.26 <a href="#ext-rfc2629.section">Extensions to Xml2rfc <section> element</a></li><li>11.27 <a href="#ext-rfc2629.xref">Extensions to Xml2rfc <xref> element</a></li></ul></li><li>12. <a href="#utilities">Utilities</a><ul><li>12.1 <a href="#checking-references">Checking References</a></li><li>12.2 <a href="#rfc.section.12.2">Generating Graphs from References</a></li><li>12.3 <a href="#rfc.section.12.3">Producing reference entries for books</a></li><li>12.4 <a href="#clean-for-dtd">Down-converting to RFC2629bis DTD</a></li><li>12.5 <a href="#extract-artwork">Extracting artwork</a></li><li>12.6 <a href="#grddl">GRRDL</a></li></ul></li><li>13. <a href="#rfc.references">Informative References</a></li><li><a href="#rfc.authors">Author's Address</a></li><li>A. <a href="#grammar">RELAX NG Compact Schema</a></li><li>B. <a href="#rfc.section.B">Implementation Notes</a><ul><li>B.1 <a href="#rfc.section.B.1">Recognized type attributes for <artwork> element</a></li></ul></li><li>C. <a href="#examples">Examples</a><ul><li>C.1 <a href="#examples.internalsubset">Using the 'Internal Subset'</a></li><li>C.2 <a href="#examples.customizing">Customization</a></li></ul></li><li>D. <a href="#boilerplate">Producing the IETF 'Boilerplate'</a><ul><li>D.1 <a href="#attribute-ipr">The /rfc/@ipr Attribute</a><ul><li>D.1.1 <a href="#attribute-ipr-current">Current Values: '*trust200902'</a><ul><li>D.1.1.1 <a href="#attribute-ipr-trust200902">trust200902</a></li><li>D.1.1.2 <a href="#attribute-ipr-noModificationTrust200902">noModificationTrust200902</a></li><li>D.1.1.3 <a href="#attribute-ipr-noDerivativesTrust200902">noDerivativesTrust200902</a></li><li>D.1.1.4 <a href="#attribute-ipr-pre5378Trust200902">pre5378Trust200902</a></li></ul></li><li>D.1.2 <a href="#attribute-ipr-historic">Historic Values</a><ul><li>D.1.2.1 <a href="#attribute-ipr-200811">Historic Values: '*trust200811'</a></li><li>D.1.2.2 <a href="#attribute-ipr-3978">Historic Values: '*3978'</a></li><li>D.1.2.3 <a href="#attribute-ipr-3667">Historic Values: '*3667'</a></li><li>D.1.2.4 <a href="#attribute-ipr-2026">Historic Values: '*2026'</a></li></ul></li></ul></li><li>D.2 <a href="#attribute-category">The /rfc/@category Attribute</a></li><li>D.3 <a href="#attribute-submissiontype">The /rfc/@submissionType Attribute</a></li><li>D.4 <a href="#attribute-consensus">The /rfc/@consensus Attribute</a></li><li>D.5 <a href="#attribute-number">The /rfc/@number Attribute</a></li><li>D.6 <a href="#attribute-docname">The /rfc/@docName Attribute</a></li><li>D.7 <a href="#attribute-obsoletes">The /rfc/@obsoletes Attribute</a></li><li>D.8 <a href="#attribute-updates">The /rfc/@updates Attribute</a></li></ul></li><li>E. <a href="#license">License</a></li><li>F. <a href="#rfc.section.F">Change Logs</a><ul><li>F.1 <a href="#rfc.section.F.1">Package</a></li><li>F.2 <a href="#rfc.section.F.2">amazon-asin.xslt</a></li><li>F.3 <a href="#rfc.section.F.3">check-references.xslt</a></li><li>F.4 <a href="#rfc.section.F.4">gen-reference-graph.xslt</a></li><li>F.5 <a href="#rfc.section.F.5">rfc2629.xslt</a></li><li>F.6 <a href="#rfc.section.F.6">rfc2629toFO.xslt</a></li><li>F.7 <a href="#rfc.section.F.7">xsl11toAn.xslt</a></li><li>F.8 <a href="#rfc.section.F.8">xsl11toFop.xslt</a></li><li>F.9 <a href="#rfc.section.F.9">xsl11toXep.xslt</a></li></ul></li><li><a href="#rfc.index">Index</a></li></ul><hr class="noprint"><h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> Introduction</h1><p id="rfc.section.1.p.1">This document describes a set of XSLT transformations that can be used to transform RFC2629-compliant XML (see <a href="#RFC2629" id="rfc.xref.RFC2629.1"><cite title="Writing I-Ds and RFCs using XML">[RFC2629]</cite></a>) to various output formats, such as HTML and PDF. The main topics are </p><ul><li>compliance to the xml2rfc XML element set (<a href="#supported.elements" title="Supported RFC2629 elements">Section 2</a>),</li><li>support for xml2rfc processing instructions (<a href="#processing.instructions" title="Processing Instructions">Section 3</a>),</li><li>the names of anchor elements generated in HTML and PDF output (<a href="#anchors" title="Anchors">Section 4</a>),</li><li>various XSLT engines that can be used (<a href="#xslt.engines" title="Supported XSLT engines">Section 5</a>),</li><li>outputting HTML (<a href="#output.html" title="Transforming to HTML">Section 6</a>) and XHTML (<a href="#output.xhtml" title="Transforming to XHTML">Section 7</a>),</li><li>outputting CHM (Compiled Microsoft Help, <a href="#output.chm" title="Transforming to CHM (Microsoft Compiled Help)">Section 8</a>),</li><li>outputting PDF (<a href="#output.pdf" title="Transforming to PDF">Section 9</a>),</li><li>outputting ePub (<a href="#output.epub" title="Transforming to ePub">Section 10</a>),</li><li>extensions to the xml2rfc vocabulary (<a href="#extensions" title="Generic Extensions">Section 11</a>).</li><li>various utilities (<a href="#utilities" title="Utilities">Section 12</a>).</li></ul><p id="rfc.section.1.p.2">The full distribution is available at <<a href="http://greenbytes.de/tech/webdav/rfc2629xslt.zip">http://greenbytes.de/tech/webdav/rfc2629xslt.zip</a>>.</p><hr class="noprint"><h1 id="rfc.section.2" class="np"><a href="#rfc.section.2">2.</a> <a id="supported.elements" href="#supported.elements">Supported RFC2629 elements</a></h1><p id="rfc.section.2.p.1"> <samp>rfc2629.xslt</samp> supports both all RFC2629 grammar elements and the extensions implemented in xml2rfc 1.36.</p><h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> Extension elements</h2><p id="rfc.section.2.1.p.1"> <samp>rfc2629.xslt</samp> supports two kind of extension elements, using different XML namespaces.</p><p id="rfc.section.2.1.p.2">The first set contains (hopefully) generally useful extensions, see <a href="#extensions" title="Generic Extensions">Section 11</a>.</p><p id="rfc.section.2.1.p.3">The second set is used for change and issue tracking and currently is not documented here. Please email the author in case you're interested in using these extensions.</p><hr class="noprint"><h1 id="rfc.section.3" class="np"><a href="#rfc.section.3">3.</a> <a id="processing.instructions" href="#processing.instructions">Processing Instructions</a></h1><p id="rfc.section.3.p.1">All PIs can be set as XSLT parameter as well, overriding any value that is found in the source file to be transformed.</p><div id="rfc.figure.u.1"></div> <p>Using processing instructions:</p> <pre class="text"><?rfc toc="yes"?>385 </style><link rel="Contents" href="#rfc.toc"><link rel="Author" href="#rfc.authors"><link rel="Index" href="#rfc.index"><link rel="Chapter" title="1 Introduction" href="#rfc.section.1"><link rel="Chapter" title="2 Supported RFC2629 elements" href="#rfc.section.2"><link rel="Chapter" title="3 Processing Instructions" href="#rfc.section.3"><link rel="Chapter" title="4 Anchors" href="#rfc.section.4"><link rel="Chapter" title="5 Supported XSLT engines" href="#rfc.section.5"><link rel="Chapter" title="6 Transforming to HTML" href="#rfc.section.6"><link rel="Chapter" title="7 Transforming to XHTML" href="#rfc.section.7"><link rel="Chapter" title="8 Transforming to CHM (Microsoft Compiled Help)" href="#rfc.section.8"><link rel="Chapter" title="9 Transforming to PDF" href="#rfc.section.9"><link rel="Chapter" title="10 Transforming to ePub" href="#rfc.section.10"><link rel="Chapter" title="11 Generic Extensions" href="#rfc.section.11"><link rel="Chapter" title="12 Utilities" href="#rfc.section.12"><link rel="Chapter" href="#rfc.section.13" title="13 Informative References"><link rel="Appendix" title="A RELAX NG Compact Schema" href="#rfc.section.A"><link rel="Appendix" title="B Implementation Notes" href="#rfc.section.B"><link rel="Appendix" title="C Examples" href="#rfc.section.C"><link rel="Appendix" title="D Producing the IETF 'Boilerplate'" href="#rfc.section.D"><link rel="Appendix" title="E License" href="#rfc.section.E"><link rel="Appendix" title="F Change Logs" href="#rfc.section.F"><meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.576, 2012-05-02 14:26:45, XSLT vendor: SAXON 6.5.5 from Michael Kay http://saxon.sf.net/"><meta name="keywords" content="RFC2629, xml2rfc, XSLT, hCard, XSL-FO, PDF, GRDDL, epub, Dublin Core"><link rel="schema.dct" href="http://purl.org/dc/terms/"><meta name="dct.creator" content="Reschke, J. F."></head><body><table class="header"><tbody><tr><td class="left">RFC2629 through XSLT</td><td class="right">J. Reschke</td></tr><tr><td class="left"></td><td class="right">greenbytes</td></tr><tr><td class="left"></td><td class="right">March 2012</td></tr></tbody></table><p class="title">Transforming RFC2629-formatted XML through XSLT</p><hr class="noprint"><h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1><ul class="toc"><li>1. <a href="#rfc.section.1">Introduction</a></li><li>2. <a href="#supported.elements">Supported RFC2629 elements</a><ul><li>2.1 <a href="#rfc.section.2.1">Extension elements</a></li></ul></li><li>3. <a href="#processing.instructions">Processing Instructions</a><ul><li>3.1 <a href="#rfc.section.3.1">Supported xml2rfc-compatible PIs</a></li><li>3.2 <a href="#rfc.section.3.2">Unsupported xml2rfc-compatible PIs</a></li><li>3.3 <a href="#rfc.section.3.3">Extension PIs</a></li></ul></li><li>4. <a href="#anchors">Anchors</a></li><li>5. <a href="#xslt.engines">Supported XSLT engines</a><ul><li>5.1 <a href="#rfc.section.5.1">Standalone Engines</a></li><li>5.2 <a href="#xslt.engines.browser">In-Browser Engines</a></li></ul></li><li>6. <a href="#output.html">Transforming to HTML</a><ul><li>6.1 <a href="#rfc.section.6.1">HTML compliance</a></li><li>6.2 <a href="#html.link">Standard HTML LINK elements</a></li><li>6.3 <a href="#rfc.section.6.3">Standard HTML metadata</a></li><li>6.4 <a href="#rfc2731.properties">Dublin Core (RFC2731) metadata</a></li><li>6.5 <a href="#hcard">Experimental hCard support</a></li></ul></li><li>7. <a href="#output.xhtml">Transforming to XHTML</a></li><li>8. <a href="#output.chm">Transforming to CHM (Microsoft Compiled Help)</a></li><li>9. <a href="#output.pdf">Transforming to PDF</a><ul><li>9.1 <a href="#output.pdf.fop">Via XSL-FO</a><ul><li>9.1.1 <a href="#rfc.section.9.1.1">Extension feature matrix</a></li><li>9.1.2 <a href="#rfc.section.9.1.2">Example: producing output for Apache FOP</a></li></ul></li><li>9.2 <a href="#output.pdf.html">Via X(HTML)</a></li></ul></li><li>10. <a href="#output.epub">Transforming to ePub</a></li><li>11. <a href="#extensions">Generic Extensions</a><ul><li>11.1 <a href="#ext.element.abnf-char-sequence"><abnf-char-sequence> element</a></li><li>11.2 <a href="#ext.element.anchor-alias"><anchor-alias> element</a></li><li>11.3 <a href="#ext.element.bcp14"><bcp14> element</a></li><li>11.4 <a href="#ext.element.bb"><bb> element</a></li><li>11.5 <a href="#ext.element.bc"><bc> element</a></li><li>11.6 <a href="#ext.element.blockquote"><blockquote> element</a></li><li>11.7 <a href="#ext.element.boilerplate"><boilerplate> element</a></li><li>11.8 <a href="#ext.element.bt"><bt> element</a></li><li>11.9 <a href="#ext.element.dfn"><dfn> element</a></li><li>11.10 <a href="#ext.element.feedback"><feedback> element</a></li><li>11.11 <a href="#ext.element.h"><h> element</a></li><li>11.12 <a href="#ext.element.highlight"><highlight> element</a></li><li>11.13 <a href="#ext.element.length-of"><length-of> element</a></li><li>11.14 <a href="#ext.element.link"><link> element</a></li><li>11.15 <a href="#ext.element.lt"><lt> element</a></li><li>11.16 <a href="#ext.element.note"><note> element</a></li><li>11.17 <a href="#ext.element.parse-xml"><parse-xml> element</a></li><li>11.18 <a href="#ext.element.prose"><prose> element</a></li><li>11.19 <a href="#ext.element.q"><q> element</a></li><li>11.20 <a href="#ext.element.ref"><ref> element</a></li><li>11.21 <a href="#ext.element.source"><source> element</a></li><li>11.22 <a href="#ext.element.sup"><sup> element</a></li><li>11.23 <a href="#ext-rfc2629.artwork">Extensions to Xml2rfc <artwork> element</a></li><li>11.24 <a href="#ext-rfc2629.iref">Extensions to Xml2rfc <iref> element</a></li><li>11.25 <a href="#ext-rfc2629.list">Extensions to Xml2rfc <list> element</a></li><li>11.26 <a href="#ext-rfc2629.rfc">Extensions to Xml2rfc <rfc> element</a></li><li>11.27 <a href="#ext-rfc2629.section">Extensions to Xml2rfc <section> element</a></li><li>11.28 <a href="#ext-rfc2629.xref">Extensions to Xml2rfc <xref> element</a></li></ul></li><li>12. <a href="#utilities">Utilities</a><ul><li>12.1 <a href="#checking-references">Checking References</a></li><li>12.2 <a href="#rfc.section.12.2">Generating Graphs from References</a></li><li>12.3 <a href="#rfc.section.12.3">Producing reference entries for books</a></li><li>12.4 <a href="#clean-for-dtd">Down-converting to RFC2629bis DTD</a></li><li>12.5 <a href="#extract-artwork">Extracting artwork</a></li><li>12.6 <a href="#grddl">GRRDL</a></li></ul></li><li>13. <a href="#rfc.references">Informative References</a></li><li><a href="#rfc.authors">Author's Address</a></li><li>A. <a href="#grammar">RELAX NG Compact Schema</a></li><li>B. <a href="#rfc.section.B">Implementation Notes</a><ul><li>B.1 <a href="#rfc.section.B.1">Recognized type attributes for <artwork> element</a></li></ul></li><li>C. <a href="#examples">Examples</a><ul><li>C.1 <a href="#examples.internalsubset">Using the 'Internal Subset'</a></li><li>C.2 <a href="#examples.customizing">Customization</a></li></ul></li><li>D. <a href="#boilerplate">Producing the IETF 'Boilerplate'</a><ul><li>D.1 <a href="#attribute-ipr">The /rfc/@ipr Attribute</a><ul><li>D.1.1 <a href="#attribute-ipr-current">Current Values: '*trust200902'</a><ul><li>D.1.1.1 <a href="#attribute-ipr-trust200902">trust200902</a></li><li>D.1.1.2 <a href="#attribute-ipr-noModificationTrust200902">noModificationTrust200902</a></li><li>D.1.1.3 <a href="#attribute-ipr-noDerivativesTrust200902">noDerivativesTrust200902</a></li><li>D.1.1.4 <a href="#attribute-ipr-pre5378Trust200902">pre5378Trust200902</a></li></ul></li><li>D.1.2 <a href="#attribute-ipr-historic">Historic Values</a><ul><li>D.1.2.1 <a href="#attribute-ipr-200811">Historic Values: '*trust200811'</a></li><li>D.1.2.2 <a href="#attribute-ipr-3978">Historic Values: '*3978'</a></li><li>D.1.2.3 <a href="#attribute-ipr-3667">Historic Values: '*3667'</a></li><li>D.1.2.4 <a href="#attribute-ipr-2026">Historic Values: '*2026'</a></li></ul></li></ul></li><li>D.2 <a href="#attribute-category">The /rfc/@category Attribute</a></li><li>D.3 <a href="#attribute-submissiontype">The /rfc/@submissionType Attribute</a></li><li>D.4 <a href="#attribute-consensus">The /rfc/@consensus Attribute</a></li><li>D.5 <a href="#attribute-number">The /rfc/@number Attribute</a></li><li>D.6 <a href="#attribute-docname">The /rfc/@docName Attribute</a></li><li>D.7 <a href="#attribute-obsoletes">The /rfc/@obsoletes Attribute</a></li><li>D.8 <a href="#attribute-updates">The /rfc/@updates Attribute</a></li></ul></li><li>E. <a href="#license">License</a></li><li>F. <a href="#rfc.section.F">Change Logs</a><ul><li>F.1 <a href="#rfc.section.F.1">Package</a></li><li>F.2 <a href="#rfc.section.F.2">amazon-asin.xslt</a></li><li>F.3 <a href="#rfc.section.F.3">check-references.xslt</a></li><li>F.4 <a href="#rfc.section.F.4">gen-reference-graph.xslt</a></li><li>F.5 <a href="#rfc.section.F.5">rfc2629.xslt</a></li><li>F.6 <a href="#rfc.section.F.6">rfc2629toFO.xslt</a></li><li>F.7 <a href="#rfc.section.F.7">xsl11toAn.xslt</a></li><li>F.8 <a href="#rfc.section.F.8">xsl11toFop.xslt</a></li><li>F.9 <a href="#rfc.section.F.9">xsl11toXep.xslt</a></li></ul></li><li><a href="#rfc.index">Index</a></li></ul><hr class="noprint"><h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> Introduction</h1><p id="rfc.section.1.p.1">This document describes a set of XSLT transformations that can be used to transform RFC2629-compliant XML (see <a href="#RFC2629" id="rfc.xref.RFC2629.1"><cite title="Writing I-Ds and RFCs using XML">[RFC2629]</cite></a>) to various output formats, such as HTML and PDF. The main topics are </p><ul><li>compliance to the xml2rfc XML element set (<a href="#supported.elements" title="Supported RFC2629 elements">Section 2</a>),</li><li>support for xml2rfc processing instructions (<a href="#processing.instructions" title="Processing Instructions">Section 3</a>),</li><li>the names of anchor elements generated in HTML and PDF output (<a href="#anchors" title="Anchors">Section 4</a>),</li><li>various XSLT engines that can be used (<a href="#xslt.engines" title="Supported XSLT engines">Section 5</a>),</li><li>outputting HTML (<a href="#output.html" title="Transforming to HTML">Section 6</a>) and XHTML (<a href="#output.xhtml" title="Transforming to XHTML">Section 7</a>),</li><li>outputting CHM (Compiled Microsoft Help, <a href="#output.chm" title="Transforming to CHM (Microsoft Compiled Help)">Section 8</a>),</li><li>outputting PDF (<a href="#output.pdf" title="Transforming to PDF">Section 9</a>),</li><li>outputting ePub (<a href="#output.epub" title="Transforming to ePub">Section 10</a>),</li><li>extensions to the xml2rfc vocabulary (<a href="#extensions" title="Generic Extensions">Section 11</a>).</li><li>various utilities (<a href="#utilities" title="Utilities">Section 12</a>).</li></ul><p id="rfc.section.1.p.2">The full distribution is available at <<a href="http://greenbytes.de/tech/webdav/rfc2629xslt.zip">http://greenbytes.de/tech/webdav/rfc2629xslt.zip</a>>.</p><hr class="noprint"><h1 id="rfc.section.2" class="np"><a href="#rfc.section.2">2.</a> <a id="supported.elements" href="#supported.elements">Supported RFC2629 elements</a></h1><p id="rfc.section.2.p.1"> <samp>rfc2629.xslt</samp> supports both all RFC2629 grammar elements and the extensions implemented in xml2rfc 1.36.</p><h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> Extension elements</h2><p id="rfc.section.2.1.p.1"> <samp>rfc2629.xslt</samp> supports two kind of extension elements, using different XML namespaces.</p><p id="rfc.section.2.1.p.2">The first set contains (hopefully) generally useful extensions, see <a href="#extensions" title="Generic Extensions">Section 11</a>.</p><p id="rfc.section.2.1.p.3">The second set is used for change and issue tracking and currently is not documented here. Please email the author in case you're interested in using these extensions.</p><hr class="noprint"><h1 id="rfc.section.3" class="np"><a href="#rfc.section.3">3.</a> <a id="processing.instructions" href="#processing.instructions">Processing Instructions</a></h1><p id="rfc.section.3.p.1">All PIs can be set as XSLT parameter as well, overriding any value that is found in the source file to be transformed.</p><div id="rfc.figure.u.1"></div> <p>Using processing instructions:</p> <pre class="text"><?rfc toc="yes"?> 386 386 <?rfc-ext support-rfc2731="no"?> 387 387 </pre> <div id="rfc.figure.u.2"></div> <p>Using XSLT parameters (Saxon):</p> <pre class="text">java -cp saxon.jar com.icl.saxon.StyleSheet source.xml rfc2629.xslt \ … … 420 420 >SHOULD</bcp14>"> 421 421 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext' 422 >SHOULD NOT</bcp14>">]></pre> <div id="rfc.iref.e.5"></div><div id="rfc.iref.b.3"></div><h2 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a> <a id="ext.element.bb" href="#ext.element.bb"><bb> element</a></h2><p id="rfc.section.11.4.p.1">Marking up a string as <bb> indicates that it represents the bottom line of a box drawing, replacing the "+" and "-" characters accordingly.</p><div id="rfc.iref.e.6"></div><div id="rfc.iref.b.4"></div><h2 id="rfc.section.11.5"><a href="#rfc.section.11.5">11.5</a> <a id="ext.element.bc" href="#ext.element.bc"><bc> element</a></h2><p id="rfc.section.11.5.p.1">Marking up a string as <bc> indicates that it represents a center line of a box drawing, replacing the "|" character accordingly.</p><div id="rfc.iref.e.7"></div><div id="rfc.iref.b.5"></div><h2 id="rfc.section.11.6"><a href="#rfc.section.11.6">11.6</a> <a id="ext.element.blockquote" href="#ext.element.blockquote"><blockquote> element</a></h2><p id="rfc.section.11.6.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-BLOCKQUOTE">blockquote</a>" element in <a href="#HTML" id="rfc.xref.HTML.2"><cite title="HTML 4.01 Specification">[HTML]</cite></a> (note this is a block-level element!). It should contain one or more <t> child elements.</p><div id="rfc.iref.e.8"></div><div id="rfc.iref.b.6"></div><h2 id="rfc.section.11.7"><a href="#rfc.section.11.7">11.7</a> <a id="ext.element.boilerplate" href="#ext.element.boilerplate"><boilerplate> element</a></h2><p id="rfc.section.11.7.p.1">Can be used to include boilerplate (status, copyright, ...) into the front or back section. <section> elements within <x:boilerplate> appear as unnumbered sections in the output.</p><p id="rfc.section.11.7.p.2"> <em>This element currently can not be "down-translated" for use in xml2rfc!</em> </p><div id="rfc.iref.e.9"></div><div id="rfc.iref.b.7"></div><h2 id="rfc.section.11.8"><a href="#rfc.section.11.8">11.8</a> <a id="ext.element.bt" href="#ext.element.bt"><bt> element</a></h2><p id="rfc.section.11.8.p.1">Marking up a string as <bt> indicates that it represents the top line of a box drawing, replacing the "+" and "-" characters accordingly.</p><div id="rfc.iref.e.10"></div><div id="rfc.iref.d.10"></div><h2 id="rfc.section.11.9"><a href="#rfc.section.11.9">11.9</a> <a id="ext.element.dfn" href="#ext.element.dfn"><dfn> element</a></h2><p id="rfc.section.11.9.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-DFN">dfn</a>" element in <a href="#HTML" id="rfc.xref.HTML.3"><cite title="HTML 4.01 Specification">[HTML]</cite></a>.</p><div id="rfc.iref.e.11"></div><div id="rfc.iref.h.12"></div><h2 id="rfc.section.11.10"><a href="#rfc.section.11.10">11.10</a> <a id="ext.element.h" href="#ext.element.h"><h> element</a></h2><p id="rfc.section.11.10.p.1">This element is like the "<a href="http://www.w3.org/TR/2006/WD-xhtml2-20060726/mod-structural.html#edef_structural_h">h</a>" element in <a href="#XHTML2" id="rfc.xref.XHTML2.1"><cite title="XHTML™ 2.0">[XHTML2]</cite></a>.</p><div id="rfc.iref.e.12"></div><div id="rfc.iref.h.13"></div><h2 id="rfc.section.11.11"><a href="#rfc.section.11.11">11.11</a> <a id="ext.element.highlight" href="#ext.element.highlight"><highlight> element</a></h2><p id="rfc.section.11.11.p.1">Used to highlight text passages, currently only allowed in <artwork>.</p><p id="rfc.section.11.11.p.2"> <b>Note:</b> this is stripped when generating input for xml2rfc, so please use with care.</p><div id="rfc.iref.e.13"></div><div id="rfc.iref.l.2"></div><h2 id="rfc.section.11.12"><a href="#rfc.section.11.12">11.12</a> <a id="ext.element.length-of" href="#ext.element.length-of"><length-of> element</a></h2><p id="rfc.section.11.12.p.1">This element can be used to insert the length of another formatted section (in decimal).</p><div id="rfc.figure.u.11"></div> <p>Example: computing the Content-Length header value</p> <pre class="text"><artwork> 422 >SHOULD NOT</bcp14>">]></pre> <div id="rfc.iref.e.5"></div><div id="rfc.iref.b.3"></div><h2 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a> <a id="ext.element.bb" href="#ext.element.bb"><bb> element</a></h2><p id="rfc.section.11.4.p.1">Marking up a string as <bb> indicates that it represents the bottom line of a box drawing, replacing the "+" and "-" characters accordingly.</p><div id="rfc.iref.e.6"></div><div id="rfc.iref.b.4"></div><h2 id="rfc.section.11.5"><a href="#rfc.section.11.5">11.5</a> <a id="ext.element.bc" href="#ext.element.bc"><bc> element</a></h2><p id="rfc.section.11.5.p.1">Marking up a string as <bc> indicates that it represents a center line of a box drawing, replacing the "|" character accordingly.</p><div id="rfc.iref.e.7"></div><div id="rfc.iref.b.5"></div><h2 id="rfc.section.11.6"><a href="#rfc.section.11.6">11.6</a> <a id="ext.element.blockquote" href="#ext.element.blockquote"><blockquote> element</a></h2><p id="rfc.section.11.6.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-BLOCKQUOTE">blockquote</a>" element in <a href="#HTML" id="rfc.xref.HTML.2"><cite title="HTML 4.01 Specification">[HTML]</cite></a> (note this is a block-level element!). It should contain one or more <t> child elements.</p><div id="rfc.iref.e.8"></div><div id="rfc.iref.b.6"></div><h2 id="rfc.section.11.7"><a href="#rfc.section.11.7">11.7</a> <a id="ext.element.boilerplate" href="#ext.element.boilerplate"><boilerplate> element</a></h2><p id="rfc.section.11.7.p.1">Can be used to include boilerplate (status, copyright, ...) into the front or back section. <section> elements within <x:boilerplate> appear as unnumbered sections in the output.</p><p id="rfc.section.11.7.p.2"> <em>This element currently can not be "down-translated" for use in xml2rfc!</em> </p><div id="rfc.iref.e.9"></div><div id="rfc.iref.b.7"></div><h2 id="rfc.section.11.8"><a href="#rfc.section.11.8">11.8</a> <a id="ext.element.bt" href="#ext.element.bt"><bt> element</a></h2><p id="rfc.section.11.8.p.1">Marking up a string as <bt> indicates that it represents the top line of a box drawing, replacing the "+" and "-" characters accordingly.</p><div id="rfc.iref.e.10"></div><div id="rfc.iref.d.10"></div><h2 id="rfc.section.11.9"><a href="#rfc.section.11.9">11.9</a> <a id="ext.element.dfn" href="#ext.element.dfn"><dfn> element</a></h2><p id="rfc.section.11.9.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-DFN">dfn</a>" element in <a href="#HTML" id="rfc.xref.HTML.3"><cite title="HTML 4.01 Specification">[HTML]</cite></a>.</p><div id="rfc.iref.e.11"></div><div id="rfc.iref.f.4"></div><h2 id="rfc.section.11.10"><a href="#rfc.section.11.10">11.10</a> <a id="ext.element.feedback" href="#ext.element.feedback"><feedback> element</a></h2><p id="rfc.section.11.10.p.1">This elements allows declaring a feedback link for document reviewers. The template string takes the form of a URI template, such as:</p><div id="rfc.figure.u.11"></div> <pre class="text"><x:feedback template="mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&amp;body=&lt;{ref}&gt;:"/> 423 </pre><p id="rfc.section.11.10.p.3">where "docname" is substituted by the document name, "section" is substituted by section title (number and name), and "ref" is substituted by a URI pointing to the section being referenced.</p><div id="rfc.iref.e.12"></div><div id="rfc.iref.h.12"></div><h2 id="rfc.section.11.11"><a href="#rfc.section.11.11">11.11</a> <a id="ext.element.h" href="#ext.element.h"><h> element</a></h2><p id="rfc.section.11.11.p.1">This element is like the "<a href="http://www.w3.org/TR/2006/WD-xhtml2-20060726/mod-structural.html#edef_structural_h">h</a>" element in <a href="#XHTML2" id="rfc.xref.XHTML2.1"><cite title="XHTML™ 2.0">[XHTML2]</cite></a>.</p><div id="rfc.iref.e.13"></div><div id="rfc.iref.h.13"></div><h2 id="rfc.section.11.12"><a href="#rfc.section.11.12">11.12</a> <a id="ext.element.highlight" href="#ext.element.highlight"><highlight> element</a></h2><p id="rfc.section.11.12.p.1">Used to highlight text passages, currently only allowed in <artwork>.</p><p id="rfc.section.11.12.p.2"> <b>Note:</b> this is stripped when generating input for xml2rfc, so please use with care.</p><div id="rfc.iref.e.14"></div><div id="rfc.iref.l.2"></div><h2 id="rfc.section.11.13"><a href="#rfc.section.11.13">11.13</a> <a id="ext.element.length-of" href="#ext.element.length-of"><length-of> element</a></h2><p id="rfc.section.11.13.p.1">This element can be used to insert the length of another formatted section (in decimal).</p><div id="rfc.figure.u.12"></div> <p>Example: computing the Content-Length header value</p> <pre class="text"><artwork> 423 424 ... 424 425 Content-Length: <x:length-of target="req"/> … … 426 427 <x:span anchor="req">123456789 427 428 <x:span><artwork/> 428 </pre> <p id="rfc.section.11.1 2.p.3">The lenght computation counts line ends as two characters (CRLF).</p><p id="rfc.section.11.12.p.4">Note that indentation characters in artwork <em>will</em> be counted. The "indented" attribute allows to specify the amount of indentation to be substracted from the computed length.</p><div id="rfc.iref.e.14"></div><div id="rfc.iref.l.3"></div><h2 id="rfc.section.11.13"><a href="#rfc.section.11.13">11.13</a> <a id="ext.element.link" href="#ext.element.link"><link> element</a></h2><p id="rfc.section.11.13.p.1">This element can be added as a top-level child element below <rfc> to indicate additional link information. It's currently used only when generating HTML output, in which case an HTML <a href="http://www.w3.org/TR/html4/struct/links.html#edef-LINK"><link></a> element with identical attributes gets generated.</p><div id="rfc.figure.u.12"></div> <p>Example: generating HTML link element</p> <pre class="text"> <x:link xmlns="http://purl.org/net/xml2rfc/ext"429 </pre> <p id="rfc.section.11.13.p.3">The lenght computation counts line ends as two characters (CRLF).</p><p id="rfc.section.11.13.p.4">Note that indentation characters in artwork <em>will</em> be counted. The "indented" attribute allows to specify the amount of indentation to be substracted from the computed length.</p><div id="rfc.iref.e.15"></div><div id="rfc.iref.l.3"></div><h2 id="rfc.section.11.14"><a href="#rfc.section.11.14">11.14</a> <a id="ext.element.link" href="#ext.element.link"><link> element</a></h2><p id="rfc.section.11.14.p.1">This element can be added as a top-level child element below <rfc> to indicate additional link information. It's currently used only when generating HTML output, in which case an HTML <a href="http://www.w3.org/TR/html4/struct/links.html#edef-LINK"><link></a> element with identical attributes gets generated.</p><div id="rfc.figure.u.13"></div> <p>Example: generating HTML link element</p> <pre class="text"> <x:link xmlns="http://purl.org/net/xml2rfc/ext" 429 430 rel="Bookmark" 430 431 title="IETF WEBDAV Working Group" 431 href="http://ftp.ics.uci.edu/pub/ietf/webdav/"/></pre> <div id="rfc.iref.e.15"></div><div id="rfc.iref.l.4"></div><h2 id="rfc.section.11.14"><a href="#rfc.section.11.14">11.14</a> <a id="ext.element.lt" href="#ext.element.lt"><lt> element</a></h2><p id="rfc.section.11.14.p.1">Used for grouping multiple <t> elements into a single list item.</p><div id="rfc.iref.e.16"></div><div id="rfc.iref.n.3"></div><h2 id="rfc.section.11.15"><a href="#rfc.section.11.15">11.15</a> <a id="ext.element.note" href="#ext.element.note"><note> element</a></h2><p id="rfc.section.11.15.p.1">Can be used to add a note, usually indented by a few characters. It should contain one or more <t> child elements.</p><div id="rfc.iref.e.17"></div><div id="rfc.iref.p.62"></div><h2 id="rfc.section.11.16"><a href="#rfc.section.11.16">11.16</a> <a id="ext.element.parse-xml" href="#ext.element.parse-xml"><parse-xml> element</a></h2><p id="rfc.section.11.16.p.1">This element instructs the processor to parse the contents as XML and to warn when there's a problem (requires either MSXML or Saxon8 or newer).</p><div id="rfc.iref.e.18"></div><div id="rfc.iref.p.63"></div><h2 id="rfc.section.11.17"><a href="#rfc.section.11.17">11.17</a> <a id="ext.element.prose" href="#ext.element.prose"><prose> element</a></h2><p id="rfc.section.11.17.p.1">This element can be used inside <reference> to add plain text (before the date, when present).</p><div id="rfc.iref.e.19"></div><div id="rfc.iref.q.1"></div><h2 id="rfc.section.11.18"><a href="#rfc.section.11.18">11.18</a> <a id="ext.element.q" href="#ext.element.q"><q> element</a></h2><p id="rfc.section.11.18.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-Q">q</a>" element in <a href="#HTML" id="rfc.xref.HTML.4"><cite title="HTML 4.01 Specification">[HTML]</cite></a>.</p><div id="rfc.iref.e.20"></div><div id="rfc.iref.r.23"></div><h2 id="rfc.section.11.19"><a href="#rfc.section.11.19">11.19</a> <a id="ext.element.ref" href="#ext.element.ref"><ref> element</a></h2><p id="rfc.section.11.19.p.1">This element is a simplified variant of the <xref> element, in that no "target" attribute needs to be specified, instead the text contents acts as identifier. That in itself wouldn't be terribly useful, but together with the <<a href="#ext.element.anchor-alias" class="smpl">anchor-alias</a>>, it allows referring to other parts of the document with minimal additional markup.</p><p id="rfc.section.11.19.p.2">For instance, given an alias definition such as</p><div id="rfc.figure.u.13"></div> <pre class="text"> <section title="Test" anchor="test"> 432 href="http://ftp.ics.uci.edu/pub/ietf/webdav/"/></pre> <p id="rfc.section.11.14.p.3">If the attribute "basename" is present, it is used to compute the target href based on the output format being generated (this is handy for "next"/"prev" links in a series of documents. In this case, the href attribute is not required.</p><div id="rfc.figure.u.14"></div> <p>For instance:</p> <pre class="text"> <x:link xmlns="http://purl.org/net/xml2rfc/ext" 433 rel="next" 434 title="Part2" 435 basename="draft-foobar-protocol-p2-latest"/></pre> <div id="rfc.iref.e.16"></div><div id="rfc.iref.l.4"></div><h2 id="rfc.section.11.15"><a href="#rfc.section.11.15">11.15</a> <a id="ext.element.lt" href="#ext.element.lt"><lt> element</a></h2><p id="rfc.section.11.15.p.1">Used for grouping multiple <t> elements into a single list item.</p><div id="rfc.iref.e.17"></div><div id="rfc.iref.n.3"></div><h2 id="rfc.section.11.16"><a href="#rfc.section.11.16">11.16</a> <a id="ext.element.note" href="#ext.element.note"><note> element</a></h2><p id="rfc.section.11.16.p.1">Can be used to add a note, usually indented by a few characters. It should contain one or more <t> child elements.</p><div id="rfc.iref.e.18"></div><div id="rfc.iref.p.62"></div><h2 id="rfc.section.11.17"><a href="#rfc.section.11.17">11.17</a> <a id="ext.element.parse-xml" href="#ext.element.parse-xml"><parse-xml> element</a></h2><p id="rfc.section.11.17.p.1">This element instructs the processor to parse the contents as XML and to warn when there's a problem (requires either MSXML or Saxon8 or newer).</p><div id="rfc.iref.e.19"></div><div id="rfc.iref.p.63"></div><h2 id="rfc.section.11.18"><a href="#rfc.section.11.18">11.18</a> <a id="ext.element.prose" href="#ext.element.prose"><prose> element</a></h2><p id="rfc.section.11.18.p.1">This element can be used inside <reference> to add plain text (before the date, when present).</p><div id="rfc.iref.e.20"></div><div id="rfc.iref.q.1"></div><h2 id="rfc.section.11.19"><a href="#rfc.section.11.19">11.19</a> <a id="ext.element.q" href="#ext.element.q"><q> element</a></h2><p id="rfc.section.11.19.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-Q">q</a>" element in <a href="#HTML" id="rfc.xref.HTML.4"><cite title="HTML 4.01 Specification">[HTML]</cite></a>.</p><div id="rfc.iref.e.21"></div><div id="rfc.iref.r.23"></div><h2 id="rfc.section.11.20"><a href="#rfc.section.11.20">11.20</a> <a id="ext.element.ref" href="#ext.element.ref"><ref> element</a></h2><p id="rfc.section.11.20.p.1">This element is a simplified variant of the <xref> element, in that no "target" attribute needs to be specified, instead the text contents acts as identifier. That in itself wouldn't be terribly useful, but together with the <<a href="#ext.element.anchor-alias" class="smpl">anchor-alias</a>>, it allows referring to other parts of the document with minimal additional markup.</p><p id="rfc.section.11.20.p.2">For instance, given an alias definition such as</p><div id="rfc.figure.u.15"></div> <pre class="text"> <section title="Test" anchor="test"> 432 436 <x:anchor-alias value="alias1"/> 433 437 <x:anchor-alias value="alias 2"/> 434 438 ... 435 </section></pre> <p id="rfc.section.11. 19.p.4">the following simple references</p><div id="rfc.figure.u.14"></div> <pre class="text"> <x:ref>test</x:ref>439 </section></pre> <p id="rfc.section.11.20.p.4">the following simple references</p><div id="rfc.figure.u.16"></div> <pre class="text"> <x:ref>test</x:ref> 436 440 <x:ref>alias1</x:ref> 437 <x:ref>alias 2</x:ref></pre> <p id="rfc.section.11. 19.p.6">are equivalent to...:</p><div id="rfc.figure.u.15"></div> <pre class="text"> <xref target="test">test</xref>441 <x:ref>alias 2</x:ref></pre> <p id="rfc.section.11.20.p.6">are equivalent to...:</p><div id="rfc.figure.u.17"></div> <pre class="text"> <xref target="test">test</xref> 438 442 <xref target="test">alias1</xref> 439 <xref target="test">alias 2</xref></pre> <div id="rfc.iref.e.2 1"></div><div id="rfc.iref.s.12"></div><h2 id="rfc.section.11.20"><a href="#rfc.section.11.20">11.20</a> <a id="ext.element.source" href="#ext.element.source"><source> element</a></h2><p id="rfc.section.11.20.p.1">Can be used to enhance a <reference> with information about the location for the XML source. This can be used by the <xref> processing code to automatically extract the target section number.</p><div id="rfc.figure.u.16"></div> <p>For example:</p> <pre class="text"> ...443 <xref target="test">alias 2</xref></pre> <div id="rfc.iref.e.22"></div><div id="rfc.iref.s.12"></div><h2 id="rfc.section.11.21"><a href="#rfc.section.11.21">11.21</a> <a id="ext.element.source" href="#ext.element.source"><source> element</a></h2><p id="rfc.section.11.21.p.1">Can be used to enhance a <reference> with information about the location for the XML source. This can be used by the <xref> processing code to automatically extract the target section number.</p><div id="rfc.figure.u.18"></div> <p>For example:</p> <pre class="text"> ... 440 444 <xref target="RFC2616" x:fmt="of" x:rel="#PUT" /> 441 445 ... … … 445 449 <x:source href="rfc2616.xml"/> 446 450 ... 447 </pre> <div id="rfc.iref.e.2 2"></div><div id="rfc.iref.s.13"></div><h2 id="rfc.section.11.21"><a href="#rfc.section.11.21">11.21</a> <a id="ext.element.sup" href="#ext.element.sup"><sup> element</a></h2><p id="rfc.section.11.21.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-SUP">sup</a>" element in <a href="#HTML" id="rfc.xref.HTML.5"><cite title="HTML 4.01 Specification">[HTML]</cite></a>.</p><p id="rfc.section.11.21.p.2">Note: the down conversion to RFC2629 format replaces "x<sup>y</sup>" by "x^y".</p><h2 id="rfc.section.11.22"><a href="#rfc.section.11.22">11.22</a> <a id="ext-rfc2629.artwork" href="#ext-rfc2629.artwork">Extensions to Xml2rfc <artwork> element</a></h2><p id="rfc.section.11.22.p.1">Sometimes, artwork occurs inside lists. To get it indent properly in xml2rfc's text output, it needs to be indented in the source. This is sub-optimal, as this whitespace will also appear in the HTML output, where it's already indented due to HTML's semantics.</p><p id="rfc.section.11.22.p.2">As a workaround, a "x:indent-with" attribute can be specified, containing a string that will be prepended to each line when <samp>clean-for-DTD.xslt</samp> is run (see <a href="#clean-for-dtd" title="Down-converting to RFC2629bis DTD">Section 12.4</a>).</p><h2 id="rfc.section.11.23"><a href="#rfc.section.11.23">11.23</a> <a id="ext-rfc2629.iref" href="#ext-rfc2629.iref">Extensions to Xml2rfc <iref> element</a></h2><p id="rfc.section.11.23.p.1">The extension attribute below is allowed on the standard <iref> element: </p><ul><li>x:for-anchor specifies that the <iref> will also be automatically inserted whenever the specified anchor is cross-referenced -- this may save entering lots of <iref> instances. As a special case, a value of "" (empty string) refers to the anchor attribute of the closest ancestor.</li></ul><h2 id="rfc.section.11.24"><a href="#rfc.section.11.24">11.24</a> <a id="ext-rfc2629.list" href="#ext-rfc2629.list">Extensions to Xml2rfc <list> element</a></h2><p id="rfc.section.11.24.p.1">The extension attribute below is allowed on the standard <list> element: </p><ul><li>x:indent specifies the amount of indentation for list items in hanging lists. This can be useful when the output format, such as XSL-FO, does not support automatical formatting. The value takes an XSL-FO width, such as "5em". The default is <em>length of longest label in characters</em> times <em>0.8em</em>.</li></ul><p id="rfc.section.11.24.p.2">Also, the <list> element can take <x:<a href="#ext.element.lt" class="smpl">lt</a>> child elements instead of <t>, allowing to insert multiple paragraphs into a single list item.</p><h2 id="rfc.section.11.25"><a href="#rfc.section.11.25">11.25</a> <a id="ext-rfc2629.rfc" href="#ext-rfc2629.rfc">Extensions to Xml2rfc <rfc> element</a></h2><p id="rfc.section.11.25.p.1">The extension attributes below are allowed on the standard <rfc> element: </p><ul><li>grddl:transformation can be used to reference a GRDDL transform.</li><li>x:maturity-level can be used to specify the IETF Standards Track Maturity Level of "proposed", "draft" or "internet" (see <a href="http://tools.ietf.org/html/rfc2026#section-4.1">Section 4.1</a> of <a href="#RFC2026" id="rfc.xref.RFC2026.1"><cite title="The Internet Standards Process -- Revision 3">[RFC2026]</cite></a>).</li></ul><h2 id="rfc.section.11.26"><a href="#rfc.section.11.26">11.26</a> <a id="ext-rfc2629.section" href="#ext-rfc2629.section">Extensions to Xml2rfc <section> element</a></h2><p id="rfc.section.11.26.p.1">The extension attribute below is allowed on the standard <list> element: </p><ul><li>x:fixed-section-number can be used to specify a fixed section number. This can be useful when formatting historic documents that used a different numbering style.</li></ul><h2 id="rfc.section.11.27"><a href="#rfc.section.11.27">11.27</a> <a id="ext-rfc2629.xref" href="#ext-rfc2629.xref">Extensions to Xml2rfc <xref> element</a></h2><p id="rfc.section.11.27.p.1">Three extension attributes are allowed on the standard <xref> element: </p><ol><li>x:sec can be specified to point to a specific section of the referenced document,</li><li>x:rel may specify a relative reference to use when linking into the referenced document (if linking by section number is not available),</li><li>x:fmt defines the text format to be used.</li></ol><p id="rfc.section.11.27.p.2">The following formats are defined for the x:fmt attribute: </p><dl><dt>, (Comma)</dt><dd>[<em>reference</em>], Section <em>sec</em> </dd><dt>()</dt><dd>[<em>reference</em>] (Section <em>sec</em>)</dd><dt>anchor</dt><dd>Like the default format, but without brackets.</dd><dt>of</dt><dd>Section <em>sec</em> of [<em>reference</em>]</dd><dt>number</dt><dd> <em>sec</em> </dd><dt>none</dt><dd>No output (can be used to have xrefs to references without having them rendered as such)</dd><dt>sec</dt><dd>Section <em>sec</em> </dd></dl><p id="rfc.section.11.27.p.3">These extensions are currently only supported for <xref> elements without child nodes.</p><p id="rfc.section.11.27.p.4">If the processor knows how to reference the target section, it will generate a link directly to the target section, such as in <a href="#RFC2119" id="rfc.xref.RFC2119.2"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>, <a href="http://tools.ietf.org/html/rfc2119#section-5">Section 5</a>.</p><hr class="noprint"><h1 id="rfc.section.12" class="np"><a href="#rfc.section.12">12.</a> <a id="utilities" href="#utilities">Utilities</a></h1><h2 id="rfc.section.12.1"><a href="#rfc.section.12.1">12.1</a> <a id="checking-references" href="#checking-references">Checking References</a></h2><p id="rfc.section.12.1.p.1"> <samp>check-references.xslt</samp> can be used to check all references to RFC- and ID-series IETF publications and to W3C publications (note this script requires local copies of <<a href="ftp://ftp.isi.edu/in-notes/rfc-index.xml">ftp://ftp.isi.edu/in-notes/rfc-index.xml</a>> and <<a href="http://www.w3.org/2002/01/tr-automation/tr.rdf">http://www.w3.org/2002/01/tr-automation/tr.rdf</a>> and will use the XML status information provided at <<a href="http://tools.ietf.org/">http://tools.ietf.org/</a>>).</p><p id="rfc.section.12.1.p.2">If the document is supposed to be published on the IETF standards track, the desired level can be specified using the parameter <samp>intended-level</samp> as 'proposed', 'draft' or 'internet'. Alternatively, it can be specified inside the document using the attribute x:maturity-level on the <rfc> element (see <a href="#ext-rfc2629.rfc" title="Extensions to Xml2rfc <rfc> element">Section 11.25</a>).</p><p id="rfc.section.12.1.p.3"> <b>Note:</b> Downward references should be annotated using the <annotate> element, containing an <xref> to <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.</p><p id="rfc.section.12.1.p.4">When an XSLT 2.0 processor is used, links in the document can be checked as well using the <samp>link-check</samp> paramerer ('yes' or 'no'). Note that this only works for http links to documents of type text/*.</p><div id="rfc.figure.u.17"></div> <p>For instance, as of 2008-07-12, the script produces for <<a href="http://greenbytes.de/tech/webdav/rfc2518.xml">http://greenbytes.de/tech/webdav/rfc2518.xml</a>>:</p> <pre class="text">> saxon rfc2518.xml check-references.xslt intended-status=PROPOSED \451 </pre> <div id="rfc.iref.e.23"></div><div id="rfc.iref.s.13"></div><h2 id="rfc.section.11.22"><a href="#rfc.section.11.22">11.22</a> <a id="ext.element.sup" href="#ext.element.sup"><sup> element</a></h2><p id="rfc.section.11.22.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-SUP">sup</a>" element in <a href="#HTML" id="rfc.xref.HTML.5"><cite title="HTML 4.01 Specification">[HTML]</cite></a>.</p><p id="rfc.section.11.22.p.2">Note: the down conversion to RFC2629 format replaces "x<sup>y</sup>" by "x^y".</p><h2 id="rfc.section.11.23"><a href="#rfc.section.11.23">11.23</a> <a id="ext-rfc2629.artwork" href="#ext-rfc2629.artwork">Extensions to Xml2rfc <artwork> element</a></h2><p id="rfc.section.11.23.p.1">Sometimes, artwork occurs inside lists. To get it indent properly in xml2rfc's text output, it needs to be indented in the source. This is sub-optimal, as this whitespace will also appear in the HTML output, where it's already indented due to HTML's semantics.</p><p id="rfc.section.11.23.p.2">As a workaround, a "x:indent-with" attribute can be specified, containing a string that will be prepended to each line when <samp>clean-for-DTD.xslt</samp> is run (see <a href="#clean-for-dtd" title="Down-converting to RFC2629bis DTD">Section 12.4</a>).</p><h2 id="rfc.section.11.24"><a href="#rfc.section.11.24">11.24</a> <a id="ext-rfc2629.iref" href="#ext-rfc2629.iref">Extensions to Xml2rfc <iref> element</a></h2><p id="rfc.section.11.24.p.1">The extension attribute below is allowed on the standard <iref> element: </p><ul><li>x:for-anchor specifies that the <iref> will also be automatically inserted whenever the specified anchor is cross-referenced -- this may save entering lots of <iref> instances. As a special case, a value of "" (empty string) refers to the anchor attribute of the closest ancestor.</li></ul><h2 id="rfc.section.11.25"><a href="#rfc.section.11.25">11.25</a> <a id="ext-rfc2629.list" href="#ext-rfc2629.list">Extensions to Xml2rfc <list> element</a></h2><p id="rfc.section.11.25.p.1">The extension attribute below is allowed on the standard <list> element: </p><ul><li>x:indent specifies the amount of indentation for list items in hanging lists. This can be useful when the output format, such as XSL-FO, does not support automatical formatting. The value takes an XSL-FO width, such as "5em". The default is <em>length of longest label in characters</em> times <em>0.8em</em>.</li></ul><p id="rfc.section.11.25.p.2">Also, the <list> element can take <x:<a href="#ext.element.lt" class="smpl">lt</a>> child elements instead of <t>, allowing to insert multiple paragraphs into a single list item.</p><h2 id="rfc.section.11.26"><a href="#rfc.section.11.26">11.26</a> <a id="ext-rfc2629.rfc" href="#ext-rfc2629.rfc">Extensions to Xml2rfc <rfc> element</a></h2><p id="rfc.section.11.26.p.1">The extension attributes below are allowed on the standard <rfc> element: </p><ul><li>grddl:transformation can be used to reference a GRDDL transform.</li><li>x:maturity-level can be used to specify the IETF Standards Track Maturity Level of "proposed", "draft" or "internet" (see <a href="http://tools.ietf.org/html/rfc2026#section-4.1">Section 4.1</a> of <a href="#RFC2026" id="rfc.xref.RFC2026.1"><cite title="The Internet Standards Process -- Revision 3">[RFC2026]</cite></a>).</li></ul><h2 id="rfc.section.11.27"><a href="#rfc.section.11.27">11.27</a> <a id="ext-rfc2629.section" href="#ext-rfc2629.section">Extensions to Xml2rfc <section> element</a></h2><p id="rfc.section.11.27.p.1">The extension attribute below is allowed on the standard <list> element: </p><ul><li>x:fixed-section-number can be used to specify a fixed section number. This can be useful when formatting historic documents that used a different numbering style.</li></ul><h2 id="rfc.section.11.28"><a href="#rfc.section.11.28">11.28</a> <a id="ext-rfc2629.xref" href="#ext-rfc2629.xref">Extensions to Xml2rfc <xref> element</a></h2><p id="rfc.section.11.28.p.1">Three extension attributes are allowed on the standard <xref> element: </p><ol><li>x:sec can be specified to point to a specific section of the referenced document,</li><li>x:rel may specify a relative reference to use when linking into the referenced document (if linking by section number is not available),</li><li>x:fmt defines the text format to be used.</li></ol><p id="rfc.section.11.28.p.2">The following formats are defined for the x:fmt attribute: </p><dl><dt>, (Comma)</dt><dd>[<em>reference</em>], Section <em>sec</em> </dd><dt>()</dt><dd>[<em>reference</em>] (Section <em>sec</em>)</dd><dt>anchor</dt><dd>Like the default format, but without brackets.</dd><dt>of</dt><dd>Section <em>sec</em> of [<em>reference</em>]</dd><dt>number</dt><dd> <em>sec</em> </dd><dt>none</dt><dd>No output (can be used to have xrefs to references without having them rendered as such)</dd><dt>sec</dt><dd>Section <em>sec</em> </dd></dl><p id="rfc.section.11.28.p.3">These extensions are currently only supported for <xref> elements without child nodes.</p><p id="rfc.section.11.28.p.4">If the processor knows how to reference the target section, it will generate a link directly to the target section, such as in <a href="#RFC2119" id="rfc.xref.RFC2119.2"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>, <a href="http://tools.ietf.org/html/rfc2119#section-5">Section 5</a>.</p><hr class="noprint"><h1 id="rfc.section.12" class="np"><a href="#rfc.section.12">12.</a> <a id="utilities" href="#utilities">Utilities</a></h1><h2 id="rfc.section.12.1"><a href="#rfc.section.12.1">12.1</a> <a id="checking-references" href="#checking-references">Checking References</a></h2><p id="rfc.section.12.1.p.1"> <samp>check-references.xslt</samp> can be used to check all references to RFC- and ID-series IETF publications and to W3C publications (note this script requires local copies of <<a href="ftp://ftp.isi.edu/in-notes/rfc-index.xml">ftp://ftp.isi.edu/in-notes/rfc-index.xml</a>> and <<a href="http://www.w3.org/2002/01/tr-automation/tr.rdf">http://www.w3.org/2002/01/tr-automation/tr.rdf</a>> and will use the XML status information provided at <<a href="http://tools.ietf.org/">http://tools.ietf.org/</a>>).</p><p id="rfc.section.12.1.p.2">If the document is supposed to be published on the IETF standards track, the desired level can be specified using the parameter <samp>intended-level</samp> as 'proposed', 'draft' or 'internet'. Alternatively, it can be specified inside the document using the attribute x:maturity-level on the <rfc> element (see <a href="#ext-rfc2629.rfc" title="Extensions to Xml2rfc <rfc> element">Section 11.26</a>).</p><p id="rfc.section.12.1.p.3"> <b>Note:</b> Downward references should be annotated using the <annotate> element, containing an <xref> to <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.</p><p id="rfc.section.12.1.p.4">When an XSLT 2.0 processor is used, links in the document can be checked as well using the <samp>link-check</samp> paramerer ('yes' or 'no'). Note that this only works for http links to documents of type text/*.</p><div id="rfc.figure.u.19"></div> <p>For instance, as of 2008-07-12, the script produces for <<a href="http://greenbytes.de/tech/webdav/rfc2518.xml">http://greenbytes.de/tech/webdav/rfc2518.xml</a>>:</p> <pre class="text">> saxon rfc2518.xml check-references.xslt intended-status=PROPOSED \ 448 452 link-check=yes 449 453 … … 479 483 <http://www.dlib.org/dlib/july96/lagoze/07lagoze.html>: ok 480 484 <http://www.w3.org/pub/WWW/TR/REC-PICS-labels-961031.html>: ok 481 </pre><p id="rfc.section.12.1.p.6">Recognized formats in the <seriesInfo> element are: </p><ul><li>for RFCs, the name attribute must be "RFC", and the value attribute must be the number of the RFC,</li><li>for Internet Drafs, the name attribute must be "ID" or "Internet-Draft", and the value attribute must be the file name of the draft (including the two-digit running number, but excluding a file extension),</li><li>for W3C documents, the name attribute must be "W3C", must start with "W3C ", or must start with "World Wide Web Consortium ", and the value attribute must be the "shorthand" name of the specification, such as "REC-xml-19980210".</li></ul><div class="note" id="rfc.section.12.1.p.7"> <p> <b>Note:</b> this stylesheet will need network access to check links and status of Internet Drafts. When running a Java-based XSLT engine, you may have to supply Java system properties specifying the HTTP proxy to be used, such as "-Dhttp.proxyHost=hostname -Dhttp.proxyPort=80".</p> </div><h2 id="rfc.section.12.2"><a href="#rfc.section.12.2">12.2</a> Generating Graphs from References</h2><p id="rfc.section.12.2.p.1"> <samp>gen-reference-graph.xslt</samp> generates a graph of RFC dependencies, using the same base data as in <samp>check-references.xslt</samp> (see <a href="#checking-references" title="Checking References">Section 12.1</a>). Its output is a "dot" file, to be processed by GraphViz (see <<a href="http://www.graphviz.org/">http://www.graphviz.org/</a>>).</p><div id="rfc.figure.u. 18"></div> <p>The picture below shows the RFC dependencies in RFC2629.</p> <p><img src="rfc2629xslt-fig2.png" alt="
(PNG output obtained from GraphViz)
"></p> <h2 id="rfc.section.12.3"><a href="#rfc.section.12.3">12.3</a> Producing reference entries for books</h2><p id="rfc.section.12.3.p.1"> <samp>amazon-asin.xslt</samp> uses the Amazon web services to generate a <reference> element for a given ASIN (ISBN).</p><div id="rfc.figure.u.19"></div> <p>For instance:</p> <pre class="text"><?xml version="1.0" encoding="utf-8"?>485 </pre><p id="rfc.section.12.1.p.6">Recognized formats in the <seriesInfo> element are: </p><ul><li>for RFCs, the name attribute must be "RFC", and the value attribute must be the number of the RFC,</li><li>for Internet Drafs, the name attribute must be "ID" or "Internet-Draft", and the value attribute must be the file name of the draft (including the two-digit running number, but excluding a file extension),</li><li>for W3C documents, the name attribute must be "W3C", must start with "W3C ", or must start with "World Wide Web Consortium ", and the value attribute must be the "shorthand" name of the specification, such as "REC-xml-19980210".</li></ul><div class="note" id="rfc.section.12.1.p.7"> <p> <b>Note:</b> this stylesheet will need network access to check links and status of Internet Drafts. When running a Java-based XSLT engine, you may have to supply Java system properties specifying the HTTP proxy to be used, such as "-Dhttp.proxyHost=hostname -Dhttp.proxyPort=80".</p> </div><h2 id="rfc.section.12.2"><a href="#rfc.section.12.2">12.2</a> Generating Graphs from References</h2><p id="rfc.section.12.2.p.1"> <samp>gen-reference-graph.xslt</samp> generates a graph of RFC dependencies, using the same base data as in <samp>check-references.xslt</samp> (see <a href="#checking-references" title="Checking References">Section 12.1</a>). Its output is a "dot" file, to be processed by GraphViz (see <<a href="http://www.graphviz.org/">http://www.graphviz.org/</a>>).</p><div id="rfc.figure.u.20"></div> <p>The picture below shows the RFC dependencies in RFC2629.</p> <p><img src="rfc2629xslt-fig2.png" alt="
(PNG output obtained from GraphViz)
"></p> <h2 id="rfc.section.12.3"><a href="#rfc.section.12.3">12.3</a> Producing reference entries for books</h2><p id="rfc.section.12.3.p.1"> <samp>amazon-asin.xslt</samp> uses the Amazon web services to generate a <reference> element for a given ASIN (ISBN).</p><div id="rfc.figure.u.21"></div> <p>For instance:</p> <pre class="text"><?xml version="1.0" encoding="utf-8"?> 482 486 <references> 483 487 <reference target="urn:isbn:0134516591"> … … 498 502 </reference> 499 503 </references> 500 </pre><p id="rfc.section.12.3.p.3">Note that the resulting XML usually requires checking, in this case Amazon's database is playing tricks with Marshall's name...</p><h2 id="rfc.section.12.4"><a href="#rfc.section.12.4">12.4</a> <a id="clean-for-dtd" href="#clean-for-dtd">Down-converting to RFC2629bis DTD</a></h2><p id="rfc.section.12.4.p.1"> <samp>clean-for-DTD.xslt</samp> can be used to down-convert some extensions to a format that is supported by the base xml2rfc distribution. Note that these extensions are experimental (feedback appreciated).</p><p id="rfc.section.12.4.p.2">The following mappings are done: </p><ul><li><iref> elements inside <artwork> elements are moved in front of the enclosing <figure> element.</li><li><xref> elements inside <artwork> are expanded just like in regular text (that is, the markup is stripped, but the element is replaced by the applicable replacement text).</li><li><x:<a href="#ext.element.anchor-alias" class="smpl">anchor-alias</a>> elements get stripped.</li><li><x:<a href="#ext.element.bcp14" class="smpl">bcp14</a>> elements get stripped.</li><li><x:<a href="#ext.element.bb" class="smpl">bb</a>>, <x:<a href="#ext.element.bc" class="smpl">bc</a>> and <x:<a href="#ext.element.bt" class="smpl">bt</a>> elements get stripped.</li><li><x:<a href="#ext.element.blockquote" class="smpl">blockquote</a>> elements get converted to indented text (through a <list> element).</li><li><x:<a href="#ext.element.dfn" class="smpl">dfn</a>> elements get stripped.</li><li><x:<a href="#ext.element.h" class="smpl">h</a>> elements get stripped.</li><li><x:<a href="#ext.element.link" class="smpl">link</a>> elements get stripped.</li><li><x:<a href="#ext.element.lt" class="smpl">lt</a>> elements get collapsed into a single <lt> element with added <vspace> added to simulate paragraph breaks.</li><li><x:<a href="#ext.element.note" class="smpl">note</a>> elements get converted to indented text (through a <list> element).</li><li><x:<a href="#ext.element.q" class="smpl">q</a>> elements get stripped, with apostrophes added around the text.</li><li><x:<a href="#ext.element.prose" class="smpl">prose</a>> elements are transformed into <seriesInfo> elements (which is an abuse of the element and only a workaround until xml2rfc gets a matching extension).</li><li><x:<a href="#ext.element.ref" class="smpl">ref</a>> elements get replaced by <xref> elements, targetting either the anchor or another anchor with matching <x:<a href="#ext.element.anchor-alias" class="smpl">anchor-alias</a>> child element.</li></ul><h2 id="rfc.section.12.5"><a href="#rfc.section.12.5">12.5</a> <a id="extract-artwork" href="#extract-artwork">Extracting artwork</a></h2><p id="rfc.section.12.5.p.1">With <samp>extract-artwork.xslt</samp>, artwork elements named through the "name" attribute can be extracted. This can be used to automatically check their syntax (for instance, when ABNFs appear within a figure element).</p><div id="rfc.figure.u.2 0"></div><p>For instance:</p> <pre class="text">saxon rfc3986.xml extract-artwork.xslt name=uri.abnf501 </pre> <p id="rfc.section.12.5.p.3">In addition, artwork of a specific type can be extracted, such as with:</p><div id="rfc.figure.u.2 1"></div> <pre class="text">saxon rfc3986.xml extract-artwork.xslt type=abnf502 </pre> <p id="rfc.section.12.5.p.5">When extracting by type, artwork elements with a specified name can be excluded; this can be handy when the document uses some kind of schema language, and an appendix contains the collected schema, repeating definitions from earlier on. Example:</p><div id="rfc.figure.u.2 2"></div><pre class="text">saxon rfc3986.xml extract-artwork.xslt type=abnf except-name=clschm503 </pre><h2 id="rfc.section.12.6"><a href="#rfc.section.12.6">12.6</a> <a id="grddl" href="#grddl">GRRDL</a></h2><p id="rfc.section.12.6.p.1"> <samp>rfc2629grddl.xslt</samp> extracts RDF information. This is experimental work-in-progress. See <<a href="http://www.w3.org/TR/grddl/">http://www.w3.org/TR/grddl/</a>> for more information.</p><h1 class="np" id="rfc.references"><a href="#rfc.section.13" id="rfc.section.13">13.</a> Informative References</h1><table> <tr><td class="reference"><b id="BCP97">[BCP97]</b></td><td class="top"><a href="mailto:klensin+ietf@jck.com">Klensin, J.</a> and <a href="mailto:hartmans-ietf@mit.edu" title="MIT">S. Hartman</a>, “<a href="http://tools.ietf.org/html/rfc4897">Handling Normative References to Standards-Track Documents</a>”, BCP 97, RFC 4897, June 2007.</td></tr><tr><td class="reference"><b id="DC-HTML">[DC-HTML]</b></td><td class="top"><a href="mailto:pete.johnston@eduserv.org.uk" title="Eduserv Foundation">Johnston, P.</a> and <a href="mailto:andy.powell@eduserv.org.uk" title="Eduserv Foundation">A. Powell</a>, “<a href="http://dublincore.org/documents/2008/08/04/dc-html/">Expressing Dublin Core metadata using HTML/XHTML meta and link elements</a>”, Dublin Core Metadata Initiative, August 2008, <<a href="http://dublincore.org/documents/2008/08/04/dc-html/">http://dublincore.org/documents/2008/08/04/dc-html/</a>>.</td></tr><tr><td class="reference"><b id="HTML">[HTML]</b></td><td class="top"><a href="mailto:dsr@w3.org" title="W3C">Raggett, D.</a>, Hors, A., and I. Jacobs, “<a href="http://www.w3.org/TR/html401/">HTML 4.01 Specification</a>”, W3C REC-html401-19991224, December 1999, <<a href="http://www.w3.org/TR/html401/">http://www.w3.org/TR/html401/</a>>.</td></tr><tr><td class="reference"><b id="RFC2026">[RFC2026]</b></td><td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2026">The Internet Standards Process -- Revision 3</a>”, BCP 9, RFC 2026, October 1996.</td></tr><tr><td class="reference"><b id="RFC2119">[RFC2119]</b></td><td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997.</td></tr><tr><td class="reference"><b id="RFC2616">[RFC2616]</b></td><td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Information and Computer Science">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="World Wide Web Consortium, MIT Laboratory for Computer Science">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation, Western Research Laboratory">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="World Wide Web Consortium, MIT Laboratory for Computer Science">Nielsen, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="World Wide Web Consortium, MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2616, June 1999.</td></tr><tr><td class="reference"><b id="RFC2629">[RFC2629]</b></td><td class="top"><a href="mailto:mrose@not.invisible.net" title="Invisible Worlds, Inc.">Rose, M.</a>, “<a href="http://tools.ietf.org/html/rfc2629">Writing I-Ds and RFCs using XML</a>”, RFC 2629, June 1999.</td></tr><tr><td class="reference"><b id="RFC2648">[RFC2648]</b></td><td class="top"><a href="mailto:jayhawk@att.com" title="AT&T">Moats, R.</a>, “<a href="http://tools.ietf.org/html/rfc2648">A URN Namespace for IETF Documents</a>”, RFC 2648, August 1999.</td></tr><tr><td class="reference"><b id="RFC2731">[RFC2731]</b></td><td class="top"><a href="mailto:jak@ckm.ucsf.edu" title="University of California, San Francisco, Center for Knowledge Management">Kunze, J.</a>, “<a href="http://tools.ietf.org/html/rfc2731">Encoding Dublin Core Metadata in HTML</a>”, RFC 2731, December 1999.</td></tr><tr><td class="reference"><b id="RFC5234">[RFC5234]</b></td><td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD 68, RFC 5234, January 2008.</td></tr><tr><td class="reference"><b id="RFC5741">[RFC5741]</b></td><td class="top">Daigle, L. and O. Kolkman, “<a href="http://tools.ietf.org/html/rfc5741">RFC Streams, Headers, and Boilerplates</a>”, RFC 5741, December 2009.</td></tr><tr><td class="reference"><b id="RNC">[RNC]</b></td><td class="top"><a href="mailto:jjc@jclark.com">Clark, J.</a>, “<a href="http://www.oasis-open.org/committees/relax-ng/compact-20021121.html">RELAX NG Compact Syntax</a>”, OASIS, Nov 2002, <<a href="http://www.oasis-open.org/committees/relax-ng/compact-20021121.html">http://www.oasis-open.org/committees/relax-ng/compact-20021121.html</a>>.</td></tr><tr><td class="reference"><b id="XHTML2">[XHTML2]</b></td><td class="top">Axelsson, J., Birbeck, M., Dubinko, M., Epperson, B., Ishikawa, M., McCarron, S., Navarro, A., and S. Pemberton, “<a href="http://www.w3.org/TR/xhtml2">XHTML™ 2.0</a>”, W3C WD-xhtml2-20060726, July 2006, <<a href="http://www.w3.org/TR/xhtml2">http://www.w3.org/TR/xhtml2</a>>.</td></tr><tr><td class="reference"><b id="XML">[XML]</b></td><td class="top"><a href="mailto:tbray@textuality.com" title="Textuality and Netscape">Bray, T.</a>, <a href="mailto:jeanpa@microsoft.com" title="Microsoft">Paoli, J.</a>, <a href="mailto:cmsmcq@w3.org" title="W3C">Sperberg-McQueen, C.</a>, <a href="mailto:eve.maler@east.sun.com" title="Sun Microsystems">Maler, E.</a>, and F. Yergeau, “<a href="http://www.w3.org/TR/2008/REC-xml-20081126/">Extensible Markup Language (XML) 1.0 (Fifth Edition)</a>”, W3C REC-xml-20081126, November 2008, <<a href="http://www.w3.org/TR/2008/REC-xml-20081126/">http://www.w3.org/TR/2008/REC-xml-20081126/</a>>.</td></tr><tr><td class="reference"><b id="XSL-FO">[XSL-FO]</b></td><td class="top"><a href="mailto:alrb@us.ibm.com" title="IBM">Berglund, A.</a>, “<a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/">Extensible Stylesheet Language (XSL) Version 1.1</a>”, W3C REC-xsl11-20061205, Dec 2006, <<a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/">http://www.w3.org/TR/2006/REC-xsl11-20061205/</a>>.</td></tr></table><hr class="noprint"><div class="avoidbreak"><h1 id="rfc.authors" class="np"><a href="#rfc.authors">Author's Address</a></h1><address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span><span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline">EMail: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address></div><hr class="noprint"><div id="rfc.iref.g.3"></div><div id="rfc.iref.s.14"></div><div id="rfc.iref.r.24"></div><h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="grammar" href="#grammar">RELAX NG Compact Schema</a></h1><p id="rfc.section.A.p.1">The RelaxNG schema (<a href="#RNC" id="rfc.xref.RNC.1"><cite title="RELAX NG Compact Syntax">[RNC]</cite></a>) below can be used to validate input documents (for instance, with <a href="http://www.thaiopensource.com/relaxng/jing.html">Jing</a>).</p><p id="rfc.section.A.p.2"> <em>Note that this is work in progress, and doesn't yet cover all extensions completely.</em> </p><div id="rfc.figure.u.2 3"></div> <pre class="inline"><em># WORK IN PROGRESS! PLEASE REPORT PROBLEMS TO THE AUTHOR.</em>504 </pre><p id="rfc.section.12.3.p.3">Note that the resulting XML usually requires checking, in this case Amazon's database is playing tricks with Marshall's name...</p><h2 id="rfc.section.12.4"><a href="#rfc.section.12.4">12.4</a> <a id="clean-for-dtd" href="#clean-for-dtd">Down-converting to RFC2629bis DTD</a></h2><p id="rfc.section.12.4.p.1"> <samp>clean-for-DTD.xslt</samp> can be used to down-convert some extensions to a format that is supported by the base xml2rfc distribution. Note that these extensions are experimental (feedback appreciated).</p><p id="rfc.section.12.4.p.2">The following mappings are done: </p><ul><li><iref> elements inside <artwork> elements are moved in front of the enclosing <figure> element.</li><li><xref> elements inside <artwork> are expanded just like in regular text (that is, the markup is stripped, but the element is replaced by the applicable replacement text).</li><li><x:<a href="#ext.element.anchor-alias" class="smpl">anchor-alias</a>> elements get stripped.</li><li><x:<a href="#ext.element.bcp14" class="smpl">bcp14</a>> elements get stripped.</li><li><x:<a href="#ext.element.bb" class="smpl">bb</a>>, <x:<a href="#ext.element.bc" class="smpl">bc</a>> and <x:<a href="#ext.element.bt" class="smpl">bt</a>> elements get stripped.</li><li><x:<a href="#ext.element.blockquote" class="smpl">blockquote</a>> elements get converted to indented text (through a <list> element).</li><li><x:<a href="#ext.element.dfn" class="smpl">dfn</a>> elements get stripped.</li><li><x:<a href="#ext.element.h" class="smpl">h</a>> elements get stripped.</li><li><x:<a href="#ext.element.link" class="smpl">link</a>> elements get stripped.</li><li><x:<a href="#ext.element.lt" class="smpl">lt</a>> elements get collapsed into a single <lt> element with added <vspace> added to simulate paragraph breaks.</li><li><x:<a href="#ext.element.note" class="smpl">note</a>> elements get converted to indented text (through a <list> element).</li><li><x:<a href="#ext.element.q" class="smpl">q</a>> elements get stripped, with apostrophes added around the text.</li><li><x:<a href="#ext.element.prose" class="smpl">prose</a>> elements are transformed into <seriesInfo> elements (which is an abuse of the element and only a workaround until xml2rfc gets a matching extension).</li><li><x:<a href="#ext.element.ref" class="smpl">ref</a>> elements get replaced by <xref> elements, targetting either the anchor or another anchor with matching <x:<a href="#ext.element.anchor-alias" class="smpl">anchor-alias</a>> child element.</li></ul><h2 id="rfc.section.12.5"><a href="#rfc.section.12.5">12.5</a> <a id="extract-artwork" href="#extract-artwork">Extracting artwork</a></h2><p id="rfc.section.12.5.p.1">With <samp>extract-artwork.xslt</samp>, artwork elements named through the "name" attribute can be extracted. This can be used to automatically check their syntax (for instance, when ABNFs appear within a figure element).</p><div id="rfc.figure.u.22"></div><p>For instance:</p> <pre class="text">saxon rfc3986.xml extract-artwork.xslt name=uri.abnf 505 </pre> <p id="rfc.section.12.5.p.3">In addition, artwork of a specific type can be extracted, such as with:</p><div id="rfc.figure.u.23"></div> <pre class="text">saxon rfc3986.xml extract-artwork.xslt type=abnf 506 </pre> <p id="rfc.section.12.5.p.5">When extracting by type, artwork elements with a specified name can be excluded; this can be handy when the document uses some kind of schema language, and an appendix contains the collected schema, repeating definitions from earlier on. Example:</p><div id="rfc.figure.u.24"></div><pre class="text">saxon rfc3986.xml extract-artwork.xslt type=abnf except-name=clschm 507 </pre><h2 id="rfc.section.12.6"><a href="#rfc.section.12.6">12.6</a> <a id="grddl" href="#grddl">GRRDL</a></h2><p id="rfc.section.12.6.p.1"> <samp>rfc2629grddl.xslt</samp> extracts RDF information. This is experimental work-in-progress. See <<a href="http://www.w3.org/TR/grddl/">http://www.w3.org/TR/grddl/</a>> for more information.</p><h1 class="np" id="rfc.references"><a href="#rfc.section.13" id="rfc.section.13">13.</a> Informative References</h1><table> <tr><td class="reference"><b id="BCP97">[BCP97]</b></td><td class="top"><a href="mailto:klensin+ietf@jck.com">Klensin, J.</a> and <a href="mailto:hartmans-ietf@mit.edu" title="MIT">S. Hartman</a>, “<a href="http://tools.ietf.org/html/rfc4897">Handling Normative References to Standards-Track Documents</a>”, BCP 97, RFC 4897, June 2007.</td></tr><tr><td class="reference"><b id="DC-HTML">[DC-HTML]</b></td><td class="top"><a href="mailto:pete.johnston@eduserv.org.uk" title="Eduserv Foundation">Johnston, P.</a> and <a href="mailto:andy.powell@eduserv.org.uk" title="Eduserv Foundation">A. Powell</a>, “<a href="http://dublincore.org/documents/2008/08/04/dc-html/">Expressing Dublin Core metadata using HTML/XHTML meta and link elements</a>”, Dublin Core Metadata Initiative, August 2008, <<a href="http://dublincore.org/documents/2008/08/04/dc-html/">http://dublincore.org/documents/2008/08/04/dc-html/</a>>.</td></tr><tr><td class="reference"><b id="HTML">[HTML]</b></td><td class="top"><a href="mailto:dsr@w3.org" title="W3C">Raggett, D.</a>, Hors, A., and I. Jacobs, “<a href="http://www.w3.org/TR/html401/">HTML 4.01 Specification</a>”, W3C REC-html401-19991224, December 1999, <<a href="http://www.w3.org/TR/html401/">http://www.w3.org/TR/html401/</a>>.</td></tr><tr><td class="reference"><b id="RFC2026">[RFC2026]</b></td><td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2026">The Internet Standards Process -- Revision 3</a>”, BCP 9, RFC 2026, October 1996.</td></tr><tr><td class="reference"><b id="RFC2119">[RFC2119]</b></td><td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997.</td></tr><tr><td class="reference"><b id="RFC2616">[RFC2616]</b></td><td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Information and Computer Science">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="World Wide Web Consortium, MIT Laboratory for Computer Science">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation, Western Research Laboratory">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="World Wide Web Consortium, MIT Laboratory for Computer Science">Nielsen, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="World Wide Web Consortium, MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2616, June 1999.</td></tr><tr><td class="reference"><b id="RFC2629">[RFC2629]</b></td><td class="top"><a href="mailto:mrose@not.invisible.net" title="Invisible Worlds, Inc.">Rose, M.</a>, “<a href="http://tools.ietf.org/html/rfc2629">Writing I-Ds and RFCs using XML</a>”, RFC 2629, June 1999.</td></tr><tr><td class="reference"><b id="RFC2648">[RFC2648]</b></td><td class="top"><a href="mailto:jayhawk@att.com" title="AT&T">Moats, R.</a>, “<a href="http://tools.ietf.org/html/rfc2648">A URN Namespace for IETF Documents</a>”, RFC 2648, August 1999.</td></tr><tr><td class="reference"><b id="RFC2731">[RFC2731]</b></td><td class="top"><a href="mailto:jak@ckm.ucsf.edu" title="University of California, San Francisco, Center for Knowledge Management">Kunze, J.</a>, “<a href="http://tools.ietf.org/html/rfc2731">Encoding Dublin Core Metadata in HTML</a>”, RFC 2731, December 1999.</td></tr><tr><td class="reference"><b id="RFC5234">[RFC5234]</b></td><td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD 68, RFC 5234, January 2008.</td></tr><tr><td class="reference"><b id="RFC5741">[RFC5741]</b></td><td class="top">Daigle, L. and O. Kolkman, “<a href="http://tools.ietf.org/html/rfc5741">RFC Streams, Headers, and Boilerplates</a>”, RFC 5741, December 2009.</td></tr><tr><td class="reference"><b id="RNC">[RNC]</b></td><td class="top"><a href="mailto:jjc@jclark.com">Clark, J.</a>, “<a href="http://www.oasis-open.org/committees/relax-ng/compact-20021121.html">RELAX NG Compact Syntax</a>”, OASIS, Nov 2002, <<a href="http://www.oasis-open.org/committees/relax-ng/compact-20021121.html">http://www.oasis-open.org/committees/relax-ng/compact-20021121.html</a>>.</td></tr><tr><td class="reference"><b id="XHTML2">[XHTML2]</b></td><td class="top">Axelsson, J., Birbeck, M., Dubinko, M., Epperson, B., Ishikawa, M., McCarron, S., Navarro, A., and S. Pemberton, “<a href="http://www.w3.org/TR/xhtml2">XHTML™ 2.0</a>”, W3C WD-xhtml2-20060726, July 2006, <<a href="http://www.w3.org/TR/xhtml2">http://www.w3.org/TR/xhtml2</a>>.</td></tr><tr><td class="reference"><b id="XML">[XML]</b></td><td class="top"><a href="mailto:tbray@textuality.com" title="Textuality and Netscape">Bray, T.</a>, <a href="mailto:jeanpa@microsoft.com" title="Microsoft">Paoli, J.</a>, <a href="mailto:cmsmcq@w3.org" title="W3C">Sperberg-McQueen, C.</a>, <a href="mailto:eve.maler@east.sun.com" title="Sun Microsystems">Maler, E.</a>, and F. Yergeau, “<a href="http://www.w3.org/TR/2008/REC-xml-20081126/">Extensible Markup Language (XML) 1.0 (Fifth Edition)</a>”, W3C REC-xml-20081126, November 2008, <<a href="http://www.w3.org/TR/2008/REC-xml-20081126/">http://www.w3.org/TR/2008/REC-xml-20081126/</a>>.</td></tr><tr><td class="reference"><b id="XSL-FO">[XSL-FO]</b></td><td class="top"><a href="mailto:alrb@us.ibm.com" title="IBM">Berglund, A.</a>, “<a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/">Extensible Stylesheet Language (XSL) Version 1.1</a>”, W3C REC-xsl11-20061205, Dec 2006, <<a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/">http://www.w3.org/TR/2006/REC-xsl11-20061205/</a>>.</td></tr></table><hr class="noprint"><div class="avoidbreak"><h1 id="rfc.authors" class="np"><a href="#rfc.authors">Author's Address</a></h1><address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span><span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline">EMail: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address></div><hr class="noprint"><div id="rfc.iref.g.3"></div><div id="rfc.iref.s.14"></div><div id="rfc.iref.r.24"></div><h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="grammar" href="#grammar">RELAX NG Compact Schema</a></h1><p id="rfc.section.A.p.1">The RelaxNG schema (<a href="#RNC" id="rfc.xref.RNC.1"><cite title="RELAX NG Compact Syntax">[RNC]</cite></a>) below can be used to validate input documents (for instance, with <a href="http://www.thaiopensource.com/relaxng/jing.html">Jing</a>).</p><p id="rfc.section.A.p.2"> <em>Note that this is work in progress, and doesn't yet cover all extensions completely.</em> </p><div id="rfc.figure.u.25"></div> <pre class="inline"><em># WORK IN PROGRESS! PLEASE REPORT PROBLEMS TO THE AUTHOR.</em> 504 508 505 509 <em># Define our extension namespace</em> … … 600 604 | cref 601 605 | spanx 602 <strong>| <a href="#x_anchor-alias" class="smpl">x_anchor-alias</a></strong>)* 603 } 606 <strong>| <a href="#x_anchor-alias" class="smpl">x_anchor-alias</a></strong>* 607 <strong>| <a href="#x_bcp14" class="smpl">x_bcp14</a></strong>)* 608 } 604 609 605 610 <em># Redefine <postamble> to allow our extension elements</em> … … 633 638 attlist.rfc, 634 639 <strong><a href="#x_link" class="smpl">x_link</a>*,</strong> 640 <strong><a href="#x_feedback" class="smpl">x_feedback</a>?,</strong> 635 641 <strong><a href="#x_assign-section-number" class="smpl">x_assign-section-number</a>*,</strong> 636 642 front, … … 698 704 attribute x:annotation { ATEXT }? 699 705 700 <em># Extend attribute set for <c> (see <a href="#ext-rfc2629.iref" title="Extensions to Xml2rfc <iref> element">Section 11.2 3</a>)</em>706 <em># Extend attribute set for <c> (see <a href="#ext-rfc2629.iref" title="Extensions to Xml2rfc <iref> element">Section 11.24</a>)</em> 701 707 attlist.c &= 702 708 attribute anchor { xsd:ID }? 703 709 704 <em># Extend attribute set for <iref> (see <a href="#ext-rfc2629.iref" title="Extensions to Xml2rfc <iref> element">Section 11.2 3</a>)</em>710 <em># Extend attribute set for <iref> (see <a href="#ext-rfc2629.iref" title="Extensions to Xml2rfc <iref> element">Section 11.24</a>)</em> 705 711 attlist.iref &= 706 712 attribute x:for-anchor { ATEXT }? 707 713 708 <em># Extend attribute set for <list> (see <a href="#ext-rfc2629.list" title="Extensions to Xml2rfc <list> element">Section 11.2 4</a>)</em>714 <em># Extend attribute set for <list> (see <a href="#ext-rfc2629.list" title="Extensions to Xml2rfc <list> element">Section 11.25</a>)</em> 709 715 attlist.list &= 710 716 attribute x:indent { ATEXT }? … … 719 725 attribute x:maturity-level { "proposed" | "draft" | "internet" }? 720 726 721 <em># Extend attribute set for <section> (see <a href="#ext-rfc2629.section" title="Extensions to Xml2rfc <section> element">Section 11.2 6</a>)</em>727 <em># Extend attribute set for <section> (see <a href="#ext-rfc2629.section" title="Extensions to Xml2rfc <section> element">Section 11.27</a>)</em> 722 728 attlist.section &= 723 729 attribute x:fixed-section-number { ATEXT }? … … 735 741 attribute x:annotation { ATEXT }? 736 742 737 <em># Extend attribute set for <xref> (see <a href="#ext-rfc2629.xref" title="Extensions to Xml2rfc <xref> element">Section 11.2 7</a>)</em>743 <em># Extend attribute set for <xref> (see <a href="#ext-rfc2629.xref" title="Extensions to Xml2rfc <xref> element">Section 11.28</a>)</em> 738 744 attlist.xref &= 739 745 attribute x:fmt { "()" | "," | "anchor" | "of" | "number" | "sec" | … … 742 748 attribute x:sec { ATEXT }? 743 749 744 <em id="x_abnf-char-sequence"><span id="rfc.iref.a.29"></span><span id="rfc.iref.e.2 3"></span># Conversion to ABNF char sequence (see <a href="#ext.element.abnf-char-sequence" title="<abnf-char-sequence> element">Section 11.1</a>)</em>750 <em id="x_abnf-char-sequence"><span id="rfc.iref.a.29"></span><span id="rfc.iref.e.24"></span># Conversion to ABNF char sequence (see <a href="#ext.element.abnf-char-sequence" title="<abnf-char-sequence> element">Section 11.1</a>)</em> 745 751 <a href="#x_abnf-char-sequence" class="smpl">x_abnf-char-sequence</a> = 746 752 element x:abnf-char-sequence { … … 748 754 } 749 755 750 <em id="x_anchor-alias"><span id="rfc.iref.a.30"></span><span id="rfc.iref.e.2 4"></span># Aliasing of anchors (see <a href="#ext.element.anchor-alias" title="<anchor-alias> element">Section 11.2</a>)</em>756 <em id="x_anchor-alias"><span id="rfc.iref.a.30"></span><span id="rfc.iref.e.25"></span># Aliasing of anchors (see <a href="#ext.element.anchor-alias" title="<anchor-alias> element">Section 11.2</a>)</em> 751 757 <a href="#x_anchor-alias" class="smpl">x_anchor-alias</a> = 752 758 element x:anchor-alias { … … 755 761 } 756 762 757 <em id="x_include-author"><span id="rfc.iref.i.14"></span><span id="rfc.iref.e.25"></span># Including Author information 763 <em id="x_feedback"><span id="rfc.iref.f.5"></span><span id="rfc.iref.e.26"></span># Supply feedback links (see <a href="#ext.element.feedback" title="<feedback> element">Section 11.10</a>)</em> 764 <a href="#x_feedback" class="smpl">x_feedback</a> = 765 element x:feedback { 766 attribute template { TEXT }, 767 empty 768 } 769 770 <em id="x_include-author"><span id="rfc.iref.i.14"></span><span id="rfc.iref.e.27"></span># Including Author information 758 771 # (experimental)</em> 759 772 <a href="#x_include-author" class="smpl">x_include-author</a> = … … 762 775 } 763 776 764 <em id="x_assign-section-number"><span id="rfc.iref.a.31"></span><span id="rfc.iref.e.2 6"></span># Setting section numbers for internally generated sections777 <em id="x_assign-section-number"><span id="rfc.iref.a.31"></span><span id="rfc.iref.e.28"></span># Setting section numbers for internally generated sections 765 778 # (experimental)</em> 766 779 <a href="#x_assign-section-number" class="smpl">x_assign-section-number</a> = … … 771 784 } 772 785 773 <em id="x_bb"><span id="rfc.iref.b.8"></span><span id="rfc.iref.e.2 7"></span># Bottom line of box drawing (see <a href="#ext.element.bb" title="<bb> element">Section 11.4</a>)</em>786 <em id="x_bb"><span id="rfc.iref.b.8"></span><span id="rfc.iref.e.29"></span># Bottom line of box drawing (see <a href="#ext.element.bb" title="<bb> element">Section 11.4</a>)</em> 774 787 <a href="#x_bb" class="smpl">x_bb</a> = 775 788 element x:bb { … … 783 796 } 784 797 785 <em id="x_bc"><span id="rfc.iref.b.9"></span><span id="rfc.iref.e. 28"></span># Center line of box drawing (see <a href="#ext.element.bc" title="<bc> element">Section 11.5</a>)</em>798 <em id="x_bc"><span id="rfc.iref.b.9"></span><span id="rfc.iref.e.30"></span># Center line of box drawing (see <a href="#ext.element.bc" title="<bc> element">Section 11.5</a>)</em> 786 799 <a href="#x_bc" class="smpl">x_bc</a> = 787 800 element x:bc { … … 796 809 } 797 810 798 <em id="x_bcp14"><span id="rfc.iref.b.10"></span><span id="rfc.iref.e. 29"></span># BCP14/RFC2119 keywords (see <a href="#ext.element.bcp14" title="<bcp14> element">Section 11.3</a>)</em>811 <em id="x_bcp14"><span id="rfc.iref.b.10"></span><span id="rfc.iref.e.31"></span># BCP14/RFC2119 keywords (see <a href="#ext.element.bcp14" title="<bcp14> element">Section 11.3</a>)</em> 799 812 <a href="#x_bcp14" class="smpl">x_bcp14</a> = 800 813 element x:bcp14 { … … 812 825 } 813 826 814 <em id="x_blockquote"><span id="rfc.iref.b.11"></span><span id="rfc.iref.e.3 0"></span># Blockquote (see <a href="#ext.element.blockquote" title="<blockquote> element">Section 11.6</a>)</em>827 <em id="x_blockquote"><span id="rfc.iref.b.11"></span><span id="rfc.iref.e.32"></span># Blockquote (see <a href="#ext.element.blockquote" title="<blockquote> element">Section 11.6</a>)</em> 815 828 <a href="#x_blockquote" class="smpl">x_blockquote</a> = 816 829 element x:blockquote { … … 819 832 } 820 833 821 <em id="x_boilerplate"><span id="rfc.iref.b.12"></span><span id="rfc.iref.e.3 1"></span># Boilerplate (see <a href="#ext.element.blockquote" title="<blockquote> element">Section 11.6</a>) </em>834 <em id="x_boilerplate"><span id="rfc.iref.b.12"></span><span id="rfc.iref.e.33"></span># Boilerplate (see <a href="#ext.element.blockquote" title="<blockquote> element">Section 11.6</a>) </em> 822 835 <a href="#x_boilerplate" class="smpl">x_boilerplate</a> = 823 836 element x:boilerplate { … … 825 838 } 826 839 827 <em id="x_bt"><span id="rfc.iref.b.13"></span><span id="rfc.iref.e.3 2"></span># Top line of box drawing (see <a href="#ext.element.bt" title="<bt> element">Section 11.8</a>)</em>840 <em id="x_bt"><span id="rfc.iref.b.13"></span><span id="rfc.iref.e.34"></span># Top line of box drawing (see <a href="#ext.element.bt" title="<bt> element">Section 11.8</a>)</em> 828 841 <a href="#x_bt" class="smpl">x_bt</a> = 829 842 element x:bt { … … 837 850 } 838 851 839 <em id="x_dfn"><span id="rfc.iref.d.11"></span><span id="rfc.iref.e.3 3"></span># Definition (see <a href="#ext.element.dfn" title="<dfn> element">Section 11.9</a>)</em>852 <em id="x_dfn"><span id="rfc.iref.d.11"></span><span id="rfc.iref.e.35"></span># Definition (see <a href="#ext.element.dfn" title="<dfn> element">Section 11.9</a>)</em> 840 853 <a href="#x_dfn" class="smpl">x_dfn</a> = 841 854 element x:dfn { … … 845 858 } 846 859 847 <em id="x_h"><span id="rfc.iref.h.14"></span><span id="rfc.iref.e.3 4"></span># Heading (see <a href="#ext.element.h" title="<h> element">Section 11.10</a>)</em>860 <em id="x_h"><span id="rfc.iref.h.14"></span><span id="rfc.iref.e.36"></span># Heading (see <a href="#ext.element.h" title="<h> element">Section 11.11</a>)</em> 848 861 <a href="#x_h" class="smpl">x_h</a> = 849 862 element x:h { … … 851 864 } 852 865 853 <em id="x_highlight"><span id="rfc.iref.h.15"></span><span id="rfc.iref.e.3 5"></span># Heading (see <a href="#ext.element.highlight" title="<highlight> element">Section 11.11</a>)</em>866 <em id="x_highlight"><span id="rfc.iref.h.15"></span><span id="rfc.iref.e.37"></span># Heading (see <a href="#ext.element.highlight" title="<highlight> element">Section 11.12</a>)</em> 854 867 <a href="#x_highlight" class="smpl">x_highlight</a> = 855 868 element x:highlight { … … 857 870 } 858 871 859 <em id="x_length-of"><span id="rfc.iref.l.5"></span><span id="rfc.iref.e.3 6"></span># Length Measurement (see <a href="#ext.element.length-of" title="<length-of> element">Section 11.12</a>)</em>872 <em id="x_length-of"><span id="rfc.iref.l.5"></span><span id="rfc.iref.e.38"></span># Length Measurement (see <a href="#ext.element.length-of" title="<length-of> element">Section 11.13</a>)</em> 860 873 <a href="#x_length-of" class="smpl">x_length-of</a> = 861 874 element x:length-of { … … 865 878 } 866 879 867 <em id="x_link"><span id="rfc.iref.l.6"></span><span id="rfc.iref.e.3 7"></span># Link (see <a href="#ext.element.link" title="<link> element">Section 11.13</a>)</em>880 <em id="x_link"><span id="rfc.iref.l.6"></span><span id="rfc.iref.e.39"></span># Link (see <a href="#ext.element.link" title="<link> element">Section 11.14</a>)</em> 868 881 <a href="#x_link" class="smpl">x_link</a> = 869 882 element x:link { 870 attribute basename { URI } ,871 attribute href { URI } ,883 attribute basename { URI }?, 884 attribute href { URI }?, 872 885 attribute title { TEXT }?, 873 886 attribute rel { TEXT }, … … 875 888 } 876 889 877 <em id="x_lt"><span id="rfc.iref.l.7"></span><span id="rfc.iref.e. 38"></span># Extended list item (see <a href="#ext.element.lt" title="<lt> element">Section 11.14</a>)</em>890 <em id="x_lt"><span id="rfc.iref.l.7"></span><span id="rfc.iref.e.40"></span># Extended list item (see <a href="#ext.element.lt" title="<lt> element">Section 11.15</a>)</em> 878 891 <a href="#x_lt" class="smpl">x_lt</a> = 879 892 element x:lt { … … 883 896 } 884 897 885 <em id="x_note"><span id="rfc.iref.n.4"></span><span id="rfc.iref.e. 39"></span># Note (see <a href="#ext.element.note" title="<note> element">Section 11.15</a>)</em>898 <em id="x_note"><span id="rfc.iref.n.4"></span><span id="rfc.iref.e.41"></span># Note (see <a href="#ext.element.note" title="<note> element">Section 11.16</a>)</em> 886 899 <a href="#x_note" class="smpl">x_note</a> = 887 900 element x:note { … … 889 902 } 890 903 891 <em id="x_parse-xml"><span id="rfc.iref.p.64"></span><span id="rfc.iref.e.4 0"></span># Signal XML content (see <a href="#ext.element.parse-xml" title="<parse-xml> element">Section 11.16</a>)</em>904 <em id="x_parse-xml"><span id="rfc.iref.p.64"></span><span id="rfc.iref.e.42"></span># Signal XML content (see <a href="#ext.element.parse-xml" title="<parse-xml> element">Section 11.17</a>)</em> 892 905 <a href="#x_parse-xml" class="smpl">x_parse-xml</a> = 893 906 element x:parse-xml { … … 896 909 } 897 910 898 <em id="x_prose"><span id="rfc.iref.p.65"></span><span id="rfc.iref.e.4 1"></span># Inline prose in a reference (see <a href="#ext.element.prose" title="<prose> element">Section 11.17</a>)</em>911 <em id="x_prose"><span id="rfc.iref.p.65"></span><span id="rfc.iref.e.43"></span># Inline prose in a reference (see <a href="#ext.element.prose" title="<prose> element">Section 11.18</a>)</em> 899 912 <a href="#x_prose" class="smpl">x_prose</a> = 900 913 element x:prose { … … 902 915 } 903 916 904 <em id="x_q"><span id="rfc.iref.q.2"></span><span id="rfc.iref.e.4 2"></span># Inline quote (see <a href="#ext.element.q" title="<q> element">Section 11.18</a>)</em>917 <em id="x_q"><span id="rfc.iref.q.2"></span><span id="rfc.iref.e.44"></span># Inline quote (see <a href="#ext.element.q" title="<q> element">Section 11.19</a>)</em> 905 918 <a href="#x_q" class="smpl">x_q</a> = 906 919 element x:q { … … 908 921 } 909 922 910 <em id="x_ref"><span id="rfc.iref.r.25"></span><span id="rfc.iref.e.4 3"></span># Anchor reference (see <a href="#ext.element.ref" title="<ref> element">Section 11.19</a>)</em>923 <em id="x_ref"><span id="rfc.iref.r.25"></span><span id="rfc.iref.e.45"></span># Anchor reference (see <a href="#ext.element.ref" title="<ref> element">Section 11.20</a>)</em> 911 924 <a href="#x_ref" class="smpl">x_ref</a> = 912 925 element x:ref { … … 915 928 } 916 929 917 <em id="x_source"><span id="rfc.iref.s.15"></span><span id="rfc.iref.e.4 4"></span># source information (see <a href="#ext.element.source" title="<source> element">Section 11.20</a>)</em>930 <em id="x_source"><span id="rfc.iref.s.15"></span><span id="rfc.iref.e.46"></span># source information (see <a href="#ext.element.source" title="<source> element">Section 11.21</a>)</em> 918 931 <a href="#x_source" class="smpl">x_source</a> = 919 932 element x:source { … … 923 936 } 924 937 925 <em id="x_sup"><span id="rfc.iref.s.16"></span><span id="rfc.iref.e.4 5"></span># superscript (see <a href="#ext.element.sup" title="<sup> element">Section 11.21</a>)</em>938 <em id="x_sup"><span id="rfc.iref.s.16"></span><span id="rfc.iref.e.47"></span># superscript (see <a href="#ext.element.sup" title="<sup> element">Section 11.22</a>)</em> 926 939 <a href="#x_sup" class="smpl">x_sup</a> = 927 940 element x:sup { … … 929 942 } 930 943 931 <em id="x_span"><span id="rfc.iref.s.17"></span><span id="rfc.iref.e.4 6"></span># Inline Span </em>944 <em id="x_span"><span id="rfc.iref.s.17"></span><span id="rfc.iref.e.48"></span># Inline Span </em> 932 945 <a href="#x_span" class="smpl">x_span</a> = 933 946 element x:span { … … 937 950 } 938 951 939 <em id="x_x"><span id="rfc.iref.x.31"></span><span id="rfc.iref.e.4 7"></span># Nop (for alignment in source)</em>952 <em id="x_x"><span id="rfc.iref.x.31"></span><span id="rfc.iref.e.49"></span># Nop (for alignment in source)</em> 940 953 <a href="#x_x" class="smpl">x_x</a> = 941 954 element x:x { … … 943 956 } 944 957 945 <em id="rdf_Description"><span id="rfc.iref.r.26"></span><span id="rfc.iref.e. 48"></span># Embed RDF statements </em>958 <em id="rdf_Description"><span id="rfc.iref.r.26"></span><span id="rfc.iref.e.50"></span># Embed RDF statements </em> 946 959 <a href="#rdf_Description" class="smpl">rdf_Description</a> = 947 960 element rdf:Description { … … 951 964 rdf_content = 952 965 ( TEXT | element * { rdf_content })* 953 </pre><hr class="noprint"><h1 id="rfc.section.B" class="np"><a href="#rfc.section.B">B.</a> Implementation Notes</h1><h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> Recognized type attributes for <artwork> element</h2><p id="rfc.section.B.1.p.1">Specific values in the <artwork> element's "type" attribute are recognized and cause a different visual style to be used:</p><div id="rfc.table.u.9"><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>Media Type</th><th>Comment</th></tr></thead><tbody><tr><td class="left">abnf</td><td class="left">ABNF as per <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a></td></tr><tr><td class="left">abnf2616</td><td class="left">ABNF as per <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-2.1">Section 2.1</a></td></tr><tr><td class="left">application/relax-ng-compact-syntax</td><td class="left">Relax NG Compact Syntax as per <a href="#RNC" id="rfc.xref.RNC.2"><cite title="RELAX NG Compact Syntax">[RNC]</cite></a></td></tr><tr><td class="left">application/xml-dtd</td><td class="left">XML DTD</td></tr><tr><td class="left">message/http; msgtype="request"</td><td class="left">HTTP message, as per <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-19.1">Section 19.1</a></td></tr><tr><td class="left">message/http; msgtype="response"</td><td class="left">HTTP message, as per <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-19.1">Section 19.1</a></td></tr></tbody></table></div><hr class="noprint"><h1 id="rfc.section.C" class="np"><a href="#rfc.section.C">C.</a> <a id="examples" href="#examples">Examples</a></h1><h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> <a id="examples.internalsubset" href="#examples.internalsubset">Using the 'Internal Subset'</a></h2><p id="rfc.section.C.1.p.1">The prolog of the XML document can both be used to refer to an external DTD, and also to define internal entities (<a href="http://www.w3.org/TR/2008/REC-xml-20081126/#sec-prolog-dtd">Section 2.8</a> of <a href="#XML" id="rfc.xref.XML.1"><cite title="Extensible Markup Language (XML) 1.0 (Fifth Edition)">[XML]</cite></a>):</p><div id="rfc.figure.u.2 4"></div><pre class="text"><?xml version="1.0"?>966 </pre><hr class="noprint"><h1 id="rfc.section.B" class="np"><a href="#rfc.section.B">B.</a> Implementation Notes</h1><h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> Recognized type attributes for <artwork> element</h2><p id="rfc.section.B.1.p.1">Specific values in the <artwork> element's "type" attribute are recognized and cause a different visual style to be used:</p><div id="rfc.table.u.9"><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>Media Type</th><th>Comment</th></tr></thead><tbody><tr><td class="left">abnf</td><td class="left">ABNF as per <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a></td></tr><tr><td class="left">abnf2616</td><td class="left">ABNF as per <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-2.1">Section 2.1</a></td></tr><tr><td class="left">application/relax-ng-compact-syntax</td><td class="left">Relax NG Compact Syntax as per <a href="#RNC" id="rfc.xref.RNC.2"><cite title="RELAX NG Compact Syntax">[RNC]</cite></a></td></tr><tr><td class="left">application/xml-dtd</td><td class="left">XML DTD</td></tr><tr><td class="left">message/http; msgtype="request"</td><td class="left">HTTP message, as per <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-19.1">Section 19.1</a></td></tr><tr><td class="left">message/http; msgtype="response"</td><td class="left">HTTP message, as per <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-19.1">Section 19.1</a></td></tr></tbody></table></div><hr class="noprint"><h1 id="rfc.section.C" class="np"><a href="#rfc.section.C">C.</a> <a id="examples" href="#examples">Examples</a></h1><h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> <a id="examples.internalsubset" href="#examples.internalsubset">Using the 'Internal Subset'</a></h2><p id="rfc.section.C.1.p.1">The prolog of the XML document can both be used to refer to an external DTD, and also to define internal entities (<a href="http://www.w3.org/TR/2008/REC-xml-20081126/#sec-prolog-dtd">Section 2.8</a> of <a href="#XML" id="rfc.xref.XML.1"><cite title="Extensible Markup Language (XML) 1.0 (Fifth Edition)">[XML]</cite></a>):</p><div id="rfc.figure.u.26"></div><pre class="text"><?xml version="1.0"?> 954 967 <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?> 955 968 … … 975 988 <!ENTITY mydraft PUBLIC "reference.mydraft.xml"> 976 989 ]> 977 </pre> <p>Note: including entities from a remote site will not work in Firefox, see <<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=22942">https://bugzilla.mozilla.org/show_bug.cgi?id=22942</a>>.</p> <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> <a id="examples.customizing" href="#examples.customizing">Customization</a></h2><p id="rfc.section.C.2.p.1">The XSLT code can be customized by creating a custom XSLT file that uses <xsl:import> to include the original code, and just overrides particular rules.</p><div id="rfc.figure.u.2 5"></div> <p>For instance, the code below overrides several attributes in <samp>rfc2629toFO.xslt</samp>, changing the color, spacing and font family for headers.</p> <pre class="text"><xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform"990 </pre> <p>Note: including entities from a remote site will not work in Firefox, see <<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=22942">https://bugzilla.mozilla.org/show_bug.cgi?id=22942</a>>.</p> <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> <a id="examples.customizing" href="#examples.customizing">Customization</a></h2><p id="rfc.section.C.2.p.1">The XSLT code can be customized by creating a custom XSLT file that uses <xsl:import> to include the original code, and just overrides particular rules.</p><div id="rfc.figure.u.27"></div> <p>For instance, the code below overrides several attributes in <samp>rfc2629toFO.xslt</samp>, changing the color, spacing and font family for headers.</p> <pre class="text"><xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 978 991 version="1.0"> 979 992 … … 1001 1014 1002 1015 </xsl:transform> 1003 </pre><div class="note" id="rfc.section.C.2.p.3"> <p> <b>Note:</b> the name for the attribute sets may change in the future as more working is done with respect to customizability. In any case, overriding the settings in a separate file will be easier to maintain. Please contact the author if you find yourself trying to override style definitions that currently do not use attribute sets.</p> <p> <b>Note:</b> the CSS style information used in <samp>rfc2629.xslt</samp> can be overriden in a similar (but less granular) way: just overwrite the template called "insertCss". As for XSL-FO, the class names may change in future.</p> </div><hr class="noprint"><h1 id="rfc.section.D" class="np"><a href="#rfc.section.D">D.</a> <a id="boilerplate" href="#boilerplate">Producing the IETF 'Boilerplate'</a></h1><p id="rfc.section.D.p.1">Various attributes of the <samp><rfc></samp> element plus some child elements of <samp><front></samp> affect the automatically generated parts of the front page, such as the tabular information at the beginning, the "Status Of This Memo", and the "Copyright Notice".</p><p id="rfc.section.D.p.2">When submitting an Internet Draft, this "boilerplate" is checked by "Idnits" (<<a href="http://tools.ietf.org/tools/idnits/">http://tools.ietf.org/tools/idnits/</a>>) for compliance with the current Intellectual Property rules, and thus it is important to set the correct values.</p><p id="rfc.section.D.p.3">Furthermore, the RFC Production Center uses RFC2629-based tools to generate the final RFC text, so the more accurate the supplied information is, the less additional work is left, and the risk for errors in producing the final (and immutable!) document is reduced.</p><div class="note" id="rfc.section.D.p.4"> <p> <b>Note:</b> this only applies to the case when IETF documents are produced. The "private" processing instruction <span id="rfc.iref.p.66"></span><span id="rfc.iref.p.67"></span> allows to switch off most of the autogeneration logic.</p> </div><h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a> <a id="attribute-ipr" href="#attribute-ipr">The /rfc/@ipr Attribute</a></h2><p id="rfc.section.D.1.p.1">As of the time of this writing, this attribute value can take a long list of values. As frequently, this is not the result of a grand plan, but simply for historic reasons. Of these values, only a few are currently in use; all others are supported by the various tools for backwards compatibility with old source files.</p><div class="note" id="rfc.section.D.1.p.2"> <p> <b>Note:</b> some variations of the boilerplate are selected based on the document's date; therefore it is important to specify the "year", "month" and "day" attributes of the <samp><date></samp> element when archiving the XML source of an Internet Draft on the day of submission.</p> </div><p id="rfc.section.D.1.p.3"> <em>Disclaimer: THIS ONLY PROVIDES IMPLEMENTATION INFORMATION. IF YOU NEED LEGAL ADVICE, PLEASE CONTACT A LAWYER.</em> For further information, refer to <<a href="http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf">http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf</a>>.</p><p id="rfc.section.D.1.p.4">Finally, for the current "Status Of This Memo" text, the <samp>submissionType</samp> attribute determines whether a statement about "Code Components" is inserted (this is the case for the value "IETF", which also happens to be the default). Other values, such as "independent", suppress this part of the text.</p><h3 id="rfc.section.D.1.1"><a href="#rfc.section.D.1.1">D.1.1</a> <a id="attribute-ipr-current" href="#attribute-ipr-current">Current Values: '*trust200902'</a></h3><p id="rfc.section.D.1.1.p.1">The name for these values refers to the "TLP" ("IETF TRUST Legal Provisions Relating to IETF Documents"), on effect February 15, 2009 (see <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090215.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090215.pdf</a>>). Updates to this document were published on September 12, 2009 (TLP 3.0, <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf</a>>) and on December 28, 2009 (TLP 4.0, <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf</a>>), modifying the license for code components. The actual text is located in Section 6 ("Text To Be Included in IETF Documents") of these documents.</p><p id="rfc.section.D.1.1.p.2">The tools will automatically produce the "right" text depending on the document's date information (see above):</p><div id="rfc.table.u.10"><table class="tt full left" cellpadding="3" cellspacing="0"><thead><tr><th>TLP</th><th>URI</th><th>starting with publication date</th></tr></thead><tbody><tr><td class="left">3.0</td><td class="left"><<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf</a>></td><td class="left">2009-11-01</td></tr><tr><td class="left">4.0</td><td class="left"><<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf</a>></td><td class="left">2010-04-01</td></tr></tbody></table></div><h4 id="rfc.section.D.1.1.1"><a href="#rfc.section.D.1.1.1">D.1.1.1</a> <a id="attribute-ipr-trust200902" href="#attribute-ipr-trust200902">trust200902</a></h4><p id="rfc.section.D.1.1.1.p.1">This should be the default, unless one of the more specific '*trust200902' values is a better fit. It produces the text in Sections 6.a and 6.b of the TLP.</p><h4 id="rfc.section.D.1.1.2"><a href="#rfc.section.D.1.1.2">D.1.1.2</a> <a id="attribute-ipr-noModificationTrust200902" href="#attribute-ipr-noModificationTrust200902">noModificationTrust200902</a></h4><p id="rfc.section.D.1.1.2.p.1">This produces the additional text from Section 6.c.i of the TLP:</p><blockquote id="rfc.section.D.1.1.2.p.2"> <p>This document may not be modified, and derivative works of it may not be created, except to format it for publication as an RFC or to translate it into languages other than English.</p> </blockquote><div class="note" id="rfc.section.D.1.1.2.p.3"> <p> <b>Note:</b> this clause is incompatible with RFCs to be published on the Standards Track.</p> </div><h4 id="rfc.section.D.1.1.3"><a href="#rfc.section.D.1.1.3">D.1.1.3</a> <a id="attribute-ipr-noDerivativesTrust200902" href="#attribute-ipr-noDerivativesTrust200902">noDerivativesTrust200902</a></h4><p id="rfc.section.D.1.1.3.p.1">This produces the additional text from Section 6.c.ii of the TLP:</p><blockquote id="rfc.section.D.1.1.3.p.2"> <p>This document may not be modified, and derivative works of it may not be created, and it may not be published except as an Internet-Draft.</p> </blockquote><div class="note" id="rfc.section.D.1.1.3.p.3"> <p> <b>Note:</b> this clause is incompatible with RFCs to be published on the Standards Track.</p> </div><h4 id="rfc.section.D.1.1.4"><a href="#rfc.section.D.1.1.4">D.1.1.4</a> <a id="attribute-ipr-pre5378Trust200902" href="#attribute-ipr-pre5378Trust200902">pre5378Trust200902</a></h4><p id="rfc.section.D.1.1.4.p.1">This produces the additional text from Section 6.c.iii of the TLP, frequently called the "pre-5378 escape clause":</p><blockquote id="rfc.section.D.1.1.4.p.2"> <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.</p> </blockquote><p id="rfc.section.D.1.1.4.p.3">See Section 4 of <<a href="http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf">http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf</a>> for further information about when to use this value.</p><div class="note" id="rfc.section.D.1.1.4.p.4"> <p> <b>Note:</b> this text appears under "Copyright Notice", unless the document was published before November 2009, in which case it appears under "Status Of This Memo".</p> </div><h3 id="rfc.section.D.1.2"><a href="#rfc.section.D.1.2">D.1.2</a> <a id="attribute-ipr-historic" href="#attribute-ipr-historic">Historic Values</a></h3><h4 id="rfc.section.D.1.2.1"><a href="#rfc.section.D.1.2.1">D.1.2.1</a> <a id="attribute-ipr-200811" href="#attribute-ipr-200811">Historic Values: '*trust200811'</a></h4><p id="rfc.section.D.1.2.1.p.1">The attribute values "<span id="attribute-ipr-trust200811">trust200811</span>", "<span id="attribute-ipr-noModificationTrust200811">noModificationTrust200811</span>" and "<span id="attribute-ipr-noDerivativesTrust200811">noDerivativesTrust200811</span>" are similar to their "trust200902" counterparts, except that they use text specified in <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy_11-10-08.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy_11-10-08.pdf</a>>.</p><h4 id="rfc.section.D.1.2.2"><a href="#rfc.section.D.1.2.2">D.1.2.2</a> <a id="attribute-ipr-3978" href="#attribute-ipr-3978">Historic Values: '*3978'</a></h4><p id="rfc.section.D.1.2.2.p.1">The attribute values "<span id="attribute-ipr-full3978">full3978</span>", "<span id="attribute-ipr-noModification3978">noModification3978</span>" and "<span id="attribute-ipr-noDerivatives3978">noDerivatives3978</span>" are similar to their counterparts above, except that they use text specified in RFC 3978 (March 2005).</p><h4 id="rfc.section.D.1.2.3"><a href="#rfc.section.D.1.2.3">D.1.2.3</a> <a id="attribute-ipr-3667" href="#attribute-ipr-3667">Historic Values: '*3667'</a></h4><p id="rfc.section.D.1.2.3.p.1">The attribute values "<span id="attribute-ipr-full3667">full3667</span>", "<span id="attribute-ipr-noModification3667">noModification3667</span>" and "<span id="attribute-ipr-noDerivatives3667">noDerivatives3667</span>" are similar to their counterparts above, except that they use text specified in RFC 3667 (February 2004).</p><h4 id="rfc.section.D.1.2.4"><a href="#rfc.section.D.1.2.4">D.1.2.4</a> <a id="attribute-ipr-2026" href="#attribute-ipr-2026">Historic Values: '*2026'</a></h4><p id="rfc.section.D.1.2.4.p.1">The attribute values "<span id="attribute-ipr-full2026">full2026</span>" and "<span id="attribute-ipr-noDerivativeWorks2026">noDerivativeWorks2026</span>" are similar to their counterparts above, except that they use text specified in RFC 2026 (October 1996).</p><p id="rfc.section.D.1.2.4.p.2">The special value "<span id="attribute-ipr-none">none</span>" was also used back then, and denied the IETF any rights beyond publication as Internet Draft.</p><h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a> <a id="attribute-category" href="#attribute-category">The /rfc/@category Attribute</a></h2><p id="rfc.section.D.2.p.1">For RFCs, the <samp>category</samp> determines the "maturity level" (see <a href="http://tools.ietf.org/html/rfc2026#section-4">Section 4</a> of <a href="#RFC2026" id="rfc.xref.RFC2026.2"><cite title="The Internet Standards Process -- Revision 3">[RFC2026]</cite></a>). The allowed values are "std" for "Standards Track", "bcp" for "BCP", "info" for "Informational", "exp" for "Experimental", and "historic" for - surprise - "Historic".</p><p id="rfc.section.D.2.p.2">For Internet Drafts, the category attribute is not needed, but <em>will</em> appear on the front page ("Intended Status"). Supplying this information can be useful, because reviewers may want to know.</p><div class="note" id="rfc.section.D.2.p.3"> <p> <b>Note:</b> the Standards Track consists of "Proposed Standard", "Draft Standards", and "Internet Standard". These do not appear in the boilerplate, thus the category attribute doesn't handle them. However, this information can be useful for validity checkers, and thus <samp>rfc2629.xslt</samp> supports an extension attribute for that purpose (see <a href="#ext-rfc2629.rfc" title="Extensions to Xml2rfc <rfc> element">Section 11.2 5</a> for details).</p> </div><h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a> <a id="attribute-submissiontype" href="#attribute-submissiontype">The /rfc/@submissionType Attribute</a></h2><p id="rfc.section.D.3.p.1">The RFC Editor publishes documents from different "document streams", of which the "IETF stream" of course is the most prominent one. Other streams are the "independent stream" (used for things like administrative information or April 1st RFCs), the "IAB stream" (Internet Architecture Board) and the "IRTF stream" (Internet Research Task Force).</p><p id="rfc.section.D.3.p.2">Not surprisingly, the values for the attribute are "IETF" (the default value), "independent", "IAB", and "IRTF".</p><p id="rfc.section.D.3.p.3">Historically, this did not affect the final appearance of RFCs, except for subtle differences in Copyright notices. Nowadays (as of <a href="#RFC5741" id="rfc.xref.RFC5741.1"><cite title="RFC Streams, Headers, and Boilerplates">[RFC5741]</cite></a>), the stream name appears in the first line of the front page, and it also affects the text in the "Status Of This Memo" section.</p><p id="rfc.section.D.3.p.4">For current documents, setting <samp>submissionType</samp> attribute will have the following effect: </p><ul><li>For RFCs, the stream name appears in the upper left corner of the first page (in Internet Drafts, this is either "Network Working Group", or the value of the <samp><workgroup></samp> element).</li><li>For RFCs, if affects the whole "Status Of This Memo" section (see <a href="http://tools.ietf.org/html/rfc5741#section-3.2.2">Section 3.2.2</a> of <a href="#RFC5741" id="rfc.xref.RFC5741.2"><cite title="RFC Streams, Headers, and Boilerplates">[RFC5741]</cite></a>).</li><li>For all RFCs and Internet Drafts, it determines whether the "Copyright Notice" mentions the Copyright on Code Components (see TLP, Section "Text To Be Included in IETF Documents").</li></ul><h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a> <a id="attribute-consensus" href="#attribute-consensus">The /rfc/@consensus Attribute</a></h2><p id="rfc.section.D.4.p.1">For some of the publication streams (see <a href="#attribute-submissiontype" title="The /rfc/@submissionType Attribute">Appendix D.3</a>), the "Status Of This Memo" section depends on whether there was a consensus to publish (again, see <a href="http://tools.ietf.org/html/rfc5741#section-3.2.2">Section 3.2.2</a> of <a href="#RFC5741" id="rfc.xref.RFC5741.3"><cite title="RFC Streams, Headers, and Boilerplates">[RFC5741]</cite></a>).</p><p id="rfc.section.D.4.p.2">The <samp>consensus</samp> attribute ("yes"/"no", defaulting to "yes") can be used to supply this information. The effect for the various streams is: </p><ul><li>"independent" and "IAB": none.</li><li>"IETF": mention that there was an IETF consensus.</li><li>"IRTF": mention that there was a research group consensus (where the name of the research group is extracted from the <samp><workgroup></samp> element).</li></ul><h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a> <a id="attribute-number" href="#attribute-number">The /rfc/@number Attribute</a></h2><p id="rfc.section.D.5.p.1">For RFCs, this attribute supplies the RFC number.</p><h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a> <a id="attribute-docname" href="#attribute-docname">The /rfc/@docName Attribute</a></h2><p id="rfc.section.D.6.p.1">For Internet Drafts, this specifies the draft name (which appears below the title). The file extension is <em>not</em> part of the draft, so in general it should end with the current draft number ("-", plus two digits).</p><div class="note" id="rfc.section.D.6.p.2"> <p> <b>Note:</b> "Idnits" (<<a href="http://tools.ietf.org/tools/idnits/">http://tools.ietf.org/tools/idnits/</a>>) checks the in-document draft name for consistency with the filename of the submitted document.</p> </div><h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a> <a id="attribute-obsoletes" href="#attribute-obsoletes">The /rfc/@obsoletes Attribute</a></h2><p id="rfc.section.D.7.p.1">The RFC Editor maintains a database (<<a href="http://www.rfc-editor.org/rfc.html">http://www.rfc-editor.org/rfc.html</a>>) of all RFCs, including information about which one obsoletes which. Upon publication of an RFC, this database is updated from the data on the front page.</p><p id="rfc.section.D.7.p.2">This attribute takes a list of comma-separated RFC <em>numbers</em>. Do <em>not</em> put the string "RFC" here.</p><h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a> <a id="attribute-updates" href="#attribute-updates">The /rfc/@updates Attribute</a></h2><p id="rfc.section.D.8.p.1">This is like <samp>obsoletes</samp>, but for the "updates" relation.</p><hr class="noprint"><h1 id="rfc.section.E" class="np"><a href="#rfc.section.E">E.</a> <a id="license" href="#license">License</a></h1><p id="rfc.section.E.p.1">Copyright (c) 2006-2010, Julian Reschke (julian.reschke@greenbytes.de)</p><p id="rfc.section.E.p.2">All rights reserved.</p><p id="rfc.section.E.p.3">Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: </p><ul><li>Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.</li><li>Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.</li><li>Neither the name of Julian Reschke nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.</li></ul><p id="rfc.section.E.p.4">THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</p><hr class="noprint"><h1 id="rfc.section.F" class="np"><a href="#rfc.section.F">F.</a> Change Logs</h1><h2 id="rfc.section.F.1"><a href="#rfc.section.F.1">F.1</a> Package</h2><dl><dt>2006-01-01</dt><dd>Switch to BSD License.</dd><dt>2007-01-12</dt><dd>Update to xml2rfc v1.33pre2.</dd><dt>2007-03-31</dt><dd>Update to xml2rfc v1.33pre3.</dd><dt>2007-05-01</dt><dd>Add XSLT test cases.</dd><dt>2008-07-18</dt><dd>Experimental support for inlined rdf:Description elements (ignored by the formatter, extracted by rfc2629grddl).</dd><dt>2008-12-04</dt><dd>Update to xml2rfc v1.34pre2.</dd><dt>2009-02-24</dt><dd>Experimental support for February 2009 boilerplate changes, and for the x:boilerplate element.</dd><dt>2009-07-08</dt><dd>Support new boilerplate ordering in RFCs published since July 2009. Fix problems with one-column text tables.</dd><dt>2009-07-19</dt><dd>When possible, calculate the actual Expiry date for Internet Drafts (full date must be available).</dd><dt>2009-08-01</dt><dd>For '$xml2rfc-ext-authors-section='end'", move the index in front of the authors section.</dd><dt>2009-08-04</dt><dd>Consider /rfc/@ipr="pre5378Trust200902" when producing RFCs, not IDs.</dd><dt>2009-08-29</dt><dd>Support alignment for artwork containing images (as opposed to, well, artwork).</dd><dt>2009-09-01</dt><dd>Allow xref in cref (as extension).</dd><dt>2009-09-14</dt><dd>Refactor handling of processing instructions.</dd><dt>2009-09-24</dt><dd>Fix typo in Status Of This Memo, present since November 2008. Fix formatting of iprExtract attribute. Starting with Internet Draft publication dates after 2009-11-30: use new Trust Legal Provisions text; for Internet Drafts: move Abstract up, and move "pre5378" escape clause to the Copyright Notice. Add support for refparent PI. For RFCs: use new TLP text as of September 2009. Incorporate xml2rfc v1.34pre4.</dd><dt>2009-10-06</dt><dd>Starting with Internet Draft publication dates after 2009-10-31: use new Trust Legal Provisions text; for Internet Drafts: move Abstract up, and move "pre5378" escape clause to the Copyright Notice. Incorporate xml2rfc v1.34pre5.</dd><dt>2009-10-27</dt><dd>Upgrade to xml2rfc v1.34.</dd><dt>2010-01-08</dt><dd>For RFC generation (not IDs), experimentally support RFC 5741 headers and boilerplate and Trust Legal Provisions 4.0.</dd><dt>2010-03-31</dt><dd>Upgrade to xml2rfc v1.35.</dd><dt>2010-06-27</dt><dd>Be consistent with xml2rfc.tcl in formatting initials (truncate after the first); see <<a href="http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10">http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10</a>>.</dd><dt>2010-08-31</dt><dd>Experimental support for prose in references.</dd><dt>2011-01-27</dt><dd>Update to xml2rfc v1.36pre1.</dd><dt>2011-04-17</dt><dd>Update to xml2rfc v1.36. Add support for more /rfc/@ipr values when producing RFCs.</dd></dl><h2 id="rfc.section.F.2"><a href="#rfc.section.F.2">F.2</a> amazon-asin.xslt</h2><dl><dt>2003-11-16</dt><dd>Initial release.</dd><dt>2005-04-02</dt><dd>Fix two DTD issues.</dd></dl><h2 id="rfc.section.F.3"><a href="#rfc.section.F.3">F.3</a> check-references.xslt</h2><dl><dt>2003-11-16</dt><dd>Initial release.</dd><dt>2004-05-11</dt><dd>Add document status; print references type.</dd><dt>2005-01-01</dt><dd>Add experimental check for ID status.</dd><dt>2005-04-01</dt><dd>Add fixes from Bill Fenner.</dd><dt>2005-12-03</dt><dd>Add checks against local copy of <<a href="http://www.w3.org/2002/01/tr-automation/tr.rdf">http://www.w3.org/2002/01/tr-automation/tr.rdf</a>>.</dd><dt>2006-07-22</dt><dd>Add checks for standards levels.</dd><dt>2006-08-06</dt><dd>"check-ietf-references.xslt" replaced by "check-references.xslt".</dd><dt>2007-01-04</dt><dd>Use information online at <<a href="http://tools.ietf.org/">http://tools.ietf.org/</a>> to retrieve Internet-Draft status information.</dd><dt>2007-06-16</dt><dd>Fix bug looking up ref type when inside change markup.</dd><dt>2008-06-14</dt><dd>Enhance output when draft was updated, and then published as RFC.</dd><dt>2008-07-12</dt><dd>Add XSLT2-based link target checking.</dd><dt>2008-08-10</dt><dd>Change keywords for "intended-level" to proposed/draft/internet, optionally extract intended level from /rfc/@x:maturity-level attribute.</dd></dl><h2 id="rfc.section.F.4"><a href="#rfc.section.F.4">F.4</a> gen-reference-graph.xslt</h2><dl><dt>2006-09-03</dt><dd>New.</dd><dt>2007-06-07</dt><dd>Use <a href="http://dpcarlisle.blogspot.com/2007/05/exslt-node-set-function.html">Carlisle method</a> to define exslt:node-set in msxsml (which means that the stylesheet can now be used with MSXML as well).</dd><dt>2007-10-15</dt><dd>Use W3C data from tr.rdf as well (experimental).</dd></dl><h2 id="rfc.section.F.5"><a href="#rfc.section.F.5">F.5</a> rfc2629.xslt</h2><dl><dt>2001-03-28</dt><dd>Code rearranged, generate numbered section anchors for paragraphs (t) as well. Fixes in index handling.</dd><dt>2001-04-12</dt><dd>Moved HTML output into XHTML namespace.</dd><dt>2001-10-02</dt><dd>Fixed default location for RFCs and numbering of section references. Support ?rfc editing processing instruction.</dd><dt>2001-10-07</dt><dd>Made telephone number links active.</dd><dt>2001-10-08</dt><dd>Support for vspace element.</dd><dt>2001-10-09</dt><dd>Experimental support for rfc-issue PI.</dd><dt>2001-11-11</dt><dd>Support rfc private PI. Removed bogus code reporting the WG in the header.</dd><dt>2001-11-11</dt><dd>Support rfc private PI. Removed bogus code reporting the WG in the header.</dd><dt>2001-12-17</dt><dd>Support title attribute on references element</dd><dt>2002-01-05</dt><dd>Support for list/@style="@format"</dd><dt>2002-01-09</dt><dd>Display "closed" RFC issues as deleted</dd><dt>2002-01-14</dt><dd>Experimentally and optionally parse XML encountered in artwork elements (requires MSXSL).</dd><dt>2002-01-27</dt><dd>Some cleanup. Moved RFC issues from PIs into namespaced elements.</dd><dt>2002-01-29</dt><dd>Added support for sortrefs PI. Added support for figure names.</dd><dt>2002-02-07</dt><dd>Highlight parts of artwork which are too wide (72 characters).</dd><dt>2002-02-12</dt><dd>Code rearrangement for static texts. Fixes for section numbering. TOC generation rewritten.</dd><dt>2002-02-15</dt><dd>Support for irefs in sections; support iref @primary=true</dd><dt>2002-03-03</dt><dd>Moved anchor prefix into a constant. Added sanity checks on user anchor names.</dd><dt>2002-03-23</dt><dd>Bugfix in detection of matching org names when creating the header. Fixed sorting in subitems.</dd><dt>2002-04-02</dt><dd>Fix TOC link HTML generation when no TOC is generated (created broken HTML table code).</dd><dt>2002-04-03</dt><dd>Made rendering of references more tolerant re: missing parts.</dd><dt>2002-04-08</dt><dd>Fixed reference numbering when references are split into separate sections.</dd><dt>2002-04-16</dt><dd>Fix default namespace (shouldn't be set for HTML output method).</dd><dt>2002-04-19</dt><dd>Lowercase internal CSS selectors for Mozilla compliance. Do not put TOC into ul element.</dd><dt>2002-04-21</dt><dd>Make numbered list inside numbered lists use alphanumeric numbering.</dd><dt>2002-05-05</dt><dd>Updated issue/editing support.</dd><dt>2002-05-15</dt><dd>Bugfix for section numbering after introduction of ed:replace</dd><dt>2002-06-21</dt><dd>When producing private documents, do not include document status, copyright etc.</dd><dt>2002-07-08</dt><dd>Fix xrefs to Appendices.</dd><dt>2002-07-19</dt><dd>Make artwork lightyellow for easier reading. (fielding)</dd><dt>2002-10-09</dt><dd>Translate references title to anchor name to avoid non-uri characters. (fielding)</dd><dt>2002-10-13</dt><dd>Support for tocdepth PI.</dd><dt>2002-11-03</dt><dd>Added temporariry workaround for Mozilla/Transformiix result tree fragment problem. (search for 'http://bugzilla.mozilla.org/show_bug.cgi?id=143668')</dd><dt>2002-12-25</dt><dd>xref code: attempt to uppercase "section" and "appendix" when at the start of a sentence.</dd><dt>2003-02-02</dt><dd>fixed code for vspace blankLines="0", enhanced display for list with "format" style, got rid of HTML blockquote elements, added support for "hangIndent"</dd><dt>2003-04-10</dt><dd>experimental support for appendix and spanx elements</dd><dt>2003-04-19</dt><dd>fixed counting of list numbers in "format %" styles (one counter per unique format string). Added more spanx styles.</dd><dt>2003-05-02</dt><dd>experimental texttable support</dd><dt>2003-05-02</dt><dd>Make mailto links optional (default = none) (jre: default and PI name changed) (fielding)</dd><dt>2003-05-04</dt><dd>experimental support for HTML link elements; fix default for table header alignment default</dd><dt>2003-05-06</dt><dd>support for "background" PI.</dd><dt>2003-05-11</dt><dd>change %c format to lowercase alphabetic. add support for keyword elements (generate META tag). fix various HTML conformance problems. added experimental support for role attribute. do not number paragraphs in unnumbered sections. update boilerplate texts. support for "iprnotified" PI. bugfix list numbering. strip whitespace when building tel: URIs.</dd><dt>2003-05-12</dt><dd>more conformance fixes (layout moved into CSS, move lists and figures out of para content, do not use tables for list formatting)</dd><dt>2003-05-13</dt><dd>add DC.Creator meta tag, refactoring</dd><dt>2003-05-16</dt><dd>put nbsps between "section" and section number (xref).</dd><dt>2003-05-18</dt><dd>author summary: add missing comma.</dd><dt>2003-06-06</dt><dd>fix index generation bug (transposed characters in key generation). Enhance sentence start detection (xref starting a section was using lowercase "section").</dd><dt>2003-06-22</dt><dd>exp. support for xref/@format. Add missing support for eref w/o content. exp. support for annotations in reference elements. Code cleanup reference table formatting.</dd><dt>2003-07-09</dt><dd>Another fix for DC.Creator meta tag creation based on RFC2731</dd><dt>2003-07-24</dt><dd>Fix namespace name for DC.Creator.</dd><dt>2003-08-06</dt><dd>Cleanup node-set support (only use exslt (saxon, xalan, libxslt) extension functions; remove Transformix workarounds that stopped to work in Moz 1.4)</dd><dt>2003-08-09</dt><dd>Generate HTML lang tag.</dd><dt>2003-08-10</dt><dd>Map spanx/verb to HTML "samp" element. Fix author name display in references (reverse surname/initials for last author), add "Ed.". Fix internal bookmark generation.</dd><dt>2003-08-17</dt><dd>Add DCMI dates, identifiers and abstract. Add PI to suppress DCMI generation. Do not add TOC entry to Copyright Statement when there is none. Align RFC2629 PI names and parameter names. Change style for inline URIs generated by eref. Add header and footer support. Enhance CSS paging properties. Support topblock PI. Added hooks for proper XHTML generation through separate XSLT. Enhance warning and error messages. Add support for artwork image display. Table formatting fixes (borders, thead continuation).</dd><dt>2003-08-18</dt><dd>Add workaround for MSXML4 node-set and Mozilla node-set issues (fallback just displays are warning).</dd><dt>2003-10-06</dt><dd>Add workaround for broken pre/ins handling in Mozilla (see <<a href="http://bugzilla.mozilla.org/show_bug.cgi?id=204401">http://bugzilla.mozilla.org/show_bug.cgi?id=204401</a>>). Make use of cite attribute on ed:replace. CSS cleanup.</dd><dt>2003-10-08</dt><dd>Fix minor issue detecting the same org for the header (caused by IE's non-standard whitespace handling). Fix default handling for /rfc/@category.</dd><dt>2003-11-09</dt><dd>Inherit ed:entered-by from ancestor elements. Change CSS color for inserted text to green. Generate issues-list anchor. Do not complain about missing targets when the xref element is below ed:del. Remove code that attempted to distinguish section/Section when producing links - always use uppercase. Fix date rendering for issue resolutions.</dd><dt>2003-11-29</dt><dd>Fix color values for table backgrounds for issue rendering. Change rendering of issue links to use inline-styles. Add colored issue markers to issues.</dd><dt>2003-12-13</dt><dd>Fix inheritance of ed:entered-by attribute. Display note elements inside change tracking as well.</dd><dt>2004-01-18</dt><dd>When PI compact = 'yes', make most CSS print page breaks conditional.</dd><dt>2004-02-20</dt><dd>Support for RFC3667 IPR changes (xml2rfc 1.22); see <<a href="http://lists.xml.resource.org/pipermail/xml2rfc/2004-February/001088.html">http://lists.xml.resource.org/pipermail/xml2rfc/2004-February/001088.html</a>>.</dd><dt>2004-03-11</dt><dd>Add "(if approved)" to "updates" and "obsoletes" unless the document has an RFC number.</dd><dt>2004-04-01</dt><dd>Fix RFC3667 output, see <<a href="http://lists.xml.resource.org/pipermail/xml2rfc/2004-April/001208.html">http://lists.xml.resource.org/pipermail/xml2rfc/2004-April/001208.html</a>>.</dd><dt>2004-04-04</dt><dd>Add support for section/top attribute. Move references into plain section container.</dd><dt>2004-04-06</dt><dd>Do not emit identical para anchors for deleted content.</dd><dt>2004-04-14</dt><dd>Fix references TOC generation when there are no references.</dd><dt>2004-04-24</dt><dd>Fix RFC3667 output, see <<a href="http://xml.resource.org/pipermail/xml2rfc/2004-April/001246.html">http://xml.resource.org/pipermail/xml2rfc/2004-April/001246.html</a>>.</dd><dt>2004-05-09</dt><dd>Add custom support for generating compound index documents. Add anchors for each Index letter. Add experimental cref support. Fix conditional page breaks before References section.</dd><dt>2004-05-16</dt><dd>Refactor external index generation.</dd><dt>2004-05-20</dt><dd>Rewrite anchor generation for comments.</dd><dt>2004-05-22</dt><dd>Enhance issues rendering (add links to changes).</dd><dt>2004-05-30</dt><dd>Allow single quote as delimiter in processing instructions as well. Move block-level issue pointers to floats. Disable issue pointers for print media. Add "purple numbers". Add hrefs to section headings. Add non-printing index key letter list to start of index.</dd><dt>2004-06-01</dt><dd>Use &#xb6; instead of # for PNs.</dd><dt>2004-07-18</dt><dd>Add support for list style=letters (thanks Roy F.). Make PNs optional; add new PI.</dd><dt>2004-09-05</dt><dd>Fix index links into unnumbered sections. Bring IPR boilerplate in-line with xml2rfc 1.25. Add experimental CSS3 paged media support. Various HTML fixes.</dd><dt>2004-09-21</dt><dd>Enhance checking of artwork width.</dd><dt>2004-09-26</dt><dd>Add check for unused references. Uppercase letters in list style letters when nested into another list.</dd><dt>2004-10-10</dt><dd>Fix internal change track pointers.</dd><dt>2004-11-01</dt><dd>Allow change tracking on references (as a whole). Rewrite artwork handling so that it allows change tracking inside artwork. Also allow a subset of text markup inside artwork, such as xrefs (note this requires post-processing the source to make it compliant to RFC2629bis).</dd><dt>2004-11-03</dt><dd>Enhanced placement of iref anchors.</dd><dt>2004-11-06</dt><dd>Index: display irefs that appeared (with primary=true) inside artwork elements in a monospaced font.</dd><dt>2004-11-14</dt><dd>Add special code so that changes in section titles can be change-tracked.</dd><dt>2005-01-14</dt><dd>Bugfixes for HtmlToXhtml converter.</dd><dt>2005-01-22</dt><dd>Enhance generation of HTML h* elements (for Mozilla Outliner).</dd><dt>2005-01-31</dt><dd>Put vertical space around top-level TOC entries in TOC. Switch to pt-based CSS. Re-arrange top section. Make hr elements reflect new-page settings in TXT output (compact-PI). Fix page number in footer (CSS print) and add some more experimental support for paged media (tested with Prince 4.1 alpha). Rewrite TOC and Index generation to generate HTML lists. Cleanup id generation for paragraphs. Reduce whitespace in output. Fix vspace implementation. Use right/left dqoutes and copyright sign where appropriate.</dd><dt>2005-02-04</dt><dd>Add <link> element to references section. Fix newly introduced bug in references processing.</dd><dt>2005-02-05</dt><dd>Integrate various fixes/enhancements by Roy Fielding: spelling of "Authors' Addresses", comma setting in references, position of "Authors" section, optionally place authors addresses at end (PI), trailing dots in section numbers, switch to verdana default font in CSS. Add experimental support for centered artwork.</dd><dt>2005-02-09</dt><dd>Fixes in spacing and links of references section titles. Enhance sorting in references when change tracking is in place. Re-add figure centering support. Add missing 2nd part of "Author's Adresses" fix.</dd><dt>2005-02-25</dt><dd>Align section number format with xml2rfc1.29.</dd><dt>2005-03-28</dt><dd>Get rid of table elements in Author's section. Add experimental hCard (<<a href="http://developers.technorati.com/wiki/hCard">http://developers.technorati.com/wiki/hCard</a>>) support.</dd><dt>2005-04-03</dt><dd>Add RFC3978-style IPR statement support. (fenner@research.att.com)</dd><dt>2005-04-11</dt><dd>Cleanup author display. hCard related fixes.</dd><dt>2005-05-07</dt><dd>Minor fixes to allow change tracking in doc title. Add experimental support for table border styles. CSS cleanup.</dd><dt>2005-06-18</dt><dd>Implement missing support for references to texttables.</dd><dt>2005-09-25</dt><dd>Use (-moz-)column-count when printing the index.</dd><dt>2005-10-04</dt><dd>Report missing element templates with xsl:message.</dd><dt>2005-10-15</dt><dd>Process t/@anchor.</dd><dt>2005-10-23</dt><dd>More workarounds for Mozilla's broken del/ins handling (this time for figures).</dd><dt>2005-10-27</dt><dd>lowercase hCard class names</dd><dt>2005-11-22</dt><dd>Enhance diagnostics for XML-in-artwork extension</dd><dt>2005-11-26</dt><dd>Fix formatting of section numbers for sections inserted into <back>.</dd><dt>2005-12-12</dt><dd>Fix some validity problems when change tracking occured inside lists.</dd><dt>2005-12-18</dt><dd>Add change tracking inside the index.</dd><dt>2006-02-04</dt><dd>Add prev/next links to highlighted changes (change tracking extension).</dd><dt>2006-02-10</dt><dd>Catch errors instantiating MSXML component.</dd><dt>2006-02-11</dt><dd>References: add "work in progress" for Internet Drafts.</dd><dt>2006-02-27</dt><dd>Fix front matter (lowercase Internet-Draft, say "Intended status" for non-RFC documents). Start work on experimental extension for simplified internal links.</dd><dt>2006-03-19</dt><dd>Tweaks to IESG Copyright stuff; support submissionType attribute. Fix duplicate reference anchors in HTML output. Reduce HTML Tidy warnings. Fix reference to normative ASCII version (now requires trailing ".txt"). Tweaks to hCard generation. Started to move non-issue-tracking extensions into namespace "http://purl.org/net/xml2rfc/ext".</dd><dt>2006-03-27</dt><dd>Moved "simple reference" extension into namespace "http://purl.org/net/xml2rfc/ext" and add documentation. HTML conformance enhancements.</dd><dt>2006-04-02</dt><dd>Cleanup special code for automated XHTML XSLT generation.</dd><dt>2006-04-21</dt><dd>Generate <CITE> elements where appropiate. Introduce x:blockquote, x:dfn, x:h and x:q elements.</dd><dt>2006-05-06</dt><dd>Introduce x:bcp14 element.</dd><dt>2006-05-14</dt><dd>Fix content model for x:blockquote.</dd><dt>2006-06-18</dt><dd>Add box drawing support (x:bt, x:bc, x:bb).</dd><dt>2006-06-20</dt><dd>HTML validity fixes (legal chars in anchors in index).</dd><dt>2006-06-24</dt><dd>Reduce leading empty lines in artwork. Move <dt> style info into CSS.</dd><dt>2006-07-14</dt><dd>Fix rendering of multiple street address entries (missing line break).</dd><dt>2006-07-24</dt><dd>Add extension for deep linking into RFCs, do not generate empty list items in TOC output, avoid empty <dt> elements for list items without hangText attribute.</dd><dt>2006-08-01</dt><dd>Allow @anchor on more elements; start work on Relax NG grammar for extensions. Reduce generated style elements (use CSS classes instead). Consistently use "id" instead of "name". Change default target for RFC links to "http://tools.ietf.org/html/rfcNNNN".</dd><dt>2006-08-06</dt><dd>Include appendices defined in <appendix> elements in TOC (please consider them deprecated anyhow!). Generate links to "http://tools.ietf.org/html/draft-*" for Internet Drafts. Replace x:frag by x:rel, allowing any kind of relative reference instead of just fragments.</dd><dt>2006-08-30</dt><dd>Reduce textual differences between HTML output and what xml2rfc produces in TXT output mode (section refs/reference targets). Add small workaround for Opera 9.0.1's problem with node-set().</dd><dt>2006-10-29</dt><dd>Fix problem generating internal links to change markup within references section. Enhancements when generating numbered references for deleted references. Allow inclusion of references into the index (through include-references-in-index extension). Fix a bug that caused the newer version of the IETF boilerplate to be produced rather than the pre-RFC3667 one. Update to RFC4287 boilerplate.</dd><dt>2006-11-11</dt><dd>Add extension attribute x:for-anchor to <iref> handling.</dd><dt>2006-11-26</dt><dd>Experimental (and limited) support for <x:lt>.</dd><dt>2006-12-04</dt><dd>Fix bugs in processing documents that have both the ipr and the number attribute set on the rfc root element. Add support for x:fmt='none' on xrefs. Add different pre style based on artwork type attributes (experimental).</dd><dt>2006-12-13</dt><dd>Add x:fmt='anchor' for xref elements.</dd><dt>2007-01-07</dt><dd>Fix root template for compatibility for the exslt:node-set implementation in Firefox3.</dd><dt>2007-01-29</dt><dd>Avoid empty table entry in front matter when organization is not specified for an author.</dd><dt>2007-02-10</dt><dd>Allow change tracking in table rows.</dd><dt>2007-03-09</dt><dd>Add hcard profile URI (<<a href="http://www.w3.org/2006/03/hcard">http://www.w3.org/2006/03/hcard</a>>) to head element. Add warning for misplaced <t> elements (after section).</dd><dt>2007-03-21</dt><dd>Fix internal linking from reference entries in index for some xref types. Minor CSS tweaks contributed by MTR. Allow turning on text justification through a PI. Improve iref anchor generation to generate less instable anchors.</dd><dt>2007-03-28</dt><dd>Fixes for numbering of ed:inserted references sections.</dd><dt>2007-05-04</dt><dd>Do not generate anchors for edits in deleted sections. Enhance HTML conformance.</dd><dt>2007-05-19</dt><dd>Enhance diagnostics when using Saxon (needs Saxon's "-l" command line parameter to keep line number information). Add warning when symref PI is missing (default will change in the future). Add support for overriding computed section numbers (when formatting historic documents).</dd><dt>2007-06-07</dt><dd>Change default for symrefs PI to "yes" (see change in xml2rfc 1.33pre4). Warn about docName attributes that appear to contain a file extension.</dd><dt>2007-06-26</dt><dd>Workaround author/@initials values without trailing dot, as in xml2rfc.tcl.</dd><dt>2007-07-14</dt><dd>Enhance index generation for references that use @x:sec attribute.</dd><dt>2007-09-09</dt><dd>Fix: sortrefs is a nop when symrefs=no.</dd><dt>2007-10-17</dt><dd>Work in progress: add support for referencing sections in sibling documents by anchor name.</dd><dt>2007-10-17</dt><dd>Work in progress (continued): support for referencing sections in sibling documents by anchor name.</dd><dt>2007-12-31</dt><dd>Emit warning when updating/obsoleting stuff that's not referenced.</dd><dt>2008-02-03</dt><dd>Support xml2rfc-1.33pre5's suppress-title attribute on texttable and figure.</dd><dt>2008-02-06</dt><dd>Extension: allow <eref> below <cref>.</dd><dt>2008-02-17</dt><dd>Extensions: add x:span and x:length-of.</dd><dt>2008-02-20</dt><dd>Add new RFC boilerplate (as changed in 2007-08).</dd><dt>2008-02-27</dt><dd>Improve diagnostics for artwork width problems; add defaulting of publication dates (requires XSLT processor supporting exslt:date, or msxml).</dd><dt>2008-02-29</dt><dd>Enhance CSS for link elements in the front header, update rules for generating "Acknowledgment" statement.</dd><dt>2008-03-01</dt><dd>Use line numbers in diagnostics in Saxon8/9 as well.</dd><dt>2008-03-02</dt><dd>Fix a bug in the logic choosing the boilerplate, resulting in obsolete text being inserted into IDs.</dd><dt>2008-04-01</dt><dd>Add support for superscript element.</dd><dt>2008-06-28</dt><dd>Add sanity checks for email addresses, allow multiple email elements.</dd><dt>2008-07-06</dt><dd>Add x:abnf-char-sequence.</dd><dt>2008-08-21</dt><dd>Add x:note.</dd><dt>2008-09-06</dt><dd>Add experimental support for SVG images.</dd><dt>2008-09-17</dt><dd>Add experimental support for x:author. Fix xref/@format=none.</dd><dt>2008-10-10</dt><dd>Fix a huge bug, causing text content after an XML comment to be ignored.</dd><dt>2009-02-24</dt><dd>Use table/caption when needed.</dd><dt>2009-03-07</dt><dd>Fix bug that caused text to disappear in the output in presence of processing instructions.</dd><dt>2009-03-12</dt><dd>Make inlined comments bookmarkable.</dd><dt>2009-04-09</dt><dd>Upgrade to DC-HTML from RFC 2731 (affects head/@profile).</dd><dt>2009-07-08</dt><dd>Remove table/@summary in output; the value getting inserted was just repeating stuff that appeared in the preamble.</dd><dt>2009-08-01</dt><dd>Implement table alignment (HTML output only for now).</dd><dt>2009-08-18</dt><dd>Replicate Dublin Core "abstract" metadata into meta/@name=description (search engines do use it).</dd><dt>2009-09-02</dt><dd>Fix default/left alignment of table columns, remove silly table summmary attributes.</dd><dt>2009-09-24</dt><dd>Support double-sided layout using CSS page:left/right selectors.</dd><dt>2009-11-27</dt><dd>Generate unordered lists instead of broken definition lists for list style empty.</dd></dl><h2 id="rfc.section.F.6"><a href="#rfc.section.F.6">F.6</a> rfc2629toFO.xslt</h2><dl><dt>2003-11-16</dt><dd>Initial release.</dd><dt>2003-11-29</dt><dd>Enhance handling of unknown list styles.</dd><dt>2004-04-04</dt><dd>Update reference section handling.</dd><dt>2004-04-17</dt><dd>Use XSL-WD-1.1-style fo:bookmark and index handling and add postprocessors for existing implementations. Unify PDF info generation by using XEP (postprocessors) will convert.</dd><dt>2004-04-20</dt><dd>Add experimental cref support.</dd><dt>2004-06-14</dt><dd>Set correct index-item defaults.</dd><dt>2004-07-18</dt><dd>Add list style=letters.</dd><dt>2004-09-03</dt><dd>Make URLs in text break where they are allowed to break by inserting zero-width spaces.</dd><dt>2004-09-26</dt><dd>Fix letter-style inside nested lists.</dd><dt>2004-10-31</dt><dd>Update handling of artwork.</dd><dt>2004-11-13</dt><dd>Fix handling of references inside ed:* markup. Fix whitespace handling in artwork.</dd><dt>2004-11-27</dt><dd>Irefs in artwork generate monospaced entries in index.</dd><dt>2005-01-31</dt><dd>Fix TOC generation that was broken after changes in main XSLT.</dd><dt>2005-02-05</dt><dd>Bring in sync with cosmetic changes in rfc2629.xslt.</dd><dt>2005-05-07</dt><dd>Minor fix for change tracking in document title. Support for table styles.</dd><dt>2005-06-18</dt><dd>Fix references to tables.</dd><dt>2005-10-15</dt><dd>Process t/@anchor.</dd><dt>2006-02-11</dt><dd>References: add "work in progress" for Internet Drafts.</dd><dt>2006-06-02</dt><dd>Use XSL 1.1 WD Feb 2006.</dd><dt>2007-03-21</dt><dd>Support optional text justification.</dd><dt>2007-05-19</dt><dd>Various improvements in spacing; also allow overriding the automatic list indentation via list/x:indent.</dd><dt>2009-04-08</dt><dd>Fix spacing in headers; add support for formatting for double-sided printing.</dd><dt>2009-08-01</dt><dd>Remove surplus empty pages when not generating double-sided output.</dd></dl><h2 id="rfc.section.F.7"><a href="#rfc.section.F.7">F.7</a> xsl11toAn.xslt</h2><dl><dt>2004-05-17</dt><dd>Initial release.</dd><dt>2006-06-02</dt><dd>Use XSL 1.1 WD Feb 2006.</dd></dl><h2 id="rfc.section.F.8"><a href="#rfc.section.F.8">F.8</a> xsl11toFop.xslt</h2><dl><dt>2010-08-25</dt><dd>Switch to Apache FOP 1.0.</dd><dt>2009-09-12</dt><dd>Support for FOP 0.20.5 and FOP 0.93 removed. Please use FOP 0.95.</dd><dt>2008-03-15</dt><dd>Add a workaround to the fo:inline workaround (sigh).</dd></dl><h2 id="rfc.section.F.9"><a href="#rfc.section.F.9">F.9</a> xsl11toXep.xslt</h2><dl><dt>2004-05-17</dt><dd>Initial release.</dd><dt>2004-09-04</dt><dd>Fix xep:index-item attributes.</dd><dt>2006-06-02</dt><dd>Use XSL 1.1 WD Feb 2006.</dd></dl><hr class="noprint"><h1 id="rfc.index" class="np"><a href="#rfc.index">Index</a></h1><p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.J">J</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.Q">Q</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.X">X</a> </p><div class="print2col"><ul class="ind"><li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul><li>abnf-char-sequence Extension Element <a href="#rfc.iref.a.27"><b>11.1</b></a>, <a href="#rfc.iref.a.29">A</a></li><li>allow-markup-in-artwork PI pseudo-attribute <a href="#rfc.iref.a.1">3.3</a></li><li>alternate HTML LINK element <a href="#rfc.iref.a.22">6.2</a></li><li>anchor-alias Extension Element <a href="#rfc.iref.a.28"><b>11.2</b></a>, <a href="#rfc.iref.a.30">A</a></li><li>Anchors <ul><li>rfc.abstract <a href="#rfc.iref.a.3">4</a></li><li>rfc.authors <a href="#rfc.iref.a.4">4</a></li><li>rfc.copyright <a href="#rfc.iref.a.5">4</a></li><li>rfc.copyrightnotice <a href="#rfc.iref.a.6">4</a></li><li>rfc.figure.n <a href="#rfc.iref.a.7">4</a>, <a href="#rfc.iref.a.18">4</a></li><li>rfc.figure.u.n <a href="#rfc.iref.a.8">4</a>, <a href="#rfc.iref.a.19">4</a></li><li>rfc.index <a href="#rfc.iref.a.9">4</a></li><li>rfc.ipr <a href="#rfc.iref.a.10">4</a></li><li>rfc.iref.n <a href="#rfc.iref.a.11">4</a></li><li>rfc.note.n <a href="#rfc.iref.a.12">4</a></li><li>rfc.references <a href="#rfc.iref.a.13">4</a>, <a href="#rfc.iref.a.14">4</a></li><li>rfc.section.n <a href="#rfc.iref.a.15">4</a></li><li>rfc.section.n.p.m <a href="#rfc.iref.a.16">4</a></li><li>rfc.status <a href="#rfc.iref.a.17">4</a></li><li>rfc.toc <a href="#rfc.iref.a.20">4</a></li><li>rfc.xref.name.n <a href="#rfc.iref.a.21">4</a></li></ul></li><li>AntennaHouse XSL Formatter <a href="#rfc.iref.a.26">9.1</a></li><li>Apache FOP <a href="#rfc.iref.a.25">9.1</a></li><li>appendix HTML LINK element <a href="#rfc.iref.a.23">6.2</a></li><li>assign-section-number Extension Element <a href="#rfc.iref.a.31">A</a></li><li>author HTML LINK element <a href="#rfc.iref.a.24">6.2</a></li><li>authors-section PI pseudo-attribute <a href="#rfc.iref.a.2">3.3</a></li></ul></li><li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul><li>background PI pseudo-attribute <a href="#rfc.iref.b.1">3.1</a></li><li>bb Extension Element <a href="#rfc.iref.b.3"><b>11.4</b></a>, <a href="#rfc.iref.b.8">A</a></li><li>bc Extension Element <a href="#rfc.iref.b.4"><b>11.5</b></a>, <a href="#rfc.iref.b.9">A</a></li><li>bcp14 Extension Element <a href="#rfc.iref.b.2"><b>11.3</b></a>, <a href="#rfc.iref.b.10">A</a></li><li><em>BCP97</em> <a href="#rfc.xref.BCP97.1">12.1</a>, <a href="#BCP97"><b>13</b></a></li><li>blockquote Extension Element <a href="#rfc.iref.b.5"><b>11.6</b></a>, <a href="#rfc.iref.b.11">A</a></li><li>boilerplate Extension Element <a href="#rfc.iref.b.6"><b>11.7</b></a>, <a href="#rfc.iref.b.12">A</a></li><li>bt Extension Element <a href="#rfc.iref.b.7"><b>11.8</b></a>, <a href="#rfc.iref.b.13">A</a></li></ul></li><li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul><li>chapter HTML LINK element <a href="#rfc.iref.c.3">6.2</a></li><li>CHM format <a href="#rfc.iref.c.7">8</a></li><li>comments PI pseudo-attribute <a href="#rfc.iref.c.2">3.1</a></li><li>compact PI pseudo-attribute <a href="#rfc.iref.c.1">3.1</a></li><li>contents HTML LINK element <a href="#rfc.iref.c.4">6.2</a></li><li>copyright HTML LINK element <a href="#rfc.iref.c.5">6.2</a></li><li>Creator DCMI property <a href="#rfc.iref.c.6">6.4</a></li></ul></li><li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul><li>Date.Issued DCMI property <a href="#rfc.iref.d.3">6.4</a></li><li><em>DC-HTML</em> <a href="#rfc.xref.DC-HTML.1">6.4</a>, <a href="#DC-HTML"><b>13</b></a></li><li>DCMI properties <ul><li>Creator <a href="#rfc.iref.d.2">6.4</a></li><li>Date.Issued <a href="#rfc.iref.d.4">6.4</a></li><li>Description.Abstract <a href="#rfc.iref.d.6">6.4</a></li><li>Identifier <a href="#rfc.iref.d.7">6.4</a></li><li>isPartOf <a href="#rfc.iref.d.8">6.4</a></li><li>Relation.Replaces <a href="#rfc.iref.d.9">6.4</a></li></ul></li><li>Description.Abstract DCMI property <a href="#rfc.iref.d.5">6.4</a></li><li>dfn Extension Element <a href="#rfc.iref.d.10"><b>11.9</b></a>, <a href="#rfc.iref.d.11">A</a></li><li>duplex PI pseudo-attribute <a href="#rfc.iref.d.1">3.3</a></li></ul></li><li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul><li>editing PI pseudo-attribute <a href="#rfc.iref.e.1">3.1</a></li><li>Extension Elements <ul><li>abnf-char-sequence <a href="#rfc.iref.e.2"><b>11.1</b></a>, <a href="#rfc.iref.e.23">A</a></li><li>anchor-alias <a href="#rfc.iref.e.3"><b>11.2</b></a>, <a href="#rfc.iref.e.24">A</a></li><li>assign-section-number <a href="#rfc.iref.e.26">A</a></li><li>bb <a href="#rfc.iref.e.5"><b>11.4</b></a>, <a href="#rfc.iref.e.27">A</a></li><li>bc <a href="#rfc.iref.e.6"><b>11.5</b></a>, <a href="#rfc.iref.e.28">A</a></li><li>bcp14 <a href="#rfc.iref.e.4"><b>11.3</b></a>, <a href="#rfc.iref.e.29">A</a></li><li>blockquote <a href="#rfc.iref.e.7"><b>11.6</b></a>, <a href="#rfc.iref.e.30">A</a></li><li>boilerplate <a href="#rfc.iref.e.8"><b>11.7</b></a>, <a href="#rfc.iref.e.31">A</a></li><li>bt <a href="#rfc.iref.e.9"><b>11.8</b></a>, <a href="#rfc.iref.e.32">A</a></li><li>dfn <a href="#rfc.iref.e.10"><b>11.9</b></a>, <a href="#rfc.iref.e.33">A</a></li><li>h <a href="#rfc.iref.e.11"><b>11.10</b></a>, <a href="#rfc.iref.e.34">A</a></li><li>highlight <a href="#rfc.iref.e.12"><b>11.11</b></a>, <a href="#rfc.iref.e.35">A</a></li><li>include-author <a href="#rfc.iref.e.25">A</a></li><li>length-of <a href="#rfc.iref.e.13"><b>11.12</b></a>, <a href="#rfc.iref.e.36">A</a></li><li>link <a href="#rfc.iref.e.14"><b>11.13</b></a>, <a href="#rfc.iref.e.37">A</a></li><li>lt <a href="#rfc.iref.e.15"><b>11.14</b></a>, <a href="#rfc.iref.e.38">A</a></li><li>note <a href="#rfc.iref.e.16"><b>11.15</b></a>, <a href="#rfc.iref.e.39">A</a></li><li>parse-xml <a href="#rfc.iref.e.17"><b>11.16</b></a>, <a href="#rfc.iref.e.40">A</a></li><li>prose <a href="#rfc.iref.e.18"><b>11.17</b></a>, <a href="#rfc.iref.e.41">A</a></li><li>q <a href="#rfc.iref.e.19"><b>11.18</b></a>, <a href="#rfc.iref.e.42">A</a></li><li>rdf:Description <a href="#rfc.iref.e.48">A</a></li><li>ref <a href="#rfc.iref.e.20"><b>11.19</b></a>, <a href="#rfc.iref.e.43">A</a></li><li>source <a href="#rfc.iref.e.21"><b>11.20</b></a>, <a href="#rfc.iref.e.44">A</a></li><li>span <a href="#rfc.iref.e.46">A</a></li><li>sup <a href="#rfc.iref.e.22"><b>11.21</b></a>, <a href="#rfc.iref.e.45">A</a></li><li>x <a href="#rfc.iref.e.47">A</a></li></ul></li></ul></li><li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul><li>Firefox <ul><li>1.*/2.* <a href="#rfc.iref.f.3">5.2</a></li><li>3.* <a href="#rfc.iref.f.2">5.2</a></li></ul></li><li>footer PI pseudo-attribute <a href="#rfc.iref.f.1">3.1</a></li></ul></li><li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul><li>generator HTML META element <a href="#rfc.iref.g.2">6.3</a></li><li>Google Chrome <a href="#rfc.iref.g.1">5.2</a></li><li>Grammar <a href="#rfc.iref.g.3"><b>A</b></a></li></ul></li><li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul><li>h Extension Element <a href="#rfc.iref.h.12"><b>11.10</b></a>, <a href="#rfc.iref.h.14">A</a></li><li>header PI pseudo-attribute <a href="#rfc.iref.h.1">3.1</a></li><li>highlight Extension Element <a href="#rfc.iref.h.13"><b>11.11</b></a>, <a href="#rfc.iref.h.15">A</a></li><li><em>HTML</em> <a href="#rfc.xref.HTML.1">6.1</a>, <a href="#rfc.xref.HTML.2">11.6</a>, <a href="#rfc.xref.HTML.3">11.9</a>, <a href="#rfc.xref.HTML.4">11.18</a>, <a href="#rfc.xref.HTML.5">11.21</a>, <a href="#HTML"><b>13</b></a></li><li>HTML compliance <a href="#rfc.iref.h.2">6.1</a></li><li>HTML LINK elements <ul><li>alternate <a href="#rfc.iref.h.3">6.2</a></li><li>appendix <a href="#rfc.iref.h.4">6.2</a></li><li>author <a href="#rfc.iref.h.5">6.2</a></li><li>chapter <a href="#rfc.iref.h.6">6.2</a></li><li>contents <a href="#rfc.iref.h.7">6.2</a></li><li>copyright <a href="#rfc.iref.h.8">6.2</a></li><li>index <a href="#rfc.iref.h.9">6.2</a></li></ul></li><li>HTML META elements <ul><li>generator <a href="#rfc.iref.h.10">6.3</a></li><li>keywords <a href="#rfc.iref.h.11">6.3</a></li></ul></li></ul></li><li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul><li>Identifier DCMI property <a href="#rfc.iref.i.12">6.4</a></li><li>include PI pseudo-attribute <a href="#rfc.iref.i.3">3.2</a></li><li>include-author Extension Element <a href="#rfc.iref.i.14">A</a></li><li>include-index PI pseudo-attribute <a href="#rfc.iref.i.4">3.3</a></li><li>include-references-in-index PI pseudo-attribute <a href="#rfc.iref.i.5">3.3</a></li><li>index HTML LINK element <a href="#rfc.iref.i.11">6.2</a></li><li>inline PI pseudo-attribute <a href="#rfc.iref.i.1">3.1</a></li><li>Internet Explorer 5.5 <a href="#rfc.iref.i.6">5.2</a></li><li>Internet Explorer 6 <a href="#rfc.iref.i.7">5.2</a></li><li>Internet Explorer 7 <a href="#rfc.iref.i.8">5.2</a></li><li>Internet Explorer 8 <a href="#rfc.iref.i.9">5.2</a></li><li>Internet Explorer 9 <a href="#rfc.iref.i.10">5.2</a></li><li>iprnotified PI pseudo-attribute <a href="#rfc.iref.i.2">3.1</a></li><li>isPartOf DCMI property <a href="#rfc.iref.i.13">6.4</a></li></ul></li><li><a id="rfc.index.J" href="#rfc.index.J"><b>J</b></a><ul><li>justification PI pseudo-attribute <a href="#rfc.iref.j.1">3.3</a></li></ul></li><li><a id="rfc.index.K" href="#rfc.index.K"><b>K</b></a><ul><li>keywords HTML META element <a href="#rfc.iref.k.1">6.3</a></li></ul></li><li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul><li>length-of Extension Element <a href="#rfc.iref.l.2"><b>11.12</b></a>, <a href="#rfc.iref.l.5">A</a></li><li>link Extension Element <a href="#rfc.iref.l.3"><b>11.13</b></a>, <a href="#rfc.iref.l.6">A</a></li><li>linkmailto PI pseudo-attribute <a href="#rfc.iref.l.1">3.1</a></li><li>lt Extension Element <a href="#rfc.iref.l.4"><b>11.14</b></a>, <a href="#rfc.iref.l.7">A</a></li></ul></li><li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul><li>Microsoft Help <a href="#rfc.iref.m.5">8</a></li><li>Mozilla <a href="#rfc.iref.m.3">5.2</a>, <a href="#rfc.iref.m.4">5.2</a></li><li>MSXML3 <a href="#rfc.iref.m.1">5.1</a></li><li>MSXML4 <a href="#rfc.iref.m.2">5.1</a></li></ul></li><li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul><li>needLines PI pseudo-attribute <a href="#rfc.iref.n.1">3.2</a></li><li>NoScript <a href="#rfc.iref.n.2">5.2</a></li><li>note Extension Element <a href="#rfc.iref.n.3"><b>11.15</b></a>, <a href="#rfc.iref.n.4">A</a></li></ul></li><li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul><li>Opera <a href="#rfc.iref.o.1">5.2</a>, <a href="#rfc.iref.o.2">5.2</a></li></ul></li><li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul><li>Parameters <ul><li>xml2rfc-background <a href="#rfc.iref.p.2">3.1</a></li><li>xml2rfc-comments <a href="#rfc.iref.p.6">3.1</a></li><li>xml2rfc-compact <a href="#rfc.iref.p.4">3.1</a></li><li>xml2rfc-editing <a href="#rfc.iref.p.8">3.1</a></li><li>xml2rfc-ext-allow-markup-in-artwork <a href="#rfc.iref.p.44">3.3</a></li><li>xml2rfc-ext-authors-section <a href="#rfc.iref.p.46">3.3</a></li><li>xml2rfc-ext-duplex <a href="#rfc.iref.p.48">3.3</a></li><li>xml2rfc-ext-include-index <a href="#rfc.iref.p.50">3.3</a></li><li>xml2rfc-ext-include-references-in-index <a href="#rfc.iref.p.52">3.3</a></li><li>xml2rfc-ext-justification <a href="#rfc.iref.p.54">3.3</a></li><li>xml2rfc-ext-parse-xml-in-artwork <a href="#rfc.iref.p.57">3.3</a></li><li>xml2rfc-ext-sec-no-trailing-dots <a href="#rfc.iref.p.61">3.3</a></li><li>xml2rfc-ext-support-rfc2731 <a href="#rfc.iref.p.59">3.3</a></li><li>xml2rfc-footer <a href="#rfc.iref.p.10">3.1</a></li><li>xml2rfc-header <a href="#rfc.iref.p.12">3.1</a></li><li>xml2rfc-inline <a href="#rfc.iref.p.14">3.1</a></li><li>xml2rfc-iprnotified <a href="#rfc.iref.p.16">3.1</a></li><li>xml2rfc-linkmailto <a href="#rfc.iref.p.18">3.1</a></li><li>xml2rfc-private <a href="#rfc.iref.p.21">3.1</a></li><li>xml2rfc-refparent <a href="#rfc.iref.p.23">3.1</a></li><li>xml2rfc-rfcedstyle <a href="#rfc.iref.p.25">3.1</a></li><li>xml2rfc-sortrefs <a href="#rfc.iref.p.27">3.1</a></li><li>xml2rfc-symrefs <a href="#rfc.iref.p.29">3.1</a></li><li>xml2rfc-toc <a href="#rfc.iref.p.31">3.1</a></li><li>xml2rfc-tocdepth <a href="#rfc.iref.p.33">3.1</a></li><li>xml2rfc-topblock <a href="#rfc.iref.p.35">3.1</a></li></ul></li><li>parse-xml Extension Element <a href="#rfc.iref.p.62"><b>11.16</b></a>, <a href="#rfc.iref.p.64">A</a></li><li>parse-xml-in-artwork PI pseudo-attribute <a href="#rfc.iref.p.55">3.3</a></li><li>private PI pseudo-attribute <a href="#rfc.iref.p.19">3.1</a>, <a href="#rfc.iref.p.66">D</a></li><li>Processing Instruction pseudo attributes <ul><li>allow-markup-in-artwork <a href="#rfc.iref.p.43">3.3</a></li><li>authors-section <a href="#rfc.iref.p.45">3.3</a></li><li>background <a href="#rfc.iref.p.1">3.1</a></li><li>comments <a href="#rfc.iref.p.5">3.1</a></li><li>compact <a href="#rfc.iref.p.3">3.1</a></li><li>duplex <a href="#rfc.iref.p.47">3.3</a></li><li>editing <a href="#rfc.iref.p.7">3.1</a></li><li>footer <a href="#rfc.iref.p.9">3.1</a></li><li>header <a href="#rfc.iref.p.11">3.1</a></li><li>ijustification <a href="#rfc.iref.p.53">3.3</a></li><li>include <a href="#rfc.iref.p.36">3.2</a></li><li>include-index <a href="#rfc.iref.p.49">3.3</a></li><li>include-references-in-index <a href="#rfc.iref.p.51">3.3</a></li><li>inline <a href="#rfc.iref.p.13">3.1</a></li><li>iprnotified <a href="#rfc.iref.p.15">3.1</a></li><li>linkmailto <a href="#rfc.iref.p.17">3.1</a></li><li>needLines <a href="#rfc.iref.p.37">3.2</a></li><li>parse-xml-in-artwork <a href="#rfc.iref.p.56">3.3</a></li><li>private <a href="#rfc.iref.p.20">3.1</a>, <a href="#rfc.iref.p.67">D</a></li><li>refparent <a href="#rfc.iref.p.22">3.1</a></li><li>rfcedstyle <a href="#rfc.iref.p.24">3.1</a></li><li>sec-no-trailing-dots <a href="#rfc.iref.p.60">3.3</a></li><li>slides <a href="#rfc.iref.p.38">3.2</a></li><li>sortrefs <a href="#rfc.iref.p.26">3.1</a></li><li>strict <a href="#rfc.iref.p.39">3.2</a></li><li>subcompact <a href="#rfc.iref.p.40">3.2</a></li><li>support-rfc2731 <a href="#rfc.iref.p.58">3.3</a></li><li>symrefs <a href="#rfc.iref.p.28">3.1</a></li><li>toc <a href="#rfc.iref.p.30">3.1</a></li><li>tocdepth <a href="#rfc.iref.p.32">3.1</a></li><li>tocindent <a href="#rfc.iref.p.41">3.2</a></li><li>tocompact <a href="#rfc.iref.p.42">3.2</a></li><li>topblock <a href="#rfc.iref.p.34">3.1</a></li></ul></li><li>prose Extension Element <a href="#rfc.iref.p.63"><b>11.17</b></a>, <a href="#rfc.iref.p.65">A</a></li></ul></li><li><a id="rfc.index.Q" href="#rfc.index.Q"><b>Q</b></a><ul><li>q Extension Element <a href="#rfc.iref.q.1"><b>11.18</b></a>, <a href="#rfc.iref.q.2">A</a></li></ul></li><li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul><li>rdf:Description Extension Element <a href="#rfc.iref.r.26">A</a></li><li>ref Extension Element <a href="#rfc.iref.r.23"><b>11.19</b></a>, <a href="#rfc.iref.r.25">A</a></li><li>refparent PI pseudo-attribute <a href="#rfc.iref.r.1">3.1</a></li><li>Relation.Replaces DCMI property <a href="#rfc.iref.r.22">6.4</a></li><li>RELAX NG Compact Schema <a href="#rfc.iref.r.24"><b>A</b></a></li><li>rfc.abstract anchor <a href="#rfc.iref.r.3">4</a></li><li>rfc.authors anchor <a href="#rfc.iref.r.4">4</a></li><li>rfc.copyright anchor <a href="#rfc.iref.r.5">4</a></li><li>rfc.copyrightnotice anchor <a href="#rfc.iref.r.6">4</a></li><li>rfc.figure.n anchor <a href="#rfc.iref.r.7">4</a>, <a href="#rfc.iref.r.18">4</a></li><li>rfc.figure.u.n anchor <a href="#rfc.iref.r.8">4</a>, <a href="#rfc.iref.r.19">4</a></li><li>rfc.index anchor <a href="#rfc.iref.r.9">4</a></li><li>rfc.ipr anchor <a href="#rfc.iref.r.10">4</a></li><li>rfc.iref.n anchor <a href="#rfc.iref.r.11">4</a></li><li>rfc.note.n anchor <a href="#rfc.iref.r.12">4</a></li><li>rfc.references anchor <a href="#rfc.iref.r.13">4</a></li><li>rfc.references.n anchor <a href="#rfc.iref.r.14">4</a></li><li>rfc.section.n anchor <a href="#rfc.iref.r.15">4</a></li><li>rfc.section.n.p.m anchor <a href="#rfc.iref.r.16">4</a></li><li>rfc.status anchor <a href="#rfc.iref.r.17">4</a></li><li>rfc.toc anchor <a href="#rfc.iref.r.20">4</a></li><li>rfc.xref.name.n anchor <a href="#rfc.iref.r.21">4</a></li><li><em>RFC2026</em> <a href="#rfc.xref.RFC2026.1">11.25</a>, <a href="#RFC2026"><b>13</b></a>, <a href="#rfc.xref.RFC2026.2">D.2</a><ul><li><em>Section 4</em> <a href="#rfc.xref.RFC2026.2">D.2</a></li><li><em>Section 4.1</em> <a href="#rfc.xref.RFC2026.1">11.25</a></li></ul></li><li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">11.3</a>, <a href="#rfc.xref.RFC2119.2">11.27</a>, <a href="#RFC2119"><b>13</b></a><ul><li><em>Section 5</em> <a href="#rfc.xref.RFC2119.2">11.27</a></li></ul></li><li><em>RFC2616</em> <a href="#RFC2616"><b>13</b></a>, <a href="#rfc.xref.RFC2616.1">B.1</a>, <a href="#rfc.xref.RFC2616.2">B.1</a>, <a href="#rfc.xref.RFC2616.3">B.1</a><ul><li><em>Section 2.1</em> <a href="#rfc.xref.RFC2616.1">B.1</a></li><li><em>Section 19.1</em> <a href="#rfc.xref.RFC2616.2">B.1</a>, <a href="#rfc.xref.RFC2616.3">B.1</a></li></ul></li><li><em>RFC2629</em> <a href="#rfc.xref.RFC2629.1">1</a>, <a href="#RFC2629"><b>13</b></a></li><li><em>RFC2648</em> <a href="#rfc.xref.RFC2648.1">6.4</a>, <a href="#RFC2648"><b>13</b></a></li><li><em>RFC2731</em> <a href="#rfc.xref.RFC2731.1">6.4</a>, <a href="#RFC2731"><b>13</b></a></li><li><em>RFC5234</em> <a href="#RFC5234"><b>13</b></a>, <a href="#rfc.xref.RFC5234.1">B.1</a></li><li><em>RFC5741</em> <a href="#RFC5741"><b>13</b></a>, <a href="#rfc.xref.RFC5741.1">D.3</a>, <a href="#rfc.xref.RFC5741.2">D.3</a>, <a href="#rfc.xref.RFC5741.3">D.4</a><ul><li><em>Section 3.2.2</em> <a href="#rfc.xref.RFC5741.2">D.3</a>, <a href="#rfc.xref.RFC5741.3">D.4</a></li></ul></li><li>rfcedstyle PI pseudo-attribute <a href="#rfc.iref.r.2">3.1</a></li><li><em>RNC</em> <a href="#RNC"><b>13</b></a>, <a href="#rfc.xref.RNC.1">A</a>, <a href="#rfc.xref.RNC.2">B.1</a></li></ul></li><li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul><li>Safari <a href="#rfc.iref.s.9">5.2</a>, <a href="#rfc.iref.s.11">5.2</a><ul><li>3.* <a href="#rfc.iref.s.10">5.2</a></li></ul></li><li>Saxon <a href="#rfc.iref.s.8">5.1</a></li><li>Schema <a href="#rfc.iref.s.14"><b>A</b></a></li><li>sec-no-trailing-dots PI pseudo-attribute <a href="#rfc.iref.s.7">3.3</a></li><li>slides PI pseudo-attribute <a href="#rfc.iref.s.3">3.2</a></li><li>sortrefs PI pseudo-attribute <a href="#rfc.iref.s.1">3.1</a></li><li>source Extension Element <a href="#rfc.iref.s.12"><b>11.20</b></a>, <a href="#rfc.iref.s.15">A</a></li><li>span Extension Element <a href="#rfc.iref.s.17">A</a></li><li>strict PI pseudo-attribute <a href="#rfc.iref.s.4">3.2</a></li><li>subcompact PI pseudo-attribute <a href="#rfc.iref.s.5">3.2</a></li><li>sup Extension Element <a href="#rfc.iref.s.13"><b>11.21</b></a>, <a href="#rfc.iref.s.16">A</a></li><li>support-rfc2731 PI pseudo-attribute <a href="#rfc.iref.s.6">3.3</a></li><li>symrefs PI pseudo-attribute <a href="#rfc.iref.s.2">3.1</a></li></ul></li><li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul><li>toc PI pseudo-attribute <a href="#rfc.iref.t.1">3.1</a></li><li>tocdepth PI pseudo-attribute <a href="#rfc.iref.t.2">3.1</a></li><li>tocindent PI pseudo-attribute <a href="#rfc.iref.t.4">3.2</a></li><li>tocompact PI pseudo-attribute <a href="#rfc.iref.t.5">3.2</a></li><li>topblock PI pseudo-attribute <a href="#rfc.iref.t.3">3.1</a></li></ul></li><li><a id="rfc.index.X" href="#rfc.index.X"><b>X</b></a><ul><li>x Extension Element <a href="#rfc.iref.x.31">A</a></li><li>Xalan <a href="#rfc.iref.x.28">5.1</a></li><li><em>XHTML2</em> <a href="#rfc.xref.XHTML2.1">11.10</a>, <a href="#XHTML2"><b>13</b></a></li><li><em>XML</em> <a href="#XML"><b>13</b></a>, <a href="#rfc.xref.XML.1">C.1</a><ul><li><em>Section 2.8</em> <a href="#rfc.xref.XML.1">C.1</a></li></ul></li><li>xml-stylesheet PI <a href="#rfc.iref.x.30">6</a></li><li>xml2rfc-background parameter <a href="#rfc.iref.x.2">3.1</a></li><li>xml2rfc-comments parameter <a href="#rfc.iref.x.4">3.1</a></li><li>xml2rfc-editing parameter <a href="#rfc.iref.x.3">3.1</a>, <a href="#rfc.iref.x.5">3.1</a></li><li>xml2rfc-ext-allow-markup-in-artwork parameter <a href="#rfc.iref.x.19">3.3</a></li><li>xml2rfc-ext-authors-section parameter <a href="#rfc.iref.x.20">3.3</a></li><li>xml2rfc-ext-duplex <a href="#rfc.iref.x.21">3.3</a></li><li>xml2rfc-ext-include-index parameter <a href="#rfc.iref.x.22">3.3</a></li><li>xml2rfc-ext-include-references-in-index parameter <a href="#rfc.iref.x.23">3.3</a></li><li>xml2rfc-ext-justification parameter <a href="#rfc.iref.x.24">3.3</a></li><li>xml2rfc-ext-parse-xml-in-artwork parameter <a href="#rfc.iref.x.25">3.3</a></li><li>xml2rfc-ext-sec-no-trailing-dots parameter <a href="#rfc.iref.x.27">3.3</a></li><li>xml2rfc-ext-support-rfc2731 parameter <a href="#rfc.iref.x.26">3.3</a></li><li>xml2rfc-footer parameter <a href="#rfc.iref.x.6">3.1</a></li><li>xml2rfc-header parameter <a href="#rfc.iref.x.7">3.1</a></li><li>xml2rfc-inline parameter <a href="#rfc.iref.x.8">3.1</a></li><li>xml2rfc-iprnotified parameter <a href="#rfc.iref.x.9">3.1</a></li><li>xml2rfc-linkmailto parameter <a href="#rfc.iref.x.10">3.1</a></li><li>xml2rfc-private parameter <a href="#rfc.iref.x.11">3.1</a></li><li>xml2rfc-refparent parameter <a href="#rfc.iref.x.12">3.1</a></li><li>xml2rfc-rfcedstyle parameter <a href="#rfc.iref.x.13">3.1</a></li><li>xml2rfc-sortrefs parameter <a href="#rfc.iref.x.14">3.1</a></li><li>xml2rfc-symrefs parameter <a href="#rfc.iref.x.15">3.1</a></li><li>xml2rfc-toc parameter <a href="#rfc.iref.x.16">3.1</a></li><li>xml2rfc-tocdepth parameter <a href="#rfc.iref.x.17">3.1</a></li><li>xml2rfc-topblock parameter <a href="#rfc.iref.x.18">3.1</a></li><li><em>XSL-FO</em> <a href="#rfc.xref.XSL-FO.1">9.1</a>, <a href="#rfc.xref.XSL-FO.2">9.1</a>, <a href="#XSL-FO"><b>13</b></a></li><li>xsltproc <a href="#rfc.iref.x.29">5.1</a><ul><li>passing parameters <a href="#rfc.iref.x.1">3</a></li></ul></li></ul></li></ul></div></body></html>1016 </pre><div class="note" id="rfc.section.C.2.p.3"> <p> <b>Note:</b> the name for the attribute sets may change in the future as more working is done with respect to customizability. In any case, overriding the settings in a separate file will be easier to maintain. Please contact the author if you find yourself trying to override style definitions that currently do not use attribute sets.</p> <p> <b>Note:</b> the CSS style information used in <samp>rfc2629.xslt</samp> can be overriden in a similar (but less granular) way: just overwrite the template called "insertCss". As for XSL-FO, the class names may change in future.</p> </div><hr class="noprint"><h1 id="rfc.section.D" class="np"><a href="#rfc.section.D">D.</a> <a id="boilerplate" href="#boilerplate">Producing the IETF 'Boilerplate'</a></h1><p id="rfc.section.D.p.1">Various attributes of the <samp><rfc></samp> element plus some child elements of <samp><front></samp> affect the automatically generated parts of the front page, such as the tabular information at the beginning, the "Status Of This Memo", and the "Copyright Notice".</p><p id="rfc.section.D.p.2">When submitting an Internet Draft, this "boilerplate" is checked by "Idnits" (<<a href="http://tools.ietf.org/tools/idnits/">http://tools.ietf.org/tools/idnits/</a>>) for compliance with the current Intellectual Property rules, and thus it is important to set the correct values.</p><p id="rfc.section.D.p.3">Furthermore, the RFC Production Center uses RFC2629-based tools to generate the final RFC text, so the more accurate the supplied information is, the less additional work is left, and the risk for errors in producing the final (and immutable!) document is reduced.</p><div class="note" id="rfc.section.D.p.4"> <p> <b>Note:</b> this only applies to the case when IETF documents are produced. The "private" processing instruction <span id="rfc.iref.p.66"></span><span id="rfc.iref.p.67"></span> allows to switch off most of the autogeneration logic.</p> </div><h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a> <a id="attribute-ipr" href="#attribute-ipr">The /rfc/@ipr Attribute</a></h2><p id="rfc.section.D.1.p.1">As of the time of this writing, this attribute value can take a long list of values. As frequently, this is not the result of a grand plan, but simply for historic reasons. Of these values, only a few are currently in use; all others are supported by the various tools for backwards compatibility with old source files.</p><div class="note" id="rfc.section.D.1.p.2"> <p> <b>Note:</b> some variations of the boilerplate are selected based on the document's date; therefore it is important to specify the "year", "month" and "day" attributes of the <samp><date></samp> element when archiving the XML source of an Internet Draft on the day of submission.</p> </div><p id="rfc.section.D.1.p.3"> <em>Disclaimer: THIS ONLY PROVIDES IMPLEMENTATION INFORMATION. IF YOU NEED LEGAL ADVICE, PLEASE CONTACT A LAWYER.</em> For further information, refer to <<a href="http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf">http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf</a>>.</p><p id="rfc.section.D.1.p.4">Finally, for the current "Status Of This Memo" text, the <samp>submissionType</samp> attribute determines whether a statement about "Code Components" is inserted (this is the case for the value "IETF", which also happens to be the default). Other values, such as "independent", suppress this part of the text.</p><h3 id="rfc.section.D.1.1"><a href="#rfc.section.D.1.1">D.1.1</a> <a id="attribute-ipr-current" href="#attribute-ipr-current">Current Values: '*trust200902'</a></h3><p id="rfc.section.D.1.1.p.1">The name for these values refers to the "TLP" ("IETF TRUST Legal Provisions Relating to IETF Documents"), on effect February 15, 2009 (see <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090215.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090215.pdf</a>>). Updates to this document were published on September 12, 2009 (TLP 3.0, <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf</a>>) and on December 28, 2009 (TLP 4.0, <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf</a>>), modifying the license for code components. The actual text is located in Section 6 ("Text To Be Included in IETF Documents") of these documents.</p><p id="rfc.section.D.1.1.p.2">The tools will automatically produce the "right" text depending on the document's date information (see above):</p><div id="rfc.table.u.10"><table class="tt full left" cellpadding="3" cellspacing="0"><thead><tr><th>TLP</th><th>URI</th><th>starting with publication date</th></tr></thead><tbody><tr><td class="left">3.0</td><td class="left"><<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf</a>></td><td class="left">2009-11-01</td></tr><tr><td class="left">4.0</td><td class="left"><<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf</a>></td><td class="left">2010-04-01</td></tr></tbody></table></div><h4 id="rfc.section.D.1.1.1"><a href="#rfc.section.D.1.1.1">D.1.1.1</a> <a id="attribute-ipr-trust200902" href="#attribute-ipr-trust200902">trust200902</a></h4><p id="rfc.section.D.1.1.1.p.1">This should be the default, unless one of the more specific '*trust200902' values is a better fit. It produces the text in Sections 6.a and 6.b of the TLP.</p><h4 id="rfc.section.D.1.1.2"><a href="#rfc.section.D.1.1.2">D.1.1.2</a> <a id="attribute-ipr-noModificationTrust200902" href="#attribute-ipr-noModificationTrust200902">noModificationTrust200902</a></h4><p id="rfc.section.D.1.1.2.p.1">This produces the additional text from Section 6.c.i of the TLP:</p><blockquote id="rfc.section.D.1.1.2.p.2"> <p>This document may not be modified, and derivative works of it may not be created, except to format it for publication as an RFC or to translate it into languages other than English.</p> </blockquote><div class="note" id="rfc.section.D.1.1.2.p.3"> <p> <b>Note:</b> this clause is incompatible with RFCs to be published on the Standards Track.</p> </div><h4 id="rfc.section.D.1.1.3"><a href="#rfc.section.D.1.1.3">D.1.1.3</a> <a id="attribute-ipr-noDerivativesTrust200902" href="#attribute-ipr-noDerivativesTrust200902">noDerivativesTrust200902</a></h4><p id="rfc.section.D.1.1.3.p.1">This produces the additional text from Section 6.c.ii of the TLP:</p><blockquote id="rfc.section.D.1.1.3.p.2"> <p>This document may not be modified, and derivative works of it may not be created, and it may not be published except as an Internet-Draft.</p> </blockquote><div class="note" id="rfc.section.D.1.1.3.p.3"> <p> <b>Note:</b> this clause is incompatible with RFCs to be published on the Standards Track.</p> </div><h4 id="rfc.section.D.1.1.4"><a href="#rfc.section.D.1.1.4">D.1.1.4</a> <a id="attribute-ipr-pre5378Trust200902" href="#attribute-ipr-pre5378Trust200902">pre5378Trust200902</a></h4><p id="rfc.section.D.1.1.4.p.1">This produces the additional text from Section 6.c.iii of the TLP, frequently called the "pre-5378 escape clause":</p><blockquote id="rfc.section.D.1.1.4.p.2"> <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.</p> </blockquote><p id="rfc.section.D.1.1.4.p.3">See Section 4 of <<a href="http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf">http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf</a>> for further information about when to use this value.</p><div class="note" id="rfc.section.D.1.1.4.p.4"> <p> <b>Note:</b> this text appears under "Copyright Notice", unless the document was published before November 2009, in which case it appears under "Status Of This Memo".</p> </div><h3 id="rfc.section.D.1.2"><a href="#rfc.section.D.1.2">D.1.2</a> <a id="attribute-ipr-historic" href="#attribute-ipr-historic">Historic Values</a></h3><h4 id="rfc.section.D.1.2.1"><a href="#rfc.section.D.1.2.1">D.1.2.1</a> <a id="attribute-ipr-200811" href="#attribute-ipr-200811">Historic Values: '*trust200811'</a></h4><p id="rfc.section.D.1.2.1.p.1">The attribute values "<span id="attribute-ipr-trust200811">trust200811</span>", "<span id="attribute-ipr-noModificationTrust200811">noModificationTrust200811</span>" and "<span id="attribute-ipr-noDerivativesTrust200811">noDerivativesTrust200811</span>" are similar to their "trust200902" counterparts, except that they use text specified in <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy_11-10-08.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy_11-10-08.pdf</a>>.</p><h4 id="rfc.section.D.1.2.2"><a href="#rfc.section.D.1.2.2">D.1.2.2</a> <a id="attribute-ipr-3978" href="#attribute-ipr-3978">Historic Values: '*3978'</a></h4><p id="rfc.section.D.1.2.2.p.1">The attribute values "<span id="attribute-ipr-full3978">full3978</span>", "<span id="attribute-ipr-noModification3978">noModification3978</span>" and "<span id="attribute-ipr-noDerivatives3978">noDerivatives3978</span>" are similar to their counterparts above, except that they use text specified in RFC 3978 (March 2005).</p><h4 id="rfc.section.D.1.2.3"><a href="#rfc.section.D.1.2.3">D.1.2.3</a> <a id="attribute-ipr-3667" href="#attribute-ipr-3667">Historic Values: '*3667'</a></h4><p id="rfc.section.D.1.2.3.p.1">The attribute values "<span id="attribute-ipr-full3667">full3667</span>", "<span id="attribute-ipr-noModification3667">noModification3667</span>" and "<span id="attribute-ipr-noDerivatives3667">noDerivatives3667</span>" are similar to their counterparts above, except that they use text specified in RFC 3667 (February 2004).</p><h4 id="rfc.section.D.1.2.4"><a href="#rfc.section.D.1.2.4">D.1.2.4</a> <a id="attribute-ipr-2026" href="#attribute-ipr-2026">Historic Values: '*2026'</a></h4><p id="rfc.section.D.1.2.4.p.1">The attribute values "<span id="attribute-ipr-full2026">full2026</span>" and "<span id="attribute-ipr-noDerivativeWorks2026">noDerivativeWorks2026</span>" are similar to their counterparts above, except that they use text specified in RFC 2026 (October 1996).</p><p id="rfc.section.D.1.2.4.p.2">The special value "<span id="attribute-ipr-none">none</span>" was also used back then, and denied the IETF any rights beyond publication as Internet Draft.</p><h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a> <a id="attribute-category" href="#attribute-category">The /rfc/@category Attribute</a></h2><p id="rfc.section.D.2.p.1">For RFCs, the <samp>category</samp> determines the "maturity level" (see <a href="http://tools.ietf.org/html/rfc2026#section-4">Section 4</a> of <a href="#RFC2026" id="rfc.xref.RFC2026.2"><cite title="The Internet Standards Process -- Revision 3">[RFC2026]</cite></a>). The allowed values are "std" for "Standards Track", "bcp" for "BCP", "info" for "Informational", "exp" for "Experimental", and "historic" for - surprise - "Historic".</p><p id="rfc.section.D.2.p.2">For Internet Drafts, the category attribute is not needed, but <em>will</em> appear on the front page ("Intended Status"). Supplying this information can be useful, because reviewers may want to know.</p><div class="note" id="rfc.section.D.2.p.3"> <p> <b>Note:</b> the Standards Track consists of "Proposed Standard", "Draft Standards", and "Internet Standard". These do not appear in the boilerplate, thus the category attribute doesn't handle them. However, this information can be useful for validity checkers, and thus <samp>rfc2629.xslt</samp> supports an extension attribute for that purpose (see <a href="#ext-rfc2629.rfc" title="Extensions to Xml2rfc <rfc> element">Section 11.26</a> for details).</p> </div><h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a> <a id="attribute-submissiontype" href="#attribute-submissiontype">The /rfc/@submissionType Attribute</a></h2><p id="rfc.section.D.3.p.1">The RFC Editor publishes documents from different "document streams", of which the "IETF stream" of course is the most prominent one. Other streams are the "independent stream" (used for things like administrative information or April 1st RFCs), the "IAB stream" (Internet Architecture Board) and the "IRTF stream" (Internet Research Task Force).</p><p id="rfc.section.D.3.p.2">Not surprisingly, the values for the attribute are "IETF" (the default value), "independent", "IAB", and "IRTF".</p><p id="rfc.section.D.3.p.3">Historically, this did not affect the final appearance of RFCs, except for subtle differences in Copyright notices. Nowadays (as of <a href="#RFC5741" id="rfc.xref.RFC5741.1"><cite title="RFC Streams, Headers, and Boilerplates">[RFC5741]</cite></a>), the stream name appears in the first line of the front page, and it also affects the text in the "Status Of This Memo" section.</p><p id="rfc.section.D.3.p.4">For current documents, setting <samp>submissionType</samp> attribute will have the following effect: </p><ul><li>For RFCs, the stream name appears in the upper left corner of the first page (in Internet Drafts, this is either "Network Working Group", or the value of the <samp><workgroup></samp> element).</li><li>For RFCs, if affects the whole "Status Of This Memo" section (see <a href="http://tools.ietf.org/html/rfc5741#section-3.2.2">Section 3.2.2</a> of <a href="#RFC5741" id="rfc.xref.RFC5741.2"><cite title="RFC Streams, Headers, and Boilerplates">[RFC5741]</cite></a>).</li><li>For all RFCs and Internet Drafts, it determines whether the "Copyright Notice" mentions the Copyright on Code Components (see TLP, Section "Text To Be Included in IETF Documents").</li></ul><h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a> <a id="attribute-consensus" href="#attribute-consensus">The /rfc/@consensus Attribute</a></h2><p id="rfc.section.D.4.p.1">For some of the publication streams (see <a href="#attribute-submissiontype" title="The /rfc/@submissionType Attribute">Appendix D.3</a>), the "Status Of This Memo" section depends on whether there was a consensus to publish (again, see <a href="http://tools.ietf.org/html/rfc5741#section-3.2.2">Section 3.2.2</a> of <a href="#RFC5741" id="rfc.xref.RFC5741.3"><cite title="RFC Streams, Headers, and Boilerplates">[RFC5741]</cite></a>).</p><p id="rfc.section.D.4.p.2">The <samp>consensus</samp> attribute ("yes"/"no", defaulting to "yes") can be used to supply this information. The effect for the various streams is: </p><ul><li>"independent" and "IAB": none.</li><li>"IETF": mention that there was an IETF consensus.</li><li>"IRTF": mention that there was a research group consensus (where the name of the research group is extracted from the <samp><workgroup></samp> element).</li></ul><h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a> <a id="attribute-number" href="#attribute-number">The /rfc/@number Attribute</a></h2><p id="rfc.section.D.5.p.1">For RFCs, this attribute supplies the RFC number.</p><h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a> <a id="attribute-docname" href="#attribute-docname">The /rfc/@docName Attribute</a></h2><p id="rfc.section.D.6.p.1">For Internet Drafts, this specifies the draft name (which appears below the title). The file extension is <em>not</em> part of the draft, so in general it should end with the current draft number ("-", plus two digits).</p><div class="note" id="rfc.section.D.6.p.2"> <p> <b>Note:</b> "Idnits" (<<a href="http://tools.ietf.org/tools/idnits/">http://tools.ietf.org/tools/idnits/</a>>) checks the in-document draft name for consistency with the filename of the submitted document.</p> </div><h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a> <a id="attribute-obsoletes" href="#attribute-obsoletes">The /rfc/@obsoletes Attribute</a></h2><p id="rfc.section.D.7.p.1">The RFC Editor maintains a database (<<a href="http://www.rfc-editor.org/rfc.html">http://www.rfc-editor.org/rfc.html</a>>) of all RFCs, including information about which one obsoletes which. Upon publication of an RFC, this database is updated from the data on the front page.</p><p id="rfc.section.D.7.p.2">This attribute takes a list of comma-separated RFC <em>numbers</em>. Do <em>not</em> put the string "RFC" here.</p><h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a> <a id="attribute-updates" href="#attribute-updates">The /rfc/@updates Attribute</a></h2><p id="rfc.section.D.8.p.1">This is like <samp>obsoletes</samp>, but for the "updates" relation.</p><hr class="noprint"><h1 id="rfc.section.E" class="np"><a href="#rfc.section.E">E.</a> <a id="license" href="#license">License</a></h1><p id="rfc.section.E.p.1">Copyright (c) 2006-2010, Julian Reschke (julian.reschke@greenbytes.de)</p><p id="rfc.section.E.p.2">All rights reserved.</p><p id="rfc.section.E.p.3">Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: </p><ul><li>Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.</li><li>Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.</li><li>Neither the name of Julian Reschke nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.</li></ul><p id="rfc.section.E.p.4">THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</p><hr class="noprint"><h1 id="rfc.section.F" class="np"><a href="#rfc.section.F">F.</a> Change Logs</h1><h2 id="rfc.section.F.1"><a href="#rfc.section.F.1">F.1</a> Package</h2><dl><dt>2006-01-01</dt><dd>Switch to BSD License.</dd><dt>2007-01-12</dt><dd>Update to xml2rfc v1.33pre2.</dd><dt>2007-03-31</dt><dd>Update to xml2rfc v1.33pre3.</dd><dt>2007-05-01</dt><dd>Add XSLT test cases.</dd><dt>2008-07-18</dt><dd>Experimental support for inlined rdf:Description elements (ignored by the formatter, extracted by rfc2629grddl).</dd><dt>2008-12-04</dt><dd>Update to xml2rfc v1.34pre2.</dd><dt>2009-02-24</dt><dd>Experimental support for February 2009 boilerplate changes, and for the x:boilerplate element.</dd><dt>2009-07-08</dt><dd>Support new boilerplate ordering in RFCs published since July 2009. Fix problems with one-column text tables.</dd><dt>2009-07-19</dt><dd>When possible, calculate the actual Expiry date for Internet Drafts (full date must be available).</dd><dt>2009-08-01</dt><dd>For '$xml2rfc-ext-authors-section='end'", move the index in front of the authors section.</dd><dt>2009-08-04</dt><dd>Consider /rfc/@ipr="pre5378Trust200902" when producing RFCs, not IDs.</dd><dt>2009-08-29</dt><dd>Support alignment for artwork containing images (as opposed to, well, artwork).</dd><dt>2009-09-01</dt><dd>Allow xref in cref (as extension).</dd><dt>2009-09-14</dt><dd>Refactor handling of processing instructions.</dd><dt>2009-09-24</dt><dd>Fix typo in Status Of This Memo, present since November 2008. Fix formatting of iprExtract attribute. Starting with Internet Draft publication dates after 2009-11-30: use new Trust Legal Provisions text; for Internet Drafts: move Abstract up, and move "pre5378" escape clause to the Copyright Notice. Add support for refparent PI. For RFCs: use new TLP text as of September 2009. Incorporate xml2rfc v1.34pre4.</dd><dt>2009-10-06</dt><dd>Starting with Internet Draft publication dates after 2009-10-31: use new Trust Legal Provisions text; for Internet Drafts: move Abstract up, and move "pre5378" escape clause to the Copyright Notice. Incorporate xml2rfc v1.34pre5.</dd><dt>2009-10-27</dt><dd>Upgrade to xml2rfc v1.34.</dd><dt>2010-01-08</dt><dd>For RFC generation (not IDs), experimentally support RFC 5741 headers and boilerplate and Trust Legal Provisions 4.0.</dd><dt>2010-03-31</dt><dd>Upgrade to xml2rfc v1.35.</dd><dt>2010-06-27</dt><dd>Be consistent with xml2rfc.tcl in formatting initials (truncate after the first); see <<a href="http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10">http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10</a>>.</dd><dt>2010-08-31</dt><dd>Experimental support for prose in references.</dd><dt>2011-01-27</dt><dd>Update to xml2rfc v1.36pre1.</dd><dt>2011-04-17</dt><dd>Update to xml2rfc v1.36. Add support for more /rfc/@ipr values when producing RFCs.</dd></dl><h2 id="rfc.section.F.2"><a href="#rfc.section.F.2">F.2</a> amazon-asin.xslt</h2><dl><dt>2003-11-16</dt><dd>Initial release.</dd><dt>2005-04-02</dt><dd>Fix two DTD issues.</dd></dl><h2 id="rfc.section.F.3"><a href="#rfc.section.F.3">F.3</a> check-references.xslt</h2><dl><dt>2003-11-16</dt><dd>Initial release.</dd><dt>2004-05-11</dt><dd>Add document status; print references type.</dd><dt>2005-01-01</dt><dd>Add experimental check for ID status.</dd><dt>2005-04-01</dt><dd>Add fixes from Bill Fenner.</dd><dt>2005-12-03</dt><dd>Add checks against local copy of <<a href="http://www.w3.org/2002/01/tr-automation/tr.rdf">http://www.w3.org/2002/01/tr-automation/tr.rdf</a>>.</dd><dt>2006-07-22</dt><dd>Add checks for standards levels.</dd><dt>2006-08-06</dt><dd>"check-ietf-references.xslt" replaced by "check-references.xslt".</dd><dt>2007-01-04</dt><dd>Use information online at <<a href="http://tools.ietf.org/">http://tools.ietf.org/</a>> to retrieve Internet-Draft status information.</dd><dt>2007-06-16</dt><dd>Fix bug looking up ref type when inside change markup.</dd><dt>2008-06-14</dt><dd>Enhance output when draft was updated, and then published as RFC.</dd><dt>2008-07-12</dt><dd>Add XSLT2-based link target checking.</dd><dt>2008-08-10</dt><dd>Change keywords for "intended-level" to proposed/draft/internet, optionally extract intended level from /rfc/@x:maturity-level attribute.</dd></dl><h2 id="rfc.section.F.4"><a href="#rfc.section.F.4">F.4</a> gen-reference-graph.xslt</h2><dl><dt>2006-09-03</dt><dd>New.</dd><dt>2007-06-07</dt><dd>Use <a href="http://dpcarlisle.blogspot.com/2007/05/exslt-node-set-function.html">Carlisle method</a> to define exslt:node-set in msxsml (which means that the stylesheet can now be used with MSXML as well).</dd><dt>2007-10-15</dt><dd>Use W3C data from tr.rdf as well (experimental).</dd></dl><h2 id="rfc.section.F.5"><a href="#rfc.section.F.5">F.5</a> rfc2629.xslt</h2><dl><dt>2001-03-28</dt><dd>Code rearranged, generate numbered section anchors for paragraphs (t) as well. Fixes in index handling.</dd><dt>2001-04-12</dt><dd>Moved HTML output into XHTML namespace.</dd><dt>2001-10-02</dt><dd>Fixed default location for RFCs and numbering of section references. Support ?rfc editing processing instruction.</dd><dt>2001-10-07</dt><dd>Made telephone number links active.</dd><dt>2001-10-08</dt><dd>Support for vspace element.</dd><dt>2001-10-09</dt><dd>Experimental support for rfc-issue PI.</dd><dt>2001-11-11</dt><dd>Support rfc private PI. Removed bogus code reporting the WG in the header.</dd><dt>2001-11-11</dt><dd>Support rfc private PI. Removed bogus code reporting the WG in the header.</dd><dt>2001-12-17</dt><dd>Support title attribute on references element</dd><dt>2002-01-05</dt><dd>Support for list/@style="@format"</dd><dt>2002-01-09</dt><dd>Display "closed" RFC issues as deleted</dd><dt>2002-01-14</dt><dd>Experimentally and optionally parse XML encountered in artwork elements (requires MSXSL).</dd><dt>2002-01-27</dt><dd>Some cleanup. Moved RFC issues from PIs into namespaced elements.</dd><dt>2002-01-29</dt><dd>Added support for sortrefs PI. Added support for figure names.</dd><dt>2002-02-07</dt><dd>Highlight parts of artwork which are too wide (72 characters).</dd><dt>2002-02-12</dt><dd>Code rearrangement for static texts. Fixes for section numbering. TOC generation rewritten.</dd><dt>2002-02-15</dt><dd>Support for irefs in sections; support iref @primary=true</dd><dt>2002-03-03</dt><dd>Moved anchor prefix into a constant. Added sanity checks on user anchor names.</dd><dt>2002-03-23</dt><dd>Bugfix in detection of matching org names when creating the header. Fixed sorting in subitems.</dd><dt>2002-04-02</dt><dd>Fix TOC link HTML generation when no TOC is generated (created broken HTML table code).</dd><dt>2002-04-03</dt><dd>Made rendering of references more tolerant re: missing parts.</dd><dt>2002-04-08</dt><dd>Fixed reference numbering when references are split into separate sections.</dd><dt>2002-04-16</dt><dd>Fix default namespace (shouldn't be set for HTML output method).</dd><dt>2002-04-19</dt><dd>Lowercase internal CSS selectors for Mozilla compliance. Do not put TOC into ul element.</dd><dt>2002-04-21</dt><dd>Make numbered list inside numbered lists use alphanumeric numbering.</dd><dt>2002-05-05</dt><dd>Updated issue/editing support.</dd><dt>2002-05-15</dt><dd>Bugfix for section numbering after introduction of ed:replace</dd><dt>2002-06-21</dt><dd>When producing private documents, do not include document status, copyright etc.</dd><dt>2002-07-08</dt><dd>Fix xrefs to Appendices.</dd><dt>2002-07-19</dt><dd>Make artwork lightyellow for easier reading. (fielding)</dd><dt>2002-10-09</dt><dd>Translate references title to anchor name to avoid non-uri characters. (fielding)</dd><dt>2002-10-13</dt><dd>Support for tocdepth PI.</dd><dt>2002-11-03</dt><dd>Added temporariry workaround for Mozilla/Transformiix result tree fragment problem. (search for 'http://bugzilla.mozilla.org/show_bug.cgi?id=143668')</dd><dt>2002-12-25</dt><dd>xref code: attempt to uppercase "section" and "appendix" when at the start of a sentence.</dd><dt>2003-02-02</dt><dd>fixed code for vspace blankLines="0", enhanced display for list with "format" style, got rid of HTML blockquote elements, added support for "hangIndent"</dd><dt>2003-04-10</dt><dd>experimental support for appendix and spanx elements</dd><dt>2003-04-19</dt><dd>fixed counting of list numbers in "format %" styles (one counter per unique format string). Added more spanx styles.</dd><dt>2003-05-02</dt><dd>experimental texttable support</dd><dt>2003-05-02</dt><dd>Make mailto links optional (default = none) (jre: default and PI name changed) (fielding)</dd><dt>2003-05-04</dt><dd>experimental support for HTML link elements; fix default for table header alignment default</dd><dt>2003-05-06</dt><dd>support for "background" PI.</dd><dt>2003-05-11</dt><dd>change %c format to lowercase alphabetic. add support for keyword elements (generate META tag). fix various HTML conformance problems. added experimental support for role attribute. do not number paragraphs in unnumbered sections. update boilerplate texts. support for "iprnotified" PI. bugfix list numbering. strip whitespace when building tel: URIs.</dd><dt>2003-05-12</dt><dd>more conformance fixes (layout moved into CSS, move lists and figures out of para content, do not use tables for list formatting)</dd><dt>2003-05-13</dt><dd>add DC.Creator meta tag, refactoring</dd><dt>2003-05-16</dt><dd>put nbsps between "section" and section number (xref).</dd><dt>2003-05-18</dt><dd>author summary: add missing comma.</dd><dt>2003-06-06</dt><dd>fix index generation bug (transposed characters in key generation). Enhance sentence start detection (xref starting a section was using lowercase "section").</dd><dt>2003-06-22</dt><dd>exp. support for xref/@format. Add missing support for eref w/o content. exp. support for annotations in reference elements. Code cleanup reference table formatting.</dd><dt>2003-07-09</dt><dd>Another fix for DC.Creator meta tag creation based on RFC2731</dd><dt>2003-07-24</dt><dd>Fix namespace name for DC.Creator.</dd><dt>2003-08-06</dt><dd>Cleanup node-set support (only use exslt (saxon, xalan, libxslt) extension functions; remove Transformix workarounds that stopped to work in Moz 1.4)</dd><dt>2003-08-09</dt><dd>Generate HTML lang tag.</dd><dt>2003-08-10</dt><dd>Map spanx/verb to HTML "samp" element. Fix author name display in references (reverse surname/initials for last author), add "Ed.". Fix internal bookmark generation.</dd><dt>2003-08-17</dt><dd>Add DCMI dates, identifiers and abstract. Add PI to suppress DCMI generation. Do not add TOC entry to Copyright Statement when there is none. Align RFC2629 PI names and parameter names. Change style for inline URIs generated by eref. Add header and footer support. Enhance CSS paging properties. Support topblock PI. Added hooks for proper XHTML generation through separate XSLT. Enhance warning and error messages. Add support for artwork image display. Table formatting fixes (borders, thead continuation).</dd><dt>2003-08-18</dt><dd>Add workaround for MSXML4 node-set and Mozilla node-set issues (fallback just displays are warning).</dd><dt>2003-10-06</dt><dd>Add workaround for broken pre/ins handling in Mozilla (see <<a href="http://bugzilla.mozilla.org/show_bug.cgi?id=204401">http://bugzilla.mozilla.org/show_bug.cgi?id=204401</a>>). Make use of cite attribute on ed:replace. CSS cleanup.</dd><dt>2003-10-08</dt><dd>Fix minor issue detecting the same org for the header (caused by IE's non-standard whitespace handling). Fix default handling for /rfc/@category.</dd><dt>2003-11-09</dt><dd>Inherit ed:entered-by from ancestor elements. Change CSS color for inserted text to green. Generate issues-list anchor. Do not complain about missing targets when the xref element is below ed:del. Remove code that attempted to distinguish section/Section when producing links - always use uppercase. Fix date rendering for issue resolutions.</dd><dt>2003-11-29</dt><dd>Fix color values for table backgrounds for issue rendering. Change rendering of issue links to use inline-styles. Add colored issue markers to issues.</dd><dt>2003-12-13</dt><dd>Fix inheritance of ed:entered-by attribute. Display note elements inside change tracking as well.</dd><dt>2004-01-18</dt><dd>When PI compact = 'yes', make most CSS print page breaks conditional.</dd><dt>2004-02-20</dt><dd>Support for RFC3667 IPR changes (xml2rfc 1.22); see <<a href="http://lists.xml.resource.org/pipermail/xml2rfc/2004-February/001088.html">http://lists.xml.resource.org/pipermail/xml2rfc/2004-February/001088.html</a>>.</dd><dt>2004-03-11</dt><dd>Add "(if approved)" to "updates" and "obsoletes" unless the document has an RFC number.</dd><dt>2004-04-01</dt><dd>Fix RFC3667 output, see <<a href="http://lists.xml.resource.org/pipermail/xml2rfc/2004-April/001208.html">http://lists.xml.resource.org/pipermail/xml2rfc/2004-April/001208.html</a>>.</dd><dt>2004-04-04</dt><dd>Add support for section/top attribute. Move references into plain section container.</dd><dt>2004-04-06</dt><dd>Do not emit identical para anchors for deleted content.</dd><dt>2004-04-14</dt><dd>Fix references TOC generation when there are no references.</dd><dt>2004-04-24</dt><dd>Fix RFC3667 output, see <<a href="http://xml.resource.org/pipermail/xml2rfc/2004-April/001246.html">http://xml.resource.org/pipermail/xml2rfc/2004-April/001246.html</a>>.</dd><dt>2004-05-09</dt><dd>Add custom support for generating compound index documents. Add anchors for each Index letter. Add experimental cref support. Fix conditional page breaks before References section.</dd><dt>2004-05-16</dt><dd>Refactor external index generation.</dd><dt>2004-05-20</dt><dd>Rewrite anchor generation for comments.</dd><dt>2004-05-22</dt><dd>Enhance issues rendering (add links to changes).</dd><dt>2004-05-30</dt><dd>Allow single quote as delimiter in processing instructions as well. Move block-level issue pointers to floats. Disable issue pointers for print media. Add "purple numbers". Add hrefs to section headings. Add non-printing index key letter list to start of index.</dd><dt>2004-06-01</dt><dd>Use &#xb6; instead of # for PNs.</dd><dt>2004-07-18</dt><dd>Add support for list style=letters (thanks Roy F.). Make PNs optional; add new PI.</dd><dt>2004-09-05</dt><dd>Fix index links into unnumbered sections. Bring IPR boilerplate in-line with xml2rfc 1.25. Add experimental CSS3 paged media support. Various HTML fixes.</dd><dt>2004-09-21</dt><dd>Enhance checking of artwork width.</dd><dt>2004-09-26</dt><dd>Add check for unused references. Uppercase letters in list style letters when nested into another list.</dd><dt>2004-10-10</dt><dd>Fix internal change track pointers.</dd><dt>2004-11-01</dt><dd>Allow change tracking on references (as a whole). Rewrite artwork handling so that it allows change tracking inside artwork. Also allow a subset of text markup inside artwork, such as xrefs (note this requires post-processing the source to make it compliant to RFC2629bis).</dd><dt>2004-11-03</dt><dd>Enhanced placement of iref anchors.</dd><dt>2004-11-06</dt><dd>Index: display irefs that appeared (with primary=true) inside artwork elements in a monospaced font.</dd><dt>2004-11-14</dt><dd>Add special code so that changes in section titles can be change-tracked.</dd><dt>2005-01-14</dt><dd>Bugfixes for HtmlToXhtml converter.</dd><dt>2005-01-22</dt><dd>Enhance generation of HTML h* elements (for Mozilla Outliner).</dd><dt>2005-01-31</dt><dd>Put vertical space around top-level TOC entries in TOC. Switch to pt-based CSS. Re-arrange top section. Make hr elements reflect new-page settings in TXT output (compact-PI). Fix page number in footer (CSS print) and add some more experimental support for paged media (tested with Prince 4.1 alpha). Rewrite TOC and Index generation to generate HTML lists. Cleanup id generation for paragraphs. Reduce whitespace in output. Fix vspace implementation. Use right/left dqoutes and copyright sign where appropriate.</dd><dt>2005-02-04</dt><dd>Add <link> element to references section. Fix newly introduced bug in references processing.</dd><dt>2005-02-05</dt><dd>Integrate various fixes/enhancements by Roy Fielding: spelling of "Authors' Addresses", comma setting in references, position of "Authors" section, optionally place authors addresses at end (PI), trailing dots in section numbers, switch to verdana default font in CSS. Add experimental support for centered artwork.</dd><dt>2005-02-09</dt><dd>Fixes in spacing and links of references section titles. Enhance sorting in references when change tracking is in place. Re-add figure centering support. Add missing 2nd part of "Author's Adresses" fix.</dd><dt>2005-02-25</dt><dd>Align section number format with xml2rfc1.29.</dd><dt>2005-03-28</dt><dd>Get rid of table elements in Author's section. Add experimental hCard (<<a href="http://developers.technorati.com/wiki/hCard">http://developers.technorati.com/wiki/hCard</a>>) support.</dd><dt>2005-04-03</dt><dd>Add RFC3978-style IPR statement support. (fenner@research.att.com)</dd><dt>2005-04-11</dt><dd>Cleanup author display. hCard related fixes.</dd><dt>2005-05-07</dt><dd>Minor fixes to allow change tracking in doc title. Add experimental support for table border styles. CSS cleanup.</dd><dt>2005-06-18</dt><dd>Implement missing support for references to texttables.</dd><dt>2005-09-25</dt><dd>Use (-moz-)column-count when printing the index.</dd><dt>2005-10-04</dt><dd>Report missing element templates with xsl:message.</dd><dt>2005-10-15</dt><dd>Process t/@anchor.</dd><dt>2005-10-23</dt><dd>More workarounds for Mozilla's broken del/ins handling (this time for figures).</dd><dt>2005-10-27</dt><dd>lowercase hCard class names</dd><dt>2005-11-22</dt><dd>Enhance diagnostics for XML-in-artwork extension</dd><dt>2005-11-26</dt><dd>Fix formatting of section numbers for sections inserted into <back>.</dd><dt>2005-12-12</dt><dd>Fix some validity problems when change tracking occured inside lists.</dd><dt>2005-12-18</dt><dd>Add change tracking inside the index.</dd><dt>2006-02-04</dt><dd>Add prev/next links to highlighted changes (change tracking extension).</dd><dt>2006-02-10</dt><dd>Catch errors instantiating MSXML component.</dd><dt>2006-02-11</dt><dd>References: add "work in progress" for Internet Drafts.</dd><dt>2006-02-27</dt><dd>Fix front matter (lowercase Internet-Draft, say "Intended status" for non-RFC documents). Start work on experimental extension for simplified internal links.</dd><dt>2006-03-19</dt><dd>Tweaks to IESG Copyright stuff; support submissionType attribute. Fix duplicate reference anchors in HTML output. Reduce HTML Tidy warnings. Fix reference to normative ASCII version (now requires trailing ".txt"). Tweaks to hCard generation. Started to move non-issue-tracking extensions into namespace "http://purl.org/net/xml2rfc/ext".</dd><dt>2006-03-27</dt><dd>Moved "simple reference" extension into namespace "http://purl.org/net/xml2rfc/ext" and add documentation. HTML conformance enhancements.</dd><dt>2006-04-02</dt><dd>Cleanup special code for automated XHTML XSLT generation.</dd><dt>2006-04-21</dt><dd>Generate <CITE> elements where appropiate. Introduce x:blockquote, x:dfn, x:h and x:q elements.</dd><dt>2006-05-06</dt><dd>Introduce x:bcp14 element.</dd><dt>2006-05-14</dt><dd>Fix content model for x:blockquote.</dd><dt>2006-06-18</dt><dd>Add box drawing support (x:bt, x:bc, x:bb).</dd><dt>2006-06-20</dt><dd>HTML validity fixes (legal chars in anchors in index).</dd><dt>2006-06-24</dt><dd>Reduce leading empty lines in artwork. Move <dt> style info into CSS.</dd><dt>2006-07-14</dt><dd>Fix rendering of multiple street address entries (missing line break).</dd><dt>2006-07-24</dt><dd>Add extension for deep linking into RFCs, do not generate empty list items in TOC output, avoid empty <dt> elements for list items without hangText attribute.</dd><dt>2006-08-01</dt><dd>Allow @anchor on more elements; start work on Relax NG grammar for extensions. Reduce generated style elements (use CSS classes instead). Consistently use "id" instead of "name". Change default target for RFC links to "http://tools.ietf.org/html/rfcNNNN".</dd><dt>2006-08-06</dt><dd>Include appendices defined in <appendix> elements in TOC (please consider them deprecated anyhow!). Generate links to "http://tools.ietf.org/html/draft-*" for Internet Drafts. Replace x:frag by x:rel, allowing any kind of relative reference instead of just fragments.</dd><dt>2006-08-30</dt><dd>Reduce textual differences between HTML output and what xml2rfc produces in TXT output mode (section refs/reference targets). Add small workaround for Opera 9.0.1's problem with node-set().</dd><dt>2006-10-29</dt><dd>Fix problem generating internal links to change markup within references section. Enhancements when generating numbered references for deleted references. Allow inclusion of references into the index (through include-references-in-index extension). Fix a bug that caused the newer version of the IETF boilerplate to be produced rather than the pre-RFC3667 one. Update to RFC4287 boilerplate.</dd><dt>2006-11-11</dt><dd>Add extension attribute x:for-anchor to <iref> handling.</dd><dt>2006-11-26</dt><dd>Experimental (and limited) support for <x:lt>.</dd><dt>2006-12-04</dt><dd>Fix bugs in processing documents that have both the ipr and the number attribute set on the rfc root element. Add support for x:fmt='none' on xrefs. Add different pre style based on artwork type attributes (experimental).</dd><dt>2006-12-13</dt><dd>Add x:fmt='anchor' for xref elements.</dd><dt>2007-01-07</dt><dd>Fix root template for compatibility for the exslt:node-set implementation in Firefox3.</dd><dt>2007-01-29</dt><dd>Avoid empty table entry in front matter when organization is not specified for an author.</dd><dt>2007-02-10</dt><dd>Allow change tracking in table rows.</dd><dt>2007-03-09</dt><dd>Add hcard profile URI (<<a href="http://www.w3.org/2006/03/hcard">http://www.w3.org/2006/03/hcard</a>>) to head element. Add warning for misplaced <t> elements (after section).</dd><dt>2007-03-21</dt><dd>Fix internal linking from reference entries in index for some xref types. Minor CSS tweaks contributed by MTR. Allow turning on text justification through a PI. Improve iref anchor generation to generate less instable anchors.</dd><dt>2007-03-28</dt><dd>Fixes for numbering of ed:inserted references sections.</dd><dt>2007-05-04</dt><dd>Do not generate anchors for edits in deleted sections. Enhance HTML conformance.</dd><dt>2007-05-19</dt><dd>Enhance diagnostics when using Saxon (needs Saxon's "-l" command line parameter to keep line number information). Add warning when symref PI is missing (default will change in the future). Add support for overriding computed section numbers (when formatting historic documents).</dd><dt>2007-06-07</dt><dd>Change default for symrefs PI to "yes" (see change in xml2rfc 1.33pre4). Warn about docName attributes that appear to contain a file extension.</dd><dt>2007-06-26</dt><dd>Workaround author/@initials values without trailing dot, as in xml2rfc.tcl.</dd><dt>2007-07-14</dt><dd>Enhance index generation for references that use @x:sec attribute.</dd><dt>2007-09-09</dt><dd>Fix: sortrefs is a nop when symrefs=no.</dd><dt>2007-10-17</dt><dd>Work in progress: add support for referencing sections in sibling documents by anchor name.</dd><dt>2007-10-17</dt><dd>Work in progress (continued): support for referencing sections in sibling documents by anchor name.</dd><dt>2007-12-31</dt><dd>Emit warning when updating/obsoleting stuff that's not referenced.</dd><dt>2008-02-03</dt><dd>Support xml2rfc-1.33pre5's suppress-title attribute on texttable and figure.</dd><dt>2008-02-06</dt><dd>Extension: allow <eref> below <cref>.</dd><dt>2008-02-17</dt><dd>Extensions: add x:span and x:length-of.</dd><dt>2008-02-20</dt><dd>Add new RFC boilerplate (as changed in 2007-08).</dd><dt>2008-02-27</dt><dd>Improve diagnostics for artwork width problems; add defaulting of publication dates (requires XSLT processor supporting exslt:date, or msxml).</dd><dt>2008-02-29</dt><dd>Enhance CSS for link elements in the front header, update rules for generating "Acknowledgment" statement.</dd><dt>2008-03-01</dt><dd>Use line numbers in diagnostics in Saxon8/9 as well.</dd><dt>2008-03-02</dt><dd>Fix a bug in the logic choosing the boilerplate, resulting in obsolete text being inserted into IDs.</dd><dt>2008-04-01</dt><dd>Add support for superscript element.</dd><dt>2008-06-28</dt><dd>Add sanity checks for email addresses, allow multiple email elements.</dd><dt>2008-07-06</dt><dd>Add x:abnf-char-sequence.</dd><dt>2008-08-21</dt><dd>Add x:note.</dd><dt>2008-09-06</dt><dd>Add experimental support for SVG images.</dd><dt>2008-09-17</dt><dd>Add experimental support for x:author. Fix xref/@format=none.</dd><dt>2008-10-10</dt><dd>Fix a huge bug, causing text content after an XML comment to be ignored.</dd><dt>2009-02-24</dt><dd>Use table/caption when needed.</dd><dt>2009-03-07</dt><dd>Fix bug that caused text to disappear in the output in presence of processing instructions.</dd><dt>2009-03-12</dt><dd>Make inlined comments bookmarkable.</dd><dt>2009-04-09</dt><dd>Upgrade to DC-HTML from RFC 2731 (affects head/@profile).</dd><dt>2009-07-08</dt><dd>Remove table/@summary in output; the value getting inserted was just repeating stuff that appeared in the preamble.</dd><dt>2009-08-01</dt><dd>Implement table alignment (HTML output only for now).</dd><dt>2009-08-18</dt><dd>Replicate Dublin Core "abstract" metadata into meta/@name=description (search engines do use it).</dd><dt>2009-09-02</dt><dd>Fix default/left alignment of table columns, remove silly table summmary attributes.</dd><dt>2009-09-24</dt><dd>Support double-sided layout using CSS page:left/right selectors.</dd><dt>2009-11-27</dt><dd>Generate unordered lists instead of broken definition lists for list style empty.</dd></dl><h2 id="rfc.section.F.6"><a href="#rfc.section.F.6">F.6</a> rfc2629toFO.xslt</h2><dl><dt>2003-11-16</dt><dd>Initial release.</dd><dt>2003-11-29</dt><dd>Enhance handling of unknown list styles.</dd><dt>2004-04-04</dt><dd>Update reference section handling.</dd><dt>2004-04-17</dt><dd>Use XSL-WD-1.1-style fo:bookmark and index handling and add postprocessors for existing implementations. Unify PDF info generation by using XEP (postprocessors) will convert.</dd><dt>2004-04-20</dt><dd>Add experimental cref support.</dd><dt>2004-06-14</dt><dd>Set correct index-item defaults.</dd><dt>2004-07-18</dt><dd>Add list style=letters.</dd><dt>2004-09-03</dt><dd>Make URLs in text break where they are allowed to break by inserting zero-width spaces.</dd><dt>2004-09-26</dt><dd>Fix letter-style inside nested lists.</dd><dt>2004-10-31</dt><dd>Update handling of artwork.</dd><dt>2004-11-13</dt><dd>Fix handling of references inside ed:* markup. Fix whitespace handling in artwork.</dd><dt>2004-11-27</dt><dd>Irefs in artwork generate monospaced entries in index.</dd><dt>2005-01-31</dt><dd>Fix TOC generation that was broken after changes in main XSLT.</dd><dt>2005-02-05</dt><dd>Bring in sync with cosmetic changes in rfc2629.xslt.</dd><dt>2005-05-07</dt><dd>Minor fix for change tracking in document title. Support for table styles.</dd><dt>2005-06-18</dt><dd>Fix references to tables.</dd><dt>2005-10-15</dt><dd>Process t/@anchor.</dd><dt>2006-02-11</dt><dd>References: add "work in progress" for Internet Drafts.</dd><dt>2006-06-02</dt><dd>Use XSL 1.1 WD Feb 2006.</dd><dt>2007-03-21</dt><dd>Support optional text justification.</dd><dt>2007-05-19</dt><dd>Various improvements in spacing; also allow overriding the automatic list indentation via list/x:indent.</dd><dt>2009-04-08</dt><dd>Fix spacing in headers; add support for formatting for double-sided printing.</dd><dt>2009-08-01</dt><dd>Remove surplus empty pages when not generating double-sided output.</dd></dl><h2 id="rfc.section.F.7"><a href="#rfc.section.F.7">F.7</a> xsl11toAn.xslt</h2><dl><dt>2004-05-17</dt><dd>Initial release.</dd><dt>2006-06-02</dt><dd>Use XSL 1.1 WD Feb 2006.</dd></dl><h2 id="rfc.section.F.8"><a href="#rfc.section.F.8">F.8</a> xsl11toFop.xslt</h2><dl><dt>2010-08-25</dt><dd>Switch to Apache FOP 1.0.</dd><dt>2009-09-12</dt><dd>Support for FOP 0.20.5 and FOP 0.93 removed. Please use FOP 0.95.</dd><dt>2008-03-15</dt><dd>Add a workaround to the fo:inline workaround (sigh).</dd></dl><h2 id="rfc.section.F.9"><a href="#rfc.section.F.9">F.9</a> xsl11toXep.xslt</h2><dl><dt>2004-05-17</dt><dd>Initial release.</dd><dt>2004-09-04</dt><dd>Fix xep:index-item attributes.</dd><dt>2006-06-02</dt><dd>Use XSL 1.1 WD Feb 2006.</dd></dl><hr class="noprint"><h1 id="rfc.index" class="np"><a href="#rfc.index">Index</a></h1><p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.J">J</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.Q">Q</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.X">X</a> </p><div class="print2col"><ul class="ind"><li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul><li>abnf-char-sequence Extension Element <a href="#rfc.iref.a.27"><b>11.1</b></a>, <a href="#rfc.iref.a.29">A</a></li><li>allow-markup-in-artwork PI pseudo-attribute <a href="#rfc.iref.a.1">3.3</a></li><li>alternate HTML LINK element <a href="#rfc.iref.a.22">6.2</a></li><li>anchor-alias Extension Element <a href="#rfc.iref.a.28"><b>11.2</b></a>, <a href="#rfc.iref.a.30">A</a></li><li>Anchors <ul><li>rfc.abstract <a href="#rfc.iref.a.3">4</a></li><li>rfc.authors <a href="#rfc.iref.a.4">4</a></li><li>rfc.copyright <a href="#rfc.iref.a.5">4</a></li><li>rfc.copyrightnotice <a href="#rfc.iref.a.6">4</a></li><li>rfc.figure.n <a href="#rfc.iref.a.7">4</a>, <a href="#rfc.iref.a.18">4</a></li><li>rfc.figure.u.n <a href="#rfc.iref.a.8">4</a>, <a href="#rfc.iref.a.19">4</a></li><li>rfc.index <a href="#rfc.iref.a.9">4</a></li><li>rfc.ipr <a href="#rfc.iref.a.10">4</a></li><li>rfc.iref.n <a href="#rfc.iref.a.11">4</a></li><li>rfc.note.n <a href="#rfc.iref.a.12">4</a></li><li>rfc.references <a href="#rfc.iref.a.13">4</a>, <a href="#rfc.iref.a.14">4</a></li><li>rfc.section.n <a href="#rfc.iref.a.15">4</a></li><li>rfc.section.n.p.m <a href="#rfc.iref.a.16">4</a></li><li>rfc.status <a href="#rfc.iref.a.17">4</a></li><li>rfc.toc <a href="#rfc.iref.a.20">4</a></li><li>rfc.xref.name.n <a href="#rfc.iref.a.21">4</a></li></ul></li><li>AntennaHouse XSL Formatter <a href="#rfc.iref.a.26">9.1</a></li><li>Apache FOP <a href="#rfc.iref.a.25">9.1</a></li><li>appendix HTML LINK element <a href="#rfc.iref.a.23">6.2</a></li><li>assign-section-number Extension Element <a href="#rfc.iref.a.31">A</a></li><li>author HTML LINK element <a href="#rfc.iref.a.24">6.2</a></li><li>authors-section PI pseudo-attribute <a href="#rfc.iref.a.2">3.3</a></li></ul></li><li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul><li>background PI pseudo-attribute <a href="#rfc.iref.b.1">3.1</a></li><li>bb Extension Element <a href="#rfc.iref.b.3"><b>11.4</b></a>, <a href="#rfc.iref.b.8">A</a></li><li>bc Extension Element <a href="#rfc.iref.b.4"><b>11.5</b></a>, <a href="#rfc.iref.b.9">A</a></li><li>bcp14 Extension Element <a href="#rfc.iref.b.2"><b>11.3</b></a>, <a href="#rfc.iref.b.10">A</a></li><li><em>BCP97</em> <a href="#rfc.xref.BCP97.1">12.1</a>, <a href="#BCP97"><b>13</b></a></li><li>blockquote Extension Element <a href="#rfc.iref.b.5"><b>11.6</b></a>, <a href="#rfc.iref.b.11">A</a></li><li>boilerplate Extension Element <a href="#rfc.iref.b.6"><b>11.7</b></a>, <a href="#rfc.iref.b.12">A</a></li><li>bt Extension Element <a href="#rfc.iref.b.7"><b>11.8</b></a>, <a href="#rfc.iref.b.13">A</a></li></ul></li><li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul><li>chapter HTML LINK element <a href="#rfc.iref.c.3">6.2</a></li><li>CHM format <a href="#rfc.iref.c.7">8</a></li><li>comments PI pseudo-attribute <a href="#rfc.iref.c.2">3.1</a></li><li>compact PI pseudo-attribute <a href="#rfc.iref.c.1">3.1</a></li><li>contents HTML LINK element <a href="#rfc.iref.c.4">6.2</a></li><li>copyright HTML LINK element <a href="#rfc.iref.c.5">6.2</a></li><li>Creator DCMI property <a href="#rfc.iref.c.6">6.4</a></li></ul></li><li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul><li>Date.Issued DCMI property <a href="#rfc.iref.d.3">6.4</a></li><li><em>DC-HTML</em> <a href="#rfc.xref.DC-HTML.1">6.4</a>, <a href="#DC-HTML"><b>13</b></a></li><li>DCMI properties <ul><li>Creator <a href="#rfc.iref.d.2">6.4</a></li><li>Date.Issued <a href="#rfc.iref.d.4">6.4</a></li><li>Description.Abstract <a href="#rfc.iref.d.6">6.4</a></li><li>Identifier <a href="#rfc.iref.d.7">6.4</a></li><li>isPartOf <a href="#rfc.iref.d.8">6.4</a></li><li>Relation.Replaces <a href="#rfc.iref.d.9">6.4</a></li></ul></li><li>Description.Abstract DCMI property <a href="#rfc.iref.d.5">6.4</a></li><li>dfn Extension Element <a href="#rfc.iref.d.10"><b>11.9</b></a>, <a href="#rfc.iref.d.11">A</a></li><li>duplex PI pseudo-attribute <a href="#rfc.iref.d.1">3.3</a></li></ul></li><li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul><li>editing PI pseudo-attribute <a href="#rfc.iref.e.1">3.1</a></li><li>Extension Elements <ul><li>abnf-char-sequence <a href="#rfc.iref.e.2"><b>11.1</b></a>, <a href="#rfc.iref.e.24">A</a></li><li>anchor-alias <a href="#rfc.iref.e.3"><b>11.2</b></a>, <a href="#rfc.iref.e.25">A</a></li><li>assign-section-number <a href="#rfc.iref.e.28">A</a></li><li>bb <a href="#rfc.iref.e.5"><b>11.4</b></a>, <a href="#rfc.iref.e.29">A</a></li><li>bc <a href="#rfc.iref.e.6"><b>11.5</b></a>, <a href="#rfc.iref.e.30">A</a></li><li>bcp14 <a href="#rfc.iref.e.4"><b>11.3</b></a>, <a href="#rfc.iref.e.31">A</a></li><li>blockquote <a href="#rfc.iref.e.7"><b>11.6</b></a>, <a href="#rfc.iref.e.32">A</a></li><li>boilerplate <a href="#rfc.iref.e.8"><b>11.7</b></a>, <a href="#rfc.iref.e.33">A</a></li><li>bt <a href="#rfc.iref.e.9"><b>11.8</b></a>, <a href="#rfc.iref.e.34">A</a></li><li>dfn <a href="#rfc.iref.e.10"><b>11.9</b></a>, <a href="#rfc.iref.e.35">A</a></li><li>feedback <a href="#rfc.iref.e.11"><b>11.10</b></a>, <a href="#rfc.iref.e.26">A</a></li><li>h <a href="#rfc.iref.e.12"><b>11.11</b></a>, <a href="#rfc.iref.e.36">A</a></li><li>highlight <a href="#rfc.iref.e.13"><b>11.12</b></a>, <a href="#rfc.iref.e.37">A</a></li><li>include-author <a href="#rfc.iref.e.27">A</a></li><li>length-of <a href="#rfc.iref.e.14"><b>11.13</b></a>, <a href="#rfc.iref.e.38">A</a></li><li>link <a href="#rfc.iref.e.15"><b>11.14</b></a>, <a href="#rfc.iref.e.39">A</a></li><li>lt <a href="#rfc.iref.e.16"><b>11.15</b></a>, <a href="#rfc.iref.e.40">A</a></li><li>note <a href="#rfc.iref.e.17"><b>11.16</b></a>, <a href="#rfc.iref.e.41">A</a></li><li>parse-xml <a href="#rfc.iref.e.18"><b>11.17</b></a>, <a href="#rfc.iref.e.42">A</a></li><li>prose <a href="#rfc.iref.e.19"><b>11.18</b></a>, <a href="#rfc.iref.e.43">A</a></li><li>q <a href="#rfc.iref.e.20"><b>11.19</b></a>, <a href="#rfc.iref.e.44">A</a></li><li>rdf:Description <a href="#rfc.iref.e.50">A</a></li><li>ref <a href="#rfc.iref.e.21"><b>11.20</b></a>, <a href="#rfc.iref.e.45">A</a></li><li>source <a href="#rfc.iref.e.22"><b>11.21</b></a>, <a href="#rfc.iref.e.46">A</a></li><li>span <a href="#rfc.iref.e.48">A</a></li><li>sup <a href="#rfc.iref.e.23"><b>11.22</b></a>, <a href="#rfc.iref.e.47">A</a></li><li>x <a href="#rfc.iref.e.49">A</a></li></ul></li></ul></li><li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul><li>feedback Extension Element <a href="#rfc.iref.f.4"><b>11.10</b></a>, <a href="#rfc.iref.f.5">A</a></li><li>Firefox <ul><li>1.*/2.* <a href="#rfc.iref.f.3">5.2</a></li><li>3.* <a href="#rfc.iref.f.2">5.2</a></li></ul></li><li>footer PI pseudo-attribute <a href="#rfc.iref.f.1">3.1</a></li></ul></li><li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul><li>generator HTML META element <a href="#rfc.iref.g.2">6.3</a></li><li>Google Chrome <a href="#rfc.iref.g.1">5.2</a></li><li>Grammar <a href="#rfc.iref.g.3"><b>A</b></a></li></ul></li><li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul><li>h Extension Element <a href="#rfc.iref.h.12"><b>11.11</b></a>, <a href="#rfc.iref.h.14">A</a></li><li>header PI pseudo-attribute <a href="#rfc.iref.h.1">3.1</a></li><li>highlight Extension Element <a href="#rfc.iref.h.13"><b>11.12</b></a>, <a href="#rfc.iref.h.15">A</a></li><li><em>HTML</em> <a href="#rfc.xref.HTML.1">6.1</a>, <a href="#rfc.xref.HTML.2">11.6</a>, <a href="#rfc.xref.HTML.3">11.9</a>, <a href="#rfc.xref.HTML.4">11.19</a>, <a href="#rfc.xref.HTML.5">11.22</a>, <a href="#HTML"><b>13</b></a></li><li>HTML compliance <a href="#rfc.iref.h.2">6.1</a></li><li>HTML LINK elements <ul><li>alternate <a href="#rfc.iref.h.3">6.2</a></li><li>appendix <a href="#rfc.iref.h.4">6.2</a></li><li>author <a href="#rfc.iref.h.5">6.2</a></li><li>chapter <a href="#rfc.iref.h.6">6.2</a></li><li>contents <a href="#rfc.iref.h.7">6.2</a></li><li>copyright <a href="#rfc.iref.h.8">6.2</a></li><li>index <a href="#rfc.iref.h.9">6.2</a></li></ul></li><li>HTML META elements <ul><li>generator <a href="#rfc.iref.h.10">6.3</a></li><li>keywords <a href="#rfc.iref.h.11">6.3</a></li></ul></li></ul></li><li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul><li>Identifier DCMI property <a href="#rfc.iref.i.12">6.4</a></li><li>include PI pseudo-attribute <a href="#rfc.iref.i.3">3.2</a></li><li>include-author Extension Element <a href="#rfc.iref.i.14">A</a></li><li>include-index PI pseudo-attribute <a href="#rfc.iref.i.4">3.3</a></li><li>include-references-in-index PI pseudo-attribute <a href="#rfc.iref.i.5">3.3</a></li><li>index HTML LINK element <a href="#rfc.iref.i.11">6.2</a></li><li>inline PI pseudo-attribute <a href="#rfc.iref.i.1">3.1</a></li><li>Internet Explorer 5.5 <a href="#rfc.iref.i.6">5.2</a></li><li>Internet Explorer 6 <a href="#rfc.iref.i.7">5.2</a></li><li>Internet Explorer 7 <a href="#rfc.iref.i.8">5.2</a></li><li>Internet Explorer 8 <a href="#rfc.iref.i.9">5.2</a></li><li>Internet Explorer 9 <a href="#rfc.iref.i.10">5.2</a></li><li>iprnotified PI pseudo-attribute <a href="#rfc.iref.i.2">3.1</a></li><li>isPartOf DCMI property <a href="#rfc.iref.i.13">6.4</a></li></ul></li><li><a id="rfc.index.J" href="#rfc.index.J"><b>J</b></a><ul><li>justification PI pseudo-attribute <a href="#rfc.iref.j.1">3.3</a></li></ul></li><li><a id="rfc.index.K" href="#rfc.index.K"><b>K</b></a><ul><li>keywords HTML META element <a href="#rfc.iref.k.1">6.3</a></li></ul></li><li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul><li>length-of Extension Element <a href="#rfc.iref.l.2"><b>11.13</b></a>, <a href="#rfc.iref.l.5">A</a></li><li>link Extension Element <a href="#rfc.iref.l.3"><b>11.14</b></a>, <a href="#rfc.iref.l.6">A</a></li><li>linkmailto PI pseudo-attribute <a href="#rfc.iref.l.1">3.1</a></li><li>lt Extension Element <a href="#rfc.iref.l.4"><b>11.15</b></a>, <a href="#rfc.iref.l.7">A</a></li></ul></li><li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul><li>Microsoft Help <a href="#rfc.iref.m.5">8</a></li><li>Mozilla <a href="#rfc.iref.m.3">5.2</a>, <a href="#rfc.iref.m.4">5.2</a></li><li>MSXML3 <a href="#rfc.iref.m.1">5.1</a></li><li>MSXML4 <a href="#rfc.iref.m.2">5.1</a></li></ul></li><li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul><li>needLines PI pseudo-attribute <a href="#rfc.iref.n.1">3.2</a></li><li>NoScript <a href="#rfc.iref.n.2">5.2</a></li><li>note Extension Element <a href="#rfc.iref.n.3"><b>11.16</b></a>, <a href="#rfc.iref.n.4">A</a></li></ul></li><li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul><li>Opera <a href="#rfc.iref.o.1">5.2</a>, <a href="#rfc.iref.o.2">5.2</a></li></ul></li><li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul><li>Parameters <ul><li>xml2rfc-background <a href="#rfc.iref.p.2">3.1</a></li><li>xml2rfc-comments <a href="#rfc.iref.p.6">3.1</a></li><li>xml2rfc-compact <a href="#rfc.iref.p.4">3.1</a></li><li>xml2rfc-editing <a href="#rfc.iref.p.8">3.1</a></li><li>xml2rfc-ext-allow-markup-in-artwork <a href="#rfc.iref.p.44">3.3</a></li><li>xml2rfc-ext-authors-section <a href="#rfc.iref.p.46">3.3</a></li><li>xml2rfc-ext-duplex <a href="#rfc.iref.p.48">3.3</a></li><li>xml2rfc-ext-include-index <a href="#rfc.iref.p.50">3.3</a></li><li>xml2rfc-ext-include-references-in-index <a href="#rfc.iref.p.52">3.3</a></li><li>xml2rfc-ext-justification <a href="#rfc.iref.p.54">3.3</a></li><li>xml2rfc-ext-parse-xml-in-artwork <a href="#rfc.iref.p.57">3.3</a></li><li>xml2rfc-ext-sec-no-trailing-dots <a href="#rfc.iref.p.61">3.3</a></li><li>xml2rfc-ext-support-rfc2731 <a href="#rfc.iref.p.59">3.3</a></li><li>xml2rfc-footer <a href="#rfc.iref.p.10">3.1</a></li><li>xml2rfc-header <a href="#rfc.iref.p.12">3.1</a></li><li>xml2rfc-inline <a href="#rfc.iref.p.14">3.1</a></li><li>xml2rfc-iprnotified <a href="#rfc.iref.p.16">3.1</a></li><li>xml2rfc-linkmailto <a href="#rfc.iref.p.18">3.1</a></li><li>xml2rfc-private <a href="#rfc.iref.p.21">3.1</a></li><li>xml2rfc-refparent <a href="#rfc.iref.p.23">3.1</a></li><li>xml2rfc-rfcedstyle <a href="#rfc.iref.p.25">3.1</a></li><li>xml2rfc-sortrefs <a href="#rfc.iref.p.27">3.1</a></li><li>xml2rfc-symrefs <a href="#rfc.iref.p.29">3.1</a></li><li>xml2rfc-toc <a href="#rfc.iref.p.31">3.1</a></li><li>xml2rfc-tocdepth <a href="#rfc.iref.p.33">3.1</a></li><li>xml2rfc-topblock <a href="#rfc.iref.p.35">3.1</a></li></ul></li><li>parse-xml Extension Element <a href="#rfc.iref.p.62"><b>11.17</b></a>, <a href="#rfc.iref.p.64">A</a></li><li>parse-xml-in-artwork PI pseudo-attribute <a href="#rfc.iref.p.55">3.3</a></li><li>private PI pseudo-attribute <a href="#rfc.iref.p.19">3.1</a>, <a href="#rfc.iref.p.66">D</a></li><li>Processing Instruction pseudo attributes <ul><li>allow-markup-in-artwork <a href="#rfc.iref.p.43">3.3</a></li><li>authors-section <a href="#rfc.iref.p.45">3.3</a></li><li>background <a href="#rfc.iref.p.1">3.1</a></li><li>comments <a href="#rfc.iref.p.5">3.1</a></li><li>compact <a href="#rfc.iref.p.3">3.1</a></li><li>duplex <a href="#rfc.iref.p.47">3.3</a></li><li>editing <a href="#rfc.iref.p.7">3.1</a></li><li>footer <a href="#rfc.iref.p.9">3.1</a></li><li>header <a href="#rfc.iref.p.11">3.1</a></li><li>ijustification <a href="#rfc.iref.p.53">3.3</a></li><li>include <a href="#rfc.iref.p.36">3.2</a></li><li>include-index <a href="#rfc.iref.p.49">3.3</a></li><li>include-references-in-index <a href="#rfc.iref.p.51">3.3</a></li><li>inline <a href="#rfc.iref.p.13">3.1</a></li><li>iprnotified <a href="#rfc.iref.p.15">3.1</a></li><li>linkmailto <a href="#rfc.iref.p.17">3.1</a></li><li>needLines <a href="#rfc.iref.p.37">3.2</a></li><li>parse-xml-in-artwork <a href="#rfc.iref.p.56">3.3</a></li><li>private <a href="#rfc.iref.p.20">3.1</a>, <a href="#rfc.iref.p.67">D</a></li><li>refparent <a href="#rfc.iref.p.22">3.1</a></li><li>rfcedstyle <a href="#rfc.iref.p.24">3.1</a></li><li>sec-no-trailing-dots <a href="#rfc.iref.p.60">3.3</a></li><li>slides <a href="#rfc.iref.p.38">3.2</a></li><li>sortrefs <a href="#rfc.iref.p.26">3.1</a></li><li>strict <a href="#rfc.iref.p.39">3.2</a></li><li>subcompact <a href="#rfc.iref.p.40">3.2</a></li><li>support-rfc2731 <a href="#rfc.iref.p.58">3.3</a></li><li>symrefs <a href="#rfc.iref.p.28">3.1</a></li><li>toc <a href="#rfc.iref.p.30">3.1</a></li><li>tocdepth <a href="#rfc.iref.p.32">3.1</a></li><li>tocindent <a href="#rfc.iref.p.41">3.2</a></li><li>tocompact <a href="#rfc.iref.p.42">3.2</a></li><li>topblock <a href="#rfc.iref.p.34">3.1</a></li></ul></li><li>prose Extension Element <a href="#rfc.iref.p.63"><b>11.18</b></a>, <a href="#rfc.iref.p.65">A</a></li></ul></li><li><a id="rfc.index.Q" href="#rfc.index.Q"><b>Q</b></a><ul><li>q Extension Element <a href="#rfc.iref.q.1"><b>11.19</b></a>, <a href="#rfc.iref.q.2">A</a></li></ul></li><li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul><li>rdf:Description Extension Element <a href="#rfc.iref.r.26">A</a></li><li>ref Extension Element <a href="#rfc.iref.r.23"><b>11.20</b></a>, <a href="#rfc.iref.r.25">A</a></li><li>refparent PI pseudo-attribute <a href="#rfc.iref.r.1">3.1</a></li><li>Relation.Replaces DCMI property <a href="#rfc.iref.r.22">6.4</a></li><li>RELAX NG Compact Schema <a href="#rfc.iref.r.24"><b>A</b></a></li><li>rfc.abstract anchor <a href="#rfc.iref.r.3">4</a></li><li>rfc.authors anchor <a href="#rfc.iref.r.4">4</a></li><li>rfc.copyright anchor <a href="#rfc.iref.r.5">4</a></li><li>rfc.copyrightnotice anchor <a href="#rfc.iref.r.6">4</a></li><li>rfc.figure.n anchor <a href="#rfc.iref.r.7">4</a>, <a href="#rfc.iref.r.18">4</a></li><li>rfc.figure.u.n anchor <a href="#rfc.iref.r.8">4</a>, <a href="#rfc.iref.r.19">4</a></li><li>rfc.index anchor <a href="#rfc.iref.r.9">4</a></li><li>rfc.ipr anchor <a href="#rfc.iref.r.10">4</a></li><li>rfc.iref.n anchor <a href="#rfc.iref.r.11">4</a></li><li>rfc.note.n anchor <a href="#rfc.iref.r.12">4</a></li><li>rfc.references anchor <a href="#rfc.iref.r.13">4</a></li><li>rfc.references.n anchor <a href="#rfc.iref.r.14">4</a></li><li>rfc.section.n anchor <a href="#rfc.iref.r.15">4</a></li><li>rfc.section.n.p.m anchor <a href="#rfc.iref.r.16">4</a></li><li>rfc.status anchor <a href="#rfc.iref.r.17">4</a></li><li>rfc.toc anchor <a href="#rfc.iref.r.20">4</a></li><li>rfc.xref.name.n anchor <a href="#rfc.iref.r.21">4</a></li><li><em>RFC2026</em> <a href="#rfc.xref.RFC2026.1">11.26</a>, <a href="#RFC2026"><b>13</b></a>, <a href="#rfc.xref.RFC2026.2">D.2</a><ul><li><em>Section 4</em> <a href="#rfc.xref.RFC2026.2">D.2</a></li><li><em>Section 4.1</em> <a href="#rfc.xref.RFC2026.1">11.26</a></li></ul></li><li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">11.3</a>, <a href="#rfc.xref.RFC2119.2">11.28</a>, <a href="#RFC2119"><b>13</b></a><ul><li><em>Section 5</em> <a href="#rfc.xref.RFC2119.2">11.28</a></li></ul></li><li><em>RFC2616</em> <a href="#RFC2616"><b>13</b></a>, <a href="#rfc.xref.RFC2616.1">B.1</a>, <a href="#rfc.xref.RFC2616.2">B.1</a>, <a href="#rfc.xref.RFC2616.3">B.1</a><ul><li><em>Section 2.1</em> <a href="#rfc.xref.RFC2616.1">B.1</a></li><li><em>Section 19.1</em> <a href="#rfc.xref.RFC2616.2">B.1</a>, <a href="#rfc.xref.RFC2616.3">B.1</a></li></ul></li><li><em>RFC2629</em> <a href="#rfc.xref.RFC2629.1">1</a>, <a href="#RFC2629"><b>13</b></a></li><li><em>RFC2648</em> <a href="#rfc.xref.RFC2648.1">6.4</a>, <a href="#RFC2648"><b>13</b></a></li><li><em>RFC2731</em> <a href="#rfc.xref.RFC2731.1">6.4</a>, <a href="#RFC2731"><b>13</b></a></li><li><em>RFC5234</em> <a href="#RFC5234"><b>13</b></a>, <a href="#rfc.xref.RFC5234.1">B.1</a></li><li><em>RFC5741</em> <a href="#RFC5741"><b>13</b></a>, <a href="#rfc.xref.RFC5741.1">D.3</a>, <a href="#rfc.xref.RFC5741.2">D.3</a>, <a href="#rfc.xref.RFC5741.3">D.4</a><ul><li><em>Section 3.2.2</em> <a href="#rfc.xref.RFC5741.2">D.3</a>, <a href="#rfc.xref.RFC5741.3">D.4</a></li></ul></li><li>rfcedstyle PI pseudo-attribute <a href="#rfc.iref.r.2">3.1</a></li><li><em>RNC</em> <a href="#RNC"><b>13</b></a>, <a href="#rfc.xref.RNC.1">A</a>, <a href="#rfc.xref.RNC.2">B.1</a></li></ul></li><li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul><li>Safari <a href="#rfc.iref.s.9">5.2</a>, <a href="#rfc.iref.s.11">5.2</a><ul><li>3.* <a href="#rfc.iref.s.10">5.2</a></li></ul></li><li>Saxon <a href="#rfc.iref.s.8">5.1</a></li><li>Schema <a href="#rfc.iref.s.14"><b>A</b></a></li><li>sec-no-trailing-dots PI pseudo-attribute <a href="#rfc.iref.s.7">3.3</a></li><li>slides PI pseudo-attribute <a href="#rfc.iref.s.3">3.2</a></li><li>sortrefs PI pseudo-attribute <a href="#rfc.iref.s.1">3.1</a></li><li>source Extension Element <a href="#rfc.iref.s.12"><b>11.21</b></a>, <a href="#rfc.iref.s.15">A</a></li><li>span Extension Element <a href="#rfc.iref.s.17">A</a></li><li>strict PI pseudo-attribute <a href="#rfc.iref.s.4">3.2</a></li><li>subcompact PI pseudo-attribute <a href="#rfc.iref.s.5">3.2</a></li><li>sup Extension Element <a href="#rfc.iref.s.13"><b>11.22</b></a>, <a href="#rfc.iref.s.16">A</a></li><li>support-rfc2731 PI pseudo-attribute <a href="#rfc.iref.s.6">3.3</a></li><li>symrefs PI pseudo-attribute <a href="#rfc.iref.s.2">3.1</a></li></ul></li><li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul><li>toc PI pseudo-attribute <a href="#rfc.iref.t.1">3.1</a></li><li>tocdepth PI pseudo-attribute <a href="#rfc.iref.t.2">3.1</a></li><li>tocindent PI pseudo-attribute <a href="#rfc.iref.t.4">3.2</a></li><li>tocompact PI pseudo-attribute <a href="#rfc.iref.t.5">3.2</a></li><li>topblock PI pseudo-attribute <a href="#rfc.iref.t.3">3.1</a></li></ul></li><li><a id="rfc.index.X" href="#rfc.index.X"><b>X</b></a><ul><li>x Extension Element <a href="#rfc.iref.x.31">A</a></li><li>Xalan <a href="#rfc.iref.x.28">5.1</a></li><li><em>XHTML2</em> <a href="#rfc.xref.XHTML2.1">11.11</a>, <a href="#XHTML2"><b>13</b></a></li><li><em>XML</em> <a href="#XML"><b>13</b></a>, <a href="#rfc.xref.XML.1">C.1</a><ul><li><em>Section 2.8</em> <a href="#rfc.xref.XML.1">C.1</a></li></ul></li><li>xml-stylesheet PI <a href="#rfc.iref.x.30">6</a></li><li>xml2rfc-background parameter <a href="#rfc.iref.x.2">3.1</a></li><li>xml2rfc-comments parameter <a href="#rfc.iref.x.4">3.1</a></li><li>xml2rfc-editing parameter <a href="#rfc.iref.x.3">3.1</a>, <a href="#rfc.iref.x.5">3.1</a></li><li>xml2rfc-ext-allow-markup-in-artwork parameter <a href="#rfc.iref.x.19">3.3</a></li><li>xml2rfc-ext-authors-section parameter <a href="#rfc.iref.x.20">3.3</a></li><li>xml2rfc-ext-duplex <a href="#rfc.iref.x.21">3.3</a></li><li>xml2rfc-ext-include-index parameter <a href="#rfc.iref.x.22">3.3</a></li><li>xml2rfc-ext-include-references-in-index parameter <a href="#rfc.iref.x.23">3.3</a></li><li>xml2rfc-ext-justification parameter <a href="#rfc.iref.x.24">3.3</a></li><li>xml2rfc-ext-parse-xml-in-artwork parameter <a href="#rfc.iref.x.25">3.3</a></li><li>xml2rfc-ext-sec-no-trailing-dots parameter <a href="#rfc.iref.x.27">3.3</a></li><li>xml2rfc-ext-support-rfc2731 parameter <a href="#rfc.iref.x.26">3.3</a></li><li>xml2rfc-footer parameter <a href="#rfc.iref.x.6">3.1</a></li><li>xml2rfc-header parameter <a href="#rfc.iref.x.7">3.1</a></li><li>xml2rfc-inline parameter <a href="#rfc.iref.x.8">3.1</a></li><li>xml2rfc-iprnotified parameter <a href="#rfc.iref.x.9">3.1</a></li><li>xml2rfc-linkmailto parameter <a href="#rfc.iref.x.10">3.1</a></li><li>xml2rfc-private parameter <a href="#rfc.iref.x.11">3.1</a></li><li>xml2rfc-refparent parameter <a href="#rfc.iref.x.12">3.1</a></li><li>xml2rfc-rfcedstyle parameter <a href="#rfc.iref.x.13">3.1</a></li><li>xml2rfc-sortrefs parameter <a href="#rfc.iref.x.14">3.1</a></li><li>xml2rfc-symrefs parameter <a href="#rfc.iref.x.15">3.1</a></li><li>xml2rfc-toc parameter <a href="#rfc.iref.x.16">3.1</a></li><li>xml2rfc-tocdepth parameter <a href="#rfc.iref.x.17">3.1</a></li><li>xml2rfc-topblock parameter <a href="#rfc.iref.x.18">3.1</a></li><li><em>XSL-FO</em> <a href="#rfc.xref.XSL-FO.1">9.1</a>, <a href="#rfc.xref.XSL-FO.2">9.1</a>, <a href="#XSL-FO"><b>13</b></a></li><li>xsltproc <a href="#rfc.iref.x.29">5.1</a><ul><li>passing parameters <a href="#rfc.iref.x.1">3</a></li></ul></li></ul></li></ul></div></body></html> -
rfc2629xslt/rfc2629xslt.txt
r1497 r1661 4 4 RFC2629 through XSLT J. Reschke 5 5 greenbytes 6 November 20116 March 2012 7 7 8 8 … … 13 13 Table of Contents 14 14 15 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 416 2. Supported RFC2629 elements . . . . . . . . . . . . . . . . . . 517 2.1. Extension elements . . . . . . . . . . . . . . . . . . . 518 3. Processing Instructions . . . . . . . . . . . . . . . . . . . 619 3.1. Supported xml2rfc-compatible PIs . . . . . . . . . . . . 720 3.2. Unsupported xml2rfc-compatible PIs . . . . . . . . . . . 821 3.3. Extension PIs . . . . . . . . . . . . . . . . . . . . . . 922 4. Anchors . . . . . . . . . . . . . . . . . . . . . . . . . . . 1323 5. Supported XSLT engines . . . . . . . . . . . . . . . . . . . . 1524 5.1. Standalone Engines . . . . . . . . . . . . . . . . . . . 1525 5.2. In-Browser Engines . . . . . . . . . . . . . . . . . . . 1526 6. Transforming to HTML . . . . . . . . . . . . . . . . . . . . . 1727 6.1. HTML compliance . . . . . . . . . . . . . . . . . . . . . 1728 6.2. Standard HTML LINK elements . . . . . . . . . . . . . . . 1729 6.3. Standard HTML metadata . . . . . . . . . . . . . . . . . 1830 6.4. Dublin Core (RFC2731) metadata . . . . . . . . . . . . . 1831 6.5. Experimental hCard support . . . . . . . . . . . . . . . 1832 7. Transforming to XHTML . . . . . . . . . . . . . . . . . . . . 1933 8. Transforming to CHM (Microsoft Compiled Help) . . . . . . . . 2034 9. Transforming to PDF . . . . . . . . . . . . . . . . . . . . . 2135 9.1. Via XSL-FO . . . . . . . . . . . . . . . . . . . . . . . 2136 9.1.1. Extension feature matrix . . . . . . . . . . . . . . . 2137 9.1.2. Example: producing output for Apache FOP . . . . . . . 2238 9.2. Via X(HTML) . . . . . . . . . . . . . . . . . . . . . . . 2239 10. Transforming to ePub . . . . . . . . . . . . . . . . . . . . . 2340 11. Generic Extensions . . . . . . . . . . . . . . . . . . . . . . 2441 11.1. <abnf-char-sequence> element . . . . . . . . . . . . . . 2442 11.2. <anchor-alias> element . . . . . . . . . . . . . . . . . 2443 11.3. <bcp14> element . . . . . . . . . . . . . . . . . . . . . 2444 11.4. <bb> element . . . . . . . . . . . . . . . . . . . . . . 2545 11.5. <bc> element . . . . . . . . . . . . . . . . . . . . . . 2546 11.6. <blockquote> element . . . . . . . . . . . . . . . . . . 2547 11.7. <boilerplate> element . . . . . . . . . . . . . . . . . . 2548 11.8. <bt> element . . . . . . . . . . . . . . . . . . . . . . 2649 11.9. <dfn> element . . . . . . . . . . . . . . . . . . . . . . 2650 11.10. < h> element . . . . . . . . . . . . . . . . . . . . . . . 2651 11.11. <h ighlight> element . . . . . . . . . . . . . . . . . . . 2615 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . ancho 16 2. Supported RFC2629 elements . . . . . . . . . . . . . . . . suppo 17 2.1. Extension elements . . . . . . . . . . . . . . . . . . ancho 18 3. Processing Instructions . . . . . . . . . . . . . . . . . . proce 19 3.1. Supported xml2rfc-compatible PIs . . . . . . . . . . . ancho 20 3.2. Unsupported xml2rfc-compatible PIs . . . . . . . . . . ancho 21 3.3. Extension PIs . . . . . . . . . . . . . . . . . . . . ancho 22 4. Anchors . . . . . . . . . . . . . . . . . . . . . . . . . . ancho 23 5. Supported XSLT engines . . . . . . . . . . . . . . . . . . xslt. 24 5.1. Standalone Engines . . . . . . . . . . . . . . . . . . ancho 25 5.2. In-Browser Engines . . . . . . . . . . . . . . . . . . xslt. 26 6. Transforming to HTML . . . . . . . . . . . . . . . . . . . outpu 27 6.1. HTML compliance . . . . . . . . . . . . . . . . . . . ancho 28 6.2. Standard HTML LINK elements . . . . . . . . . . . . . html. 29 6.3. Standard HTML metadata . . . . . . . . . . . . . . . . ancho 30 6.4. Dublin Core (RFC2731) metadata . . . . . . . . . . . . rfc27 31 6.5. Experimental hCard support . . . . . . . . . . . . . . hcard 32 7. Transforming to XHTML . . . . . . . . . . . . . . . . . . . outpu 33 8. Transforming to CHM (Microsoft Compiled Help) . . . . . . . outpu 34 9. Transforming to PDF . . . . . . . . . . . . . . . . . . . . outpu 35 9.1. Via XSL-FO . . . . . . . . . . . . . . . . . . . . . . outpu 36 9.1.1. Extension feature matrix . . . . . . . . . . . . . ancho 37 9.1.2. Example: producing output for Apache FOP . . . . . ancho 38 9.2. Via X(HTML) . . . . . . . . . . . . . . . . . . . . . outpu 39 10. Transforming to ePub . . . . . . . . . . . . . . . . . . . outpu 40 11. Generic Extensions . . . . . . . . . . . . . . . . . . . . exten 41 11.1. <abnf-char-sequence> element . . . . . . . . . . . . . ext.e 42 11.2. <anchor-alias> element . . . . . . . . . . . . . . . . ext.e 43 11.3. <bcp14> element . . . . . . . . . . . . . . . . . . . ext.e 44 11.4. <bb> element . . . . . . . . . . . . . . . . . . . . . ext.e 45 11.5. <bc> element . . . . . . . . . . . . . . . . . . . . . ext.e 46 11.6. <blockquote> element . . . . . . . . . . . . . . . . . ext.e 47 11.7. <boilerplate> element . . . . . . . . . . . . . . . . ext.e 48 11.8. <bt> element . . . . . . . . . . . . . . . . . . . . . ext.e 49 11.9. <dfn> element . . . . . . . . . . . . . . . . . . . . ext.e 50 11.10. <feedback> element . . . . . . . . . . . . . . . . . . ext.e 51 11.11. <h> element . . . . . . . . . . . . . . . . . . . . . ext.e 52 52 53 53 … … 56 56 57 57 58 Documentation RFC2629 through XSLT November 201159 60 61 11.12. < length-of> element . . . . . . . . . . . . . . . . . . . 2662 11.13. <l ink> element . . . . . . . . . . . . . . . . . . . . . 2663 11.14. <l t> element . . . . . . . . . . . . . . . . . . . . . . 2764 11.15. < note> element . . . . . . . . . . . . . . . . . . . . . 2765 11.16. < parse-xml> element . . . . . . . . . . . . . . . . . . . 2766 11.17. <p rose> element . . . . . . . . . . . . . . . . . . . . . 2767 11.18. < q> element . . . . . . . . . . . . . . . . . . . . . . . 2768 11.19. < ref> element . . . . . . . . . . . . . . . . . . . . . . 2769 11.20. < source> element . . . . . . . . . . . . . . . . . . . . 2870 11.21. <s up> element . . . . . . . . . . . . . . . . . . . . . . 2871 11.22. Extensions to Xml2rfc <artwork> element . . . . . . . . . 2872 11.23. Extensions to Xml2rfc < iref> element . . . . . . . . . . 2973 11.24. Extensions to Xml2rfc < list> element . . . . . . . . . . 2974 11.25. Extensions to Xml2rfc < rfc> element . . . . . . . . . . . 2975 11.26. Extensions to Xml2rfc < section> element . . . . . . . . . 2976 11.27. Extensions to Xml2rfc < xref> element . . . . . . . . . . 3077 12. Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . 3178 12.1. Checking References . . . . . . . . . . . . . . . . . . . 3179 12. 2. Generating Graphs from References . . . . . . . . . . . . 3380 12. 3. Producing reference entries for books . . . . . . . . . . 3381 12. 4. Down-converting to RFC2629bis DTD . . . . . . . . . . . . 3482 12. 5. Extracting artwork . . . . . . . . . . . . . . . . . . . 3583 12. 6. GRRDL . . . . . . . . . . . . . . . . . . . . . . . . . . 3584 13. Informative References . . . . . . . . . . . . . . . . . . . . 3685 Appendix A. RELAX NG Compact Schema . . . . . . . . . . . . . . . 3886 Appendix B. Implementation Notes . . . . . . . . . . . . . . . . 4887 B.1. Recognized type attributes for <artwork> element . . . . 4888 Appendix C. Examples . . . . . . . . . . . . . . . . . . . . . . 4989 C.1. Using the 'Internal Subset' . . . . . . . . . . . . . . . 4990 C. 2. Customization . . . . . . . . . . . . . . . . . . . . . . 4991 Appendix D. Producing the IETF 'Boilerplate' . . . . . . . . . . 5192 D.1. The /rfc/@ipr Attribute . . . . . . . . . . . . . . . . . 5193 D.1.1. Current Values: '*trust200902' . . . . . . . . . . . . 5294 D.1. 2. Historic Values . . . . . . . . . . . . . . . . . . . 5395 D.2. The /rfc/@category Attribute . . . . . . . . . . . . . . 5496 D. 3. The /rfc/@submissionType Attribute . . . . . . . . . . . 5497 D. 4. The /rfc/@consensus Attribute . . . . . . . . . . . . . . 5598 D. 5. The /rfc/@number Attribute . . . . . . . . . . . . . . . 5599 D. 6. The /rfc/@docName Attribute . . . . . . . . . . . . . . . 56100 D. 7. The /rfc/@obsoletes Attribute . . . . . . . . . . . . . . 56101 D. 8. The /rfc/@updates Attribute . . . . . . . . . . . . . . . 56102 Appendix E. License . . . . . . . . . . . . . . . . . . . . . . . 57103 Appendix F. Change Logs . . . . . . . . . . . . . . . . . . . . . 58104 F.1. Package . . . . . . . . . . . . . . . . . . . . . . . . . 58105 F. 2. amazon-asin.xslt . . . . . . . . . . . . . . . . . . . . 59106 F. 3. check-references.xslt . . . . . . . . . . . . . . . . . . 59107 F. 4. gen-reference-graph.xslt . . . . . . . . . . . . . . . . 60108 F. 5. rfc2629.xslt . . . . . . . . . . . . . . . . . . . . . . 6058 Documentation RFC2629 through XSLT March 2012 59 60 61 11.12. <highlight> element . . . . . . . . . . . . . . . . . ext.e 62 11.13. <length-of> element . . . . . . . . . . . . . . . . . ext.e 63 11.14. <link> element . . . . . . . . . . . . . . . . . . . . ext.e 64 11.15. <lt> element . . . . . . . . . . . . . . . . . . . . . ext.e 65 11.16. <note> element . . . . . . . . . . . . . . . . . . . . ext.e 66 11.17. <parse-xml> element . . . . . . . . . . . . . . . . . ext.e 67 11.18. <prose> element . . . . . . . . . . . . . . . . . . . ext.e 68 11.19. <q> element . . . . . . . . . . . . . . . . . . . . . ext.e 69 11.20. <ref> element . . . . . . . . . . . . . . . . . . . . ext.e 70 11.21. <source> element . . . . . . . . . . . . . . . . . . . ext.e 71 11.22. <sup> element . . . . . . . . . . . . . . . . . . . . ext.e 72 11.23. Extensions to Xml2rfc <artwork> element . . . . . . . ext-r 73 11.24. Extensions to Xml2rfc <iref> element . . . . . . . . . ext-r 74 11.25. Extensions to Xml2rfc <list> element . . . . . . . . . ext-r 75 11.26. Extensions to Xml2rfc <rfc> element . . . . . . . . . ext-r 76 11.27. Extensions to Xml2rfc <section> element . . . . . . . ext-r 77 11.28. Extensions to Xml2rfc <xref> element . . . . . . . . . ext-r 78 12. Utilities . . . . . . . . . . . . . . . . . . . . . . . . . utili 79 12.1. Checking References . . . . . . . . . . . . . . . . . check 80 12.2. Generating Graphs from References . . . . . . . . . . ancho 81 12.3. Producing reference entries for books . . . . . . . . ancho 82 12.4. Down-converting to RFC2629bis DTD . . . . . . . . . . clean 83 12.5. Extracting artwork . . . . . . . . . . . . . . . . . . extra 84 12.6. GRRDL . . . . . . . . . . . . . . . . . . . . . . . . grddl 85 13. Informative References . . . . . . . . . . . . . . . . . . ancho 86 Appendix A. RELAX NG Compact Schema . . . . . . . . . . . . . gramm 87 Appendix B. Implementation Notes . . . . . . . . . . . . . . . ancho 88 B.1. Recognized type attributes for <artwork> element . . . ancho 89 Appendix C. Examples . . . . . . . . . . . . . . . . . . . . . examp 90 C.1. Using the 'Internal Subset' . . . . . . . . . . . . . examp 91 C.2. Customization . . . . . . . . . . . . . . . . . . . . examp 92 Appendix D. Producing the IETF 'Boilerplate' . . . . . . . . . boile 93 D.1. The /rfc/@ipr Attribute . . . . . . . . . . . . . . . attri 94 D.1.1. Current Values: '*trust200902' . . . . . . . . . . attri 95 D.1.2. Historic Values . . . . . . . . . . . . . . . . . . attri 96 D.2. The /rfc/@category Attribute . . . . . . . . . . . . . attri 97 D.3. The /rfc/@submissionType Attribute . . . . . . . . . . attri 98 D.4. The /rfc/@consensus Attribute . . . . . . . . . . . . attri 99 D.5. The /rfc/@number Attribute . . . . . . . . . . . . . . attri 100 D.6. The /rfc/@docName Attribute . . . . . . . . . . . . . attri 101 D.7. The /rfc/@obsoletes Attribute . . . . . . . . . . . . attri 102 D.8. The /rfc/@updates Attribute . . . . . . . . . . . . . attri 103 Appendix E. License . . . . . . . . . . . . . . . . . . . . . licen 104 Appendix F. Change Logs . . . . . . . . . . . . . . . . . . . ancho 105 F.1. Package . . . . . . . . . . . . . . . . . . . . . . . ancho 106 F.2. amazon-asin.xslt . . . . . . . . . . . . . . . . . . . ancho 107 F.3. check-references.xslt . . . . . . . . . . . . . . . . ancho 108 F.4. gen-reference-graph.xslt . . . . . . . . . . . . . . . ancho 109 109 110 110 … … 113 113 114 114 115 Documentation RFC2629 through XSLT November 2011116 117 118 F. 6. rfc2629toFO.xslt . . . . . . . . . . . . . . . . . . . . 71119 F. 7. xsl11toAn.xslt . . . . . . . . . . . . . . . . . . . . . 73120 F. 8. xsl11toFop.xslt . . . . . . . . . . . . . . . . . . . . . 73121 F. 9. xsl11toXep.xslt . . . . . . . . . . . . . . . . . . . . . 73122 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74123 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 82124 115 Documentation RFC2629 through XSLT March 2012 116 117 118 F.5. rfc2629.xslt . . . . . . . . . . . . . . . . . . . . . ancho 119 F.6. rfc2629toFO.xslt . . . . . . . . . . . . . . . . . . . ancho 120 F.7. xsl11toAn.xslt . . . . . . . . . . . . . . . . . . . . ancho 121 F.8. xsl11toFop.xslt . . . . . . . . . . . . . . . . . . . ancho 122 F.9. xsl11toXep.xslt . . . . . . . . . . . . . . . . . . . ancho 123 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0 124 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 0 125 125 126 126 … … 170 170 171 171 172 Documentation RFC2629 through XSLT November 2011172 Documentation RFC2629 through XSLT March 2012 173 173 174 174 … … 227 227 228 228 229 Documentation RFC2629 through XSLT November 2011229 Documentation RFC2629 through XSLT March 2012 230 230 231 231 … … 284 284 285 285 286 Documentation RFC2629 through XSLT November 2011286 Documentation RFC2629 through XSLT March 2012 287 287 288 288 … … 341 341 342 342 343 Documentation RFC2629 through XSLT November 2011343 Documentation RFC2629 through XSLT March 2012 344 344 345 345 … … 398 398 399 399 400 Documentation RFC2629 through XSLT November 2011400 Documentation RFC2629 through XSLT March 2012 401 401 402 402 … … 455 455 456 456 457 Documentation RFC2629 through XSLT November 2011457 Documentation RFC2629 through XSLT March 2012 458 458 459 459 … … 512 512 513 513 514 Documentation RFC2629 through XSLT November 2011514 Documentation RFC2629 through XSLT March 2012 515 515 516 516 … … 569 569 570 570 571 Documentation RFC2629 through XSLT November 2011571 Documentation RFC2629 through XSLT March 2012 572 572 573 573 … … 626 626 627 627 628 Documentation RFC2629 through XSLT November 2011628 Documentation RFC2629 through XSLT March 2012 629 629 630 630 … … 683 683 684 684 685 Documentation RFC2629 through XSLT November 2011685 Documentation RFC2629 through XSLT March 2012 686 686 687 687 … … 740 740 741 741 742 Documentation RFC2629 through XSLT November 2011742 Documentation RFC2629 through XSLT March 2012 743 743 744 744 … … 797 797 798 798 799 Documentation RFC2629 through XSLT November 2011799 Documentation RFC2629 through XSLT March 2012 800 800 801 801 … … 854 854 855 855 856 Documentation RFC2629 through XSLT November 2011856 Documentation RFC2629 through XSLT March 2012 857 857 858 858 … … 911 911 912 912 913 Documentation RFC2629 through XSLT November 2011913 Documentation RFC2629 through XSLT March 2012 914 914 915 915 … … 968 968 969 969 970 Documentation RFC2629 through XSLT November 2011970 Documentation RFC2629 through XSLT March 2012 971 971 972 972 … … 1025 1025 1026 1026 1027 Documentation RFC2629 through XSLT November 20111027 Documentation RFC2629 through XSLT March 2012 1028 1028 1029 1029 … … 1082 1082 1083 1083 1084 Documentation RFC2629 through XSLT November 20111084 Documentation RFC2629 through XSLT March 2012 1085 1085 1086 1086 … … 1139 1139 1140 1140 1141 Documentation RFC2629 through XSLT November 20111141 Documentation RFC2629 through XSLT March 2012 1142 1142 1143 1143 … … 1196 1196 1197 1197 1198 Documentation RFC2629 through XSLT November 20111198 Documentation RFC2629 through XSLT March 2012 1199 1199 1200 1200 … … 1253 1253 1254 1254 1255 Documentation RFC2629 through XSLT November 20111255 Documentation RFC2629 through XSLT March 2012 1256 1256 1257 1257 … … 1310 1310 1311 1311 1312 Documentation RFC2629 through XSLT November 20111312 Documentation RFC2629 through XSLT March 2012 1313 1313 1314 1314 … … 1367 1367 1368 1368 1369 Documentation RFC2629 through XSLT November 20111369 Documentation RFC2629 through XSLT March 2012 1370 1370 1371 1371 … … 1424 1424 1425 1425 1426 Documentation RFC2629 through XSLT November 20111426 Documentation RFC2629 through XSLT March 2012 1427 1427 1428 1428 … … 1439 1439 This element is like the "dfn" element in [HTML]. 1440 1440 1441 11.10. <h> element 1442 1443 This element is like the "h" element in [XHTML2]. 1444 1445 11.11. <highlight> element 1446 1447 Used to highlight text passages, currently only allowed in <artwork>. 1448 1449 Note: this is stripped when generating input for xml2rfc, so please 1450 use with care. 1451 1452 11.12. <length-of> element 1453 1454 This element can be used to insert the length of another formatted 1455 section (in decimal). 1456 1457 Example: computing the Content-Length header value 1458 1459 <artwork> 1460 ... 1461 Content-Length: <x:length-of target="req"/> 1462 1463 <x:span anchor="req">123456789 1464 <x:span><artwork/> 1465 1466 The lenght computation counts line ends as two characters (CRLF). 1467 1468 Note that indentation characters in artwork _will_ be counted. The 1469 "indented" attribute allows to specify the amount of indentation to 1470 be substracted from the computed length. 1471 1472 11.13. <link> element 1473 1474 This element can be added as a top-level child element below <rfc> to 1475 indicate additional link information. It's currently used only when 1476 generating HTML output, in which case an HTML <link> element with 1477 1478 1479 1480 Reschke [Page 26] 1481 1482 1483 Documentation RFC2629 through XSLT November 2011 1484 1485 1486 identical attributes gets generated. 1487 1488 Example: generating HTML link element 1489 1490 <x:link xmlns="http://purl.org/net/xml2rfc/ext" 1491 rel="Bookmark" 1492 title="IETF WEBDAV Working Group" 1493 href="http://ftp.ics.uci.edu/pub/ietf/webdav/"/> 1494 1495 11.14. <lt> element 1496 1497 Used for grouping multiple <t> elements into a single list item. 1498 1499 11.15. <note> element 1500 1501 Can be used to add a note, usually indented by a few characters. It 1502 should contain one or more <t> child elements. 1503 1504 11.16. <parse-xml> element 1505 1506 This element instructs the processor to parse the contents as XML and 1507 to warn when there's a problem (requires either MSXML or Saxon8 or 1508 newer). 1509 1510 11.17. <prose> element 1511 1512 This element can be used inside <reference> to add plain text (before 1513 the date, when present). 1514 1515 11.18. <q> element 1516 1517 This element is like the "q" element in [HTML]. 1518 1519 11.19. <ref> element 1520 1521 This element is a simplified variant of the <xref> element, in that 1522 no "target" attribute needs to be specified, instead the text 1523 contents acts as identifier. That in itself wouldn't be terribly 1524 useful, but together with the <anchor-alias>, it allows referring to 1525 other parts of the document with minimal additional markup. 1526 1527 For instance, given an alias definition such as 1528 1529 <section title="Test" anchor="test"> 1530 <x:anchor-alias value="alias1"/> 1531 <x:anchor-alias value="alias 2"/> 1532 ... 1533 </section> 1534 1535 1536 1537 Reschke [Page 27] 1538 1539 1540 Documentation RFC2629 through XSLT November 2011 1541 1542 1543 the following simple references 1544 1545 <x:ref>test</x:ref> 1546 <x:ref>alias1</x:ref> 1547 <x:ref>alias 2</x:ref> 1548 1549 are equivalent to...: 1550 1551 <xref target="test">test</xref> 1552 <xref target="test">alias1</xref> 1553 <xref target="test">alias 2</xref> 1554 1555 11.20. <source> element 1556 1557 Can be used to enhance a <reference> with information about the 1558 location for the XML source. This can be used by the <xref> 1559 processing code to automatically extract the target section number. 1560 1561 For example: 1562 1563 ... 1564 <xref target="RFC2616" x:fmt="of" x:rel="#PUT" /> 1565 ... 1566 1567 <reference target="RFC2616"/> 1568 ... 1569 <x:source href="rfc2616.xml"/> 1570 ... 1571 1572 11.21. <sup> element 1573 1574 This element is like the "sup" element in [HTML]. 1575 1576 Note: the down conversion to RFC2629 format replaces "x^y" by "x^y". 1577 1578 11.22. Extensions to Xml2rfc <artwork> element 1579 1580 Sometimes, artwork occurs inside lists. To get it indent properly in 1581 xml2rfc's text output, it needs to be indented in the source. This 1582 is sub-optimal, as this whitespace will also appear in the HTML 1583 output, where it's already indented due to HTML's semantics. 1584 1585 As a workaround, a "x:indent-with" attribute can be specified, 1586 containing a string that will be prepended to each line when 1587 "clean-for-DTD.xslt" is run (see Section 12.4). 1588 1589 1590 1591 1592 1593 1594 Reschke [Page 28] 1595 1596 1597 Documentation RFC2629 through XSLT November 2011 1598 1599 1600 11.23. Extensions to Xml2rfc <iref> element 1601 1602 The extension attribute below is allowed on the standard <iref> 1603 element: 1604 1605 o x:for-anchor specifies that the <iref> will also be automatically 1606 inserted whenever the specified anchor is cross-referenced -- this 1607 may save entering lots of <iref> instances. As a special case, a 1608 value of "" (empty string) refers to the anchor attribute of the 1609 closest ancestor. 1610 1611 11.24. Extensions to Xml2rfc <list> element 1612 1613 The extension attribute below is allowed on the standard <list> 1614 element: 1615 1616 o x:indent specifies the amount of indentation for list items in 1617 hanging lists. This can be useful when the output format, such as 1618 XSL-FO, does not support automatical formatting. The value takes 1619 an XSL-FO width, such as "5em". The default is _length of longest 1620 label in characters_ times _0.8em_. 1621 1622 Also, the <list> element can take <x:lt> child elements instead of 1623 <t>, allowing to insert multiple paragraphs into a single list item. 1624 1625 11.25. Extensions to Xml2rfc <rfc> element 1626 1627 The extension attributes below are allowed on the standard <rfc> 1628 element: 1629 1630 o grddl:transformation can be used to reference a GRDDL transform. 1631 1632 o x:maturity-level can be used to specify the IETF Standards Track 1633 Maturity Level of "proposed", "draft" or "internet" (see Section 1634 4.1 of [RFC2026]). 1635 1636 11.26. Extensions to Xml2rfc <section> element 1637 1638 The extension attribute below is allowed on the standard <list> 1639 element: 1640 1641 o x:fixed-section-number can be used to specify a fixed section 1642 number. This can be useful when formatting historic documents 1643 that used a different numbering style. 1644 1645 1646 1647 1648 1649 1650 1651 Reschke [Page 29] 1652 1653 1654 Documentation RFC2629 through XSLT November 2011 1655 1656 1657 11.27. Extensions to Xml2rfc <xref> element 1658 1659 Three extension attributes are allowed on the standard <xref> 1660 element: 1661 1662 1. x:sec can be specified to point to a specific section of the 1663 referenced document, 1664 1665 2. x:rel may specify a relative reference to use when linking into 1666 the referenced document (if linking by section number is not 1667 available), 1668 1669 3. x:fmt defines the text format to be used. 1670 1671 The following formats are defined for the x:fmt attribute: 1672 1673 , (Comma) [_reference_], Section _sec_ 1674 1675 () [_reference_] (Section _sec_) 1676 1677 anchor Like the default format, but without brackets. 1678 1679 of Section _sec_ of [_reference_] 1680 1681 number _sec_ 1682 1683 none No output (can be used to have xrefs to references without 1684 having them rendered as such) 1685 1686 sec Section _sec_ 1687 1688 These extensions are currently only supported for <xref> elements 1689 without child nodes. 1690 1691 If the processor knows how to reference the target section, it will 1692 generate a link directly to the target section, such as in [RFC2119], 1693 Section 5. 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 Reschke [Page 30] 1709 1710 1711 Documentation RFC2629 through XSLT November 2011 1712 1713 1714 12. Utilities 1715 1716 12.1. Checking References 1717 1718 "check-references.xslt" can be used to check all references to RFC- 1719 and ID-series IETF publications and to W3C publications (note this 1720 script requires local copies of 1721 <ftp://ftp.isi.edu/in-notes/rfc-index.xml> and 1722 <http://www.w3.org/2002/01/tr-automation/tr.rdf> and will use the XML 1723 status information provided at <http://tools.ietf.org/>). 1724 1725 If the document is supposed to be published on the IETF standards 1726 track, the desired level can be specified using the parameter 1727 "intended-level" as 'proposed', 'draft' or 'internet'. 1728 Alternatively, it can be specified inside the document using the 1729 attribute x:maturity-level on the <rfc> element (see Section 11.25). 1730 1731 Note: Downward references should be annotated using the <annotate> 1732 element, containing an <xref> to [BCP97]. 1733 1734 When an XSLT 2.0 processor is used, links in the document can be 1735 checked as well using the "link-check" paramerer ('yes' or 'no'). 1736 Note that this only works for http links to documents of type text/*. 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 Reschke [Page 31] 1766 1767 1768 Documentation RFC2629 through XSLT November 2011 1769 1770 1771 For instance, as of 2008-07-12, the script produces for 1772 <http://greenbytes.de/tech/webdav/rfc2518.xml>: 1773 1774 > saxon rfc2518.xml check-references.xslt intended-status=PROPOSED \ 1775 link-check=yes 1776 1777 Normative References: 1778 ISO-11578: not checked 1779 ISO-639: not checked 1780 ISO-8601: not checked 1781 REC-xml-19980210: [FirstEdition] obsoleted by REC-xml-20001006 1782 REC-xml-names-19990114: [FirstEdition] obsoleted by 1783 REC-xml-names-20060816 1784 RFC1766: [PROPOSED STANDARD] obsoleted by RFC3066 RFC3282 1785 RFC2068: [PROPOSED STANDARD] obsoleted by RFC2616 1786 RFC2069: [PROPOSED STANDARD] obsoleted by RFC2617 1787 RFC2119: [BEST CURRENT PRACTICE] (-> BCP0014) ok 1788 RFC2141: [PROPOSED STANDARD] ok 1789 RFC2277: [BEST CURRENT PRACTICE] (-> BCP0018) ok 1790 RFC2396: [DRAFT STANDARD] obsoleted by RFC3986 1791 RFC2279: [DRAFT STANDARD] obsoleted by RFC3629 1792 1793 Informational References: 1794 REC-PICS-labels-961031: [REC] ok 1795 RFC1807: [INFORMATIONAL] ok 1796 RFC2026: [BEST CURRENT PRACTICE] (-> BCP0009) ok 1797 RFC2291: [INFORMATIONAL] ok 1798 RFC2376: [INFORMATIONAL] obsoleted by RFC3023 1799 RFC2413: [INFORMATIONAL] obsoleted by RFC5013 1800 USMARC: not checked 1801 WF: not checked 1802 1803 Link Targets 1804 <http://www.w3.org/TR/1998/REC-xml-19980210>: ok 1805 <http://www.w3.org/TR/1999/REC-xml-names-19990114>: ok 1806 <http://www.dlib.org/dlib/july96/lagoze/07lagoze.html>: ok 1807 <http://www.w3.org/pub/WWW/TR/REC-PICS-labels-961031.html>: ok 1808 1809 Recognized formats in the <seriesInfo> element are: 1810 1811 o for RFCs, the name attribute must be "RFC", and the value 1812 attribute must be the number of the RFC, 1813 1814 o for Internet Drafs, the name attribute must be "ID" or "Internet- 1815 Draft", and the value attribute must be the file name of the draft 1816 (including the two-digit running number, but excluding a file 1817 extension), 1818 1819 1820 1821 1822 Reschke [Page 32] 1823 1824 1825 Documentation RFC2629 through XSLT November 2011 1826 1827 1828 o for W3C documents, the name attribute must be "W3C", must start 1829 with "W3C ", or must start with "World Wide Web Consortium ", and 1830 the value attribute must be the "shorthand" name of the 1831 specification, such as "REC-xml-19980210". 1832 1833 Note: this stylesheet will need network access to check links and 1834 status of Internet Drafts. When running a Java-based XSLT engine, 1835 you may have to supply Java system properties specifying the HTTP 1836 proxy to be used, such as "-Dhttp.proxyHost=hostname 1837 -Dhttp.proxyPort=80". 1838 1839 12.2. Generating Graphs from References 1840 1841 "gen-reference-graph.xslt" generates a graph of RFC dependencies, 1842 using the same base data as in "check-references.xslt" (see 1843 Section 12.1). Its output is a "dot" file, to be processed by 1844 GraphViz (see <http://www.graphviz.org/>). 1845 1846 The picture below shows the RFC dependencies in RFC2629. 1847 1848 1849 12.3. Producing reference entries for books 1850 1851 "amazon-asin.xslt" uses the Amazon web services to generate a 1852 <reference> element for a given ASIN (ISBN). 1853 1854 For instance: 1855 1856 <?xml version="1.0" encoding="utf-8"?> 1857 <references> 1858 <reference target="urn:isbn:0134516591"> 1859 <front> 1860 <title>Simple Book, The: An Introduction to Internet Management, 1861 Revised Second Edition</title> 1862 <author surname="Rose" 1863 fullname="Marshall T. Rose" initials="M. T. "> 1864 <organization/> 1865 </author> 1866 <author surname="Marshall" 1867 fullname="Rose T. Marshall" initials="R. T."> 1868 <organization/> 1869 </author> 1870 <date year="1996" month="March"/> 1871 </front> 1872 <seriesInfo name="Prentice Hall" value=""/> 1873 </reference> 1874 </references> 1875 1876 1877 1878 1879 Reschke [Page 33] 1880 1881 1882 Documentation RFC2629 through XSLT November 2011 1883 1884 1885 Note that the resulting XML usually requires checking, in this case 1886 Amazon's database is playing tricks with Marshall's name... 1887 1888 12.4. Down-converting to RFC2629bis DTD 1889 1890 "clean-for-DTD.xslt" can be used to down-convert some extensions to a 1891 format that is supported by the base xml2rfc distribution. Note that 1892 these extensions are experimental (feedback appreciated). 1893 1894 The following mappings are done: 1895 1896 o <iref> elements inside <artwork> elements are moved in front of 1897 the enclosing <figure> element. 1898 1899 o <xref> elements inside <artwork> are expanded just like in regular 1900 text (that is, the markup is stripped, but the element is replaced 1901 by the applicable replacement text). 1902 1903 o <x:anchor-alias> elements get stripped. 1904 1905 o <x:bcp14> elements get stripped. 1906 1907 o <x:bb>, <x:bc> and <x:bt> elements get stripped. 1908 1909 o <x:blockquote> elements get converted to indented text (through a 1910 <list> element). 1911 1912 o <x:dfn> elements get stripped. 1913 1914 o <x:h> elements get stripped. 1915 1916 o <x:link> elements get stripped. 1917 1918 o <x:lt> elements get collapsed into a single <lt> element with 1919 added <vspace> added to simulate paragraph breaks. 1920 1921 o <x:note> elements get converted to indented text (through a <list> 1922 element). 1923 1924 o <x:q> elements get stripped, with apostrophes added around the 1925 text. 1926 1927 o <x:prose> elements are transformed into <seriesInfo> elements 1928 (which is an abuse of the element and only a workaround until 1929 xml2rfc gets a matching extension). 1930 1931 o <x:ref> elements get replaced by <xref> elements, targetting 1932 either the anchor or another anchor with matching <x:anchor-alias> 1933 1934 1935 1936 Reschke [Page 34] 1937 1938 1939 Documentation RFC2629 through XSLT November 2011 1940 1941 1942 child element. 1943 1944 12.5. Extracting artwork 1945 1946 With "extract-artwork.xslt", artwork elements named through the 1947 "name" attribute can be extracted. This can be used to automatically 1948 check their syntax (for instance, when ABNFs appear within a figure 1949 element). 1950 1951 For instance: 1952 saxon rfc3986.xml extract-artwork.xslt name=uri.abnf 1953 1954 In addition, artwork of a specific type can be extracted, such as 1955 with: 1956 saxon rfc3986.xml extract-artwork.xslt type=abnf 1957 1958 When extracting by type, artwork elements with a specified name can 1959 be excluded; this can be handy when the document uses some kind of 1960 schema language, and an appendix contains the collected schema, 1961 repeating definitions from earlier on. Example: 1962 saxon rfc3986.xml extract-artwork.xslt type=abnf except-name=clschm 1963 1964 12.6. GRRDL 1965 1966 "rfc2629grddl.xslt" extracts RDF information. This is experimental 1967 work-in-progress. See <http://www.w3.org/TR/grddl/> for more 1968 information. 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 Reschke [Page 35] 1994 1995 1996 Documentation RFC2629 through XSLT November 2011 1997 1998 1999 13. Informative References 2000 2001 [BCP97] Klensin, J. and S. Hartman, "Handling Normative References 2002 to Standards-Track Documents", BCP 97, RFC 4897, 2003 June 2007. 2004 2005 [DC-HTML] Johnston, P. and A. Powell, "Expressing Dublin Core 2006 metadata using HTML/XHTML meta and link elements", Dublin 2007 Core Metadata Initiative , August 2008, 2008 <http://dublincore.org/documents/2008/08/04/dc-html/>. 2009 2010 [HTML] Raggett, D., Hors, A., and I. Jacobs, "HTML 4.01 2011 Specification", W3C REC-html401-19991224, December 1999, 2012 <http://www.w3.org/TR/html401/>. 2013 2014 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 2015 3", BCP 9, RFC 2026, October 1996. 2016 2017 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2018 Requirement Levels", BCP 14, RFC 2119, March 1997. 2019 2020 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., 2021 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 2022 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 2023 2024 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 2025 June 1999. 2026 2027 [RFC2648] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, 2028 August 1999. 2029 2030 [RFC2731] Kunze, J., "Encoding Dublin Core Metadata in HTML", 2031 RFC 2731, December 1999. 2032 2033 [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 2034 Specifications: ABNF", STD 68, RFC 5234, January 2008. 2035 2036 [RFC5741] Daigle, L. and O. Kolkman, "RFC Streams, Headers, and 2037 Boilerplates", RFC 5741, December 2009. 2038 2039 [RNC] Clark, J., "RELAX NG Compact Syntax", OASIS , Nov 2002, <h 2040 ttp://www.oasis-open.org/committees/relax-ng/ 2041 compact-20021121.html>. 2042 2043 [XHTML2] Axelsson, J., Birbeck, M., Dubinko, M., Epperson, B., 2044 Ishikawa, M., McCarron, S., Navarro, A., and S. Pemberton, 2045 "XHTML[TM] 2.0", W3C WD-xhtml2-20060726, July 2006, 2046 <http://www.w3.org/TR/xhtml2>. 2047 2048 2049 2050 Reschke [Page 36] 2051 2052 2053 Documentation RFC2629 through XSLT November 2011 2054 2055 2056 [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 2057 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth 2058 Edition)", W3C REC-xml-20081126, November 2008, 2059 <http://www.w3.org/TR/2008/REC-xml-20081126/>. 2060 2061 [XSL-FO] Berglund, A., "Extensible Stylesheet Language (XSL) 2062 Version 1.1", W3C REC-xsl11-20061205, Dec 2006, 2063 <http://www.w3.org/TR/2006/REC-xsl11-20061205/>. 2064 2065 [1] <http://www.exslt.org/exsl/functions/node-set/index.html> 2066 2067 [2] <http://www.exslt.org/date/functions/date-time/> 2068 2069 [3] <http://www.microsoft.com/downloads/ 2070 details.aspx?FamilyID=2FB55371-C94E-4373-B0E9-DB4816552E41> 2071 2072 [4] <https://addons.mozilla.org/de/firefox/addon/722> 2073 2074 [5] <https://bugzilla.mozilla.org/show_bug.cgi?id=22942> 2075 2076 [6] <http://bugzilla.mozilla.org/show_bug.cgi?id=193678> 2077 2078 [7] <https://addons.mozilla.org/firefox/2933/> 2079 2080 [8] <http://microformats.org/wiki/hcard> 2081 2082 [9] <http://www.w3.org/TR/2003/WD-xsl11-20031217/> 2083 2084 [10] <http://www.antennahouse.com/> 2085 2086 [11] <http://www.antennahouse.com/XSL20/axf-extension.htm> 2087 2088 [12] <http://xml.apache.org/fop/> 2089 2090 [13] <http://xep.xattic.com/> 2091 2092 [14] <http://xep.xattic.com/xep/spec.html> 2093 2094 [15] <http://www.thaiopensource.com/relaxng/jing.html> 2095 2096 [16] <http://dpcarlisle.blogspot.com/2007/05/ 2097 exslt-node-set-function.html> 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 Reschke [Page 37] 2108 2109 2110 Documentation RFC2629 through XSLT November 2011 2111 2112 2113 Appendix A. RELAX NG Compact Schema 2114 2115 The RelaxNG schema ([RNC]) below can be used to validate input 2116 documents (for instance, with Jing [15]). 2117 2118 _Note that this is work in progress, and doesn't yet cover all 2119 extensions completely._ 2120 2121 # WORK IN PROGRESS! PLEASE REPORT PROBLEMS TO THE AUTHOR. 2122 2123 # Define our extension namespace 2124 namespace x = "http://purl.org/net/xml2rfc/ext" 2125 2126 # Define GRDDL namespace 2127 namespace grddl = "http://www.w3.org/2003/g/data-view#" 2128 2129 # Define RDF namespace 2130 namespace rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#" 2131 2132 # Include rfc2629bis RNC grammar 2133 include "rfc2629.rnc" { 2134 2135 # Redefine <artwork> to allow markup 2136 artwork = 2137 element artwork { 2138 attlist.artwork, 2139 (TEXT 2140 | eref 2141 | iref 2142 | spanx 2143 | xref 2144 | x_abnf-char-sequence 2145 | x_bb 2146 | x_bc 2147 | x_bcp14 2148 | x_bt 2149 | x_highlight 2150 | x_length-of 2151 | x_parse-xml 2152 | x_ref 2153 | x_span 2154 | x_x)* 2155 } 2156 2157 # Redefine <back> to allow boilerplate 2158 back = 2159 element back { 2160 attlist.back, 2161 2162 2163 2164 Reschke [Page 38] 2165 2166 2167 Documentation RFC2629 through XSLT November 2011 2168 2169 2170 references*, 2171 section*, 2172 x_boilerplate? 2173 } 2174 2175 # Redefine <c> to allow our extension elements 2176 c = 2177 element c { 2178 attlist.c, 2179 (TEXT 2180 | xref 2181 | eref 2182 | iref 2183 | cref 2184 | spanx 2185 | x_ref)* 2186 } 2187 2188 # Redefine <cref> to allow more child elements 2189 cref = 2190 element cref { 2191 attlist.cref, 2192 (TEXT 2193 | eref 2194 | xref)* 2195 } 2196 2197 # Redefine <front> to allow boilerplate 2198 front = 2199 element front { 2200 attlist.front, 2201 title, 2202 author+, 2203 date, 2204 area*, 2205 workgroup*, 2206 keyword*, 2207 x_boilerplate?, 2208 abstract?, 2209 note* 2210 } 2211 2212 # Redefine <list> element to allow <x:lt> child elements 2213 \list = 2214 element list { 2215 attlist.list, 2216 (t+ | x_lt+) 2217 } 2218 2219 2220 2221 Reschke [Page 39] 2222 2223 2224 Documentation RFC2629 through XSLT November 2011 2225 2226 2227 # Redefine <preamble> to allow our extension elements 2228 preamble = 2229 element preamble { 2230 attlist.preamble, 2231 (TEXT 2232 | xref 2233 | eref 2234 | iref 2235 | cref 2236 | spanx 2237 | x_anchor-alias)* 2238 } 2239 2240 # Redefine <postamble> to allow our extension elements 2241 postamble = 2242 element postamble { 2243 attlist.postamble, 2244 (TEXT 2245 | xref 2246 | eref 2247 | iref 2248 | cref 2249 | spanx 2250 | x_bcp14)* 2251 } 2252 2253 # Redefine <reference> to allow our extension elements 2254 reference = 2255 element reference { 2256 attlist.reference, 2257 front, 2258 seriesInfo*, 2259 x_prose?, 2260 format*, 2261 annotation*, 2262 x_source? 2263 } 2264 2265 # Redefine <rfc> to allow our extension elements 2266 rfc = 2267 element rfc { 2268 attlist.rfc, 2269 x_link*, 2270 x_assign-section-number*, 2271 front, 2272 middle, 2273 back? 2274 } 2275 2276 2277 2278 Reschke [Page 40] 2279 2280 2281 Documentation RFC2629 through XSLT November 2011 2282 2283 2284 # Redefine <section> to allow our extension elements 2285 section = 2286 element section { 2287 attlist.section, 2288 (t 2289 | figure 2290 | texttable 2291 | iref 2292 | section 2293 | x_anchor-alias 2294 | x_blockquote 2295 | x_include-author 2296 | x_note 2297 | rdf_Description)* 2298 } 2299 2300 # Redefine <spanx> to allow some markup 2301 spanx = 2302 element spanx { 2303 attlist.spanx, 2304 (TEXT 2305 | iref 2306 | xref 2307 | x_ref)* 2308 } 2309 2310 # Redefine <t> to allow our extension elements 2311 t = 2312 element t { 2313 attlist.t, 2314 (TEXT 2315 | \list 2316 | figure 2317 | xref 2318 | eref 2319 | iref 2320 | cref 2321 | spanx 2322 | vspace 2323 | x_abnf-char-sequence 2324 | x_anchor-alias 2325 | x_bcp14 2326 | x_dfn 2327 | x_h 2328 | x_q 2329 | x_ref 2330 | x_sup)* 2331 } 2332 2333 2334 2335 Reschke [Page 41] 2336 2337 2338 Documentation RFC2629 through XSLT November 2011 2339 2340 2341 } 2342 2343 # Allow x:indent-with attribute on <artwork> 2344 attlist.artwork &= 2345 attribute x:indent-with { ATEXT }? 2346 2347 # Allow anchor and x:annotation attributes on <author> 2348 attlist.author &= 2349 attribute anchor { xsd:ID }?, 2350 attribute x:annotation { ATEXT }? 2351 2352 # Extend attribute set for <c> (see Section 11.23) 2353 attlist.c &= 2354 attribute anchor { xsd:ID }? 2355 2356 # Extend attribute set for <iref> (see Section 11.23) 2357 attlist.iref &= 2358 attribute x:for-anchor { ATEXT }? 2359 2360 # Extend attribute set for <list> (see Section 11.24) 2361 attlist.list &= 2362 attribute x:indent { ATEXT }? 2363 2364 # Extend attribute set for <preamble> 2365 attlist.preamble &= 2366 attribute anchor { xsd:ID }? 2367 2368 # Extend attribute set for <rfc> 2369 attlist.rfc &= 2370 attribute grddl:transformation { ATEXT }?, 2371 attribute x:maturity-level { "proposed" | "draft" | "internet" }? 2372 2373 # Extend attribute set for <section> (see Section 11.26) 2374 attlist.section &= 2375 attribute x:fixed-section-number { ATEXT }? 2376 2377 # Allow anchor attribute on <spanx> 2378 attlist.spanx &= 2379 attribute anchor { xsd:ID }? 2380 2381 # Allow x:quotes attribute on <title> 2382 attlist.title &= 2383 attribute x:quotes { "true" | "false" }? 2384 2385 # Allow annotation attribute on <uri> 2386 attlist.uri &= 2387 attribute x:annotation { ATEXT }? 2388 2389 2390 2391 2392 Reschke [Page 42] 2393 2394 2395 Documentation RFC2629 through XSLT November 2011 2396 2397 2398 # Extend attribute set for <xref> (see Section 11.27) 2399 attlist.xref &= 2400 attribute x:fmt { "()" | "," | "anchor" | "of" | "number" | "sec" | 2401 "none" }?, 2402 attribute x:rel { ATEXT }?, 2403 attribute x:sec { ATEXT }? 2404 2405 # Conversion to ABNF char sequence (see Section 11.1) 2406 x_abnf-char-sequence = 2407 element x:abnf-char-sequence { 2408 TEXT 2409 } 2410 2411 # Aliasing of anchors (see Section 11.2) 2412 x_anchor-alias = 2413 element x:anchor-alias { 2414 attribute value { TEXT }, 2415 empty 2416 } 2417 2418 # Including Author information 2419 # (experimental) 2420 x_include-author = 2421 element x:include-author { 2422 attribute target { xsd:IDREF } 2423 } 2424 2425 # Setting section numbers for internally generated sections 2426 # (experimental) 2427 x_assign-section-number = 2428 element x:assign-section-number { 2429 attribute builtin-target { "authors" }, 2430 attribute number { TEXT }, 2431 empty 2432 } 2433 2434 # Bottom line of box drawing (see Section 11.4) 2435 x_bb = 2436 element x:bb { 2437 (TEXT 2438 | iref 2439 | xref 2440 | x_bb 2441 | x_bc 2442 | x_bt 2443 | x_ref)* 2444 } 2445 2446 2447 2448 2449 Reschke [Page 43] 2450 2451 2452 Documentation RFC2629 through XSLT November 2011 2453 2454 2455 # Center line of box drawing (see Section 11.5) 2456 x_bc = 2457 element x:bc { 2458 (TEXT 2459 | iref 2460 | spanx 2461 | xref 2462 | x_bb 2463 | x_bc 2464 | x_bt 2465 | x_ref)* 2466 } 2467 2468 # BCP14/RFC2119 keywords (see Section 11.3) 2469 x_bcp14 = 2470 element x:bcp14 { 2471 "MAY" 2472 | "MUST" 2473 | "MUST NOT" 2474 | "NOT RECOMMENDED" 2475 | "OPTIONAL" 2476 | "RECOMMENDED" 2477 | "REQUIRED" 2478 | "SHALL" 2479 | "SHALL NOT" 2480 | "SHOULD" 2481 | "SHOULD NOT" 2482 } 2483 2484 # Blockquote (see Section 11.6) 2485 x_blockquote = 2486 element x:blockquote { 2487 attribute cite { URI }?, 2488 t+ 2489 } 2490 2491 # Boilerplate (see Section 11.6) 2492 x_boilerplate = 2493 element x:boilerplate { 2494 section+ 2495 } 2496 2497 # Top line of box drawing (see Section 11.8) 2498 x_bt = 2499 element x:bt { 2500 (TEXT 2501 | iref 2502 | xref 2503 2504 2505 2506 Reschke [Page 44] 2507 2508 2509 Documentation RFC2629 through XSLT November 2011 2510 2511 2512 | x_bb 2513 | x_bc 2514 | x_bt 2515 | x_ref)* 2516 } 2517 2518 # Definition (see Section 11.9) 2519 x_dfn = 2520 element x:dfn { 2521 attribute anchor { xsd:ID }?, 2522 (TEXT 2523 | iref)* 2524 } 2525 2526 # Heading (see Section 11.10) 2527 x_h = 2528 element x:h { 2529 TEXT 2530 } 2531 2532 # Heading (see Section 11.11) 2533 x_highlight = 2534 element x:highlight { 2535 TEXT 2536 } 2537 2538 # Length Measurement (see Section 11.12) 2539 x_length-of = 2540 element x:length-of { 2541 attribute indented { NUMBER }?, 2542 attribute target { xsd:IDREF }, 2543 empty 2544 } 2545 2546 # Link (see Section 11.13) 2547 x_link = 2548 element x:link { 2549 attribute basename { URI }, 2550 attribute href { URI }, 2551 attribute title { TEXT }?, 2552 attribute rel { TEXT }, 2553 empty 2554 } 2555 2556 # Extended list item (see Section 11.14) 2557 x_lt = 2558 element x:lt { 2559 attribute anchor { xsd:ID }?, 2560 2561 2562 2563 Reschke [Page 45] 2564 2565 2566 Documentation RFC2629 through XSLT November 2011 2567 2568 2569 attribute hangText { TEXT }?, 2570 t+ 2571 } 2572 2573 # Note (see Section 11.15) 2574 x_note = 2575 element x:note { 2576 t+ 2577 } 2578 2579 # Signal XML content (see Section 11.16) 2580 x_parse-xml = 2581 element x:parse-xml { 2582 (TEXT 2583 | xref)* 2584 } 2585 2586 # Inline prose in a reference (see Section 11.17) 2587 x_prose = 2588 element x:prose { 2589 TEXT 2590 } 2591 2592 # Inline quote (see Section 11.18) 2593 x_q = 2594 element x:q { 2595 TEXT 2596 } 2597 2598 # Anchor reference (see Section 11.19) 2599 x_ref = 2600 element x:ref { 2601 attribute anchor { xsd:ID }?, 2602 TEXT 2603 } 2604 2605 # source information (see Section 11.20) 2606 x_source = 2607 element x:source { 2608 attribute basename { ATEXT }?, 2609 attribute href { URI }, 2610 empty 2611 } 2612 2613 # superscript (see Section 11.21) 2614 x_sup = 2615 element x:sup { 2616 TEXT 2617 2618 2619 2620 Reschke [Page 46] 2621 2622 2623 Documentation RFC2629 through XSLT November 2011 2624 2625 2626 } 2627 2628 # Inline Span 2629 x_span = 2630 element x:span { 2631 attribute anchor { xsd:ID }?, 2632 (TEXT 2633 | x_parse-xml)* 2634 } 2635 2636 # Nop (for alignment in source) 2637 x_x = 2638 element x:x { 2639 empty 2640 } 2641 2642 # Embed RDF statements 2643 rdf_Description = 2644 element rdf:Description { 2645 rdf_content 2646 } 2647 2648 rdf_content = 2649 ( TEXT | element * { rdf_content })* 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 Reschke [Page 47] 2678 2679 2680 Documentation RFC2629 through XSLT November 2011 2681 2682 2683 Appendix B. Implementation Notes 2684 2685 B.1. Recognized type attributes for <artwork> element 2686 2687 Specific values in the <artwork> element's "type" attribute are 2688 recognized and cause a different visual style to be used: 2689 2690 +-------------------------------------+-----------------------------+ 2691 | Media Type | Comment | 2692 +-------------------------------------+-----------------------------+ 2693 | abnf | ABNF as per [RFC5234] | 2694 | | | 2695 | abnf2616 | ABNF as per [RFC2616], | 2696 | | Section 2.1 | 2697 | | | 2698 | application/relax-ng-compact-syntax | Relax NG Compact Syntax as | 2699 | | per [RNC] | 2700 | | | 2701 | application/xml-dtd | XML DTD | 2702 | | | 2703 | message/http; msgtype="request" | HTTP message, as per | 2704 | | [RFC2616], Section 19.1 | 2705 | | | 2706 | message/http; msgtype="response" | HTTP message, as per | 2707 | | [RFC2616], Section 19.1 | 2708 +-------------------------------------+-----------------------------+ 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 Reschke [Page 48] 2735 2736 2737 Documentation RFC2629 through XSLT November 2011 2738 2739 2740 Appendix C. Examples 2741 2742 C.1. Using the 'Internal Subset' 2743 2744 The prolog of the XML document can both be used to refer to an 2745 external DTD, and also to define internal entities (Section 2.8 of 2746 [XML]): 2747 2748 <?xml version="1.0"?> 2749 <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?> 2750 2751 <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ 2752 2753 <!-- use "&MAY;" for a BCP 14 "MAY", see Section 11.3 --> 2754 <!ENTITY MAY 2755 "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MAY</bcp14>"> 2756 2757 <!-- re-declare " " as code point 160 (non-breaking space) --> 2758 <!-- you may need this for UAs that do not read external DTDs --> 2759 <!ENTITY nbsp 2760 " "> 2761 2762 <!-- allow later RFC2616 reference using "&rfc2616;" --> 2763 <!-- the data will be fetched from xml.resource.org --> 2764 <!ENTITY rfc2616 PUBLIC 2765 "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2616.xml"> 2766 2767 <!-- allow a custom reference using "&mydraft;" --> 2768 <!-- the data will be fetched from the same location as the 2769 source file --> 2770 <!ENTITY mydraft PUBLIC "reference.mydraft.xml"> 2771 ]> 2772 2773 Note: including entities from a remote site will not work in Firefox, 2774 see <https://bugzilla.mozilla.org/show_bug.cgi?id=22942>. 2775 2776 C.2. Customization 2777 2778 The XSLT code can be customized by creating a custom XSLT file that 2779 uses <xsl:import> to include the original code, and just overrides 2780 particular rules. 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 Reschke [Page 49] 2792 2793 2794 Documentation RFC2629 through XSLT November 2011 2795 2796 2797 For instance, the code below overrides several attributes in 2798 "rfc2629toFO.xslt", changing the color, spacing and font family for 2799 headers. 2800 2801 <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 2802 version="1.0"> 2803 2804 <xsl:import href="rfc2629toFO.xslt"/> 2805 2806 <xsl:attribute-set name="h1"> 2807 <xsl:attribute name="color">darkblue</xsl:attribute> 2808 <xsl:attribute name="font-family">sans-serif</xsl:attribute> 2809 <xsl:attribute name="space-before">24pt</xsl:attribute> 2810 </xsl:attribute-set> 2811 2812 <xsl:attribute-set name="h2"> 2813 <xsl:attribute name="color">darkblue</xsl:attribute> 2814 <xsl:attribute name="font-family">sans-serif</xsl:attribute> 2815 <xsl:attribute name="space-before">18pt</xsl:attribute> 2816 <xsl:attribute name="space-after">3pt</xsl:attribute> 2817 </xsl:attribute-set> 2818 2819 <xsl:attribute-set name="h3"> 2820 <xsl:attribute name="color">darkblue</xsl:attribute> 2821 <xsl:attribute name="font-family">sans-serif</xsl:attribute> 2822 <xsl:attribute name="space-before">16pt</xsl:attribute> 2823 <xsl:attribute name="space-after">2pt</xsl:attribute> 2824 </xsl:attribute-set> 2825 2826 </xsl:transform> 2827 2828 Note: the name for the attribute sets may change in the future as 2829 more working is done with respect to customizability. In any 2830 case, overriding the settings in a separate file will be easier to 2831 maintain. Please contact the author if you find yourself trying 2832 to override style definitions that currently do not use attribute 2833 sets. 2834 2835 Note: the CSS style information used in "rfc2629.xslt" can be 2836 overriden in a similar (but less granular) way: just overwrite the 2837 template called "insertCss". As for XSL-FO, the class names may 2838 change in future. 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 Reschke [Page 50] 2849 2850 2851 Documentation RFC2629 through XSLT November 2011 2852 2853 2854 Appendix D. Producing the IETF 'Boilerplate' 2855 2856 Various attributes of the "<rfc>" element plus some child elements of 2857 "<front>" affect the automatically generated parts of the front page, 2858 such as the tabular information at the beginning, the "Status Of This 2859 Memo", and the "Copyright Notice". 2860 2861 When submitting an Internet Draft, this "boilerplate" is checked by 2862 "Idnits" (<http://tools.ietf.org/tools/idnits/>) for compliance with 2863 the current Intellectual Property rules, and thus it is important to 2864 set the correct values. 2865 2866 Furthermore, the RFC Production Center uses RFC2629-based tools to 2867 generate the final RFC text, so the more accurate the supplied 2868 information is, the less additional work is left, and the risk for 2869 errors in producing the final (and immutable!) document is reduced. 2870 2871 Note: this only applies to the case when IETF documents are 2872 produced. The "private" processing instruction allows to switch 2873 off most of the autogeneration logic. 2874 2875 D.1. The /rfc/@ipr Attribute 2876 2877 As of the time of this writing, this attribute value can take a long 2878 list of values. As frequently, this is not the result of a grand 2879 plan, but simply for historic reasons. Of these values, only a few 2880 are currently in use; all others are supported by the various tools 2881 for backwards compatibility with old source files. 2882 2883 Note: some variations of the boilerplate are selected based on the 2884 document's date; therefore it is important to specify the "year", 2885 "month" and "day" attributes of the "<date>" element when 2886 archiving the XML source of an Internet Draft on the day of 2887 submission. 2888 2889 _Disclaimer: THIS ONLY PROVIDES IMPLEMENTATION INFORMATION. IF YOU 2890 NEED LEGAL ADVICE, PLEASE CONTACT A LAWYER._ For further information, 2891 refer to <http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf>. 2892 2893 Finally, for the current "Status Of This Memo" text, the 2894 "submissionType" attribute determines whether a statement about "Code 2895 Components" is inserted (this is the case for the value "IETF", which 2896 also happens to be the default). Other values, such as 2897 "independent", suppress this part of the text. 2898 2899 2900 2901 2902 2903 2904 2905 Reschke [Page 51] 2906 2907 2908 Documentation RFC2629 through XSLT November 2011 2909 2910 2911 D.1.1. Current Values: '*trust200902' 2912 2913 The name for these values refers to the "TLP" ("IETF TRUST Legal 2914 Provisions Relating to IETF Documents"), on effect February 15, 2009 2915 (see <http://trustee.ietf.org/license-info/archive/ 2916 IETF-Trust-License-Policy-20090215.pdf>). Updates to this document 2917 were published on September 12, 2009 (TLP 3.0, <http:// 2918 trustee.ietf.org/license-info/archive/ 2919 IETF-Trust-License-Policy-20090912.pdf>) and on December 28, 2009 2920 (TLP 4.0, <http://trustee.ietf.org/license-info/archive/ 2921 IETF-Trust-License-Policy-20091228.pdf>), modifying the license for 2922 code components. The actual text is located in Section 6 ("Text To 2923 Be Included in IETF Documents") of these documents. 2924 2925 The tools will automatically produce the "right" text depending on 2926 the document's date information (see above): 2927 2928 +----+----------------------------------------------------+---------+ 2929 | TL | URI | startin | 2930 | P | | g with | 2931 | | | publica | 2932 | | | tion | 2933 | | | date | 2934 +----+----------------------------------------------------+---------+ 2935 | 3. | <http://trustee.ietf.org/license-info/archive/IETF | 2009-11 | 2936 | 0 | -Trust-License-Policy-20090912.pdf> | -01 | 2937 | | | | 2938 | 4. | <http://trustee.ietf.org/license-info/archive/IETF | 2010-04 | 2939 | 0 | -Trust-License-Policy-20091228.pdf> | -01 | 2940 +----+----------------------------------------------------+---------+ 2941 2942 D.1.1.1. trust200902 2943 2944 This should be the default, unless one of the more specific 2945 '*trust200902' values is a better fit. It produces the text in 2946 Sections 6.a and 6.b of the TLP. 2947 2948 D.1.1.2. noModificationTrust200902 2949 2950 This produces the additional text from Section 6.c.i of the TLP: 2951 2952 This document may not be modified, and derivative works of it may 2953 not be created, except to format it for publication as an RFC or 2954 to translate it into languages other than English. 2955 2956 Note: this clause is incompatible with RFCs to be published on the 2957 Standards Track. 2958 2959 2960 2961 2962 Reschke [Page 52] 2963 2964 2965 Documentation RFC2629 through XSLT November 2011 2966 2967 2968 D.1.1.3. noDerivativesTrust200902 2969 2970 This produces the additional text from Section 6.c.ii of the TLP: 2971 2972 This document may not be modified, and derivative works of it may 2973 not be created, and it may not be published except as an Internet- 2974 Draft. 2975 2976 Note: this clause is incompatible with RFCs to be published on the 2977 Standards Track. 2978 2979 D.1.1.4. pre5378Trust200902 2980 2981 This produces the additional text from Section 6.c.iii of the TLP, 2982 frequently called the "pre-5378 escape clause": 2983 2984 This document may contain material from IETF Documents or IETF 2985 Contributions published or made publicly available before November 2986 10, 2008. The person(s) controlling the copyright in some of this 2987 material may not have granted the IETF Trust the right to allow 2988 modifications of such material outside the IETF Standards Process. 2989 Without obtaining an adequate license from the person(s) 2990 controlling the copyright in such materials, this document may not 2991 be modified outside the IETF Standards Process, and derivative 2992 works of it may not be created outside the IETF Standards Process, 2993 except to format it for publication as an RFC or to translate it 2994 into languages other than English. 2995 2996 See Section 4 of 2997 <http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf> for further 2998 information about when to use this value. 2999 3000 Note: this text appears under "Copyright Notice", unless the 3001 document was published before November 2009, in which case it 3002 appears under "Status Of This Memo". 3003 3004 D.1.2. Historic Values 3005 3006 D.1.2.1. Historic Values: '*trust200811' 3007 3008 The attribute values "trust200811", "noModificationTrust200811" and 3009 "noDerivativesTrust200811" are similar to their "trust200902" 3010 counterparts, except that they use text specified in <http:// 3011 trustee.ietf.org/license-info/archive/ 3012 IETF-Trust-License-Policy_11-10-08.pdf>. 3013 3014 3015 3016 3017 3018 3019 Reschke [Page 53] 3020 3021 3022 Documentation RFC2629 through XSLT November 2011 3023 3024 3025 D.1.2.2. Historic Values: '*3978' 3026 3027 The attribute values "full3978", "noModification3978" and 3028 "noDerivatives3978" are similar to their counterparts above, except 3029 that they use text specified in RFC 3978 (March 2005). 3030 3031 D.1.2.3. Historic Values: '*3667' 3032 3033 The attribute values "full3667", "noModification3667" and 3034 "noDerivatives3667" are similar to their counterparts above, except 3035 that they use text specified in RFC 3667 (February 2004). 3036 3037 D.1.2.4. Historic Values: '*2026' 3038 3039 The attribute values "full2026" and "noDerivativeWorks2026" are 3040 similar to their counterparts above, except that they use text 3041 specified in RFC 2026 (October 1996). 3042 3043 The special value "none" was also used back then, and denied the IETF 3044 any rights beyond publication as Internet Draft. 3045 3046 D.2. The /rfc/@category Attribute 3047 3048 For RFCs, the "category" determines the "maturity level" (see Section 3049 4 of [RFC2026]). The allowed values are "std" for "Standards Track", 3050 "bcp" for "BCP", "info" for "Informational", "exp" for 3051 "Experimental", and "historic" for - surprise - "Historic". 3052 3053 For Internet Drafts, the category attribute is not needed, but _will_ 3054 appear on the front page ("Intended Status"). Supplying this 3055 information can be useful, because reviewers may want to know. 3056 3057 Note: the Standards Track consists of "Proposed Standard", "Draft 3058 Standards", and "Internet Standard". These do not appear in the 3059 boilerplate, thus the category attribute doesn't handle them. 3060 However, this information can be useful for validity checkers, and 3061 thus "rfc2629.xslt" supports an extension attribute for that 3062 purpose (see Section 11.25 for details). 3063 3064 D.3. The /rfc/@submissionType Attribute 3065 3066 The RFC Editor publishes documents from different "document streams", 3067 of which the "IETF stream" of course is the most prominent one. 3068 Other streams are the "independent stream" (used for things like 3069 administrative information or April 1st RFCs), the "IAB stream" 3070 (Internet Architecture Board) and the "IRTF stream" (Internet 3071 Research Task Force). 3072 3073 3074 3075 3076 Reschke [Page 54] 3077 3078 3079 Documentation RFC2629 through XSLT November 2011 3080 3081 3082 Not surprisingly, the values for the attribute are "IETF" (the 3083 default value), "independent", "IAB", and "IRTF". 3084 3085 Historically, this did not affect the final appearance of RFCs, 3086 except for subtle differences in Copyright notices. Nowadays (as of 3087 [RFC5741]), the stream name appears in the first line of the front 3088 page, and it also affects the text in the "Status Of This Memo" 3089 section. 3090 3091 For current documents, setting "submissionType" attribute will have 3092 the following effect: 3093 3094 o For RFCs, the stream name appears in the upper left corner of the 3095 first page (in Internet Drafts, this is either "Network Working 3096 Group", or the value of the "<workgroup>" element). 3097 3098 o For RFCs, if affects the whole "Status Of This Memo" section (see 3099 Section 3.2.2 of [RFC5741]). 3100 3101 o For all RFCs and Internet Drafts, it determines whether the 3102 "Copyright Notice" mentions the Copyright on Code Components (see 3103 TLP, Section "Text To Be Included in IETF Documents"). 3104 3105 D.4. The /rfc/@consensus Attribute 3106 3107 For some of the publication streams (see Appendix D.3), the "Status 3108 Of This Memo" section depends on whether there was a consensus to 3109 publish (again, see Section 3.2.2 of [RFC5741]). 3110 3111 The "consensus" attribute ("yes"/"no", defaulting to "yes") can be 3112 used to supply this information. The effect for the various streams 3113 is: 3114 3115 o "independent" and "IAB": none. 3116 3117 o "IETF": mention that there was an IETF consensus. 3118 3119 o "IRTF": mention that there was a research group consensus (where 3120 the name of the research group is extracted from the "<workgroup>" 3121 element). 3122 3123 D.5. The /rfc/@number Attribute 3124 3125 For RFCs, this attribute supplies the RFC number. 3126 3127 3128 3129 3130 3131 3132 3133 Reschke [Page 55] 3134 3135 3136 Documentation RFC2629 through XSLT November 2011 3137 3138 3139 D.6. The /rfc/@docName Attribute 3140 3141 For Internet Drafts, this specifies the draft name (which appears 3142 below the title). The file extension is _not_ part of the draft, so 3143 in general it should end with the current draft number ("-", plus two 3144 digits). 3145 3146 Note: "Idnits" (<http://tools.ietf.org/tools/idnits/>) checks the 3147 in-document draft name for consistency with the filename of the 3148 submitted document. 3149 3150 D.7. The /rfc/@obsoletes Attribute 3151 3152 The RFC Editor maintains a database 3153 (<http://www.rfc-editor.org/rfc.html>) of all RFCs, including 3154 information about which one obsoletes which. Upon publication of an 3155 RFC, this database is updated from the data on the front page. 3156 3157 This attribute takes a list of comma-separated RFC _numbers_. Do 3158 _not_ put the string "RFC" here. 3159 3160 D.8. The /rfc/@updates Attribute 3161 3162 This is like "obsoletes", but for the "updates" relation. 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 Reschke [Page 56] 3191 3192 3193 Documentation RFC2629 through XSLT November 2011 3194 3195 3196 Appendix E. License 3197 3198 Copyright (c) 2006-2010, Julian Reschke 3199 (julian.reschke@greenbytes.de) 3200 3201 All rights reserved. 3202 3203 Redistribution and use in source and binary forms, with or without 3204 modification, are permitted provided that the following conditions 3205 are met: 3206 3207 o Redistributions of source code must retain the above copyright 3208 notice, this list of conditions and the following disclaimer. 3209 3210 o Redistributions in binary form must reproduce the above copyright 3211 notice, this list of conditions and the following disclaimer in 3212 the documentation and/or other materials provided with the 3213 distribution. 3214 3215 o Neither the name of Julian Reschke nor the names of its 3216 contributors may be used to endorse or promote products derived 3217 from this software without specific prior written permission. 3218 3219 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 3220 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 3221 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 3222 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 3223 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 3224 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 3225 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 3226 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 3227 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 3228 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 3229 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 Reschke [Page 57] 3248 3249 3250 Documentation RFC2629 through XSLT November 2011 3251 3252 3253 Appendix F. Change Logs 3254 3255 F.1. Package 3256 3257 2006-01-01 Switch to BSD License. 3258 3259 2007-01-12 Update to xml2rfc v1.33pre2. 3260 3261 2007-03-31 Update to xml2rfc v1.33pre3. 3262 3263 2007-05-01 Add XSLT test cases. 3264 3265 2008-07-18 Experimental support for inlined rdf:Description elements 3266 (ignored by the formatter, extracted by rfc2629grddl). 3267 3268 2008-12-04 Update to xml2rfc v1.34pre2. 3269 3270 2009-02-24 Experimental support for February 2009 boilerplate 3271 changes, and for the x:boilerplate element. 3272 3273 2009-07-08 Support new boilerplate ordering in RFCs published since 3274 July 2009. Fix problems with one-column text tables. 3275 3276 2009-07-19 When possible, calculate the actual Expiry date for 3277 Internet Drafts (full date must be available). 3278 3279 2009-08-01 For '$xml2rfc-ext-authors-section='end'", move the index 3280 in front of the authors section. 3281 3282 2009-08-04 Consider /rfc/@ipr="pre5378Trust200902" when producing 3283 RFCs, not IDs. 3284 3285 2009-08-29 Support alignment for artwork containing images (as 3286 opposed to, well, artwork). 3287 3288 2009-09-01 Allow xref in cref (as extension). 3289 3290 2009-09-14 Refactor handling of processing instructions. 3291 3292 2009-09-24 Fix typo in Status Of This Memo, present since November 3293 2008. Fix formatting of iprExtract attribute. Starting with 3294 Internet Draft publication dates after 2009-11-30: use new Trust 3295 Legal Provisions text; for Internet Drafts: move Abstract up, and 3296 move "pre5378" escape clause to the Copyright Notice. Add support 3297 for refparent PI. For RFCs: use new TLP text as of September 3298 2009. Incorporate xml2rfc v1.34pre4. 3299 3300 3301 3302 3303 3304 Reschke [Page 58] 3305 3306 3307 Documentation RFC2629 through XSLT November 2011 3308 3309 3310 2009-10-06 Starting with Internet Draft publication dates after 3311 2009-10-31: use new Trust Legal Provisions text; for Internet 3312 Drafts: move Abstract up, and move "pre5378" escape clause to the 3313 Copyright Notice. Incorporate xml2rfc v1.34pre5. 3314 3315 2009-10-27 Upgrade to xml2rfc v1.34. 3316 3317 2010-01-08 For RFC generation (not IDs), experimentally support RFC 3318 5741 headers and boilerplate and Trust Legal Provisions 4.0. 3319 3320 2010-03-31 Upgrade to xml2rfc v1.35. 3321 3322 2010-06-27 Be consistent with xml2rfc.tcl in formatting initials 3323 (truncate after the first); see 3324 <http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10>. 3325 3326 2010-08-31 Experimental support for prose in references. 3327 3328 2011-01-27 Update to xml2rfc v1.36pre1. 3329 3330 2011-04-17 Update to xml2rfc v1.36. Add support for more /rfc/@ipr 3331 values when producing RFCs. 3332 3333 F.2. amazon-asin.xslt 3334 3335 2003-11-16 Initial release. 3336 3337 2005-04-02 Fix two DTD issues. 3338 3339 F.3. check-references.xslt 3340 3341 2003-11-16 Initial release. 3342 3343 2004-05-11 Add document status; print references type. 3344 3345 2005-01-01 Add experimental check for ID status. 3346 3347 2005-04-01 Add fixes from Bill Fenner. 3348 3349 2005-12-03 Add checks against local copy of 3350 <http://www.w3.org/2002/01/tr-automation/tr.rdf>. 3351 3352 2006-07-22 Add checks for standards levels. 3353 3354 2006-08-06 "check-ietf-references.xslt" replaced by "check- 3355 references.xslt". 3356 3357 3358 3359 3360 3361 Reschke [Page 59] 3362 3363 3364 Documentation RFC2629 through XSLT November 2011 3365 3366 3367 2007-01-04 Use information online at <http://tools.ietf.org/> to 3368 retrieve Internet-Draft status information. 3369 3370 2007-06-16 Fix bug looking up ref type when inside change markup. 3371 3372 2008-06-14 Enhance output when draft was updated, and then published 3373 as RFC. 3374 3375 2008-07-12 Add XSLT2-based link target checking. 3376 3377 2008-08-10 Change keywords for "intended-level" to proposed/draft/ 3378 internet, optionally extract intended level from /rfc/@ 3379 x:maturity-level attribute. 3380 3381 F.4. gen-reference-graph.xslt 3382 3383 2006-09-03 New. 3384 3385 2007-06-07 Use Carlisle method [16] to define exslt:node-set in 3386 msxsml (which means that the stylesheet can now be used with MSXML 3387 as well). 3388 3389 2007-10-15 Use W3C data from tr.rdf as well (experimental). 3390 3391 F.5. rfc2629.xslt 3392 3393 2001-03-28 Code rearranged, generate numbered section anchors for 3394 paragraphs (t) as well. Fixes in index handling. 3395 3396 2001-04-12 Moved HTML output into XHTML namespace. 3397 3398 2001-10-02 Fixed default location for RFCs and numbering of section 3399 references. Support ?rfc editing processing instruction. 3400 3401 2001-10-07 Made telephone number links active. 3402 3403 2001-10-08 Support for vspace element. 3404 3405 2001-10-09 Experimental support for rfc-issue PI. 3406 3407 2001-11-11 Support rfc private PI. Removed bogus code reporting the 3408 WG in the header. 3409 3410 2001-11-11 Support rfc private PI. Removed bogus code reporting the 3411 WG in the header. 3412 3413 3414 3415 3416 3417 3418 Reschke [Page 60] 3419 3420 3421 Documentation RFC2629 through XSLT November 2011 3422 3423 3424 2001-12-17 Support title attribute on references element 3425 3426 2002-01-05 Support for list/@style="@format" 3427 3428 2002-01-09 Display "closed" RFC issues as deleted 3429 3430 2002-01-14 Experimentally and optionally parse XML encountered in 3431 artwork elements (requires MSXSL). 3432 3433 2002-01-27 Some cleanup. Moved RFC issues from PIs into namespaced 3434 elements. 3435 3436 2002-01-29 Added support for sortrefs PI. Added support for figure 3437 names. 3438 3439 2002-02-07 Highlight parts of artwork which are too wide (72 3440 characters). 3441 3442 2002-02-12 Code rearrangement for static texts. Fixes for section 3443 numbering. TOC generation rewritten. 3444 3445 2002-02-15 Support for irefs in sections; support iref @primary=true 3446 3447 2002-03-03 Moved anchor prefix into a constant. Added sanity checks 3448 on user anchor names. 3449 3450 2002-03-23 Bugfix in detection of matching org names when creating 3451 the header. Fixed sorting in subitems. 3452 3453 2002-04-02 Fix TOC link HTML generation when no TOC is generated 3454 (created broken HTML table code). 3455 3456 2002-04-03 Made rendering of references more tolerant re: missing 3457 parts. 3458 3459 2002-04-08 Fixed reference numbering when references are split into 3460 separate sections. 3461 3462 2002-04-16 Fix default namespace (shouldn't be set for HTML output 3463 method). 3464 3465 2002-04-19 Lowercase internal CSS selectors for Mozilla compliance. 3466 Do not put TOC into ul element. 3467 3468 2002-04-21 Make numbered list inside numbered lists use alphanumeric 3469 numbering. 3470 3471 3472 3473 3474 3475 Reschke [Page 61] 3476 3477 3478 Documentation RFC2629 through XSLT November 2011 3479 3480 3481 2002-05-05 Updated issue/editing support. 3482 3483 2002-05-15 Bugfix for section numbering after introduction of ed: 3484 replace 3485 3486 2002-06-21 When producing private documents, do not include document 3487 status, copyright etc. 3488 3489 2002-07-08 Fix xrefs to Appendices. 3490 3491 2002-07-19 Make artwork lightyellow for easier reading. (fielding) 3492 3493 2002-10-09 Translate references title to anchor name to avoid non- 3494 uri characters. (fielding) 3495 3496 2002-10-13 Support for tocdepth PI. 3497 3498 2002-11-03 Added temporariry workaround for Mozilla/Transformiix 3499 result tree fragment problem. (search for 3500 'http://bugzilla.mozilla.org/show_bug.cgi?id=143668') 3501 3502 2002-12-25 xref code: attempt to uppercase "section" and "appendix" 3503 when at the start of a sentence. 3504 3505 2003-02-02 fixed code for vspace blankLines="0", enhanced display 3506 for list with "format" style, got rid of HTML blockquote elements, 3507 added support for "hangIndent" 3508 3509 2003-04-10 experimental support for appendix and spanx elements 3510 3511 2003-04-19 fixed counting of list numbers in "format %" styles (one 3512 counter per unique format string). Added more spanx styles. 3513 3514 2003-05-02 experimental texttable support 3515 3516 2003-05-02 Make mailto links optional (default = none) (jre: default 3517 and PI name changed) (fielding) 3518 3519 2003-05-04 experimental support for HTML link elements; fix default 3520 for table header alignment default 3521 3522 2003-05-06 support for "background" PI. 3523 3524 2003-05-11 change %c format to lowercase alphabetic. add support for 3525 keyword elements (generate META tag). fix various HTML conformance 3526 problems. added experimental support for role attribute. do not 3527 number paragraphs in unnumbered sections. update boilerplate 3528 texts. support for "iprnotified" PI. bugfix list numbering. strip 3529 3530 3531 3532 Reschke [Page 62] 3533 3534 3535 Documentation RFC2629 through XSLT November 2011 3536 3537 3538 whitespace when building tel: URIs. 3539 3540 2003-05-12 more conformance fixes (layout moved into CSS, move lists 3541 and figures out of para content, do not use tables for list 3542 formatting) 3543 3544 2003-05-13 add DC.Creator meta tag, refactoring 3545 3546 2003-05-16 put nbsps between "section" and section number (xref). 3547 3548 2003-05-18 author summary: add missing comma. 3549 3550 2003-06-06 fix index generation bug (transposed characters in key 3551 generation). Enhance sentence start detection (xref starting a 3552 section was using lowercase "section"). 3553 3554 2003-06-22 exp. support for xref/@format. Add missing support for 3555 eref w/o content. exp. support for annotations in reference 3556 elements. Code cleanup reference table formatting. 3557 3558 2003-07-09 Another fix for DC.Creator meta tag creation based on 3559 RFC2731 3560 3561 2003-07-24 Fix namespace name for DC.Creator. 3562 3563 2003-08-06 Cleanup node-set support (only use exslt (saxon, xalan, 3564 libxslt) extension functions; remove Transformix workarounds that 3565 stopped to work in Moz 1.4) 3566 3567 2003-08-09 Generate HTML lang tag. 3568 3569 2003-08-10 Map spanx/verb to HTML "samp" element. Fix author name 3570 display in references (reverse surname/initials for last author), 3571 add "Ed.". Fix internal bookmark generation. 3572 3573 2003-08-17 Add DCMI dates, identifiers and abstract. Add PI to 3574 suppress DCMI generation. Do not add TOC entry to Copyright 3575 Statement when there is none. Align RFC2629 PI names and 3576 parameter names. Change style for inline URIs generated by eref. 3577 Add header and footer support. Enhance CSS paging properties. 3578 Support topblock PI. Added hooks for proper XHTML generation 3579 through separate XSLT. Enhance warning and error messages. Add 3580 support for artwork image display. Table formatting fixes 3581 (borders, thead continuation). 3582 3583 3584 3585 3586 3587 3588 3589 Reschke [Page 63] 3590 3591 3592 Documentation RFC2629 through XSLT November 2011 3593 3594 3595 2003-08-18 Add workaround for MSXML4 node-set and Mozilla node-set 3596 issues (fallback just displays are warning). 3597 3598 2003-10-06 Add workaround for broken pre/ins handling in Mozilla 3599 (see <http://bugzilla.mozilla.org/show_bug.cgi?id=204401>). Make 3600 use of cite attribute on ed:replace. CSS cleanup. 3601 3602 2003-10-08 Fix minor issue detecting the same org for the header 3603 (caused by IE's non-standard whitespace handling). Fix default 3604 handling for /rfc/@category. 3605 3606 2003-11-09 Inherit ed:entered-by from ancestor elements. Change CSS 3607 color for inserted text to green. Generate issues-list anchor. 3608 Do not complain about missing targets when the xref element is 3609 below ed:del. Remove code that attempted to distinguish section/ 3610 Section when producing links - always use uppercase. Fix date 3611 rendering for issue resolutions. 3612 3613 2003-11-29 Fix color values for table backgrounds for issue 3614 rendering. Change rendering of issue links to use inline-styles. 3615 Add colored issue markers to issues. 3616 3617 2003-12-13 Fix inheritance of ed:entered-by attribute. Display note 3618 elements inside change tracking as well. 3619 3620 2004-01-18 When PI compact = 'yes', make most CSS print page breaks 3621 conditional. 3622 3623 2004-02-20 Support for RFC3667 IPR changes (xml2rfc 1.22); see <http 3624 ://lists.xml.resource.org/pipermail/xml2rfc/2004-February/ 3625 001088.html>. 3626 3627 2004-03-11 Add "(if approved)" to "updates" and "obsoletes" unless 3628 the document has an RFC number. 3629 3630 2004-04-01 Fix RFC3667 output, see <http://lists.xml.resource.org/ 3631 pipermail/xml2rfc/2004-April/001208.html>. 3632 3633 2004-04-04 Add support for section/top attribute. Move references 3634 into plain section container. 3635 3636 2004-04-06 Do not emit identical para anchors for deleted content. 3637 3638 2004-04-14 Fix references TOC generation when there are no 3639 references. 3640 3641 3642 3643 3644 3645 3646 Reschke [Page 64] 3647 3648 3649 Documentation RFC2629 through XSLT November 2011 3650 3651 3652 2004-04-24 Fix RFC3667 output, see 3653 <http://xml.resource.org/pipermail/xml2rfc/2004-April/ 3654 001246.html>. 3655 3656 2004-05-09 Add custom support for generating compound index 3657 documents. Add anchors for each Index letter. Add experimental 3658 cref support. Fix conditional page breaks before References 3659 section. 3660 3661 2004-05-16 Refactor external index generation. 3662 3663 2004-05-20 Rewrite anchor generation for comments. 3664 3665 2004-05-22 Enhance issues rendering (add links to changes). 3666 3667 2004-05-30 Allow single quote as delimiter in processing 3668 instructions as well. Move block-level issue pointers to floats. 3669 Disable issue pointers for print media. Add "purple numbers". 3670 Add hrefs to section headings. Add non-printing index key letter 3671 list to start of index. 3672 3673 2004-06-01 Use ¶ instead of # for PNs. 3674 3675 2004-07-18 Add support for list style=letters (thanks Roy F.). Make 3676 PNs optional; add new PI. 3677 3678 2004-09-05 Fix index links into unnumbered sections. Bring IPR 3679 boilerplate in-line with xml2rfc 1.25. Add experimental CSS3 3680 paged media support. Various HTML fixes. 3681 3682 2004-09-21 Enhance checking of artwork width. 3683 3684 2004-09-26 Add check for unused references. Uppercase letters in 3685 list style letters when nested into another list. 3686 3687 2004-10-10 Fix internal change track pointers. 3688 3689 2004-11-01 Allow change tracking on references (as a whole). 3690 Rewrite artwork handling so that it allows change tracking inside 3691 artwork. Also allow a subset of text markup inside artwork, such 3692 as xrefs (note this requires post-processing the source to make it 3693 compliant to RFC2629bis). 3694 3695 2004-11-03 Enhanced placement of iref anchors. 3696 3697 3698 3699 3700 3701 3702 3703 Reschke [Page 65] 3704 3705 3706 Documentation RFC2629 through XSLT November 2011 3707 3708 3709 2004-11-06 Index: display irefs that appeared (with primary=true) 3710 inside artwork elements in a monospaced font. 3711 3712 2004-11-14 Add special code so that changes in section titles can be 3713 change-tracked. 3714 3715 2005-01-14 Bugfixes for HtmlToXhtml converter. 3716 3717 2005-01-22 Enhance generation of HTML h* elements (for Mozilla 3718 Outliner). 3719 3720 2005-01-31 Put vertical space around top-level TOC entries in TOC. 3721 Switch to pt-based CSS. Re-arrange top section. Make hr elements 3722 reflect new-page settings in TXT output (compact-PI). Fix page 3723 number in footer (CSS print) and add some more experimental 3724 support for paged media (tested with Prince 4.1 alpha). Rewrite 3725 TOC and Index generation to generate HTML lists. Cleanup id 3726 generation for paragraphs. Reduce whitespace in output. Fix 3727 vspace implementation. Use right/left dqoutes and copyright sign 3728 where appropriate. 3729 3730 2005-02-04 Add <link> element to references section. Fix newly 3731 introduced bug in references processing. 3732 3733 2005-02-05 Integrate various fixes/enhancements by Roy Fielding: 3734 spelling of "Authors' Addresses", comma setting in references, 3735 position of "Authors" section, optionally place authors addresses 3736 at end (PI), trailing dots in section numbers, switch to verdana 3737 default font in CSS. Add experimental support for centered 3738 artwork. 3739 3740 2005-02-09 Fixes in spacing and links of references section titles. 3741 Enhance sorting in references when change tracking is in place. 3742 Re-add figure centering support. Add missing 2nd part of 3743 "Author's Adresses" fix. 3744 3745 2005-02-25 Align section number format with xml2rfc1.29. 3746 3747 2005-03-28 Get rid of table elements in Author's section. Add 3748 experimental hCard (<http://developers.technorati.com/wiki/hCard>) 3749 support. 3750 3751 2005-04-03 Add RFC3978-style IPR statement support. 3752 (fenner@research.att.com) 3753 3754 3755 3756 3757 3758 3759 3760 Reschke [Page 66] 3761 3762 3763 Documentation RFC2629 through XSLT November 2011 3764 3765 3766 2005-04-11 Cleanup author display. hCard related fixes. 3767 3768 2005-05-07 Minor fixes to allow change tracking in doc title. Add 3769 experimental support for table border styles. CSS cleanup. 3770 3771 2005-06-18 Implement missing support for references to texttables. 3772 3773 2005-09-25 Use (-moz-)column-count when printing the index. 3774 3775 2005-10-04 Report missing element templates with xsl:message. 3776 3777 2005-10-15 Process t/@anchor. 3778 3779 2005-10-23 More workarounds for Mozilla's broken del/ins handling 3780 (this time for figures). 3781 3782 2005-10-27 lowercase hCard class names 3783 3784 2005-11-22 Enhance diagnostics for XML-in-artwork extension 3785 3786 2005-11-26 Fix formatting of section numbers for sections inserted 3787 into <back>. 3788 3789 2005-12-12 Fix some validity problems when change tracking occured 3790 inside lists. 3791 3792 2005-12-18 Add change tracking inside the index. 3793 3794 2006-02-04 Add prev/next links to highlighted changes (change 3795 tracking extension). 3796 3797 2006-02-10 Catch errors instantiating MSXML component. 3798 3799 2006-02-11 References: add "work in progress" for Internet Drafts. 3800 3801 2006-02-27 Fix front matter (lowercase Internet-Draft, say "Intended 3802 status" for non-RFC documents). Start work on experimental 3803 extension for simplified internal links. 3804 3805 2006-03-19 Tweaks to IESG Copyright stuff; support submissionType 3806 attribute. Fix duplicate reference anchors in HTML output. 3807 Reduce HTML Tidy warnings. Fix reference to normative ASCII 3808 version (now requires trailing ".txt"). Tweaks to hCard 3809 generation. Started to move non-issue-tracking extensions into 3810 namespace "http://purl.org/net/xml2rfc/ext". 3811 3812 3813 3814 3815 3816 3817 Reschke [Page 67] 3818 3819 3820 Documentation RFC2629 through XSLT November 2011 3821 3822 3823 2006-03-27 Moved "simple reference" extension into namespace 3824 "http://purl.org/net/xml2rfc/ext" and add documentation. HTML 3825 conformance enhancements. 3826 3827 2006-04-02 Cleanup special code for automated XHTML XSLT generation. 3828 3829 2006-04-21 Generate <CITE> elements where appropiate. Introduce 3830 x:blockquote, x:dfn, x:h and x:q elements. 3831 3832 2006-05-06 Introduce x:bcp14 element. 3833 3834 2006-05-14 Fix content model for x:blockquote. 3835 3836 2006-06-18 Add box drawing support (x:bt, x:bc, x:bb). 3837 3838 2006-06-20 HTML validity fixes (legal chars in anchors in index). 3839 3840 2006-06-24 Reduce leading empty lines in artwork. Move <dt> style 3841 info into CSS. 3842 3843 2006-07-14 Fix rendering of multiple street address entries (missing 3844 line break). 3845 3846 2006-07-24 Add extension for deep linking into RFCs, do not generate 3847 empty list items in TOC output, avoid empty <dt> elements for list 3848 items without hangText attribute. 3849 3850 2006-08-01 Allow @anchor on more elements; start work on Relax NG 3851 grammar for extensions. Reduce generated style elements (use CSS 3852 classes instead). Consistently use "id" instead of "name". 3853 Change default target for RFC links to 3854 "http://tools.ietf.org/html/rfcNNNN". 3855 3856 2006-08-06 Include appendices defined in <appendix> elements in TOC 3857 (please consider them deprecated anyhow!). Generate links to 3858 "http://tools.ietf.org/html/draft-*" for Internet Drafts. Replace 3859 x:frag by x:rel, allowing any kind of relative reference instead 3860 of just fragments. 3861 3862 2006-08-30 Reduce textual differences between HTML output and what 3863 xml2rfc produces in TXT output mode (section refs/reference 3864 targets). Add small workaround for Opera 9.0.1's problem with 3865 node-set(). 3866 3867 2006-10-29 Fix problem generating internal links to change markup 3868 within references section. Enhancements when generating numbered 3869 references for deleted references. Allow inclusion of references 3870 into the index (through include-references-in-index extension). 3871 3872 3873 3874 Reschke [Page 68] 3875 3876 3877 Documentation RFC2629 through XSLT November 2011 3878 3879 3880 Fix a bug that caused the newer version of the IETF boilerplate to 3881 be produced rather than the pre-RFC3667 one. Update to RFC4287 3882 boilerplate. 3883 3884 2006-11-11 Add extension attribute x:for-anchor to <iref> handling. 3885 3886 2006-11-26 Experimental (and limited) support for <x:lt>. 3887 3888 2006-12-04 Fix bugs in processing documents that have both the ipr 3889 and the number attribute set on the rfc root element. Add support 3890 for x:fmt='none' on xrefs. Add different pre style based on 3891 artwork type attributes (experimental). 3892 3893 2006-12-13 Add x:fmt='anchor' for xref elements. 3894 3895 2007-01-07 Fix root template for compatibility for the exslt:node- 3896 set implementation in Firefox3. 3897 3898 2007-01-29 Avoid empty table entry in front matter when organization 3899 is not specified for an author. 3900 3901 2007-02-10 Allow change tracking in table rows. 3902 3903 2007-03-09 Add hcard profile URI (<http://www.w3.org/2006/03/hcard>) 3904 to head element. Add warning for misplaced <t> elements (after 3905 section). 3906 3907 2007-03-21 Fix internal linking from reference entries in index for 3908 some xref types. Minor CSS tweaks contributed by MTR. Allow 3909 turning on text justification through a PI. Improve iref anchor 3910 generation to generate less instable anchors. 3911 3912 2007-03-28 Fixes for numbering of ed:inserted references sections. 3913 3914 2007-05-04 Do not generate anchors for edits in deleted sections. 3915 Enhance HTML conformance. 3916 3917 2007-05-19 Enhance diagnostics when using Saxon (needs Saxon's "-l" 3918 command line parameter to keep line number information). Add 3919 warning when symref PI is missing (default will change in the 3920 future). Add support for overriding computed section numbers 3921 (when formatting historic documents). 3922 3923 2007-06-07 Change default for symrefs PI to "yes" (see change in 3924 xml2rfc 1.33pre4). Warn about docName attributes that appear to 3925 contain a file extension. 3926 3927 3928 3929 3930 3931 Reschke [Page 69] 3932 3933 3934 Documentation RFC2629 through XSLT November 2011 3935 3936 3937 2007-06-26 Workaround author/@initials values without trailing dot, 3938 as in xml2rfc.tcl. 3939 3940 2007-07-14 Enhance index generation for references that use @x:sec 3941 attribute. 3942 3943 2007-09-09 Fix: sortrefs is a nop when symrefs=no. 3944 3945 2007-10-17 Work in progress: add support for referencing sections in 3946 sibling documents by anchor name. 3947 3948 2007-10-17 Work in progress (continued): support for referencing 3949 sections in sibling documents by anchor name. 3950 3951 2007-12-31 Emit warning when updating/obsoleting stuff that's not 3952 referenced. 3953 3954 2008-02-03 Support xml2rfc-1.33pre5's suppress-title attribute on 3955 texttable and figure. 3956 3957 2008-02-06 Extension: allow <eref> below <cref>. 3958 3959 2008-02-17 Extensions: add x:span and x:length-of. 3960 3961 2008-02-20 Add new RFC boilerplate (as changed in 2007-08). 3962 3963 2008-02-27 Improve diagnostics for artwork width problems; add 3964 defaulting of publication dates (requires XSLT processor 3965 supporting exslt:date, or msxml). 3966 3967 2008-02-29 Enhance CSS for link elements in the front header, update 3968 rules for generating "Acknowledgment" statement. 3969 3970 2008-03-01 Use line numbers in diagnostics in Saxon8/9 as well. 3971 3972 2008-03-02 Fix a bug in the logic choosing the boilerplate, 3973 resulting in obsolete text being inserted into IDs. 3974 3975 2008-04-01 Add support for superscript element. 3976 3977 2008-06-28 Add sanity checks for email addresses, allow multiple 3978 email elements. 3979 3980 2008-07-06 Add x:abnf-char-sequence. 3981 3982 3983 3984 3985 3986 3987 3988 Reschke [Page 70] 3989 3990 3991 Documentation RFC2629 through XSLT November 2011 3992 3993 3994 2008-08-21 Add x:note. 3995 3996 2008-09-06 Add experimental support for SVG images. 3997 3998 2008-09-17 Add experimental support for x:author. Fix xref/@ 3999 format=none. 4000 4001 2008-10-10 Fix a huge bug, causing text content after an XML comment 4002 to be ignored. 4003 4004 2009-02-24 Use table/caption when needed. 4005 4006 2009-03-07 Fix bug that caused text to disappear in the output in 4007 presence of processing instructions. 4008 4009 2009-03-12 Make inlined comments bookmarkable. 4010 4011 2009-04-09 Upgrade to DC-HTML from RFC 2731 (affects head/@profile). 4012 4013 2009-07-08 Remove table/@summary in output; the value getting 4014 inserted was just repeating stuff that appeared in the preamble. 4015 4016 2009-08-01 Implement table alignment (HTML output only for now). 4017 4018 2009-08-18 Replicate Dublin Core "abstract" metadata into meta/@ 4019 name=description (search engines do use it). 4020 4021 2009-09-02 Fix default/left alignment of table columns, remove silly 4022 table summmary attributes. 4023 4024 2009-09-24 Support double-sided layout using CSS page:left/right 4025 selectors. 4026 4027 2009-11-27 Generate unordered lists instead of broken definition 4028 lists for list style empty. 4029 4030 F.6. rfc2629toFO.xslt 4031 4032 2003-11-16 Initial release. 4033 4034 2003-11-29 Enhance handling of unknown list styles. 4035 4036 2004-04-04 Update reference section handling. 4037 4038 2004-04-17 Use XSL-WD-1.1-style fo:bookmark and index handling and 4039 add postprocessors for existing implementations. Unify PDF info 4040 generation by using XEP (postprocessors) will convert. 4041 4042 4043 4044 4045 Reschke [Page 71] 4046 4047 4048 Documentation RFC2629 through XSLT November 2011 4049 4050 4051 2004-04-20 Add experimental cref support. 4052 4053 2004-06-14 Set correct index-item defaults. 4054 4055 2004-07-18 Add list style=letters. 4056 4057 2004-09-03 Make URLs in text break where they are allowed to break 4058 by inserting zero-width spaces. 4059 4060 2004-09-26 Fix letter-style inside nested lists. 4061 4062 2004-10-31 Update handling of artwork. 4063 4064 2004-11-13 Fix handling of references inside ed:* markup. Fix 4065 whitespace handling in artwork. 4066 4067 2004-11-27 Irefs in artwork generate monospaced entries in index. 4068 4069 2005-01-31 Fix TOC generation that was broken after changes in main 4070 XSLT. 4071 4072 2005-02-05 Bring in sync with cosmetic changes in rfc2629.xslt. 4073 4074 2005-05-07 Minor fix for change tracking in document title. Support 4075 for table styles. 4076 4077 2005-06-18 Fix references to tables. 4078 4079 2005-10-15 Process t/@anchor. 4080 4081 2006-02-11 References: add "work in progress" for Internet Drafts. 4082 4083 2006-06-02 Use XSL 1.1 WD Feb 2006. 4084 4085 2007-03-21 Support optional text justification. 4086 4087 2007-05-19 Various improvements in spacing; also allow overriding 4088 the automatic list indentation via list/x:indent. 4089 4090 2009-04-08 Fix spacing in headers; add support for formatting for 4091 double-sided printing. 4092 4093 2009-08-01 Remove surplus empty pages when not generating double- 4094 sided output. 4095 4096 4097 4098 4099 4100 4101 4102 Reschke [Page 72] 4103 4104 4105 Documentation RFC2629 through XSLT November 2011 4106 4107 4108 F.7. xsl11toAn.xslt 4109 4110 2004-05-17 Initial release. 4111 4112 2006-06-02 Use XSL 1.1 WD Feb 2006. 4113 4114 F.8. xsl11toFop.xslt 4115 4116 2010-08-25 Switch to Apache FOP 1.0. 4117 4118 2009-09-12 Support for FOP 0.20.5 and FOP 0.93 removed. Please use 4119 FOP 0.95. 4120 4121 2008-03-15 Add a workaround to the fo:inline workaround (sigh). 4122 4123 F.9. xsl11toXep.xslt 4124 4125 2004-05-17 Initial release. 4126 4127 2004-09-04 Fix xep:index-item attributes. 4128 4129 2006-06-02 Use XSL 1.1 WD Feb 2006. 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 Reschke [Page 73] 4160 4161 4162 Documentation RFC2629 through XSLT November 2011 4163 4164 4165 Index 4166 4167 A 4168 abnf-char-sequence Extension Element 24, 38 4169 allow-markup-in-artwork PI pseudo-attribute 9 4170 alternate HTML LINK element 17 4171 anchor-alias Extension Element 24, 38 4172 Anchors 4173 rfc.abstract 14 4174 rfc.authors 14 4175 rfc.copyright 14 4176 rfc.copyrightnotice 14 4177 rfc.figure.n 14 4178 rfc.figure.u.n 14 4179 rfc.index 14 4180 rfc.ipr 14 4181 rfc.iref.n 14 4182 rfc.note.n 14 4183 rfc.references 14 4184 rfc.section.n 14 4185 rfc.section.n.p.m 14 4186 rfc.status 14 4187 rfc.toc 14 4188 rfc.xref.name.n 14 4189 AntennaHouse XSL Formatter 21 4190 Apache FOP 21 4191 appendix HTML LINK element 17 4192 assign-section-number Extension Element 38 4193 author HTML LINK element 17 4194 authors-section PI pseudo-attribute 9 4195 4196 B 4197 background PI pseudo-attribute 7 4198 bb Extension Element 25, 38 4199 bc Extension Element 25, 38 4200 bcp14 Extension Element 24, 38 4201 blockquote Extension Element 25, 38 4202 boilerplate Extension Element 25, 38 4203 bt Extension Element 26, 38 4204 4205 C 4206 chapter HTML LINK element 17 4207 CHM format 20 4208 comments PI pseudo-attribute 7 4209 compact PI pseudo-attribute 7 4210 contents HTML LINK element 17 4211 copyright HTML LINK element 17 4212 Creator DCMI property 18 4213 4214 4215 4216 Reschke [Page 74] 4217 4218 4219 Documentation RFC2629 through XSLT November 2011 4220 4221 4222 D 4223 Date.Issued DCMI property 18 4224 DCMI properties 4225 Creator 18 4226 Date.Issued 18 4227 Description.Abstract 18 4228 Identifier 18 4229 isPartOf 18 4230 Relation.Replaces 18 4231 Description.Abstract DCMI property 18 4232 dfn Extension Element 26, 38 4233 duplex PI pseudo-attribute 9 4234 4235 E 4236 editing PI pseudo-attribute 7 4237 Extension Elements 4238 abnf-char-sequence 24, 38 4239 anchor-alias 24, 38 4240 assign-section-number 38 4241 bb 25, 38 4242 bc 25, 38 4243 bcp14 24, 38 4244 blockquote 25, 38 4245 boilerplate 25, 38 4246 bt 26, 38 4247 dfn 26, 38 4248 h 26, 38 4249 highlight 26, 38 4250 include-author 38 4251 length-of 26, 38 4252 link 26, 38 4253 lt 27, 38 4254 note 27, 38 4255 parse-xml 27, 38 4256 prose 27, 38 4257 q 27, 38 4258 rdf:Description 38 4259 ref 27, 38 4260 source 28, 38 4261 span 38 4262 sup 28, 38 4263 x 38 4264 4265 F 4266 Firefox 4267 1.*/2.* 16 4268 3.* 15 4269 footer PI pseudo-attribute 7 4270 4271 4272 4273 Reschke [Page 75] 4274 4275 4276 Documentation RFC2629 through XSLT November 2011 4277 4278 4279 G 4280 generator HTML META element 18 4281 Google Chrome 16 4282 Grammar 38 4283 4284 H 4285 h Extension Element 26, 38 4286 header PI pseudo-attribute 7 4287 highlight Extension Element 26, 38 4288 HTML compliance 17 4289 HTML LINK elements 4290 alternate 17 4291 appendix 17 4292 author 17 4293 chapter 17 4294 contents 17 4295 copyright 17 4296 index 17 4297 HTML META elements 4298 generator 18 4299 keywords 18 4300 4301 I 4302 Identifier DCMI property 18 4303 include PI pseudo-attribute 8 4304 include-author Extension Element 38 4305 include-index PI pseudo-attribute 9 4306 include-references-in-index PI pseudo-attribute 9 4307 index HTML LINK element 17 4308 inline PI pseudo-attribute 7 4309 Internet Explorer 5.5 15 4310 Internet Explorer 6 15 4311 Internet Explorer 7 15 4312 Internet Explorer 8 15 4313 Internet Explorer 9 15 4314 iprnotified PI pseudo-attribute 7 4315 isPartOf DCMI property 18 4316 4317 J 4318 justification PI pseudo-attribute 9 4319 4320 K 4321 keywords HTML META element 18 4322 4323 L 4324 length-of Extension Element 26, 38 4325 link Extension Element 26, 38 4326 linkmailto PI pseudo-attribute 7 4327 4328 4329 4330 Reschke [Page 76] 4331 4332 4333 Documentation RFC2629 through XSLT November 2011 4334 4335 4336 lt Extension Element 27, 38 4337 4338 M 4339 Microsoft Help 20 4340 Mozilla 15-16 4341 MSXML3 15 4342 MSXML4 15 4343 4344 N 4345 needLines PI pseudo-attribute 8 4346 NoScript 15 4347 note Extension Element 27, 38 4348 4349 O 4350 Opera 16 4351 4352 P 4353 Parameters 4354 xml2rfc-background 7 4355 xml2rfc-comments 7 4356 xml2rfc-compact 7 4357 xml2rfc-editing 7 4358 xml2rfc-ext-allow-markup-in-artwork 9 4359 xml2rfc-ext-authors-section 9 4360 xml2rfc-ext-duplex 9 4361 xml2rfc-ext-include-index 9 4362 xml2rfc-ext-include-references-in-index 9 4363 xml2rfc-ext-justification 9 4364 xml2rfc-ext-parse-xml-in-artwork 9 4365 xml2rfc-ext-sec-no-trailing-dots 9 4366 xml2rfc-ext-support-rfc2731 9 4367 xml2rfc-footer 7 4368 xml2rfc-header 7 4369 xml2rfc-inline 7 4370 xml2rfc-iprnotified 7 4371 xml2rfc-linkmailto 7 4372 xml2rfc-private 7 4373 xml2rfc-refparent 7 4374 xml2rfc-rfcedstyle 7 4375 xml2rfc-sortrefs 7 4376 xml2rfc-symrefs 7 4377 xml2rfc-toc 7 4378 xml2rfc-tocdepth 7 4379 xml2rfc-topblock 7 4380 parse-xml Extension Element 27, 38 4381 parse-xml-in-artwork PI pseudo-attribute 9 4382 private PI pseudo-attribute 7, 51 4383 Processing Instruction pseudo attributes 4384 4385 4386