source: rfc2629xslt/rfc2629xslt.xml @ 1103

Last change on this file since 1103 was 1103, checked in by julian.reschke@…, 9 years ago

Upgrade to latest version of rfc2629.xslt and xml2rfc.tcl; bump up document dates

  • Property svn:eol-style set to native
File size: 136.0 KB
Line 
1<?xml version="1.0" encoding="utf-8"?>
2<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
3
4<?rfc header="Documentation"?>
5<?rfc private="RFC2629 through XSLT"?>
6<?rfc toc="yes"?>
7<!-- <?rfc topblock="no"?>  -->
8<?rfc strict="yes"?>
9<?rfc symrefs="yes"?>
10<?rfc sortrefs="yes"?>
11<?rfc-ext allow-markup-in-artwork="yes" ?>
12<?rfc-ext include-references-in-index="yes" ?>
13
14<rfc xmlns:x="http://purl.org/net/xml2rfc/ext">
15        <front>
16        <title abbrev="RFC2629 through XSLT">Transforming RFC2629-formatted XML through XSLT</title>
17
18        <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke">
19                <organization abbrev="greenbytes">greenbytes GmbH</organization>
20        <address>
21                <postal>
22                <street>Hafenweg 16</street>
23            <city>Muenster</city><region>NW</region><code>48155</code>
24                <country>Germany</country>
25                </postal>
26                  <phone>+49 251 2807760</phone>       
27                  <email>julian.reschke@greenbytes.de</email>   
28                  <uri>http://greenbytes.de/tech/webdav/</uri> 
29                </address>
30        </author>
31     
32    <date month="January" year="2011"/>
33
34    <keyword>RFC2629</keyword>
35    <keyword>xml2rfc</keyword>
36    <keyword>XSLT</keyword>
37    <keyword>hCard</keyword>
38    <keyword>XSL-FO</keyword>
39    <keyword>PDF</keyword>
40    <keyword>GRDDL</keyword>
41    <keyword>epub</keyword>
42    <keyword>Dublin Core</keyword>
43        </front>
44
45        <middle>
46
47<section title="Introduction">
48<t>
49  This document describes a set of XSLT transformations that can be used to
50  transform RFC2629-compliant XML (see <xref target="RFC2629"/>) to various
51  output formats, such as HTML and PDF. The main topics are 
52  <list style="symbols">
53    <t>compliance to the xml2rfc XML element set (<xref target="supported.elements"/>),</t>
54    <t>support for xml2rfc processing instructions (<xref target="processing.instructions"/>),</t>
55    <t>the names of anchor elements generated in HTML and PDF output (<xref target="anchors"/>),</t>
56    <t>various XSLT engines that can be used (<xref target="xslt.engines"/>),</t>
57    <t>outputting HTML (<xref target="output.html"/>) and XHTML (<xref target="output.xhtml"/>),</t>
58    <t>outputting CHM (Compiled Microsoft Help, <xref target="output.chm"/>),</t>
59    <t>outputting PDF (<xref target="output.pdf"/>),</t>
60    <t>extensions to the xml2rfc vocabulary (<xref target="extensions"/>).</t>
61    <t>various utilities (<xref target="utilities"/>).</t>
62  </list>
63</t>
64<t>
65  The full distribution is available at <eref target="http://greenbytes.de/tech/webdav/rfc2629xslt.zip"/>.
66</t>
67</section>
68
69<section title="Supported RFC2629 elements" anchor="supported.elements">
70<t>
71  <spanx style="verb">rfc2629.xslt</spanx> supports both all RFC2629 grammar elements and the extensions
72  implemented in xml2rfc 1.33.
73</t>
74<section title="Extension elements">
75<t>
76  <spanx style="verb">rfc2629.xslt</spanx> supports two kind of extension
77  elements, using different XML namespaces.
78</t>
79<t>
80  The first set contains (hopefully) generally useful extensions, see
81  <xref target="extensions"/>.
82</t>
83<t>
84  The second set is used for change and issue tracking and currently is not
85  documented here. Please email the author in case
86  you're interested in using these extensions.
87</t>
88</section>
89</section>
90
91<section title="Processing Instructions" anchor="processing.instructions">
92<t>
93  All PIs can be set as XSLT parameter as well, overriding any value that
94  is found in the source file to be transformed.
95</t>
96<figure>
97<preamble>Using processing instructions:</preamble>
98<artwork type="example">
99&lt;?rfc toc="yes"?>
100&lt;?rfc-ext support-rfc2731="no"?>
101</artwork>
102</figure>
103<figure>
104<preamble>Using XSLT parameters (Saxon):</preamble>
105<artwork type="example">
106java -cp saxon.jar com.icl.saxon.StyleSheet source.xml rfc2629.xslt \
107  xml2rfc-toc=yes xml2rfc-ext-support-rfc2731=no > result.html
108</artwork></figure>
109<figure>
110<preamble>Using XSLT parameters (xsltproc):</preamble>
111<artwork type="example">
112xsltproc --param xml2rfc-toc '"yes"' \
113   --param xml2rfc-ext-support-rfc2731 '"no"' \
114   rfc2629.xslt source.xml > result.html
115</artwork>
116<postamble>(note the required quoting of string parameters)<iref item="xsltproc" subitem="passing parameters"/></postamble>
117</figure>
118
119<section title="Supported xml2rfc-compatible PIs">
120<texttable>
121  <ttcol>PI target</ttcol>
122  <ttcol>PI pseudo-attribute</ttcol>
123  <ttcol>XSLT parameter name</ttcol>
124  <ttcol>default</ttcol>
125  <ttcol>comment</ttcol>
126
127  <c>rfc</c>
128  <c>background<iref item="background PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="background"/></c>
129  <c>xml2rfc-background<iref item="xml2rfc-background parameter"/> <iref item="Parameters" subitem="xml2rfc-background"/></c>
130  <c>(not set)</c>
131  <c/>
132 
133  <c>rfc</c>
134  <c>compact<iref item="compact PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="compact"/></c>
135  <c>xml2rfc-compact<iref item="xml2rfc-editing parameter"/> <iref item="Parameters" subitem="xml2rfc-compact"/></c>
136  <c>"no"</c>
137  <c>only applies to HTML output method when printing</c>
138
139  <c>rfc</c>
140  <c>comments<iref item="comments PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="comments"/></c>
141  <c>xml2rfc-comments<iref item="xml2rfc-comments parameter"/> <iref item="Parameters" subitem="xml2rfc-comments"/></c>
142  <c>(not set)</c>
143  <c/>
144
145  <c>rfc</c>
146  <c>editing<iref item="editing PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="editing"/></c>
147  <c>xml2rfc-editing<iref item="xml2rfc-editing parameter"/> <iref item="Parameters" subitem="xml2rfc-editing"/></c>
148  <c>"no"</c>
149  <c/>
150 
151  <c>rfc</c>
152  <c>footer<iref item="footer PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="footer"/></c>
153  <c>xml2rfc-footer<iref item="xml2rfc-footer parameter"/> <iref item="Parameters" subitem="xml2rfc-footer"/></c>
154  <c>(not set)</c>
155  <c/>
156 
157  <c>rfc</c>
158  <c>header<iref item="header PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="header"/></c>
159  <c>xml2rfc-header<iref item="xml2rfc-header parameter"/> <iref item="Parameters" subitem="xml2rfc-header"/></c>
160  <c>(not set)</c>
161  <c/>
162
163  <c>rfc</c>
164  <c>inline<iref item="inline PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="inline"/></c>
165  <c>xml2rfc-inline<iref item="xml2rfc-inline parameter"/> <iref item="Parameters" subitem="xml2rfc-inline"/></c>
166  <c>(not set)</c>
167  <c/>
168
169  <c>rfc</c>
170  <c>iprnotified<iref item="iprnotified PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="iprnotified"/></c>
171  <c>xml2rfc-iprnotified<iref item="xml2rfc-iprnotified parameter"/> <iref item="Parameters" subitem="xml2rfc-iprnotified"/></c>
172  <c>"no"</c>
173  <c/>
174
175  <c>rfc</c>
176  <c>linkmailto<iref item="linkmailto PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="linkmailto"/></c>
177  <c>xml2rfc-linkmailto<iref item="xml2rfc-linkmailto parameter"/> <iref item="Parameters" subitem="xml2rfc-linkmailto"/></c>
178  <c>"yes"</c>
179  <c/>
180 
181  <c>rfc</c>
182  <c>private<iref item="private PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="private"/></c>
183  <c>xml2rfc-private<iref item="xml2rfc-private parameter"/> <iref item="Parameters" subitem="xml2rfc-private"/></c>
184  <c>(not set)</c>
185  <c/>
186 
187  <c>rfc</c>
188  <c>refparent<iref item="refparent PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="refparent"/></c>
189  <c>xml2rfc-private<iref item="xml2rfc-refparent parameter"/> <iref item="Parameters" subitem="xml2rfc-refparent"/></c>
190  <c>"References"</c>
191  <c>Title for References sections when automatically inserted</c>
192
193  <c>rfc</c>
194  <c>rfcedstyle<iref item="rfcedstyle PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="rfcedstyle"/></c>
195  <c>xml2rfc-rfcedstyle<iref item="xml2rfc-rfcedstyle parameter"/> <iref item="Parameters" subitem="xml2rfc-rfcedstyle"/></c>
196  <c>(not set)</c>
197  <c>(limited support)</c>
198
199  <c>rfc</c>
200  <c>sortrefs<iref item="sortrefs PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="sortrefs"/></c>
201  <c>xml2rfc-sortrefs<iref item="xml2rfc-sortrefs parameter"/> <iref item="Parameters" subitem="xml2rfc-sortrefs"/></c>
202  <c>"no"</c>
203  <c/>
204 
205  <c>rfc</c>
206  <c>symrefs<iref item="symrefs PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="symrefs"/></c>
207  <c>xml2rfc-symrefs<iref item="xml2rfc-symrefs parameter"/> <iref item="Parameters" subitem="xml2rfc-symrefs"/></c>
208  <c>"yes"</c>
209  <c>The default has changed from "no" to "yes" as of June 6, 2007 and xml2rfc 1.33pre4.</c>
210 
211  <c>rfc</c>
212  <c>toc<iref item="toc PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="toc"/></c>
213  <c>xml2rfc-toc<iref item="xml2rfc-toc parameter"/> <iref item="Parameters" subitem="xml2rfc-toc"/></c>
214  <c>"no"</c>
215  <c/>
216 
217  <c>rfc</c>
218  <c>tocdepth<iref item="tocdepth PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="tocdepth"/></c>
219  <c>xml2rfc-tocdepth<iref item="xml2rfc-tocdepth parameter"/> <iref item="Parameters" subitem="xml2rfc-tocdepth"/></c>
220  <c>99</c>
221  <c/>
222
223  <c>rfc</c>
224  <c>topblock<iref item="topblock PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="topblock"/></c>
225  <c>xml2rfc-topblock<iref item="xml2rfc-topblock parameter"/> <iref item="Parameters" subitem="xml2rfc-topblock"/></c>
226  <c>"yes"</c>
227  <c/>
228
229</texttable>
230</section>
231
232<section title="Unsupported xml2rfc-compatible PIs">
233<texttable>
234  <ttcol>PI target</ttcol>
235  <ttcol>PI pseudo-attribute</ttcol>
236  <ttcol>comment</ttcol>
237
238  <c>rfc</c>
239  <c>include<iref item="include PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="include"/></c>
240  <c>incompatible with XML/XSLT processing model, please use external entities instead</c>
241
242  <c>rfc</c>
243  <c>needLines<iref item="needLines PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="needLines"/></c>
244  <c/>
245
246  <c>rfc</c>
247  <c>slides<iref item="slides PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="slides"/></c>
248  <c/>
249
250  <c>rfc</c>
251  <c>strict<iref item="strict PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="strict"/></c>
252  <c/>
253
254  <c>rfc</c>
255  <c>subcompact<iref item="subcompact PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="subcompact"/></c>
256  <c/>
257
258  <c>rfc</c>
259  <c>tocindent<iref item="tocindent PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="tocindent"/></c>
260  <c>(defaults to "yes")</c>
261
262 <c>rfc</c>
263  <c>tocompact<iref item="tocompact PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="tocompact"/></c>
264  <c/>
265
266</texttable>
267</section>
268
269<section title="Extension PIs">
270<texttable>
271  <ttcol>PI target</ttcol>
272  <ttcol>PI pseudo-attribute</ttcol>
273  <ttcol>XSLT parameter name</ttcol>
274  <ttcol>default</ttcol>
275  <ttcol>description</ttcol>
276
277  <c>rfc-ext</c>
278  <c>allow-markup-in-artwork<iref item="allow-markup-in-artwork PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="allow-markup-in-artwork"/></c>
279  <c>xml2rfc-allow-markup-in-artwork<iref item="xml2rfc-ext-allow-markup-in-artwork parameter"/> <iref item="Parameters" subitem="xml2rfc-ext-allow-markup-in-artwork"/></c>
280  <c>"no"</c>
281  <c>Enables support for specific elements inside abstract elements (using this extension
282  makes the document incompatible to the RFC2629bis DTD; see description of
283  conversion XSLT in <xref target="clean-for-dtd"/>).</c>
284
285  <c>rfc-ext</c>
286  <c>authors-section<iref item="authors-section PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="authors-section"/></c>
287  <c>xml2rfc-ext-authors-section<iref item="xml2rfc-ext-authors-section parameter"/> <iref item="Parameters" subitem="xml2rfc-ext-authors-section"/></c>
288  <c></c>
289  <c>When "end", place the authors section at the end (just before the
290  copyright statements). This seems to be the preferred order in the
291  newest RFCs.</c>
292
293  <c>rfc-ext</c>
294  <c>duplex<iref item="duplex PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="duplex"/></c>
295  <c>xml2rfc-ext-duplex<iref item="xml2rfc-ext-duplex"/> <iref item="Parameters" subitem="xml2rfc-ext-duplex"/></c>
296  <c>no</c>
297  <c>When set to "yes", format the PDF output for doublesided printing.</c>
298
299  <c>rfc-ext</c>
300  <c>include-references-in-index<iref item="include-references-in-index PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="include-references-in-index"/></c>
301  <c>xml2rfc-ext-include-references-in-index<iref item="xml2rfc-ext-include-references-in-index parameter"/> <iref item="Parameters" subitem="xml2rfc-ext-include-references-in-index"/></c>
302  <c></c>
303  <c>When set to "yes", index entries are generated for all references.</c>
304
305  <c>rfc-ext</c>
306  <c>justification<iref item="justification PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="ijustification"/></c>
307  <c>xml2rfc-ext-justification<iref item="xml2rfc-ext-justification parameter"/> <iref item="Parameters" subitem="xml2rfc-ext-justification"/></c>
308  <c>"never"</c>
309  <c>"never": never emit justified text, "always": always emit justified text, "print": only emit justified text for print media.</c>
310
311  <c>rfc-ext</c>
312  <c>parse-xml-in-artwork<iref item="parse-xml-in-artwork PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="parse-xml-in-artwork"/></c>
313  <c>xml2rfc-parse-xml-in-artwork<iref item="xml2rfc-ext-parse-xml-in-artwork parameter"/> <iref item="Parameters" subitem="xml2rfc-ext-parse-xml-in-artwork"/></c>
314  <c>"no"</c>
315  <c>May be used to enable parsing of XML content in figures (MSXML only).</c>
316
317  <c>rfc-ext</c>
318  <c>support-rfc2731<iref item="support-rfc2731 PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="support-rfc2731"/></c>
319  <c>xml2rfc-ext-support-rfc2731<iref item="xml2rfc-ext-support-rfc2731 parameter"/> <iref item="Parameters" subitem="xml2rfc-ext-support-rfc2731"/></c>
320  <c>"yes"</c>
321  <c>Decides whether the HTML transformation should generate META tags according <xref target="rfc2731.properties"/>.</c>
322
323  <c>rfc-ext</c>
324  <c>sec-no-trailing-dots<iref item="sec-no-trailing-dots PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="sec-no-trailing-dots"/></c>
325  <c>xml2rfc-ext-sec-no-trailing-dots<iref item="xml2rfc-ext-sec-no-trailing-dots parameter"/> <iref item="Parameters" subitem="xml2rfc-ext-sec-no-trailing-dots"/></c>
326  <c></c>
327  <c>When set to "yes", add trailing dots to section numbers. This seems to be the preferred format in the
328  newest RFCs.</c>
329
330</texttable>
331</section>
332
333</section>
334
335<section title="Anchors" anchor="anchors">
336<t>
337  The transformation automatically generates anchors that are supposed to
338  be stable and predictable and that can be used to identify specific
339  parts of the document. Anchors are generated both in HTML and XSL-FO
340  content (but the latter will only be used for PDF output when the XSL-FO
341  engine supports producing PDF anchors).
342</t>
343<texttable>
344<preamble>The following anchors get auto-generated:</preamble>
345<ttcol>Anchor name</ttcol><ttcol>Description</ttcol>
346
347  <c>rfc.abstract <iref item="rfc.abstract anchor"/><iref item="Anchors" subitem="rfc.abstract"/></c><c>Abstract</c>
348  <c>rfc.authors <iref item="rfc.authors anchor"/><iref item="Anchors" subitem="rfc.authors"/></c><c>Authors section</c>
349  <c>rfc.copyright <iref item="rfc.copyright anchor"/><iref item="Anchors" subitem="rfc.copyright"/></c><c>Copyright section</c>
350  <c>rfc.copyrightnotice <iref item="rfc.copyrightnotice anchor"/><iref item="Anchors" subitem="rfc.copyrightnotice"/></c><c>Copyright notice</c>
351  <c>rfc.figure.<spanx>n</spanx> <iref item="rfc.figure.n anchor"/><iref item="Anchors" subitem="rfc.figure.n"/></c><c>Figures (titled)</c>
352  <c>rfc.figure.u.<spanx>n</spanx> <iref item="rfc.figure.u.n anchor"/><iref item="Anchors" subitem="rfc.figure.u.n"/></c><c>Figures (untitled)</c>
353  <c>rfc.index <iref item="rfc.index anchor"/><iref item="Anchors" subitem="rfc.index"/></c><c>Index</c>
354  <c>rfc.ipr <iref item="rfc.ipr anchor"/><iref item="Anchors" subitem="rfc.ipr"/></c><c>Intellectual Property</c>
355  <c>rfc.iref.<spanx>n</spanx> <iref item="rfc.iref.n anchor"/><iref item="Anchors" subitem="rfc.iref.n"/></c><c>Internal references</c>
356  <c>rfc.note.<spanx>n</spanx> <iref item="rfc.note.n anchor"/><iref item="Anchors" subitem="rfc.note.n"/></c><c>Notes (from front section)</c>
357  <c>rfc.references <iref item="rfc.references anchor"/><iref item="Anchors" subitem="rfc.references"/></c><c>References</c>
358  <c>rfc.references.<spanx>n</spanx> <iref item="rfc.references.n anchor"/><iref item="Anchors" subitem="rfc.references"/></c><c>Additional references</c>
359  <c>rfc.section.<spanx>n</spanx> <iref item="rfc.section.n anchor"/><iref item="Anchors" subitem="rfc.section.n"/></c><c>Section <spanx>n</spanx></c>
360  <c>rfc.section.<spanx>n</spanx>.p.<spanx>m</spanx> <iref item="rfc.section.n.p.m anchor"/><iref item="Anchors" subitem="rfc.section.n.p.m"/></c><c>Section <spanx>n</spanx>, paragraph <spanx>m</spanx></c>
361  <c>rfc.status <iref item="rfc.status anchor"/><iref item="Anchors" subitem="rfc.status"/></c><c>Status of memo</c>
362  <c>rfc.table.<spanx>n</spanx> <iref item="rfc.figure.n anchor"/><iref item="Anchors" subitem="rfc.figure.n"/></c><c>Tables (titled)</c>
363  <c>rfc.table.u.<spanx>n</spanx> <iref item="rfc.figure.u.n anchor"/><iref item="Anchors" subitem="rfc.figure.u.n"/></c><c>Tables (untitled)</c>
364  <c>rfc.toc <iref item="rfc.toc anchor"/><iref item="Anchors" subitem="rfc.toc"/></c><c>Table of contents</c>
365  <c>rfc.xref.<spanx>name</spanx>.<spanx>n</spanx> <iref item="rfc.xref.name.n anchor"/><iref item="Anchors" subitem="rfc.xref.name.n"/></c><c>References to reference <spanx>n</spanx> to <spanx>name</spanx></c>
366
367</texttable>
368</section>
369
370<section title="Supported XSLT engines" anchor="xslt.engines">
371<t>
372  The transformation requires a non-standard extension function (see <eref target="http://www.exslt.org/exsl/functions/node-set/exsl.node-set.html">
373  exsl:node-set</eref>)
374  which is however widely available. XSLT processors that do not support this
375  extension (or a functional equivalent) currently are not supported.
376</t>
377<section title="Standalone Engines">
378<t>
379  The following XSLT engines are believed to work well:
380  <list style="symbols">
381    <t>Windows: <iref item="MSXML3"/><iref item="MSXML4"/>MSXML3 and MSXML4 (<eref target="http://msdn.microsoft.com/xml"/>;
382      command line processor "msxsl" is available from <eref target="http://www.microsoft.com/downloads/details.aspx?FamilyID=2FB55371-C94E-4373-B0E9-DB4816552E41">Microsoft Download Center</eref>)</t>
383    <t>Java: <iref item="Saxon"/>Saxon (<eref target="http://saxon.sourceforge.net/"/>)</t>
384    <t>Java: <iref item="Xalan"/>Xalan (<eref target="http://xml.apache.org/xalan-j/"/>)</t>
385    <t>C/C++: <iref item="xsltproc"/>xsltproc (libxslt) (<eref target="http://xmlsoft.org/XSLT/"/>, make sure that you
386    have a current version)</t>
387  </list>
388</t>
389</section>
390
391<section title="In-Browser Engines" anchor="xslt.engines.browser">
392<t>
393  The following browsers seem to work fine:
394  <list style="symbols">
395    <x:lt>
396      <t><iref item="Internet Explorer 5.5"/>Internet Explorer 5.5 (Windows version, if MSXML3 is installed)</t>
397    </x:lt>
398    <x:lt>
399      <t><iref item="Internet Explorer 6"/><iref item="Internet Explorer 7"/><iref item="Internet Explorer 8"/>Internet Explorer 6 and newer</t>
400    </x:lt>
401    <x:lt>
402      <t anchor="firefox3"><iref item="Mozilla"/><iref item="Firefox" subitem="3.*"/>Firefox 3.0 and newer</t>
403      <t>
404        <list style="symbols">
405          <t>Be aware that XSLT execution can be suppressed using <iref item="NoScript"/><eref target="https://addons.mozilla.org/de/firefox/addon/722">NoScript</eref></t>
406          <t>Firefox does not load external DTDs nor external entities,
407          see <eref target="https://bugzilla.mozilla.org/show_bug.cgi?id=22942">Mozilla Bug 22942</eref>, thus entities
408          like &amp;nbsp; need to be declared in the internal subset (<xref target="examples.internalsubset"/>)</t>
409        </list>
410      </t>
411    </x:lt>
412    <x:lt>
413      <t><iref item="Safari"/><iref item="Safari" subitem="3.*"/>Safari 3 (starting with version 3.0.4)</t>
414    </x:lt>
415    <x:lt>
416      <t><iref item="Google Chrome"/>Google Chrome</t>
417    </x:lt>
418    <x:lt>
419      <t><iref item="Opera"/>Opera (starting with version 10)</t>
420    </x:lt>
421  </list>
422</t>
423<t>
424  The following browsers are known not to work properly:
425  <list style="symbols">
426    <x:lt>
427      <t anchor="firefox12"><iref item="Mozilla"/><iref item="Firefox" subitem="1.*/2.*"/>Firefox 1.*/2.*: (missing extension function - see change request at Mozilla BugZilla
428      <eref target="http://bugzilla.mozilla.org/show_bug.cgi?id=193678">193678</eref>)</t>
429    </x:lt>
430    <x:lt>
431      <t anchor="opera"><iref item="Opera"/>Opera 9.21: execution fails, potentially
432      to a somewhat complex XPath expression (reported to Opera as bug 245725).</t>
433    </x:lt>
434    <x:lt>
435      <t>Opera 9.5 and 9.6:
436      transformation appears to work, but CSS isn't getting applied (reported to Opera as bug 337388 on 2008-06-12).</t>
437    </x:lt>
438    <x:lt>
439      <t anchor="safari"><iref item="Safari"/>Safari 2.* supports client-side XSLT as of MacOS X 10.4,
440      but misses required extension functions. A problem
441      with stylesheets producing non-ASCII output (such as NBSP characters)
442      has been fixed as of OSX 10.4.4. Both
443      problems have been reported through Apple's bug tracking system, see
444      <eref target="http://drakken.dbc.mtview.ca.us/pipermail/xml2rfc/2005-May/002073.html"/> and
445      <eref target="http://bugs.webkit.org/show_bug.cgi?id=4079"/>.
446      </t>
447    </x:lt>
448  </list>
449</t>
450</section>
451
452</section>
453
454<section title="Transforming to HTML" anchor="output.html">
455<t>
456  Transformation to HTML can be done inside the browser if it supports
457  XSLT. To enable this, add the following processing instruction to
458  the start of the source file:
459</t>
460<iref item="xml-stylesheet PI"/>
461<figure><artwork type="example">
462  &lt;?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
463</artwork></figure>
464<t>
465  (and ensure that <spanx style="verb">rfc2629.xslt</spanx> is present).
466</t>
467
468<section title="HTML compliance">
469<t>
470  The transformation result is supposed to conform to the HTML 4.01 strict
471  DTD <xref target="HTML"/>. This can be checked using the W3C's online
472  validator at <eref target="http://validator.w3.org" /><iref item="HTML compliance"/>.
473</t>
474</section>
475
476<section title="Standard HTML LINK elements" anchor="html.link">
477<t>
478  LINK elements exist since HTML 2.0. They can be used to embed content-independant
479  links inside the document. Unfortunately, only few user agents
480  support this element. Firefox users may want to check the
481  <eref target="https://addons.mozilla.org/firefox/2933/">Link Widgets</eref>
482  extension.
483</t>
484<texttable>
485<preamble>The following LINK elements are produced:</preamble>
486
487  <ttcol>LINK type</ttcol>
488  <ttcol>description</ttcol>
489 
490  <c>alternate<iref item="alternate HTML LINK element"/><iref item="HTML LINK elements" subitem="alternate"/></c><c>for RFCs, a link to the authorative ASCII version on the IETF web site</c>
491  <c>appendic<iref item="appendix HTML LINK element"/><iref item="HTML LINK elements" subitem="appendix"/></c><c>pointer to all top-level appendics</c>
492  <c>author<iref item="author HTML LINK element"/><iref item="HTML LINK elements" subitem="author"/></c><c>pointer to "authors" section</c>
493  <c>chapter<iref item="chapter HTML LINK element"/><iref item="HTML LINK elements" subitem="chapter"/></c><c>pointer to all top-level sections</c>
494  <c>contents<iref item="contents HTML LINK element"/><iref item="HTML LINK elements" subitem="contents"/></c><c>pointer to table of contents</c>
495  <c>copyright<iref item="copyright HTML LINK element"/><iref item="HTML LINK elements" subitem="copyright"/></c><c>pointer to copyright statement</c>
496  <c>index<iref item="index HTML LINK element"/><iref item="HTML LINK elements" subitem="index"/></c><c>pointer to index</c>
497
498</texttable>
499<figure>
500<preamble>
501The figure below shows how Mozilla Firefox 1.0 displays the Site Navigation Bar
502for rfc2396.xml.
503</preamble>
504<artwork src="rfc2629xslt-fig1.png" height="235" width="509" type="image/png">
505(LINK elements displayed in Mozilla Firefox for RFC2396.xml)
506</artwork>
507</figure>
508
509</section>
510
511
512<section title="Standard HTML metadata">
513<texttable>
514<preamble>The following standard HTML META elements are produced:</preamble>
515
516  <ttcol>META name</ttcol>
517  <ttcol>description</ttcol>
518 
519  <c>generator<iref item="generator HTML META element"/><iref item="HTML META elements" subitem="generator"/></c><c>from XSLT engine version and stylesheet version</c>
520  <c>keywords<iref item="keywords HTML META element"/><iref item="HTML META elements" subitem="keywords"/></c><c>from keyword elements in front section</c>
521
522</texttable>
523</section>
524
525
526<section title="Dublin Core (RFC2731) metadata" anchor="rfc2731.properties">
527<t>
528  Unless turned off using the "rfc-ext support-rfc2731" processing
529  instruction, the transformation will generate metadata according to
530  <xref target="RFC2731"/> and <xref target="DC-HTML"/>.
531</t>
532<texttable>
533<preamble>The following DCMI properties are produced:</preamble>
534
535  <ttcol>META name</ttcol>
536  <ttcol>description</ttcol>
537 
538  <c>DC.Creator<iref item="Creator DCMI property"/><iref item="DCMI properties" subitem="Creator"/></c><c>from author information in front section</c>
539  <c>DC.Date.Issued<iref item="Date.Issued DCMI property"/><iref item="DCMI properties" subitem="Date.Issued"/></c><c>from date information in front section</c>
540  <c>DC.Description.Abstract<iref item="Description.Abstract DCMI property"/><iref item="DCMI properties" subitem="Description.Abstract"/></c><c>from abstract</c>
541  <c>DC.Identifier<iref item="Identifier DCMI property"/><iref item="DCMI properties" subitem="Identifier"/></c><c>document URN <xref target="RFC2648" /> from "docName" attribute</c>
542  <c>DC.isPartOf<iref item="isPartOf DCMI property"/><iref item="DCMI properties" subitem="isPartOf"/></c><c>RFC ISSN (for RFCs)</c>
543  <c>DC.Relation.Replaces<iref item="Relation.Replaces DCMI property"/><iref item="DCMI properties" subitem="Relation.Replaces"/></c><c>from "obsoletes" attribute</c>
544
545</texttable>
546</section>
547
548<section title="Experimental hCard support" anchor="hcard">
549<t>
550  The generated author information is formatted in <eref target="http://microformats.org/wiki/hcard">hCard</eref>
551  format.
552</t>
553</section>
554
555
556</section>
557
558<section title="Transforming to XHTML" anchor="output.xhtml">
559<t>
560  Transforming to XHTML requires slightly different XSLT output options and
561  is implemented by the derived transformation script <spanx style="verb">rfc2629toXHTML.xslt</spanx>.
562</t>
563<t><list><t>
564  <x:h>Note:</x:h> Microsoft Internet Explorer does <spanx>not</spanx> support XHTML.
565  Therefore it usually makes more sense to generate plain old HTML.
566</t></list></t>
567</section>
568
569<section title="Transforming to CHM (Microsoft Compiled Help)" anchor="output.chm">
570<t>
571  <iref item="CHM format"/>
572  <iref item="Microsoft Help"/>
573  To generate a CHM file using Microsoft's HTML Help Compiler (hhc), three
574  files are required in addition to the HTML file.
575  <list style="numbers">
576    <t>hhc - table of contents file (HTML)</t>
577    <t>hhk - index file (HTML)</t>
578    <t>hhp - project file (plain text)</t>
579  </list> 
580</t>
581<t>
582  The three files are generated with three specific transformations, each
583  requiring the additional XSLT parameter "basename" to specify the filename
584  prefix.
585</t>
586<figure>
587<preamble>Example:</preamble>
588<artwork type="example">
589saxon rfc2616.xml rfc2629toHhp.xslt basename=rfc2616  > rfc2616.hhp
590saxon rfc2616.xml rfc2629toHhc.xslt basename=rfc2616  > rfc2616.hhc
591saxon rfc2616.xml rfc2629toHhk.xslt basename=rfc2616  > rfc2616.hhk
592hhc rfc2616.hhp
593</artwork>
594</figure>
595</section>
596
597<section title="Transforming to PDF" anchor="output.pdf">
598
599<section title="Via XSL-FO" anchor="output.pdf.fop">
600<t>
601  Transformation to XSL-FO <xref target="XSL-FO"/> format is available through
602  <spanx style="verb">rfc2629toFO.xslt</spanx> (which includes <spanx style="verb">rfc2629.xslt</spanx>, so keep both in the
603  same folder).
604</t>
605<t>
606  Compared to HTML user agents, XSL-FO engines unfortunately either come
607  as open source (for instance, <iref item="Apache FOP"/>Apache FOP) or
608  feature-complete (for instance, <iref item="AntennaHouse XSL Formatter"/>
609  AntennaHouse XSL Formatter), but not both at the same time.
610</t>
611<t>
612  As Apache FOP needs special workarounds (index generation), and
613  some popular extensions aren't standardized yet, the translation produces
614  a generic output (hopefully) conforming to <xref target="XSL-FO"/>.
615  Specific backends (<spanx style="verb">xsl11toFop.xslt</spanx>,
616  <spanx style="verb">xsl11toXep.xslt</spanx>, <spanx style="verb">xsl11toAn.xslt</spanx>)
617  then provide post-processing for the individual processors.
618</t>
619<x:note>
620  <t>
621    <x:h>Note:</x:h>
622    the output is currently targeted at Apache FOP 1.0.
623  </t>
624</x:note>
625
626<section title="Extension feature matrix">
627<texttable>
628  <ttcol/>
629  <ttcol align="center" width="20%">PDF anchors</ttcol>
630  <ttcol align="center" width="20%">PDF bookmarks</ttcol>
631  <ttcol align="center" width="20%">PDF document information</ttcol>
632  <ttcol align="center" width="20%">Index cleanup</ttcol>
633 
634  <c><eref target="http://www.w3.org/TR/2003/WD-xsl11-20031217/">XSL 1.1 WD</eref></c>
635  <c>no, but can be auto-generated from "id" attributes</c> 
636  <c><eref target="http://www.w3.org/TR/2003/WD-xsl11-20031217/#d0e12873">yes</eref></c>
637  <c>no, but uses XEP output extensions</c>
638  <c><eref target="http://www.w3.org/TR/2003/WD-xsl11-20031217/#d0e12534">yes</eref></c>
639
640  <c><eref target="http://www.antennahouse.com/">Antenna House XSL formatter</eref></c>
641  <c>no</c>
642  <c><eref target="http://www.antennahouse.com/XSL20/axf-extension.htm">yes</eref> (from XSL 1.1 bookmarks)</c>
643  <c><eref target="http://www.antennahouse.com/XSL20/axf-extension.htm">yes</eref> (from XEP document info)</c>
644  <c><eref target="http://www.antennahouse.com/XSL20/axf-extension.htm">yes</eref> (just page duplicate elimination, from XSL 1.1 page index)</c>
645
646  <c><eref target="http://xml.apache.org/fop/">Apache FOP</eref></c>
647  <c><eref target="http://xml.apache.org/fop/extensions.html#named-destinations">yes</eref></c>
648  <c><eref target="http://xml.apache.org/fop/extensions.html#bookmarks">yes</eref> (from XSL 1.1 bookmarks)</c>
649  <c><eref target="http://xmlgraphics.apache.org/fop/0.95/metadata.html#xmp-in-fo">yes</eref></c>
650  <c>no</c>
651
652  <c><eref target="http://xep.xattic.com/">RenderX XEP</eref></c>
653  <c>no</c>
654  <c><eref target="http://xep.xattic.com/xep/spec.html">yes</eref> (from XSL 1.1 bookmarks)</c>
655  <c><eref target="http://xep.xattic.com/xep/spec.html">yes</eref></c>
656  <c><eref target="http://xep.xattic.com/xep/spec.html">yes</eref> (from XSL 1.1 page index)</c>
657
658</texttable>
659</section>
660
661<section title="Example: producing output for Apache FOP">
662<figure>
663<preamble>Example:</preamble>
664<artwork type="example">
665saxon rfc2616.xml rfc2629toFo.xslt > tmp.fo
666saxon tmp.fo xsl11toFop.xslt > rfc2629.fo
667</artwork>
668</figure>
669</section>
670</section>
671
672<section title="Via X(HTML)" anchor="output.pdf.html">
673<t>
674  PDF output can also be produced directly from (X)HTML. One simple approach
675  is to rely on the browser's printing function, and to use a printer driver
676  that produces PDF. Depending on the brower's CSS capabilities, the output
677  will behave properly with respect to table breaks etc.
678</t>
679<t>
680  An alternative is PrinceXML (see <eref target="http://www.princexml.com/"/>),
681  which can produce PDF directly from (X)HTML input, based on the CSS printing
682  information.
683</t>
684<figure>
685  <preamble>
686    For instance, PDF output with text justification turned on can be
687    produced with:
688  </preamble>
689  <artwork type="example">
690saxon input.xml rfc2629toXHTML.xslt xml2rfc-ext-justification=print \
691  > output.xhtml
692prince output.xhtml output.pdf</artwork>
693</figure>
694</section>
695
696</section>
697
698<section title="Transforming to ePub" anchor="output.epub">
699<t>
700  Experimental transformation to ePub format is available through a set
701  of stylesheets, and the Unix Shell script
702  <spanx style="verb">mkepub.sh</spanx> (which requires that "zip" and either
703  "saxon" or "xsltproc" are installed).
704</t>
705<figure>
706  <preamble>
707    For instance, an epub version of rfc2616.xml can be generated like this:
708  </preamble>
709  <artwork type="example">
710mkepub.sh rfc2616.xml
711</artwork>
712</figure>
713</section>
714
715<section title="Generic Extensions" anchor="extensions">
716<t>
717  This section documents extensions implemented in
718  <spanx style="verb">rfc2629.xslt</spanx>, using the extension
719  namespace "http://purl.org/net/xml2rfc/ext".
720</t>
721
722<section title="&lt;abnf-char-sequence> element" anchor="ext.element.abnf-char-sequence">
723  <iref item="Extension Elements" subitem="abnf-char-sequence" primary="true"/>
724  <iref item="abnf-char-sequence Extension Element" primary="true"/>
725  <x:anchor-alias value="abnf-char-sequence"/>
726  <t>
727    Converts the contained quoted string into a hex-encoded character
728    sequence, for use in case-sensitive ABNF productions.
729  </t>
730  <t>
731    For instance, "&lt;x:abnf-char-sequence>"HTTP"&lt;/x:abnf-char-sequence>"
732    gets converted to "<x:abnf-char-sequence>"HTTP"</x:abnf-char-sequence>".
733  </t>
734</section>
735
736<section title="&lt;anchor-alias> element" anchor="ext.element.anchor-alias">
737  <iref item="Extension Elements" subitem="anchor-alias" primary="true"/>
738  <iref item="anchor-alias Extension Element" primary="true"/>
739  <x:anchor-alias value="anchor-alias"/>
740  <t>
741    Using its "value" attribute, this element allows the definition of an
742    internal link target alias for the enclosing element. This alias can
743    then be used with the &lt;<x:ref>ref</x:ref>> element for intra-document
744    references.
745  </t>
746  <t>
747    Note that the anchor alias is not subject to the naming constraints that
748    apply to anchor elements (which are <eref target="http://www.w3.org/TR/REC-xml/#NT-Name">XML
749    names</eref>).
750  </t>
751</section>
752
753<!--<section title="&lt;include-author> element" anchor="ext.element.include-author">
754  <iref item="Extension Elements" subitem="include-author" primary="true"/>
755  <iref item="include-author Extension Element" primary="true"/>
756  <x:anchor-alias value="include-author"/>
757  <t>
758    This element can be used to include an author's contact information in
759    place where a paragraphj (&lt;t>) would be allowed otherwise.
760  </t>
761</section> -->
762
763<section title="&lt;bcp14> element" anchor="ext.element.bcp14">
764  <iref item="Extension Elements" subitem="bcp14" primary="true"/>
765  <iref item="bcp14 Extension Element" primary="true"/>
766  <x:anchor-alias value="bcp14"/>
767  <t>
768    This element marks the content as being one of the normative keywords
769    defined in <xref target="RFC2119"/>.
770  </t>
771  <figure>
772    <preamble>
773      The DOCTYPE definition below allows using these keywords using XML
774      entity expansion: such as in "...server &amp;MUST; accept...".
775    </preamble>
776    <artwork type="example">
777&lt;!DOCTYPE rfc [
778 &lt;!ENTITY MAY "&lt;bcp14 xmlns='http://purl.org/net/xml2rfc/ext'
779   >MAY&lt;/bcp14>">
780 &lt;!ENTITY MUST "&lt;bcp14 xmlns='http://purl.org/net/xml2rfc/ext'
781   >MUST&lt;/bcp14>">
782 &lt;!ENTITY MUST-NOT "&lt;bcp14 xmlns='http://purl.org/net/xml2rfc/ext'
783   >MUST NOT&lt;/bcp14>">
784 &lt;!ENTITY OPTIONAL "&lt;bcp14 xmlns='http://purl.org/net/xml2rfc/ext'
785   >OPTIONAL&lt;/bcp14>">
786 &lt;!ENTITY RECOMMENDED "&lt;bcp14 xmlns='http://purl.org/net/xml2rfc/ext'
787   >RECOMMENDED&lt;/bcp14>">
788 &lt;!ENTITY REQUIRED "&lt;bcp14 xmlns='http://purl.org/net/xml2rfc/ext'
789   >REQUIRED&lt;/bcp14>">
790 &lt;!ENTITY SHALL "&lt;bcp14 xmlns='http://purl.org/net/xml2rfc/ext'
791   >SHALL&lt;/bcp14>">
792 &lt;!ENTITY SHALL-NOT "&lt;bcp14 xmlns='http://purl.org/net/xml2rfc/ext'
793   >SHALL NOT&lt;/bcp14>">
794 &lt;!ENTITY SHOULD "&lt;bcp14 xmlns='http://purl.org/net/xml2rfc/ext'
795   >SHOULD&lt;/bcp14>">
796 &lt;!ENTITY SHOULD-NOT "&lt;bcp14 xmlns='http://purl.org/net/xml2rfc/ext'
797   >SHOULD NOT&lt;/bcp14>">]></artwork>
798  </figure>
799</section>
800
801<section title="&lt;bb> element" anchor="ext.element.bb">
802  <iref item="Extension Elements" subitem="bb" primary="true"/>
803  <iref item="bb Extension Element" primary="true"/>
804  <x:anchor-alias value="bb"/>
805  <t>
806    Marking up a string as &lt;bb> indicates that it represents the bottom
807    line of a box drawing, replacing the "+" and "-" characters accordingly.
808  </t>
809</section>
810
811<section title="&lt;bc> element" anchor="ext.element.bc">
812  <iref item="Extension Elements" subitem="bc" primary="true"/>
813  <iref item="bc Extension Element" primary="true"/>
814  <x:anchor-alias value="bc"/>
815  <t>
816    Marking up a string as &lt;bc> indicates that it represents a center
817    line of a box drawing, replacing the "|" character accordingly.
818  </t>
819</section>
820
821<section title="&lt;blockquote> element" anchor="ext.element.blockquote">
822  <iref item="Extension Elements" subitem="blockquote" primary="true"/>
823  <iref item="blockquote Extension Element" primary="true"/>
824  <x:anchor-alias value="blockquote"/>
825  <t>
826    This element is like the "<eref target="http://www.w3.org/TR/html401/struct/text.html#edef-BLOCKQUOTE">blockquote</eref>" element in <xref target="HTML"/> 
827    (note this is a block-level element!). It should contain one or more
828    &lt;t> child elements.
829  </t>
830</section>
831
832<section title="&lt;boilerplate> element" anchor="ext.element.boilerplate">
833  <iref item="Extension Elements" subitem="boilerplate" primary="true"/>
834  <iref item="boilerplate Extension Element" primary="true"/>
835  <x:anchor-alias value="boilerplate"/>
836  <t>
837    Can be used to include boilerplate (status, copyright, ...) into the
838    front or back section. &lt;section> elements within &lt;x:boilerplate>
839    appear as unnumbered sections in the output.
840  </t>
841  <t>
842    <spanx>This element currently can not be "down-translated" for use
843    in xml2rfc!</spanx>
844  </t>
845</section>
846
847<section title="&lt;bt> element" anchor="ext.element.bt">
848  <iref item="Extension Elements" subitem="bt" primary="true"/>
849  <iref item="bt Extension Element" primary="true"/>
850  <x:anchor-alias value="bt"/>
851  <t>
852    Marking up a string as &lt;bt> indicates that it represents the top
853    line of a box drawing, replacing the "+" and "-" characters accordingly.
854  </t>
855</section>
856
857<section title="&lt;dfn> element" anchor="ext.element.dfn">
858  <iref item="Extension Elements" subitem="dfn" primary="true"/>
859  <iref item="dfn Extension Element" primary="true"/>
860  <x:anchor-alias value="dfn"/>
861  <t>
862    This element is like the "<eref target="http://www.w3.org/TR/html401/struct/text.html#edef-DFN">dfn</eref>" element in <xref target="HTML"/>.
863  </t>
864</section>
865
866<section title="&lt;h> element" anchor="ext.element.h">
867  <iref item="Extension Elements" subitem="h" primary="true"/>
868  <iref item="h Extension Element" primary="true"/>
869  <x:anchor-alias value="h"/>
870  <t>
871    This element is like the "<eref target="http://www.w3.org/TR/2006/WD-xhtml2-20060726/mod-structural.html#edef_structural_h">h</eref>" element in <xref target="XHTML2"/>.
872  </t>
873</section>
874
875<section title="&lt;highlight> element" anchor="ext.element.highlight">
876  <iref item="Extension Elements" subitem="highlight" primary="true"/>
877  <iref item="highlight Extension Element" primary="true"/>
878  <x:anchor-alias value="highlight"/>
879  <t>
880    Used to highlight text passages, currently only allowed in &lt;artwork>.
881  </t>
882  <t>
883    <x:h>Note:</x:h> this is stripped when generating input for xml2rfc,
884    so please use with care.
885  </t>
886</section>
887
888<section title="&lt;length-of> element" anchor="ext.element.length-of">
889  <iref item="Extension Elements" subitem="length-of" primary="true"/>
890  <iref item="length-of Extension Element" primary="true"/>
891  <x:anchor-alias value="length-of"/>
892  <t>
893    This element can be used to insert the length of another formatted
894    section (in decimal).
895  </t>
896  <figure>
897    <preamble>Example: computing the Content-Length header value</preamble>
898    <artwork type="example">
899&lt;artwork>
900...
901Content-Length: &lt;x:length-of target="req"/>
902 
903&lt;x:span anchor="req">123456789
904&lt;x:span>&lt;artwork/>
905</artwork>
906  </figure>
907  <t>
908    The lenght computation counts line ends as two characters (CRLF).
909  </t>
910  <t>
911    Note that indentation characters in artwork <spanx>will</spanx> be
912    counted. The "indented" attribute allows to specify the amount of
913    indentation to be substracted from the computed length.
914  </t>
915</section>
916
917<section title="&lt;link> element" anchor="ext.element.link">
918  <iref item="Extension Elements" subitem="link" primary="true"/>
919  <iref item="link Extension Element" primary="true"/>
920  <x:anchor-alias value="link"/>
921  <t>
922    This element can be added as a top-level child element below
923    &lt;rfc> to indicate additional link information. It's currently
924    used only when generating HTML output, in which case an HTML
925    <eref target="http://www.w3.org/TR/html4/struct/links.html#edef-LINK">&lt;link></eref> element with identical attributes gets generated.
926  </t>
927  <figure>
928    <preamble>Example: generating HTML link element</preamble>
929    <artwork type="example">
930        &lt;x:link xmlns="http://purl.org/net/xml2rfc/ext"
931            rel="Bookmark"
932            title="IETF WEBDAV Working Group"
933            href="http://ftp.ics.uci.edu/pub/ietf/webdav/"/></artwork>
934  </figure>
935</section>
936
937<section title="&lt;lt> element" anchor="ext.element.lt">
938  <iref item="Extension Elements" subitem="lt" primary="true"/>
939  <iref item="lt Extension Element" primary="true"/>
940  <x:anchor-alias value="lt"/>
941  <t>
942    Used for grouping multiple &lt;t&gt; elements into a single list item.
943  </t>
944</section>
945
946<section title="&lt;note> element" anchor="ext.element.note">
947  <iref item="Extension Elements" subitem="note" primary="true"/>
948  <iref item="note Extension Element" primary="true"/>
949  <x:anchor-alias value="note"/>
950  <t>
951    Can be used to add a note, usually indented by a few characters.
952    It should contain one or more &lt;t> child elements.
953  </t>
954</section>
955
956<section title="&lt;parse-xml> element" anchor="ext.element.parse-xml">
957  <iref item="Extension Elements" subitem="parse-xml" primary="true"/>
958  <iref item="parse-xml Extension Element" primary="true"/>
959  <x:anchor-alias value="parse-xml"/>
960  <t>
961    This element instructs the processor to parse the contents as XML and
962    to warn when there's a problem (requires either MSXML or Saxon8 or newer).
963  </t>
964</section>
965
966<section title="&lt;prose> element" anchor="ext.element.prose">
967  <iref item="Extension Elements" subitem="prose" primary="true"/>
968  <iref item="prose Extension Element" primary="true"/>
969  <x:anchor-alias value="prose"/>
970  <t>
971    This element can be used inside &lt;reference> to add plain text (before
972    the date, when present).
973  </t>
974</section>
975
976<section title="&lt;q> element" anchor="ext.element.q">
977  <iref item="Extension Elements" subitem="q" primary="true"/>
978  <iref item="q Extension Element" primary="true"/>
979  <x:anchor-alias value="q"/>
980  <t>
981    This element is like the "<eref target="http://www.w3.org/TR/html401/struct/text.html#edef-Q">q</eref>" element in <xref target="HTML"/>.
982  </t>
983</section>
984
985<section title="&lt;ref> element" anchor="ext.element.ref">
986  <iref item="Extension Elements" subitem="ref" primary="true"/>
987  <iref item="ref Extension Element" primary="true"/>
988  <x:anchor-alias value="ref"/>
989  <t>
990    This element is a simplified variant of the &lt;xref> element, in that
991    no "target" attribute needs to be specified, instead the text contents
992    acts as identifier.  That in itself wouldn't be terribly useful,
993    but together with the &lt;<x:ref>anchor-alias</x:ref>>, it allows
994    referring to other parts of the document with minimal additional markup.
995  </t>
996  <t>
997    For instance, given an alias definition such as
998  </t>
999  <figure>
1000    <artwork type="example">
1001      &lt;section title="Test" anchor="test">
1002        &lt;x:anchor-alias value="alias1"/>
1003        &lt;x:anchor-alias value="alias 2"/>
1004        ...
1005      &lt;/section></artwork>
1006  </figure>
1007  <t>
1008    the following simple references
1009  </t>
1010  <figure>
1011    <artwork type="example">
1012      &lt;x:ref>test&lt;/x:ref>
1013      &lt;x:ref>alias1&lt;/x:ref>
1014      &lt;x:ref>alias 2&lt;/x:ref></artwork>
1015  </figure>
1016  <t>
1017    are equivalent to...:
1018  </t>
1019  <figure>
1020    <artwork type="example">
1021      &lt;xref target="test">test&lt;/xref>
1022      &lt;xref target="test">alias1&lt;/xref>
1023      &lt;xref target="test">alias 2&lt;/xref></artwork>
1024  </figure>
1025</section>
1026
1027<section title="&lt;source> element" anchor="ext.element.source">
1028  <iref item="Extension Elements" subitem="source" primary="true"/>
1029  <iref item="source Extension Element" primary="true"/>
1030  <x:anchor-alias value="source"/>
1031  <t>
1032    Can be used to enhance a &lt;reference> with information about the
1033    location for the XML source. This can be used by the &lt;xref>
1034    processing code to automatically extract the target section number.
1035  </t>
1036  <figure>
1037    <preamble>
1038      For example:
1039    </preamble>
1040    <artwork type="example">
1041      ...
1042      &lt;xref target="RFC2616" x:fmt="of" x:rel="#PUT" />
1043      ...
1044   
1045      &lt;reference target="RFC2616"/>
1046        ...
1047        &lt;x:source href="rfc2616.xml"/>
1048        ...
1049    </artwork>
1050  </figure>
1051</section>
1052
1053<section title="&lt;sup> element" anchor="ext.element.sup">
1054  <iref item="Extension Elements" subitem="sup" primary="true"/>
1055  <iref item="sup Extension Element" primary="true"/>
1056  <x:anchor-alias value="sup"/>
1057  <t>
1058    This element is like the "<eref target="http://www.w3.org/TR/html401/struct/text.html#edef-SUP">sup</eref>" element in <xref target="HTML"/>.
1059  </t>
1060  <t>
1061    Note: the down conversion to RFC2629 format replaces
1062    "x<x:sup>y</x:sup>" by "x^y".
1063  </t>
1064</section>
1065
1066<section title="Extensions to Xml2rfc &lt;artwork&gt; element" anchor="ext-rfc2629.artwork">
1067<t>
1068  Sometimes, artwork occurs inside lists. To get it indent properly in xml2rfc's
1069  text output, it needs to be indented in the source. This is sub-optimal, as
1070  this whitespace will also appear in the HTML output, where it's already
1071  indented due to HTML's semantics.
1072</t>
1073<t>
1074  As a workaround, a "x:indent-with" attribute can be specified, containing
1075  a string that will be prepended to each line when <spanx style="verb">clean-for-DTD.xslt</spanx>
1076  is run (see <xref target="clean-for-dtd"/>).
1077</t>
1078</section>
1079
1080<section title="Extensions to Xml2rfc &lt;iref&gt; element" anchor="ext-rfc2629.iref">
1081<t>
1082  The extension attribute below is allowed on the standard &lt;iref&gt; element:
1083  <list style="symbols">
1084    <t>x:for-anchor specifies that the &lt;iref&gt; will also be automatically
1085    inserted whenever the specified anchor is cross-referenced -- this may
1086    save entering lots of &lt;iref&gt; instances. As a special case, a value of
1087    "" (empty string) refers to the anchor attribute of the closest ancestor.</t>
1088  </list>
1089</t>
1090</section>
1091
1092<section title="Extensions to Xml2rfc &lt;list&gt; element" anchor="ext-rfc2629.list">
1093<t>
1094  The extension attribute below is allowed on the standard &lt;list&gt; element:
1095  <list style="symbols">
1096    <t>x:indent specifies the amount of indentation for list items in hanging
1097    lists. This can be useful when the output format, such as XSL-FO, does not
1098    support automatical formatting. The value takes an XSL-FO width, such as "5em".
1099    The default is <spanx>length of longest label in characters</spanx> times
1100    <spanx>0.8em</spanx>.</t>
1101  </list>
1102</t>
1103<t>
1104  Also, the &lt;list&gt; element can take &lt;x:<x:ref>lt</x:ref>&gt; child elements instead of
1105  &lt;t&gt;, allowing to insert multiple paragraphs into a single list item.
1106</t>
1107</section>
1108
1109<section title="Extensions to Xml2rfc &lt;rfc&gt; element" anchor="ext-rfc2629.rfc">
1110<t>
1111  The extension attributes below are allowed on the standard &lt;rfc&gt; element:
1112  <list style="symbols">
1113    <t>grddl:transformation can be used to reference a GRDDL transform.</t>
1114    <t>x:maturiy-level can be used to specify the IETF Standards Track
1115    Maturity Level of "proposed", "draft" or "internet" (see <xref target="RFC2026" x:fmt="of" x:sec="4.1"/>).</t>
1116  </list>
1117</t>
1118</section>
1119
1120<section title="Extensions to Xml2rfc &lt;section&gt; element" anchor="ext-rfc2629.section">
1121<t>
1122  The extension attribute below is allowed on the standard &lt;list&gt; element:
1123  <list style="symbols">
1124    <t>x:fixed-section-number can be used to specify a fixed section number.
1125    This can be useful when formatting historic documents that used a different
1126    numbering style.</t>
1127  </list>
1128</t>
1129</section>
1130
1131<section title="Extensions to Xml2rfc &lt;xref&gt; element" anchor="ext-rfc2629.xref">
1132<t>
1133  Three extension attributes are allowed on the standard &lt;xref&gt; element:
1134  <list style="numbers">
1135    <t>x:sec can be specified to point to a specific section of the referenced document,</t>
1136    <t>x:rel may specify a relative reference to use when linking into the referenced document (if linking by section number is not available),</t>
1137    <t>x:fmt defines the text format to be used.</t>
1138  </list>
1139</t>
1140<t>
1141  The following formats are defined for the x:fmt attribute:
1142  <list style="hanging">
1143    <t hangText=", (Comma)">
1144      [<spanx>reference</spanx>], Section <spanx>sec</spanx>
1145    </t>
1146    <t hangText="()">
1147      [<spanx>reference</spanx>] (Section <spanx>sec</spanx>)
1148    </t>
1149    <t hangText="anchor">
1150      Like the default format, but without brackets.
1151    </t>
1152    <t hangText="of">
1153      Section <spanx>sec</spanx> of [<spanx>reference</spanx>]
1154    </t>
1155    <t hangText="number">
1156      <spanx>sec</spanx>
1157    </t>
1158    <t hangText="none">
1159      No output (can be used to have xrefs to references without
1160      having them rendered as such)
1161    </t>
1162    <t hangText="sec">
1163      Section <spanx>sec</spanx>
1164    </t>
1165  </list>
1166</t>
1167<t>
1168  These extensions are currently only supported for &lt;xref&gt; elements without
1169  child nodes.
1170</t>
1171<t>
1172  If the processor knows how to reference the target section, it will generate
1173  a link directly to the target section, such as in <xref target="RFC2119" x:fmt="," x:sec="5"/>.
1174</t>
1175</section>
1176
1177</section>
1178
1179<section title="Utilities" anchor="utilities">
1180
1181<section title="Checking References" anchor="checking-references">
1182<t>
1183  <spanx style="verb">check-references.xslt</spanx> can be used to check
1184  all references to RFC- and ID-series IETF publications and to W3C publications (note
1185  this script requires local copies of
1186  <eref target="ftp://ftp.isi.edu/in-notes/rfc-index.xml"/> and
1187  <eref target="http://www.w3.org/2002/01/tr-automation/tr.rdf"/> and
1188  will use the XML status information provided at <eref target="http://tools.ietf.org/"/>).
1189</t>
1190<t>
1191  If the document is supposed to be published on the IETF standards track,
1192  the desired level can be specified using the parameter <spanx style='verb'>intended-level</spanx>
1193  as 'proposed', 'draft' or 'internet'. Alternatively, it can be specified
1194  inside the document using the attribute x:maturity-level on the &lt;rfc> element.
1195</t>
1196<t>
1197  <x:h>Note:</x:h> Downward references should be
1198  annotated using the &lt;annotate> element, containing an &lt;xref> to
1199  <xref target="BCP97"/>.
1200</t>
1201<t>
1202  When an XSLT 2.0 processor is used, links in the document can be checked as well
1203  using the <spanx style='verb'>link-check</spanx> paramerer ('yes' or 'no').
1204  Note that this only works for http links to documents of type text/*.
1205</t>
1206<figure>
1207<preamble>
1208For instance, as of 2008-07-12, the script produces for <eref target="http://greenbytes.de/tech/webdav/rfc2518.xml"/>:
1209</preamble>
1210<artwork type="example">
1211> saxon rfc2518.xml check-references.xslt intended-status=PROPOSED \
1212  link-check=yes
1213
1214Normative References:
1215ISO-11578: not checked
1216ISO-639: not checked
1217ISO-8601: not checked
1218REC-xml-19980210: [FirstEdition] obsoleted by REC-xml-20001006
1219REC-xml-names-19990114: [FirstEdition] obsoleted by
1220 REC-xml-names-20060816
1221RFC1766: [PROPOSED STANDARD] obsoleted by RFC3066 RFC3282
1222RFC2068: [PROPOSED STANDARD] obsoleted by RFC2616
1223RFC2069: [PROPOSED STANDARD] obsoleted by RFC2617
1224RFC2119: [BEST CURRENT PRACTICE] (-> BCP0014) ok
1225RFC2141: [PROPOSED STANDARD] ok
1226RFC2277: [BEST CURRENT PRACTICE] (-> BCP0018) ok
1227RFC2396: [DRAFT STANDARD] obsoleted by RFC3986
1228RFC2279: [DRAFT STANDARD] obsoleted by RFC3629
1229
1230Informational References:
1231REC-PICS-labels-961031: [REC] ok
1232RFC1807: [INFORMATIONAL] ok
1233RFC2026: [BEST CURRENT PRACTICE] (-> BCP0009) ok
1234RFC2291: [INFORMATIONAL] ok
1235RFC2376: [INFORMATIONAL] obsoleted by RFC3023
1236RFC2413: [INFORMATIONAL] obsoleted by RFC5013
1237USMARC: not checked
1238WF: not checked
1239
1240Link Targets
1241&lt;http://www.w3.org/TR/1998/REC-xml-19980210>: ok
1242&lt;http://www.w3.org/TR/1999/REC-xml-names-19990114>: ok
1243&lt;http://www.dlib.org/dlib/july96/lagoze/07lagoze.html>: ok
1244&lt;http://www.w3.org/pub/WWW/TR/REC-PICS-labels-961031.html>: ok
1245</artwork></figure>
1246<t>
1247  Recognized formats in the &lt;seriesInfo> element are:
1248  <list style="symbols">
1249    <t>for RFCs, the name attribute must be "RFC", and the value attribute must
1250    be the number of the RFC,</t>
1251    <t>for Internet Drafs, the name attribute must be "ID" or "Internet-Draft", and the value attribute must
1252    be the file name of the draft (including the two-digit running number, but excluding a file extension),</t>
1253    <t>for W3C documents, the name attribute must be "W3C", must start with "W3C&#160;", or
1254    must start with "World Wide Web Consortium&#160;", and the value attribute
1255    must be the "shorthand" name of the specification, such as "REC-xml-19980210".</t>
1256  </list>
1257</t>
1258<x:note>
1259<t>
1260  <x:h>Note:</x:h> this stylesheet will need network access to check links and
1261  status of Internet Drafts. When running a Java-based XSLT engine, you may have
1262  to supply Java system properties specifying the HTTP proxy to be used, such
1263  as "-Dhttp.proxyHost=hostname -Dhttp.proxyPort=80".
1264</t>
1265</x:note>
1266
1267</section>
1268
1269<section title="Generating Graphs from References">
1270<t>
1271  <spanx style="verb">gen-reference-graph.xslt</spanx> generates a graph
1272  of RFC dependencies, using the same base data as in <spanx style="verb">check-references.xslt</spanx>
1273  (see <xref target="checking-references"/>). Its output is a "dot" file,
1274  to be processed by GraphViz (see <eref target="http://www.graphviz.org/"/>).
1275</t>
1276<figure>
1277<preamble>
1278The picture below shows the RFC dependencies in RFC2629.
1279</preamble>
1280<artwork src="rfc2629xslt-fig2.png" type="image/png">
1281(PNG output obtained from GraphViz)
1282</artwork>
1283</figure>
1284</section>
1285
1286<section title="Producing reference entries for books">
1287<t>
1288  <spanx style="verb">amazon-asin.xslt</spanx> uses the Amazon web services
1289  to generate a &lt;reference> element for a given ASIN (ISBN).
1290</t>
1291<figure>
1292<preamble>For instance:</preamble>
1293<artwork type="example">
1294&lt;?xml version="1.0" encoding="utf-8"?>
1295&lt;references>
1296 &lt;reference target="urn:isbn:0134516591">
1297   &lt;front>
1298     &lt;title>Simple Book, The: An Introduction to Internet Management,
1299               Revised Second Edition&lt;/title>
1300     &lt;author surname="Rose"
1301                fullname="Marshall T. Rose" initials="M. T. ">
1302       &lt;organization/>
1303     &lt;/author>
1304     &lt;author surname="Marshall"
1305                fullname="Rose T. Marshall" initials="R. T.">
1306       &lt;organization/>
1307     &lt;/author>
1308     &lt;date year="1996" month="March"/>
1309   &lt;/front>
1310   &lt;seriesInfo name="Prentice Hall" value=""/>
1311 &lt;/reference>
1312&lt;/references>
1313</artwork></figure>
1314<t>
1315  Note that the resulting XML usually requires checking, in this case Amazon's
1316  database is playing tricks with Marshall's name...
1317</t>
1318</section>
1319
1320<section title="Down-converting to RFC2629bis DTD" anchor="clean-for-dtd">
1321<t>
1322  <spanx style="verb">clean-for-DTD.xslt</spanx> can be used to down-convert
1323  some extensions to a format that is supported by the base xml2rfc
1324  distribution.  Note that these extensions are experimental (feedback
1325  appreciated).
1326</t>
1327<t>
1328  The following mappings are done:
1329  <list style="symbols">
1330    <t>
1331      &lt;iref> elements inside &lt;artwork> elements are moved in front
1332      of the enclosing &lt;figure> element.
1333    </t>
1334    <t>
1335      &lt;xref> elements inside &lt;artwork> are expanded just like in
1336      regular text (that is, the markup is stripped, but the element
1337      is replaced by the applicable replacement text).
1338    </t>
1339    <t>
1340      &lt;x:<x:ref>anchor-alias</x:ref>> elements get stripped.
1341    </t>
1342    <t>
1343      &lt;x:<x:ref>bcp14</x:ref>> elements get stripped.
1344    </t>
1345    <t>
1346      &lt;x:<x:ref>bb</x:ref>>, &lt;x:<x:ref>bc</x:ref>> and &lt;x:<x:ref>bt</x:ref>> elements get stripped.
1347    </t>
1348    <t>
1349      &lt;x:<x:ref>blockquote</x:ref>> elements get converted to
1350      indented text (through a &lt;list> element).
1351    </t>
1352    <t>
1353      &lt;x:<x:ref>dfn</x:ref>> elements get stripped.
1354    </t>
1355    <t>
1356      &lt;x:<x:ref>h</x:ref>> elements get stripped.
1357    </t>
1358    <t>
1359      &lt;x:<x:ref>link</x:ref>> elements get stripped.
1360    </t>
1361    <t>
1362      &lt;x:<x:ref>note</x:ref>> elements get converted to
1363      indented text (through a &lt;list> element).
1364    </t>
1365    <t>
1366      &lt;x:<x:ref>q</x:ref>> elements get stripped, with apostrophes
1367      added around the text.
1368    </t>
1369    <t>
1370      &lt;x:<x:ref>prose</x:ref>> elements are transformed into
1371      &lt;seriesInfo> elements (which is an abuse of the element and only
1372      a workaround until xml2rfc gets a matching extension).
1373    </t>
1374    <t>
1375      &lt;x:<x:ref>ref</x:ref>> elements get replaced by &lt;xref>
1376      elements, targetting either the anchor or another anchor with
1377      matching &lt;x:<x:ref>anchor-alias</x:ref>> child element.
1378    </t>
1379  </list>
1380</t>
1381</section>
1382
1383<section title="Extracting artwork" anchor="extract-artwork">
1384<t>
1385  With <spanx style="verb">extract-artwork.xslt</spanx>, artwork elements
1386  named through the "name" attribute can be extracted. This can be used
1387  to automatically check their syntax (for instance, when ABNFs appear
1388  within a figure element).
1389</t>
1390<figure><preamble>For instance:</preamble>
1391<artwork type="example">saxon rfc3986.xml extract-artwork.xslt name=uri.abnf
1392</artwork>
1393</figure>
1394<t>
1395  In addition, artwork of a specific type can be extracted, such as with:
1396</t>
1397<figure>
1398<artwork type="example">saxon rfc3986.xml extract-artwork.xslt type=abnf
1399</artwork>
1400</figure>
1401<t>
1402  When extracting by type, artwork elements with a specified name can be
1403  excluded; this can be handy when the document uses some kind of schema
1404  language, and an appendix contains the collected schema, repeating definitions
1405  from earlier on. Example:
1406</t>
1407<figure><artwork type="example">saxon rfc3986.xml extract-artwork.xslt type=abnf except-name=clschm
1408</artwork></figure>
1409</section>
1410
1411<section title="GRRDL" anchor="grddl">
1412<t>
1413  <spanx style="verb">rfc2629grddl.xslt</spanx> extracts RDF
1414  information. This is experimental work-in-progress. See
1415  <eref target="http://www.w3.org/TR/grddl/"/> for more information.
1416</t>
1417</section>
1418</section>
1419
1420 
1421
1422</middle>
1423
1424<back>
1425<references title="Informative References">
1426
1427<reference anchor='RFC2026'>
1428  <front>
1429    <title abbrev='Internet Standards Process'>The Internet Standards Process -- Revision 3</title>
1430    <author initials='S.' surname='Bradner' fullname='Scott O. Bradner'>
1431      <organization>Harvard University</organization>
1432      <address>
1433        <email>sob@harvard.edu</email>
1434      </address>
1435    </author>
1436    <date year='1996' month='October' />
1437  </front>
1438  <seriesInfo name='BCP' value='9' />
1439  <seriesInfo name='RFC' value='2026' />
1440</reference>
1441
1442<reference anchor="RFC2119">
1443  <front>
1444    <title abbrev="RFC Key Words">Key words for use in RFCs to Indicate Requirement Levels</title>
1445    <author initials="S." surname="Bradner" fullname="Scott Bradner">
1446      <organization>Harvard University</organization>
1447      <address>
1448        <email>sob@harvard.edu</email>
1449      </address>
1450    </author>
1451    <date month="March" year="1997"/>
1452  </front>
1453  <seriesInfo name="BCP" value="14"/>
1454  <seriesInfo name="RFC" value="2119"/>
1455</reference>
1456
1457<reference anchor="RFC2616">
1458  <front>
1459  <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
1460  <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
1461  <organization>University of California, Irvine, Information and Computer Science</organization>
1462  <address>
1463  <postal>
1464  <street/>
1465  <city>Irvine</city>
1466  <region>CA</region>
1467  <code>92697-3425</code>
1468  <country>US</country></postal>
1469  <phone>+1 949 824 1715</phone>
1470  <email>fielding@ics.uci.edu</email></address></author>
1471  <author initials="J." surname="Gettys" fullname="James Gettys">
1472  <organization>World Wide Web Consortium, MIT Laboratory for Computer Science</organization>
1473  <address>
1474  <postal>
1475  <street>545 Technology Square</street>
1476  <city>Cambridge</city>
1477  <region>MA</region>
1478  <code>02139</code>
1479  <country>US</country></postal>
1480  <phone/>
1481  <facsimile>+1 617 258 8682</facsimile>
1482  <email>jg@w3.org</email></address></author>
1483  <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
1484  <organization>Compaq Computer Corporation, Western Research Laboratory</organization>
1485  <address>
1486  <postal>
1487  <street>250 University Avenue</street>
1488  <city>Palo Alto</city>
1489  <region>CA</region>
1490  <code>94301</code>
1491  <country>US</country></postal>
1492  <phone/>
1493  <email>mogul@wrl.dec.com</email></address></author>
1494  <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
1495  <organization>World Wide Web Consortium, MIT Laboratory for Computer Science</organization>
1496  <address>
1497  <postal>
1498  <street>545 Technology Square</street>
1499  <city>Cambridge</city>
1500  <region>MA</region>
1501  <code>02139</code>
1502  <country>US</country></postal>
1503  <phone/>
1504  <facsimile>+1 617 258 8682</facsimile>
1505  <email>frystyk@w3.org</email></address></author>
1506  <author initials="L." surname="Masinter" fullname="Larry Masinter">
1507  <organization>Xerox Corporation</organization>
1508  <address>
1509  <postal>
1510  <street>3333 Coyote Hill Road</street>
1511  <city>Palo Alto</city>
1512  <region>CA</region>
1513  <code>94034</code>
1514  <country>US</country></postal>
1515  <phone/>
1516  <email>masinter@parc.xerox.com</email></address></author>
1517  <author initials="P.J." surname="Leach" fullname="Paul J. Leach">
1518  <organization>Microsoft Corporation</organization>
1519  <address>
1520  <postal>
1521  <street>1 Microsoft Way</street>
1522  <city>Redmond</city>
1523  <region>WA</region>
1524  <code>98052</code>
1525  <country>US</country></postal>
1526  <phone/>
1527  <email>paulle@microsoft.com</email></address></author>
1528  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1529  <organization>World Wide Web Consortium, MIT Laboratory for Computer Science</organization>
1530  <address>
1531  <postal>
1532  <street>545 Technology Square</street>
1533  <city>Cambridge</city>
1534  <region>MA</region>
1535  <code>02139</code>
1536  <country>US</country></postal>
1537  <phone>+1 617 258 8682</phone>
1538  <facsimile/>
1539  <email>timbl@w3.org</email></address></author>
1540  <date month="June" year="1999"/>
1541  </front>
1542  <seriesInfo name="RFC" value="2616"/>
1543</reference>
1544
1545<reference anchor='RFC2629'>
1546  <front>
1547    <title>Writing I-Ds and RFCs using XML</title>
1548    <author initials='M.T.' surname='Rose' fullname='Marshall T. Rose'>
1549      <organization>Invisible Worlds, Inc.</organization>
1550      <address>
1551        <postal>
1552          <street>660 York Street</street>
1553          <city>San Francisco</city>
1554          <region>CA</region>
1555          <code>94110</code>
1556          <country>US</country>
1557        </postal>
1558        <phone>+1 415 695 3975</phone>
1559        <email>mrose@not.invisible.net</email>
1560        <uri>http://invisible.net/</uri>
1561      </address>
1562    </author>
1563    <date month='June' year='1999' />
1564  </front>
1565  <seriesInfo name='RFC' value='2629' />
1566</reference>
1567
1568<reference anchor='RFC2648'>
1569  <front>
1570    <title>A URN Namespace for IETF Documents</title>
1571    <author initials='R.' surname='Moats' fullname='Ryan Moats'>
1572      <organization>AT&amp;T</organization>
1573      <address>
1574      <postal>
1575        <street>15621 Drexel Circle</street>
1576        <city>Omaha</city>
1577        <region>NE</region>
1578        <code>68135-2358</code>
1579        <country>US</country>
1580      </postal>
1581      <email>jayhawk@att.com</email></address>
1582    </author>
1583    <date month='August' year='1999' />
1584  </front>
1585  <seriesInfo name='RFC' value='2648' />
1586</reference>
1587
1588<reference anchor='RFC2731'>
1589  <front>
1590    <title>Encoding Dublin Core Metadata in HTML</title>
1591    <author initials='J.A.' surname='Kunze' fullname='John A. Kunze'>
1592      <organization>University of California, San Francisco,  Center for Knowledge Management</organization>
1593      <address>
1594        <postal>
1595          <street>530 Parnassus Ave</street>
1596          <street>Box 0840</street>
1597          <city>San Francisco</city>
1598          <region>CA</region>
1599          <code>94143-0840</code>
1600          <country>US</country>
1601        </postal>
1602        <facsimile>+1 415 476 4653</facsimile>
1603        <email>jak@ckm.ucsf.edu</email>
1604      </address>
1605    </author>
1606    <date month='December' year='1999' />
1607  </front>
1608  <seriesInfo name='RFC' value='2731' />
1609</reference>
1610
1611<reference anchor='DC-HTML' target="http://dublincore.org/documents/2008/08/04/dc-html/">
1612  <front>
1613    <title>Expressing Dublin Core metadata using HTML/XHTML meta and link elements</title>
1614    <author initials='P.' surname='Johnston' fullname='Pete Johnston'>
1615      <organization>Eduserv Foundation</organization>
1616      <address>
1617        <email>pete.johnston@eduserv.org.uk</email>
1618      </address>
1619    </author>
1620    <author initials='A.' surname='Powell' fullname='Andy Powell'>
1621      <organization>Eduserv Foundation</organization>
1622      <address>
1623        <email>andy.powell@eduserv.org.uk</email>
1624      </address>
1625    </author>
1626    <date month='August' year='2008' />
1627  </front>
1628  <seriesInfo name='Dublin Core Metadata Initiative' value='' />
1629</reference>
1630
1631<reference anchor="RFC5234">
1632  <front>
1633    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
1634    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
1635      <organization>Brandenburg InternetWorking</organization>
1636      <address>
1637      <postal>
1638      <street>675 Spruce Dr.</street>
1639      <city>Sunnyvale</city>
1640      <region>CA</region>
1641      <code>94086</code>
1642      <country>US</country></postal>
1643      <phone>+1.408.246.8253</phone>
1644      <email>dcrocker@bbiw.net</email></address> 
1645    </author>
1646    <author initials="P." surname="Overell" fullname="Paul Overell">
1647      <organization>THUS plc.</organization>
1648      <address>
1649      <postal>
1650      <street>1/2 Berkeley Square</street>
1651      <street>99 Berkely Street</street>
1652      <city>Glasgow</city>
1653      <code>G3 7HR</code>
1654      <country>UK</country></postal>
1655      <email>paul.overell@thus.net</email></address>
1656    </author>
1657    <date month="January" year="2008"/>
1658  </front>
1659  <seriesInfo name="STD" value="68"/>
1660  <seriesInfo name="RFC" value="5234"/>
1661</reference>
1662
1663<reference anchor='RFC5741'>
1664  <front>
1665    <title>RFC Streams, Headers, and Boilerplates</title>
1666    <author initials='L.' surname='Daigle' fullname='Leslie Daigle'/>
1667    <author initials='O.' surname='Kolkman' fullname='Olaf Kolkman'/>
1668    <date month='December' year='2009' />
1669  </front>
1670  <seriesInfo name='RFC' value='5741' />
1671</reference>
1672
1673
1674<reference anchor="HTML" target="http://www.w3.org/TR/html401/">
1675  <front>
1676    <title>HTML 4.01 Specification</title>
1677    <author initials="D." surname="Raggett" fullname="David Raggett">
1678      <organization>W3C</organization>
1679      <address>
1680        <email>dsr@w3.org</email>
1681      </address>
1682    </author>
1683    <author initials="A." surname="Hors" fullname="Arnaud Le Hors">
1684      <organization>W3C</organization>
1685    </author>
1686    <author initials="I." surname="Jacobs" fullname="Ian Jacobs">
1687      <organization>W3C</organization>
1688    </author>
1689    <date month="December" day="24" year="1999" />
1690  </front>
1691  <seriesInfo name="W3C" value="REC-html401-19991224" />
1692</reference>
1693
1694<reference anchor="XHTML2" target="http://www.w3.org/TR/xhtml2">
1695  <front>
1696    <title>XHTML&#8482; 2.0</title>
1697    <author initials="J." surname="Axelsson" fullname="Jonny Axelsson">
1698      <organization>Opera Software</organization>
1699    </author>
1700    <author initials="M." surname="Birbeck" fullname="Mark Birbeck">
1701      <organization>x-port.net</organization>
1702    </author>
1703    <author initials="M." surname="Dubinko" fullname="Micah Dubinko">
1704      <organization></organization>
1705    </author>
1706    <author initials="B." surname="Epperson" fullname="Beth Epperson">
1707      <organization>Websense</organization>
1708    </author>
1709    <author initials="M." surname="Ishikawa" fullname="Masayasu Ishikawa">
1710      <organization>W3C</organization>
1711    </author>
1712    <author initials="S." surname="McCarron" fullname="Shane McCarron">
1713      <organization>Applied Testing and Technology</organization>
1714    </author>
1715    <author initials="A." surname="Navarro" fullname="Ann Navarro">
1716      <organization>WebGeek, Inc.</organization>
1717    </author>
1718    <author initials="S." surname="Pemberton" fullname="Steven Pemberton">
1719      <organization>CWI</organization>
1720    </author>
1721    <date month="July" day="26" year="2006" />
1722  </front>
1723  <seriesInfo name="W3C" value="WD-xhtml2-20060726" />
1724</reference>
1725
1726<reference anchor="XSL-FO" target="http://www.w3.org/TR/2006/REC-xsl11-20061205/">
1727  <front>
1728    <title>Extensible Stylesheet Language (XSL) Version 1.1</title>
1729    <author initials="A." surname="Berglund" fullname="Anders Berglund">
1730      <organization>IBM</organization>
1731      <address>
1732        <email>alrb@us.ibm.com</email>
1733      </address>
1734    </author>
1735    <date month="Dec" day="5" year="2006" />
1736  </front>
1737  <seriesInfo name="W3C" value="REC-xsl11-20061205" />
1738</reference>
1739
1740<reference anchor="RNC" target="http://www.oasis-open.org/committees/relax-ng/compact-20021121.html">
1741  <front>
1742    <title>RELAX NG Compact Syntax</title>
1743    <author initials="J." surname="Clark" fullname="James Clark">
1744      <organization/>
1745      <address>
1746        <email>jjc@jclark.com</email>
1747      </address>
1748    </author>
1749    <date month="Nov" day="21" year="2002" />
1750  </front>
1751  <seriesInfo name="OASIS" value=""/>
1752</reference>
1753
1754<reference anchor='BCP97'>
1755  <front>
1756    <title>Handling Normative References to Standards-Track Documents</title>
1757    <author initials='J.' surname='Klensin' fullname='J. Klensin'>
1758      <organization />
1759      <address>
1760        <email>klensin+ietf@jck.com</email>
1761      </address>
1762    </author>
1763    <author initials='S.' surname='Hartman' fullname='S. Hartman'>
1764      <organization>MIT</organization>
1765      <address>
1766        <email>hartmans-ietf@mit.edu</email>
1767      </address>
1768    </author>
1769    <date year='2007' month='June' />
1770  </front>
1771  <seriesInfo name='BCP' value='97' />
1772  <seriesInfo name='RFC' value='4897' />
1773</reference>
1774
1775<reference anchor="XML" target="http://www.w3.org/TR/2008/REC-xml-20081126/">
1776  <front>
1777    <title>Extensible Markup Language (XML) 1.0 (Fifth Edition)</title>
1778    <author initials="T." surname="Bray" fullname="Tim Bray">
1779      <organization>Textuality and Netscape</organization>
1780      <address>
1781        <email>tbray@textuality.com</email>
1782      </address>
1783    </author>
1784    <author initials="J." surname="Paoli" fullname="Jean Paoli">
1785      <organization>Microsoft</organization>
1786      <address>
1787        <email>jeanpa@microsoft.com</email>
1788      </address>
1789    </author>
1790    <author initials="C.M." surname="Sperberg-McQueen" fullname="C. M. Sperberg-McQueen">
1791      <organization>W3C</organization>
1792      <address>
1793        <email>cmsmcq@w3.org</email>
1794      </address>
1795    </author>
1796    <author initials="E." surname="Maler" fullname="Eve Maler">
1797      <organization>Sun Microsystems</organization>
1798      <address>
1799        <email>eve.maler@east.sun.com</email>
1800      </address>
1801    </author>
1802    <author initials="F." surname="Yergeau" fullname="Francois Yergeau">
1803      <organization/>
1804    </author>
1805    <date day="26" month="November" year="2008"/>
1806  </front>
1807  <seriesInfo name="W3C" value="REC-xml-20081126"/>
1808</reference>
1809</references>
1810
1811  <section title="RELAX NG Compact Schema" anchor="grammar">
1812  <iref item="Grammar" primary="true"/>
1813  <iref item="Schema" primary="true"/>
1814  <iref item="RELAX NG Compact Schema" primary="true"/>
1815  <t>
1816    The RelaxNG schema (<xref target="RNC"/>) below can be used to validate
1817    input documents (for instance, with <eref target="http://www.thaiopensource.com/relaxng/jing.html">Jing</eref>).
1818  </t>
1819  <t>
1820    <spanx>Note that this is work in progress, and doesn't yet cover all
1821    extensions completely.</spanx>
1822  </t>
1823  <figure>
1824    <artwork type="application/relax-ng-compact-syntax" name="rfc2629-ext.rnc" x:extraction-note="# Automatically extracted from rfc2629xslt.xml. DO NOT EDIT!&#10;">
1825<spanx># WORK IN PROGRESS! PLEASE REPORT PROBLEMS TO THE AUTHOR.</spanx>
1826
1827<spanx># Define our extension namespace</spanx>
1828namespace x = "http://purl.org/net/xml2rfc/ext"
1829
1830<spanx># Define GRDDL namespace</spanx>
1831namespace grddl = "http://www.w3.org/2003/g/data-view#"
1832
1833<spanx># Define RDF namespace</spanx>
1834namespace rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
1835
1836<spanx># Include rfc2629bis RNC grammar</spanx>
1837include "rfc2629.rnc" {
1838 
1839  <spanx># Redefine &lt;artwork> to allow markup</spanx>
1840  artwork =
1841    element artwork {
1842      attlist.artwork,
1843      (TEXT
1844        <spanx style="strong">| eref</spanx> 
1845        <spanx style="strong">| iref</spanx> 
1846        <spanx style="strong">| spanx</spanx> 
1847        <spanx style="strong">| xref</spanx>
1848        <spanx style="strong">| <x:ref>x_abnf-char-sequence</x:ref></spanx>
1849        <spanx style="strong">| <x:ref>x_bb</x:ref></spanx>
1850        <spanx style="strong">| <x:ref>x_bc</x:ref></spanx>
1851        <spanx style="strong">| <x:ref>x_bcp14</x:ref></spanx>
1852        <spanx style="strong">| <x:ref>x_bt</x:ref></spanx>
1853        <spanx style="strong">| <x:ref>x_highlight</x:ref></spanx>
1854        <spanx style="strong">| <x:ref>x_length-of</x:ref></spanx>
1855        <spanx style="strong">| <x:ref>x_parse-xml</x:ref></spanx>
1856        <spanx style="strong">| <x:ref>x_ref</x:ref></spanx>
1857        <spanx style="strong">| <x:ref>x_span</x:ref></spanx>
1858        <spanx style="strong">| <x:ref>x_x</x:ref></spanx>)*
1859    }
1860
1861  <spanx># Redefine &lt;back> to allow boilerplate</spanx>
1862  back =
1863    element back {
1864      attlist.back,
1865      references*,
1866      section*,
1867      <spanx style="strong"><x:ref>x_boilerplate</x:ref>?</spanx>
1868    }
1869
1870  <spanx># Redefine &lt;c> to allow our extension elements</spanx>
1871  c =
1872    element c {
1873      attlist.c,
1874      (TEXT
1875        | xref
1876        | eref
1877        | iref
1878        | cref
1879        | spanx
1880        <spanx style="strong">| <x:ref>x_ref</x:ref></spanx>)*
1881    }
1882
1883  <spanx># Redefine &lt;cref> to allow more child elements</spanx>
1884  cref =
1885    element cref {
1886      attlist.cref,
1887      (TEXT
1888        | eref
1889        | xref)*
1890    }
1891
1892  <spanx># Redefine &lt;front> to allow boilerplate</spanx>
1893  front =
1894    element front {
1895      attlist.front,
1896      title,
1897      author+,
1898      date,
1899      area*,
1900      workgroup*,
1901      keyword*,
1902      <spanx style="strong"><x:ref>x_boilerplate</x:ref>?,</spanx>
1903      abstract?,
1904      note*
1905    }
1906 
1907  <spanx># Redefine &lt;list> element to allow &lt;x:<x:ref>lt</x:ref>> child elements</spanx>
1908  \list =
1909    element list {
1910      attlist.list,
1911      (t+ <spanx style="strong">| <x:ref>x_lt</x:ref>+</spanx>)
1912    }   
1913   
1914  <spanx># Redefine &lt;preamble> to allow our extension elements</spanx>
1915  preamble =
1916    element preamble {
1917      attlist.preamble,
1918      (TEXT
1919        | xref
1920        | eref
1921        | iref
1922        | cref
1923        | spanx
1924        <spanx style="strong">| <x:ref>x_anchor-alias</x:ref></spanx>)*
1925    }
1926
1927  <spanx># Redefine &lt;postamble> to allow our extension elements</spanx>
1928  postamble =
1929    element postamble {
1930      attlist.postamble,
1931      (TEXT
1932        | xref
1933        | eref
1934        | iref
1935        | cref
1936        | spanx
1937        <spanx style="strong">| <x:ref>x_bcp14</x:ref></spanx>)*
1938    }
1939
1940  <spanx># Redefine &lt;reference> to allow our extension elements</spanx>
1941  reference =
1942    element reference {
1943      attlist.reference,
1944      front,
1945      seriesInfo*,
1946      <spanx style="strong"><x:ref>x_prose</x:ref>?</spanx>
1947      format*,
1948      annotation*,
1949      <spanx style="strong"><x:ref>x_source</x:ref>?</spanx>
1950    }
1951
1952  <spanx># Redefine &lt;rfc> to allow our extension elements</spanx>
1953  rfc =
1954    element rfc {
1955      attlist.rfc,
1956      <spanx style="strong"><x:ref>x_link</x:ref>*,</spanx>
1957      <spanx style="strong"><x:ref>x_assign-section-number</x:ref>*,</spanx>
1958      front,
1959      middle,
1960      back?
1961    }
1962
1963  <spanx># Redefine &lt;section> to allow our extension elements</spanx>
1964  section =
1965    element section {
1966      attlist.section,
1967      (t
1968       | figure
1969       | texttable
1970       | iref
1971       | section
1972       <spanx style="strong">| <x:ref>x_anchor-alias</x:ref></spanx>
1973       <spanx style="strong">| <x:ref>x_blockquote</x:ref></spanx>
1974       <spanx style="strong">| <x:ref>x_include-author</x:ref></spanx>
1975       <spanx style="strong">| <x:ref>x_note</x:ref></spanx>
1976       <spanx style="strong">| <x:ref>rdf_Description</x:ref></spanx>)*
1977    }
1978
1979  <spanx># Redefine &lt;spanx> to allow some markup</spanx>
1980  spanx =
1981    element spanx {
1982      attlist.spanx,
1983      (TEXT
1984        <spanx style="strong">| iref</spanx>
1985        <spanx style="strong">| xref</spanx>
1986        <spanx style="strong">| <x:ref>x_ref</x:ref></spanx>)*
1987    }
1988
1989  <spanx># Redefine &lt;t> to allow our extension elements</spanx>
1990  t =
1991    element t {
1992      attlist.t,
1993      (TEXT
1994       | \list
1995       | figure
1996       | xref
1997       | eref
1998       | iref
1999       | cref
2000       | spanx
2001       | vspace
2002       <spanx style="strong">| <x:ref>x_abnf-char-sequence</x:ref></spanx>
2003       <spanx style="strong">| <x:ref>x_anchor-alias</x:ref></spanx>
2004       <spanx style="strong">| <x:ref>x_bcp14</x:ref></spanx>
2005       <spanx style="strong">| <x:ref>x_dfn</x:ref></spanx>
2006       <spanx style="strong">| <x:ref>x_h</x:ref></spanx>
2007       <spanx style="strong">| <x:ref>x_q</x:ref></spanx>
2008       <spanx style="strong">| <x:ref>x_ref</x:ref></spanx>
2009       <spanx style="strong">| <x:ref>x_sup</x:ref></spanx>)*
2010    }
2011}
2012
2013<spanx># Allow x:indent-with attribute on &lt;artwork></spanx>
2014attlist.artwork &amp;=
2015  attribute x:indent-with { ATEXT }?
2016
2017<spanx># Allow anchor and x:annotation attributes on &lt;author></spanx>
2018attlist.author &amp;=
2019  attribute anchor { xsd:ID }?,
2020  attribute x:annotation { ATEXT }?
2021 
2022  <spanx># Extend attribute set for &lt;iref> (see <xref target="ext-rfc2629.iref"/>)</spanx>
2023attlist.iref &amp;=
2024  attribute x:for-anchor { ATEXT }?
2025
2026<spanx># Extend attribute set for &lt;list> (see <xref target="ext-rfc2629.list"/>)</spanx>
2027attlist.list &amp;=
2028  attribute x:indent { ATEXT }?
2029
2030<spanx># Extend attribute set for &lt;preamble></spanx>
2031attlist.preamble &amp;=
2032  attribute anchor { xsd:ID }?
2033
2034<spanx># Extend attribute set for &lt;rfc></spanx>
2035attlist.rfc &amp;=
2036  attribute grddl:transformation { ATEXT }?,
2037  attribute x:maturity-level { "proposed" | "draft" | "internet" }?
2038
2039<spanx># Extend attribute set for &lt;section> (see <xref target="ext-rfc2629.section"/>)</spanx>
2040attlist.section &amp;=
2041  attribute x:fixed-section-number { ATEXT }?
2042
2043<spanx># Allow anchor attribute on &lt;spanx></spanx>
2044attlist.spanx &amp;=
2045  attribute anchor { xsd:ID }?
2046
2047<spanx># Allow x:quotes attribute on &lt;title></spanx>
2048attlist.title &amp;=
2049  attribute x:quotes { "true" | "false" }?
2050
2051<spanx># Allow annotation attribute on &lt;uri></spanx>
2052attlist.uri &amp;=
2053  attribute x:annotation { ATEXT }?
2054
2055<spanx># Extend attribute set for &lt;xref> (see <xref target="ext-rfc2629.xref"/>)</spanx>
2056attlist.xref &amp;=
2057  attribute x:fmt  { "()" | "," | "anchor" | "of" | "number" | "sec" |
2058                     "none" }?,
2059  attribute x:rel  { ATEXT }?,
2060  attribute x:sec  { ATEXT }?
2061
2062<spanx anchor="x_abnf-char-sequence"><iref item="abnf-char-sequence Extension Element"/><iref item="Extension Elements" subitem="abnf-char-sequence"
2063/># Conversion to ABNF char sequence (see <xref target="ext.element.abnf-char-sequence"/>)</spanx>
2064<x:ref>x_abnf-char-sequence</x:ref> =
2065  element x:abnf-char-sequence {
2066    TEXT
2067  }
2068
2069<spanx anchor="x_anchor-alias"><iref item="anchor-alias Extension Element"/><iref item="Extension Elements" subitem="anchor-alias"
2070/># Aliasing of anchors (see <xref target="ext.element.anchor-alias"/>)</spanx>
2071<x:ref>x_anchor-alias</x:ref> =
2072  element x:anchor-alias {
2073    attribute value { TEXT },
2074    empty
2075  }
2076
2077<spanx anchor="x_include-author"><iref item="include-author Extension Element"/><iref item="Extension Elements" subitem="include-author"
2078/># Including Author information
2079# (experimental)</spanx>
2080<x:ref>x_include-author</x:ref> =
2081  element x:include-author {
2082    attribute target { xsd:IDREF }
2083  }
2084
2085<spanx anchor="x_assign-section-number"><iref item="assign-section-number Extension Element"/><iref item="Extension Elements" subitem="assign-section-number"
2086/># Setting section numbers for internally generated sections
2087# (experimental)</spanx>
2088<x:ref>x_assign-section-number</x:ref> =
2089  element x:assign-section-number {
2090    attribute builtin-target { "authors" },
2091    attribute number { TEXT },
2092    empty
2093  }
2094
2095<spanx anchor="x_bb"><iref item="bb Extension Element"/><iref item="Extension Elements" subitem="bb"
2096/># Bottom line of box drawing (see <xref target="ext.element.bb"/>)</spanx>
2097<x:ref>x_bb</x:ref> =
2098  element x:bb {
2099    (TEXT
2100      | iref
2101      | xref
2102      | <x:ref>x_bb</x:ref>
2103      | <x:ref>x_bc</x:ref>
2104      | <x:ref>x_bt</x:ref>
2105      | <x:ref>x_ref</x:ref>)*
2106  }
2107
2108<spanx anchor="x_bc"><iref item="bc Extension Element"/><iref item="Extension Elements" subitem="bc"
2109/># Center line of box drawing (see <xref target="ext.element.bc"/>)</spanx>
2110<x:ref>x_bc</x:ref> =
2111  element x:bc {
2112    (TEXT
2113      | iref
2114      | spanx
2115      | xref
2116      | <x:ref>x_bb</x:ref>
2117      | <x:ref>x_bc</x:ref>
2118      | <x:ref>x_bt</x:ref>
2119      | <x:ref>x_ref</x:ref>)*
2120  }
2121
2122<spanx anchor="x_bcp14"><iref item="bcp14 Extension Element"/><iref item="Extension Elements" subitem="bcp14"
2123/># BCP14/RFC2119 keywords (see <xref target="ext.element.bcp14"/>)</spanx>
2124<x:ref>x_bcp14</x:ref> =
2125  element x:bcp14 {
2126    "MAY"
2127    | "MUST"
2128    | "MUST NOT"
2129    | "NOT RECOMMENDED"
2130    | "OPTIONAL"
2131    | "RECOMMENDED"
2132    | "REQUIRED"
2133    | "SHALL"
2134    | "SHALL NOT"
2135    | "SHOULD"
2136    | "SHOULD NOT"
2137  }
2138 
2139<spanx anchor="x_blockquote"><iref item="blockquote Extension Element"/><iref item="Extension Elements" subitem="blockquote"
2140/># Blockquote (see <xref target="ext.element.blockquote"/>)</spanx>
2141<x:ref>x_blockquote</x:ref> =
2142  element x:blockquote {
2143    attribute cite { URI }?,
2144    t+
2145  }
2146
2147<spanx anchor="x_boilerplate"><iref item="boilerplate Extension Element"/><iref item="Extension Elements" subitem="boilerplate"
2148/># Boilerplate (see <xref target="ext.element.blockquote"/>) </spanx>
2149<x:ref>x_boilerplate</x:ref> =
2150  element x:boilerplate {
2151    section+
2152  }
2153
2154<spanx anchor="x_bt"><iref item="bt Extension Element"/><iref item="Extension Elements" subitem="bt"
2155/># Top line of box drawing (see <xref target="ext.element.bt"/>)</spanx>
2156<x:ref>x_bt</x:ref> =
2157  element x:bt {
2158    (TEXT
2159      | iref
2160      | xref
2161      | <x:ref>x_bb</x:ref>
2162      | <x:ref>x_bc</x:ref>
2163      | <x:ref>x_bt</x:ref>
2164      | <x:ref>x_ref</x:ref>)*
2165  }
2166
2167<spanx anchor="x_dfn"><iref item="dfn Extension Element"/><iref item="Extension Elements" subitem="dfn"
2168/># Definition (see <xref target="ext.element.dfn"/>)</spanx>
2169<x:ref>x_dfn</x:ref> =
2170  element x:dfn {
2171    attribute anchor { xsd:ID }?,
2172    (TEXT
2173      | iref)*
2174  }
2175 
2176<spanx anchor="x_h"><iref item="h Extension Element"/><iref item="Extension Elements" subitem="h"
2177/># Heading (see <xref target="ext.element.h"/>)</spanx>
2178<x:ref>x_h</x:ref> =
2179  element x:h {
2180    TEXT
2181  }
2182
2183<spanx anchor="x_highlight"><iref item="highlight Extension Element"/><iref item="Extension Elements" subitem="highlight"
2184/># Heading (see <xref target="ext.element.highlight"/>)</spanx>
2185<x:ref>x_highlight</x:ref> =
2186  element x:highlight {
2187    TEXT
2188  }
2189
2190<spanx anchor="x_length-of"><iref item="length-of Extension Element"/><iref item="Extension Elements" subitem="length-of"
2191/># Length Measurement (see <xref target="ext.element.length-of"/>)</spanx>
2192<x:ref>x_length-of</x:ref> =
2193  element x:length-of {
2194    attribute indented { NUMBER }?,
2195    attribute target { xsd:IDREF },
2196    empty
2197  }
2198
2199<spanx anchor="x_link"><iref item="link Extension Element"/><iref item="Extension Elements" subitem="link"
2200/># Link (see <xref target="ext.element.link"/>)</spanx>
2201<x:ref>x_link</x:ref> =
2202  element x:link {
2203    attribute href { URI },
2204    attribute title { TEXT }?,
2205    attribute rel { TEXT },
2206    empty
2207  }
2208 
2209<spanx anchor="x_lt"><iref item="lt Extension Element"/><iref item="Extension Elements" subitem="lt"
2210/># Extended list item (see <xref target="ext.element.lt"/>)</spanx>
2211<x:ref>x_lt</x:ref> =
2212  element x:lt {
2213    attribute anchor { xsd:ID }?,
2214    attribute hangText { TEXT }?,
2215    t+
2216  }
2217
2218<spanx anchor="x_note"><iref item="note Extension Element"/><iref item="Extension Elements" subitem="note"
2219/># Note (see <xref target="ext.element.note"/>)</spanx>
2220<x:ref>x_note</x:ref> =
2221  element x:note {
2222    t+
2223  }
2224
2225<spanx anchor="x_parse-xml"><iref item="parse-xml Extension Element"/><iref item="Extension Elements" subitem="parse-xml"
2226/># Signal XML content (see <xref target="ext.element.parse-xml"/>)</spanx>
2227<x:ref>x_parse-xml</x:ref> =
2228  element x:parse-xml {
2229    (TEXT
2230      | xref)*
2231  }
2232
2233<spanx anchor="x_prose"><iref item="prose Extension Element"/><iref item="Extension Elements" subitem="prose"
2234/># Inline prose in a reference (see <xref target="ext.element.prose"/>)</spanx>
2235<x:ref>x_prose</x:ref> =
2236  element x:prose {
2237    TEXT
2238  }
2239
2240<spanx anchor="x_q"><iref item="q Extension Element"/><iref item="Extension Elements" subitem="q"
2241/># Inline quote (see <xref target="ext.element.q"/>)</spanx>
2242<x:ref>x_q</x:ref> =
2243  element x:q {
2244    TEXT
2245  }
2246
2247<spanx anchor="x_ref"><iref item="ref Extension Element"/><iref item="Extension Elements" subitem="ref"
2248/># Anchor reference (see <xref target="ext.element.ref"/>)</spanx> 
2249<x:ref>x_ref</x:ref> =
2250  element x:ref {
2251    attribute anchor { xsd:ID }?,
2252    TEXT
2253  }
2254
2255<spanx anchor="x_source"><iref item="source Extension Element"/><iref item="Extension Elements" subitem="source"
2256/># source information (see <xref target="ext.element.source"/>)</spanx> 
2257<x:ref>x_source</x:ref> =
2258  element x:source {
2259    attribute basename { ATEXT }?,
2260    attribute href { URI },
2261    empty
2262  }
2263
2264<spanx anchor="x_sup"><iref item="sup Extension Element"/><iref item="Extension Elements" subitem="sup"
2265/># superscript (see <xref target="ext.element.sup"/>)</spanx>
2266<x:ref>x_sup</x:ref> =
2267  element x:sup {
2268    TEXT
2269  }
2270
2271<spanx anchor="x_span"><iref item="span Extension Element"/><iref item="Extension Elements" subitem="span"
2272/># Inline Span <!--(see <xref target="ext.element.span"/>)--></spanx>
2273<x:ref>x_span</x:ref> =
2274  element x:span {
2275    attribute anchor { xsd:ID }?,
2276    (TEXT
2277      | <x:ref>x_parse-xml</x:ref>)*
2278  }
2279
2280<spanx anchor="x_x"><iref item="x Extension Element"/><iref item="Extension Elements" subitem="x"
2281/># Nop (for alignment in source)</spanx>
2282<x:ref>x_x</x:ref> =
2283  element x:x {
2284    empty
2285  }
2286
2287<spanx anchor="rdf_Description"><iref item="rdf:Description Extension Element"/><iref item="Extension Elements" subitem="rdf:Description"
2288/># Embed RDF statements </spanx>
2289<x:ref>rdf_Description</x:ref> =
2290  element rdf:Description {
2291    rdf_content
2292  }
2293 
2294rdf_content =
2295  ( TEXT | element * { rdf_content })*
2296</artwork></figure>
2297  </section>
2298 
2299  <section title="Implementation Notes">
2300 
2301  <section title="Recognized type attributes for &lt;artwork> element">
2302  <t>
2303    Specific values in the &lt;artwork> element's "type" attribute are
2304    recognized and cause a different visual style to be used:
2305  </t>
2306  <texttable>
2307    <ttcol>Media Type</ttcol>
2308    <ttcol>Comment</ttcol>
2309   
2310    <c>abnf</c><c>ABNF as per <xref target="RFC5234"/></c>
2311    <c>abnf2616</c><c>ABNF as per <xref target="RFC2616" x:fmt="," x:sec="2.1" /></c>
2312    <c>application/relax-ng-compact-syntax</c><c>Relax NG Compact Syntax as per <xref target="RNC"/></c>
2313    <c>application/xml-dtd</c><c>XML DTD</c>
2314    <c>message/http; msgtype="request"</c><c>HTTP message, as per <xref target="RFC2616" x:fmt="," x:sec="19.1" /></c>
2315    <c>message/http; msgtype="response"</c><c>HTTP message, as per <xref target="RFC2616" x:fmt="," x:sec="19.1" /></c>
2316  </texttable>
2317  </section>
2318 
2319  </section>
2320 
2321  <section title="Examples" anchor="examples">
2322
2323  <section title="Using the 'Internal Subset'" anchor="examples.internalsubset">
2324  <t>
2325    The prolog of the XML document can both be used to refer to an external
2326    DTD, and also to define internal entities (<xref target="XML" x:fmt="of" x:sec="2.8" x:rel="#sec-prolog-dtd"/>):
2327  </t>
2328  <figure><artwork type="example">
2329&lt;?xml version="1.0"?>
2330&lt;?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
2331
2332&lt;!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
2333
2334  &lt;!-- <spanx>use "&amp;MAY;" for a BCP 14 "MAY", see <xref target="ext.element.bcp14"/></spanx> -->
2335  &lt;!ENTITY MAY
2336  "&lt;bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MAY&lt;/bcp14>">
2337
2338  &lt;!-- <spanx>re-declare "&amp;nbsp;" as code point 160 (non-breaking space)</spanx> -->
2339  &lt;!-- <spanx>you may need this for UAs that do not read external DTDs</spanx> -->
2340  &lt;!ENTITY nbsp
2341  "&amp;#160;">
2342
2343  &lt;!-- <spanx>allow later RFC2616 reference using "&amp;rfc2616;"</spanx> -->
2344  &lt;!-- <spanx>the data will be fetched from xml.resource.org</spanx> -->
2345  &lt;!ENTITY rfc2616 PUBLIC
2346  "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2616.xml">
2347
2348  &lt;!-- <spanx>allow a custom reference using "&amp;mydraft;"</spanx> -->
2349  &lt;!-- <spanx>the data will be fetched from the same location as the
2350       source file</spanx> -->
2351  &lt;!ENTITY mydraft PUBLIC "reference.mydraft.xml">
2352]>
2353</artwork>
2354<postamble>
2355  Note: including entities from a remote site will not work in Firefox,
2356  see <eref target="https://bugzilla.mozilla.org/show_bug.cgi?id=22942"/>.</postamble>
2357</figure>
2358 
2359  </section>
2360
2361  <section title="Customization" anchor="examples.customizing">
2362  <t>
2363    The XSLT code can be customized by creating a custom XSLT file that
2364    uses &lt;xsl:import> to include the original code, and just overrides
2365    particular rules.
2366  </t>
2367  <figure>
2368  <preamble>For instance, the code below overrides several attributes in
2369  <spanx style="verb">rfc2629toFO.xslt</spanx>, changing the color, spacing and font family for
2370  headers.</preamble>
2371  <artwork type="example">
2372&lt;xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
2373               version="1.0">
2374
2375  &lt;xsl:import href="rfc2629toFO.xslt"/>
2376 
2377  &lt;xsl:attribute-set name="h1">
2378    &lt;xsl:attribute name="color">darkblue&lt;/xsl:attribute>
2379    &lt;xsl:attribute name="font-family">sans-serif&lt;/xsl:attribute>
2380    &lt;xsl:attribute name="space-before">24pt&lt;/xsl:attribute>
2381  &lt;/xsl:attribute-set>
2382 
2383  &lt;xsl:attribute-set name="h2">
2384    &lt;xsl:attribute name="color">darkblue&lt;/xsl:attribute>
2385    &lt;xsl:attribute name="font-family">sans-serif&lt;/xsl:attribute>
2386    &lt;xsl:attribute name="space-before">18pt&lt;/xsl:attribute>
2387    &lt;xsl:attribute name="space-after">3pt&lt;/xsl:attribute>
2388  &lt;/xsl:attribute-set>
2389 
2390  &lt;xsl:attribute-set name="h3">
2391    &lt;xsl:attribute name="color">darkblue&lt;/xsl:attribute>
2392    &lt;xsl:attribute name="font-family">sans-serif&lt;/xsl:attribute>
2393    &lt;xsl:attribute name="space-before">16pt&lt;/xsl:attribute>
2394    &lt;xsl:attribute name="space-after">2pt&lt;/xsl:attribute>
2395  &lt;/xsl:attribute-set>
2396
2397&lt;/xsl:transform>
2398</artwork></figure>
2399<x:note>
2400  <t>
2401    <x:h>Note:</x:h> the name for the attribute sets may change in the future
2402    as more working is done with respect to customizability. In any case,
2403    overriding the settings in a separate file will be easier to maintain.
2404    Please contact the author if you find yourself trying to override style
2405    definitions that currently do not use attribute sets.
2406  </t>
2407  <t>
2408    <x:h>Note:</x:h> the CSS style information used in <spanx style="verb">rfc2629.xslt</spanx>
2409    can be overriden in a similar (but less granular) way: just overwrite the
2410    template called "insertCss". As for XSL-FO, the class names may change in
2411    future.
2412  </t>
2413</x:note>
2414</section>
2415</section>
2416
2417<section title="Producing the IETF 'Boilerplate'" anchor="boilerplate">
2418<t>
2419  Various attributes of the <spanx style="verb">&lt;rfc&gt;</spanx>
2420  element plus some child elements of <spanx style="verb">&lt;front&gt;</spanx>
2421  affect the automatically generated parts of the front page, such as the
2422  tabular information at the beginning, the "Status Of This Memo", and the
2423  "Copyright Notice".
2424</t>
2425<t>
2426  When submitting an Internet Draft, this "boilerplate" is checked
2427  by "Idnits" (<eref target="http://tools.ietf.org/tools/idnits/"/>) for
2428  compliance with the current Intellectual Property rules, and thus
2429  it is important to set the correct values.
2430</t>
2431<t>
2432  Furthermore, the RFC Production Center uses RFC2629-based tools to
2433  generate the final RFC text, so the more accurate the supplied information
2434  is, the less additional work is left, and the risk for errors in producing
2435  the final (and immutable!) document is reduced.
2436</t>
2437<x:note>
2438  <t>
2439    <x:h>Note:</x:h> this only applies to the case when IETF documents are
2440    produced. The "private" processing instruction <iref item="private PI pseudo-attribute"/><iref item="Processing Instruction pseudo attributes" subitem="private"/>
2441    allows to switch off most of the autogeneration logic.
2442  </t>
2443</x:note>
2444
2445<section title="The /rfc/@ipr Attribute" anchor="attribute-ipr">
2446<t>
2447  As of the time of this writing, this attribute value can take a long list of values. As
2448  frequently, this is not the result of a grand plan, but simply for historic
2449  reasons. Of these values, only a few are currently in use; all others are
2450  supported by the various tools for backwards compatibility with old source
2451  files.
2452</t>
2453<x:note>
2454  <t>
2455    <x:h>Note:</x:h> some variations of the boilerplate are selected based
2456    on the document's date; therefore it is important to specify the "year",
2457    "month" and "day" attributes of the <spanx style="verb">&lt;date&gt;</spanx> element
2458    when archiving the XML source of an Internet Draft on the day of submission.
2459  </t>
2460</x:note>
2461<t>
2462  <spanx>Disclaimer: THIS ONLY PROVIDES IMPLEMENTATION INFORMATION. IF YOU NEED
2463  LEGAL ADVICE, PLEASE CONTACT A LAWYER.</spanx>
2464  For further information, refer to <eref target="http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf"/>.
2465</t>
2466<t>
2467  Finally, for the current "Status Of This Memo" text, the <spanx style="verb">submissionType</spanx> attribute
2468  determines whether a statement about "Code Components" is inserted (this is the
2469  case for the value "IETF", which also happens to be the default). Other values,
2470  such as "independent", suppress this part of the text.
2471</t>
2472
2473
2474<section title="Current Values: '*trust200902'" anchor="attribute-ipr-current">
2475<t>
2476  The name for these values refers to the "TLP" ("IETF TRUST Legal Provisions Relating
2477  to IETF Documents"), on effect February 15, 2009 (see <eref target="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090215.pdf"/>).
2478  Updates to this document were published on September 12, 2009 (TLP 3.0, <eref target="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf"/>)
2479  and on December 28, 2009 (TLP 4.0, <eref target="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf"/>),
2480  modifying the license for code components.
2481  The actual text is located in Section 6 ("Text To Be Included in IETF Documents")
2482  of these documents.
2483</t>
2484<t> 
2485  The tools will automatically produce the "right" text depending on the
2486  document's date information (see above):
2487</t>
2488<texttable align="left">
2489  <ttcol>TLP</ttcol><ttcol>URI</ttcol><ttcol>starting with publication date</ttcol>
2490
2491  <c>3.0</c>
2492  <c><eref target="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf"/></c>
2493  <c>2009-11-01</c>
2494
2495  <c>4.0</c>
2496  <c><eref target="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf"/></c>
2497  <c>2010-04-01</c>
2498
2499</texttable> 
2500
2501
2502<section title="trust200902" anchor="attribute-ipr-trust200902">
2503<t>
2504  This should be the default, unless one of the more specific '*trust200902'
2505  values is a better fit. It produces the text in Sections 6.a and 6.b of
2506  the TLP.
2507</t>
2508</section>
2509
2510<section title="noModificationTrust200902" anchor="attribute-ipr-noModificationTrust200902">
2511<t>
2512  This produces the additional text from Section 6.c.i of the TLP:
2513</t>
2514<x:blockquote>
2515  <t>
2516    This document may not be modified, and derivative works of it may
2517    not be created, except to format it for publication as an RFC or
2518    to translate it into languages other than English.
2519  </t>
2520</x:blockquote>
2521</section>
2522
2523<section title="noDerivativesTrust200902" anchor="attribute-ipr-noDerivativesTrust200902">
2524<t>
2525  This produces the additional text from Section 6.c.ii of the TLP:
2526</t>
2527<x:blockquote>
2528  <t>
2529    This document may not be modified, and derivative works of it may
2530    not be created, and it may not be published except as an Internet-Draft.
2531  </t>
2532</x:blockquote>
2533</section>
2534
2535<section title="pre5378Trust200902" anchor="attribute-ipr-pre5378Trust200902">
2536<t>
2537  This produces the additional text from Section 6.c.iii of the TLP, frequently
2538  called the "pre-5378 escape clause":
2539</t>
2540<x:blockquote>
2541  <t>
2542    This document may contain material from IETF Documents or IETF Contributions published or
2543    made publicly available before November 10, 2008. The person(s) controlling the copyright in
2544    some of this material may not have granted the IETF Trust the right to allow modifications of such
2545    material outside the IETF Standards Process. Without obtaining an adequate license from the
2546    person(s) controlling the copyright in such materials, this document may not be modified outside
2547    the IETF Standards Process, and derivative works of it may not be created outside the IETF
2548    Standards Process, except to format it for publication as an RFC or to translate it into languages
2549    other than English.
2550  </t>
2551</x:blockquote>
2552<t>
2553  See Section 4 of <eref target="http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf"/>
2554  for further information about when to use this value.
2555</t>
2556<x:note>
2557  <t>
2558    <x:h>Note:</x:h> this text appears under "Copyright Notice", unless the
2559    document was published before November 2009, in which case it appears
2560    under "Status Of This Memo".
2561  </t>
2562</x:note>
2563</section>
2564</section> 
2565
2566<section title="Historic Values" anchor="attribute-ipr-historic">
2567
2568<section title="Historic Values: '*trust200811'" anchor="attribute-ipr-200811">
2569<t>
2570  The attribute values "<x:span anchor="attribute-ipr-trust200811">trust200811</x:span>",
2571  "<x:span anchor="attribute-ipr-noModificationTrust200811">noModificationTrust200811</x:span>" and
2572  "<x:span anchor="attribute-ipr-noDerivativesTrust200811">noDerivativesTrust200811</x:span>"
2573  are similar to their "trust200902" counterparts, except that they use text
2574  specified in <eref target="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy_11-10-08.pdf"/>.
2575</t>
2576</section>
2577
2578<section title="Historic Values: '*3978'" anchor="attribute-ipr-3978">
2579<t>
2580  The attribute values "<x:span anchor="attribute-ipr-full3978">full3978</x:span>",
2581  "<x:span anchor="attribute-ipr-noModification3978">noModification3978</x:span>" and
2582  "<x:span anchor="attribute-ipr-noDerivatives3978">noDerivatives3978</x:span>"
2583  are similar to their counterparts above, except that they use text
2584  specified in RFC 3978 (March 2005).
2585</t>
2586</section>
2587
2588<section title="Historic Values: '*3667'" anchor="attribute-ipr-3667">
2589<t>
2590  The attribute values "<x:span anchor="attribute-ipr-full3667">full3667</x:span>",
2591  "<x:span anchor="attribute-ipr-noModification3667">noModification3667</x:span>" and
2592  "<x:span anchor="attribute-ipr-noDerivatives3667">noDerivatives3667</x:span>"
2593  are similar to their counterparts above, except that they use text
2594  specified in RFC 3667 (February 2004).
2595</t>
2596</section>
2597
2598<section title="Historic Values: '*2026'" anchor="attribute-ipr-2026">
2599<t>
2600  The attribute values "<x:span anchor="attribute-ipr-full2026">full2026</x:span>" and
2601  "<x:span anchor="attribute-ipr-noDerivativeWorks2026">noDerivativeWorks2026</x:span>"
2602  are similar to their counterparts above, except that they use text
2603  specified in RFC 2026 (October 1996).
2604</t>
2605<t>
2606  The special value "<x:span anchor="attribute-ipr-none">none</x:span>"
2607  was also used back then, and denied the IETF any rights beyond publication
2608  as Internet Draft.
2609</t>
2610</section>
2611
2612</section>
2613</section>
2614
2615<section title="The /rfc/@category Attribute" anchor="attribute-category">
2616<t>
2617  For RFCs, the <spanx style="verb">category</spanx> determines the "maturity level"
2618  (see <xref target="RFC2026" x:fmt="of" x:sec="4"/>). The allowed values
2619  are "std" for "Standards Track", "bcp" for "BCP", "info" for "Informational",
2620  "exp" for "Experimental", and "historic" for - surprise - "Historic".
2621</t>
2622<t>
2623  For Internet Drafts, the category attribute is not needed, but <spanx>will</spanx>
2624  appear on the front page ("Intended Status"). Supplying this information can
2625  be useful, because reviewers may want to know.
2626</t>
2627<x:note>
2628  <t>
2629    <x:h>Note:</x:h> the Standards Track consists of "Proposed Standard",
2630    "Draft Standards", and "Internet Standard". These do not appear in the
2631    boilerplate, thus the category attribute doesn't handle them.
2632    However, this information can be useful for validity checkers, and thus
2633    <spanx style="verb">rfc2629.xslt</spanx> supports an extension attribute
2634    for that purpose (see <xref target="ext-rfc2629.rfc"/> for details).
2635  </t>
2636</x:note>
2637</section>
2638
2639<section title="The /rfc/@submissionType Attribute" anchor="attribute-submissiontype">
2640<t>
2641  The RFC Editor publishes documents from different "document streams", of which
2642  the "IETF stream" of course is the most prominent one. Other streams are the "independent stream"
2643  (used for things like administrative information or April 1st RFCs),
2644  the "IAB stream" (Internet Architecture Board) and the "IRTF stream" (Internet Research Task Force).
2645</t>
2646<t>
2647  Not surprisingly, the values for the attribute are "IETF" (the default value),
2648  "independent", "IAB", and "IRTF".
2649</t>
2650<t>
2651  <spanx>The values "IAB" and "IRTF" are supported by rfc2629.xslt, but not
2652  yet allowed by the DTD (waiting for release 1.36 of xml2rfc).</spanx>
2653</t>
2654<t>
2655  Historically, this did not affect the final appearance of RFCs, except for
2656  subtle differences in Copyright notices.
2657  Nowadays (as of <xref target="RFC5741"/>), the stream name appears in the first
2658  line of the front page, and it also affects the text in the "Status Of This Memo"
2659  section.
2660</t>
2661<t>
2662  For current documents, setting <spanx style="verb">submissionType</spanx> attribute will
2663  have the following effect:
2664  <list style="symbols">
2665    <t>
2666      For RFCs, the stream name appears in the upper left corner of the
2667      first page (in Internet Drafts, this is either "Network Working Group",
2668      or the value of the <spanx style="verb">&lt;workgroup&gt;</spanx> element).
2669    </t>
2670    <t>
2671      For RFCs, if affects the whole "Status Of This Memo" section (see
2672      <xref x:sec="3.2.2" x:fmt="of" target="RFC5741"/>).
2673    </t>
2674    <t>
2675      For all RFCs and Internet Drafts, it determines whether the "Copyright
2676      Notice" mentions the Copyright on Code Components (see TLP, Section "Text To Be Included in IETF Documents").
2677    </t>
2678  </list>
2679</t>
2680<x:note>
2681  <t>
2682    <x:h>Note:</x:h> as of Version 1.35, <spanx style="verb">xml2rfc</spanx>
2683    (as opposed to <spanx style="verb">rfc2629.xslt</spanx>)
2684    does <spanx>not</spanx> implement support values other than "IETF" or
2685    "independent".
2686  </t>
2687</x:note>
2688</section>
2689
2690<section title="The /rfc/@consensus Attribute" anchor="attribute-consensus">
2691<t>
2692  <spanx>Supported by rfc2629.xslt, but not
2693  yet allowed by the DTD (waiting for release 1.36 of xml2rfc).</spanx>
2694</t>
2695<t>
2696  For some of the publication streams (see <xref target="attribute-submissiontype"/>),
2697  the "Status Of This Memo" section depends on whether there was a consensus
2698  to publish (again, see <xref x:sec="3.2.2" x:fmt="of" target="RFC5741"/>).
2699</t>
2700<t>
2701  The <spanx style="verb">consensus</spanx> attribute ("yes"/"no", defaulting to "yes")
2702  can be used to supply this information. The effect for the various streams is:
2703  <list style="symbols">
2704    <t>"independent" and "IAB": none.</t>
2705    <t>"IETF": mention that there was an IETF consensus.</t>
2706    <t>"IRTF": mention that there was a research group consensus (where the name of the research
2707    group is extracted from the <spanx style="verb">&lt;workgroup&gt;</spanx> element).</t>
2708  </list>
2709</t>
2710</section>
2711
2712<section title="The /rfc/@number Attribute" anchor="attribute-number">
2713<t>
2714  For RFCs, this attribute supplies the RFC number.
2715</t>
2716</section>
2717
2718<section title="The /rfc/@docName Attribute" anchor="attribute-docname">
2719<t>
2720  For Internet Drafts, this specifies the draft name (which appears
2721  below the title). The file extension is <spanx>not</spanx> part
2722  of the draft, so in general it should end with the current draft number
2723  ("-", plus two digits).
2724</t>
2725<x:note>
2726  <t>
2727  <x:h>Note:</x:h> "Idnits" (<eref target="http://tools.ietf.org/tools/idnits/"/>)
2728  checks the in-document draft name for consistency with the filename of
2729  the submitted document.
2730  </t>
2731</x:note>
2732</section>
2733
2734<section title="The /rfc/@obsoletes Attribute" anchor="attribute-obsoletes">
2735<t> 
2736  The RFC Editor maintains a database (<eref target="http://www.rfc-editor.org/rfc.html"/>)
2737  of all RFCs, including information about which one obsoletes which. Upon publication of an RFC, this
2738  database is updated from the data on the front page.
2739</t>
2740<t>
2741  This attribute takes a list of comma-separated RFC <spanx>numbers</spanx>.
2742  Do <spanx>not</spanx> put the string "RFC" here.
2743</t>
2744</section>
2745 
2746<section title="The /rfc/@updates Attribute" anchor="attribute-updates">
2747<t>
2748  This is like <spanx style="verb">obsoletes</spanx>, but for the "updates"
2749  relation.
2750</t>
2751</section>
2752</section>
2753  <section title="License" anchor="license">
2754  <t>
2755Copyright (c) 2006-2010, Julian Reschke (julian.reschke@greenbytes.de)
2756  </t>
2757  <t>
2758All rights reserved.
2759  </t>
2760  <t>
2761Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
2762  <list style="symbols">
2763    <t>Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.</t>
2764    <t>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.</t>
2765    <t>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.</t>
2766  </list>
2767  </t>
2768  <t>
2769THIS 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.
2770  </t>
2771  </section>
2772
2773  <section title="Change Logs">
2774   
2775 
2776    <section title="Package">
2777      <t><list style="hanging">
2778<t hangText="2006-01-01">
2779    Switch to BSD License.
2780</t>
2781<t hangText="2007-01-12">
2782    Update to xml2rfc v1.33pre2.
2783</t>
2784<t hangText="2007-03-31">
2785    Update to xml2rfc v1.33pre3.
2786</t>
2787<t hangText="2007-05-01">
2788    Add XSLT test cases.
2789</t>
2790<t hangText="2008-07-18">
2791    Experimental support for inlined rdf:Description elements (ignored
2792    by the formatter, extracted by rfc2629grddl).
2793</t>
2794<t hangText="2008-12-04">
2795    Update to xml2rfc v1.34pre2.
2796</t>
2797<t hangText="2009-02-24">
2798    Experimental support for February 2009 boilerplate changes, and for
2799    the x:boilerplate element.
2800</t>
2801<t hangText="2009-07-08">
2802    Support new boilerplate ordering in RFCs published since July 2009.
2803    Fix problems with one-column text tables.
2804</t>
2805<t hangText="2009-07-19">
2806    When possible, calculate the actual Expiry date for Internet Drafts
2807    (full date must be available).
2808</t>
2809<t hangText="2009-08-01">
2810    For '$xml2rfc-ext-authors-section='end'", move the index in front of the
2811    authors section.
2812</t>
2813<t hangText="2009-08-04">
2814    Consider /rfc/@ipr="pre5378Trust200902" when producing RFCs, not IDs.
2815</t>
2816<t hangText="2009-08-29">
2817    Support alignment for artwork containing images (as opposed to, well,
2818    artwork).
2819</t>
2820<t hangText="2009-09-01">
2821    Allow xref in cref (as extension).
2822</t>
2823<t hangText="2009-09-14">
2824    Refactor handling of processing instructions.
2825</t>
2826<t hangText="2009-09-24">
2827    Fix typo in Status Of This Memo, present since November 2008.
2828                Fix formatting of iprExtract attribute.
2829                Starting with Internet Draft publication dates after 2009-11-30: use new Trust
2830                Legal Provisions text; for Internet Drafts: move Abstract up, and
2831                move "pre5378" escape clause to the Copyright Notice.
2832                Add support for refparent PI. For RFCs: use new TLP text as of September 2009.
2833    Incorporate xml2rfc v1.34pre4.
2834</t>
2835<t hangText="2009-10-06">
2836                Starting with Internet Draft publication dates after 2009-10-31: use new Trust
2837                Legal Provisions text; for Internet Drafts: move Abstract up, and
2838                move "pre5378" escape clause to the Copyright Notice.
2839    Incorporate xml2rfc v1.34pre5.
2840</t>
2841<t hangText="2009-10-27">
2842    Upgrade to xml2rfc v1.34.
2843</t>
2844<t hangText="2010-01-08">
2845    For RFC generation (not IDs), experimentally support RFC 5741 headers and boilerplate and Trust
2846    Legal Provisions 4.0.
2847</t>
2848<t hangText="2010-03-31">
2849    Upgrade to xml2rfc v1.35.
2850</t>
2851<t hangText="2010-06-27">
2852    Be consistent with xml2rfc.tcl in formatting initials (truncate after
2853    the first); see <eref target="http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10"/>.
2854</t>
2855<t hangText="2010-08-31">
2856    Experimental support for prose in references.
2857</t>
2858<t hangText="2011-01-27">
2859    Update to xml2rfc v1.36pre1.
2860</t>
2861      </list></t>
2862    </section>
2863   
2864    <section title="amazon-asin.xslt">
2865    <t><list style="hanging">
2866<t hangText="2003-11-16">
2867     Initial release.
2868</t>
2869<t hangText="2005-04-02">
2870     Fix two DTD issues.
2871</t>
2872    </list></t>
2873    </section>
2874
2875    <section title="check-references.xslt">
2876    <t><list style="hanging">
2877<t hangText="2003-11-16">
2878     Initial release.
2879</t>
2880<t hangText="2004-05-11">
2881     Add document status; print references type.
2882</t>
2883<t hangText="2005-01-01">
2884     Add experimental check for ID status.
2885</t>
2886<t hangText="2005-04-01">
2887     Add fixes from Bill Fenner.
2888</t>
2889<t hangText="2005-12-03">
2890    Add checks against local copy of <eref target="http://www.w3.org/2002/01/tr-automation/tr.rdf"/>
2891</t>
2892<t hangText="2006-07-22">
2893    Add checks for standards levels.
2894</t>
2895<t hangText="2006-08-06">
2896    "check-ietf-references.xslt" replaced by "check-references.xslt".
2897</t>
2898<t hangText="2007-01-04">
2899    Use information online at <eref target="http://tools.ietf.org/"/> to
2900    retrieve Internet-Draft status information.
2901</t>
2902<t hangText="2007-06-16">
2903    Fix bug looking up ref type when inside change markup.
2904</t>
2905<t hangText="2008-06-14">
2906    Enhance output when draft was updated, and then published as RFC.
2907</t>
2908<t hangText="2008-07-12">
2909    Add XSLT2-based link target checking.
2910</t>
2911<t hangText="2008-08-10">
2912    Change keywords for "intended-level" to proposed/draft/internet,
2913    optionally extract intended level from /rfc/@x:maturity-level attribute.
2914</t>
2915    </list></t>
2916    </section>
2917   
2918    <section title="gen-reference-graph.xslt">
2919    <t><list style="hanging">
2920<t hangText="2006-09-03">
2921  New.
2922</t>
2923<t hangText="2007-06-07">
2924  Use <eref target="http://dpcarlisle.blogspot.com/2007/05/exslt-node-set-function.html">Carlisle method</eref> to define exslt:node-set in
2925  msxsml (which means that the stylesheet can now be used with MSXML as well).
2926</t>
2927<t hangText="2007-10-15">
2928  Use W3C data from tr.rdf as well (experimental).
2929</t>
2930    </list></t>
2931    </section>
2932
2933    <section title="rfc2629.xslt">
2934      <t><list style="hanging">
2935<t hangText="2001-03-28">
2936    Code rearranged, generate numbered section anchors for paragraphs (t)
2937    as well. Fixes in index handling.
2938</t>
2939<t hangText="2001-04-12">
2940    Moved HTML output into XHTML namespace.
2941</t>
2942<t hangText="2001-10-02">
2943    Fixed default location for RFCs and numbering of section references.
2944    Support ?rfc editing processing instruction.
2945</t>
2946<t hangText="2001-10-07">
2947    Made telephone number links active.
2948</t>
2949<t hangText="2001-10-08">
2950    Support for vspace element.
2951</t>
2952<t hangText="2001-10-09">
2953    Experimental support for rfc-issue PI.
2954</t>
2955<t hangText="2001-11-11">
2956    Support rfc private PI. Removed bogus code reporting the WG in the header.
2957</t>
2958<t hangText="2001-11-11">
2959    Support rfc private PI. Removed bogus code reporting the WG in the header.
2960</t>
2961<t hangText="2001-12-17">
2962    Support title attribute on references element
2963</t>
2964<t hangText="2002-01-05">
2965    Support for list/@style="@format"
2966</t>
2967<t hangText="2002-01-09">
2968    Display "closed" RFC issues as deleted
2969</t>
2970<t hangText="2002-01-14">
2971    Experimentally and optionally parse XML encountered in artwork elements
2972    (requires MSXSL).
2973</t>
2974<t hangText="2002-01-27">
2975    Some cleanup. Moved RFC issues from PIs into namespaced elements.
2976</t>
2977<t hangText="2002-01-29">
2978    Added support for sortrefs PI. Added support for figure names.
2979</t>
2980<t hangText="2002-02-07">
2981    Highlight parts of artwork which are too wide (72 characters).
2982</t>
2983<t hangText="2002-02-12">
2984    Code rearrangement for static texts. Fixes for section numbering.
2985    TOC generation rewritten.
2986</t>
2987<t hangText="2002-02-15">
2988    Support for irefs in sections; support iref @primary=true
2989</t>
2990<t hangText="2002-03-03">
2991    Moved anchor prefix into a constant. Added sanity checks on user anchor
2992    names.
2993</t>
2994<t hangText="2002-03-23">
2995    Bugfix in detection of matching org names when creating the header. Fixed
2996    sorting in subitems.
2997</t>
2998<t hangText="2002-04-02">
2999    Fix TOC link HTML generation when no TOC is generated (created broken
3000    HTML table code).
3001</t>
3002<t hangText="2002-04-03">
3003    Made rendering of references more tolerant re: missing parts.
3004</t>
3005<t hangText="2002-04-08">
3006    Fixed reference numbering when references are split into separate sections.
3007</t>
3008<t hangText="2002-04-16">
3009    Fix default namespace (shouldn't be set for HTML output method).
3010</t>
3011<t hangText="2002-04-19">
3012    Lowercase internal CSS selectors for Mozilla compliance. Do not put TOC
3013    into ul element.
3014</t>
3015<t hangText="2002-04-21">
3016    Make numbered list inside numbered lists use alphanumeric numbering.
3017</t>
3018<t hangText="2002-05-05">
3019    Updated issue/editing support.
3020</t>
3021<t hangText="2002-05-15">
3022    Bugfix for section numbering after introduction of ed:replace
3023</t>
3024<t hangText="2002-06-21">
3025    When producing private documents, do not include document status, copyright etc.
3026</t>
3027<t hangText="2002-07-08">
3028    Fix xrefs to Appendices.
3029</t>
3030<t hangText="2002-07-19">
3031    Make artwork lightyellow for easier reading. (fielding)
3032</t>
3033<t hangText="2002-10-09">
3034    Translate references title to anchor name to avoid non-uri characters. (fielding)
3035</t>
3036<t hangText="2002-10-13">
3037    Support for tocdepth PI.
3038</t>
3039<t hangText="2002-11-03">
3040    Added temporariry workaround for Mozilla/Transformiix result tree fragment problem.
3041    (search for 'http://bugzilla.mozilla.org/show_bug.cgi?id=143668')
3042</t>
3043<t hangText="2002-12-25">
3044    xref code: attempt to uppercase "section" and "appendix" when at the start
3045    of a sentence.
3046</t>
3047<t hangText="2003-02-02">
3048    fixed code for vspace blankLines="0", enhanced display for list with "format" style,
3049    got rid of HTML blockquote elements, added support for "hangIndent"
3050</t>
3051<t hangText="2003-04-10">
3052    experimental support for appendix and spanx elements
3053</t>
3054<t hangText="2003-04-19">
3055    fixed counting of list numbers in "format %" styles (one counter
3056    per unique format string). Added more spanx styles.
3057</t>
3058<t hangText="2003-05-02">
3059    experimental texttable support
3060</t>
3061<t hangText="2003-05-02">
3062    Make mailto links optional (default = none) (jre: default and PI name changed) (fielding)
3063</t>
3064<t hangText="2003-05-04">
3065    experimental support for HTML link elements; fix default for table header
3066    alignment default
3067</t>
3068<t hangText="2003-05-06">
3069    support for "background" PI.
3070</t>
3071<t hangText="2003-05-11">
3072    change %c format to lowercase alphabetic. add support for keyword
3073    elements (generate META tag). fix various HTML conformance problems.
3074    added experimental support for role attribute. do not number paragraphs
3075    in unnumbered sections. update boilerplate texts. support for
3076    "iprnotified" PI. bugfix list numbering. strip whitespace when
3077    building tel: URIs.
3078</t>
3079<t hangText="2003-05-12">
3080    more conformance fixes (layout moved into CSS, move lists and figures
3081    out of para content, do not use tables for list formatting)
3082</t>
3083<t hangText="2003-05-13">
3084    add DC.Creator meta tag, refactoring
3085</t>
3086<t hangText="2003-05-16">
3087    put nbsps between "section" and section number (xref).
3088</t>
3089<t hangText="2003-05-18">
3090    author summary: add missing comma.
3091</t>
3092<t hangText="2003-06-06">
3093    fix index generation bug (transposed characters in key generation). Enhance
3094    sentence start detection (xref starting a section was using lowercase
3095    "section").
3096</t>
3097<t hangText="2003-06-22">
3098    exp. support for xref/@format. Add missing support for eref w/o content.
3099    exp. support for annotations in reference elements. Code cleanup
3100    reference table formatting.
3101</t>
3102<t hangText="2003-07-09">
3103    Another fix for DC.Creator meta tag creation based on RFC2731
3104</t>
3105<t hangText="2003-07-24">
3106    Fix namespace name for DC.Creator.
3107</t>
3108<t hangText="2003-08-06">
3109    Cleanup node-set support (only use exslt (saxon, xalan, libxslt) extension
3110    functions; remove Transformix workarounds that stopped to work in Moz 1.4)
3111</t>
3112<t hangText="2003-08-09">
3113    Generate HTML lang tag.
3114</t>
3115<t hangText="2003-08-10">
3116    Map spanx/verb to HTML "samp" element. Fix author name display in
3117    references (reverse surname/initials for last author), add "Ed.".
3118    Fix internal bookmark generation.
3119</t>
3120<t hangText="2003-08-17">
3121    Add DCMI dates, identifiers and abstract. Add PI to suppress DCMI
3122    generation.  Do not add TOC entry to Copyright Statement when there is
3123    none. Align RFC2629 PI names and parameter names. Change style for
3124    inline URIs generated by eref. Add header and footer support.
3125    Enhance CSS paging properties. Support topblock PI. Added hooks for
3126    proper XHTML generation through separate XSLT. Enhance warning and
3127    error messages. Add support for artwork image display. Table formatting
3128    fixes (borders, thead continuation).
3129</t>
3130<t hangText="2003-08-18">
3131    Add workaround for MSXML4 node-set and Mozilla node-set issues (fallback
3132    just displays are warning).
3133</t>
3134<t hangText="2003-10-06">
3135    Add workaround for broken pre/ins handling in Mozilla
3136    (see <eref target="http://bugzilla.mozilla.org/show_bug.cgi?id=204401"/>). Make use
3137    of cite attribute on ed:replace. CSS cleanup.
3138</t>
3139<t hangText="2003-10-08">
3140    Fix minor issue detecting the same org for the header (caused by IE's
3141    non-standard whitespace handling). Fix default handling for /rfc/@category.
3142</t>
3143<t hangText="2003-11-09">
3144    Inherit ed:entered-by from ancestor elements. Change CSS color for inserted
3145    text to green. Generate issues-list anchor. Do not complain about missing
3146    targets when the xref element is below ed:del. Remove code that attempted
3147    to distinguish section/Section when producing links - always use
3148    uppercase. Fix date rendering for issue resolutions.
3149</t>
3150<t hangText="2003-11-29">
3151    Fix color values for table backgrounds for issue rendering. Change
3152    rendering of issue links to use inline-styles. Add colored issue markers to
3153    issues.
3154</t>
3155<t hangText="2003-12-13">
3156    Fix inheritance of ed:entered-by attribute. Display note elements inside
3157    change tracking as well.
3158</t>
3159<t hangText="2004-01-18">
3160    When PI compact = 'yes', make most CSS print page breaks conditional.
3161</t>
3162<t hangText="2004-02-20">
3163    Support for RFC3667 IPR changes (xml2rfc 1.22); see
3164    <eref target="http://lists.xml.resource.org/pipermail/xml2rfc/2004-February/001088.html"/>.
3165</t>
3166<t hangText="2004-03-11">
3167    Add "(if approved)" to "updates" and "obsoletes" unless the document has
3168    an RFC number.
3169</t>
3170<t hangText="2004-04-01">
3171    Fix RFC3667 output, see <eref target="http://lists.xml.resource.org/pipermail/xml2rfc/2004-April/001208.html"/>.
3172</t>
3173<t hangText="2004-04-04">
3174    Add support for section/top attribute. Move references into plain
3175    section container.
3176</t>
3177<t hangText="2004-04-06">
3178    Do not emit identical para anchors for deleted content.
3179</t>
3180<t hangText="2004-04-14">
3181    Fix references TOC generation when there are no references.
3182</t>
3183<t hangText="2004-04-24">
3184    Fix RFC3667 output, see <eref target="http://xml.resource.org/pipermail/xml2rfc/2004-April/001246.html"/>.
3185</t>
3186<t hangText="2004-05-09">
3187    Add custom support for generating compound index documents. Add anchors
3188    for each Index letter. Add experimental cref support. Fix conditional page
3189    breaks before References section.
3190</t>
3191<t hangText="2004-05-16">
3192    Refactor external index generation.
3193</t>
3194<t hangText="2004-05-20">
3195    Rewrite anchor generation for comments.
3196</t>
3197<t hangText="2004-05-22">
3198    Enhance issues rendering (add links to changes).
3199</t>
3200<t hangText="2004-05-30">
3201    Allow single quote as delimiter in processing instructions as well. Move
3202    block-level issue pointers to floats. Disable issue pointers for print
3203    media. Add "purple numbers". Add hrefs to section headings. Add non-printing
3204    index key letter list to start of index.
3205</t>
3206<t hangText="2004-06-01">
3207    Use &amp;#xb6; instead of # for PNs.
3208</t>
3209<t hangText="2004-07-18">
3210    Add support for list style=letters (thanks Roy F.). Make PNs optional;
3211    add new PI.
3212</t>
3213<t hangText="2004-09-05">
3214    Fix index links into unnumbered sections.  Bring IPR boilerplate in-line
3215    with xml2rfc 1.25.  Add experimental CSS3 paged media support.  Various
3216    HTML fixes.
3217</t>
3218<t hangText="2004-09-21">
3219    Enhance checking of artwork width.
3220</t>
3221<t hangText="2004-09-26">
3222    Add check for unused references. Uppercase letters in list style letters
3223    when nested into another list.
3224</t>
3225<t hangText="2004-10-10">
3226    Fix internal change track pointers.
3227</t>
3228<t hangText="2004-11-01">
3229    Allow change tracking on references (as a whole).  Rewrite artwork handling
3230    so that it allows change tracking inside artwork.  Also allow a subset of
3231    text markup inside artwork, such as xrefs (note this requires post-processing
3232    the source to make it compliant to RFC2629bis).
3233</t>
3234<t hangText="2004-11-03">
3235    Enhanced placement of iref anchors.
3236</t>
3237<t hangText="2004-11-06">
3238    Index: display irefs that appeared (with primary=true) inside artwork elements
3239    in a monospaced font.
3240</t>
3241<t hangText="2004-11-14">
3242    Add special code so that changes in section titles can be change-tracked.
3243</t>
3244<t hangText="2005-01-14">
3245    Bugfixes for HtmlToXhtml converter.
3246</t>
3247<t hangText="2005-01-22">
3248    Enhance generation of HTML h* elements (for Mozilla Outliner).
3249</t>
3250<t hangText="2005-01-31">
3251    Put vertical space around top-level TOC entries in TOC.  Switch to
3252    pt-based CSS. Re-arrange top section. Make hr elements reflect new-page
3253    settings in TXT output (compact-PI).  Fix page number in footer (CSS
3254    print) and add some more experimental support for paged media (tested
3255    with Prince 4.1 alpha).  Rewrite TOC and Index generation to generate HTML
3256    lists.  Cleanup id generation for paragraphs.  Reduce whitespace in output.
3257    Fix vspace implementation. Use right/left dqoutes and copyright sign
3258    where appropriate.
3259</t>
3260<t hangText="2005-02-04">
3261    Add &lt;link> element to references section.  Fix newly introduced bug
3262    in references processing.
3263</t>
3264<t hangText="2005-02-05">
3265    Integrate various fixes/enhancements by Roy Fielding: spelling of
3266    "Authors' Addresses", comma setting in references, position of "Authors"
3267    section, optionally place authors addresses at end (PI), trailing dots
3268    in section numbers, switch to verdana default font in CSS.  Add
3269    experimental support for centered artwork.
3270</t>
3271<t hangText="2005-02-09">
3272    Fixes in spacing and links of references section titles.  Enhance sorting
3273    in references when change tracking is in place.  Re-add figure centering
3274    support.  Add missing 2nd part of "Author's Adresses" fix.
3275</t>
3276<t hangText="2005-02-25">
3277    Align section number format with xml2rfc1.29.
3278</t>
3279<t hangText="2005-03-28">
3280    Get rid of table elements in Author's section.  Add experimental hCard
3281    (<eref target="http://developers.technorati.com/wiki/hCard"/>) support.
3282</t>
3283<t hangText="2005-04-03">
3284    Add RFC3978-style IPR statement support. (fenner@research.att.com)
3285</t>
3286<t hangText="2005-04-11">
3287    Cleanup author display. hCard related fixes.
3288</t>
3289<t hangText="2005-05-07">
3290    Minor fixes to allow change tracking in doc title.  Add experimental
3291    support for table border styles. CSS cleanup.
3292</t>
3293<t hangText="2005-06-18">
3294    Implement missing support for references to texttables.
3295</t>
3296<t hangText="2005-09-25">
3297    Use (-moz-)column-count when printing the index.
3298</t>
3299<t hangText="2005-10-04">
3300    Report missing element templates with xsl:message.
3301</t>
3302<t hangText="2005-10-15">
3303    Process t/@anchor.
3304</t>
3305<t hangText="2005-10-23">
3306    More workarounds for Mozilla's broken del/ins handling (this time for
3307    figures).
3308</t>
3309<t hangText="2005-10-27">
3310    lowercase hCard class names
3311</t>
3312<t hangText="2005-11-22">
3313    Enhance diagnostics for XML-in-artwork extension
3314</t>
3315<t hangText="2005-11-26">
3316    Fix formatting of section numbers for sections inserted into &lt;back>.
3317</t>
3318<t hangText="2005-12-12">
3319    Fix some validity problems when change tracking occured inside lists.
3320</t>
3321<t hangText="2005-12-18">
3322    Add change tracking inside the index.
3323</t>
3324<t hangText="2006-02-04">
3325    Add prev/next links to highlighted changes (change tracking extension).
3326</t>
3327<t hangText="2006-02-10">
3328    Catch errors instantiating MSXML component.
3329</t>
3330<t hangText="2006-02-11">
3331    References: add "work in progress" for Internet Drafts.
3332</t>
3333<t hangText="2006-02-27">
3334    Fix front matter (lowercase Internet-Draft, say "Intended status" for
3335    non-RFC documents). Start work on experimental extension for 
3336    simplified internal links.
3337</t>
3338<t hangText="2006-03-19">
3339    Tweaks to IESG Copyright stuff; support submissionType attribute.
3340    Fix duplicate reference anchors in HTML output.  Reduce HTML Tidy warnings.
3341    Fix reference to normative ASCII version (now requires trailing ".txt").
3342    Tweaks to hCard generation.  Started to move non-issue-tracking
3343    extensions into namespace "http://purl.org/net/xml2rfc/ext".
3344</t>
3345<t hangText="2006-03-27">
3346    Moved "simple reference" extension into namespace "http://purl.org/net/xml2rfc/ext"
3347    and add documentation.  HTML conformance enhancements.
3348</t>
3349<t hangText="2006-04-02">
3350    Cleanup special code for automated XHTML XSLT generation.
3351</t>
3352<t hangText="2006-04-21">
3353    Generate &lt;CITE> elements where appropiate.
3354    Introduce x:blockquote, x:dfn, x:h and x:q elements.
3355</t>
3356<t hangText="2006-05-06">
3357    Introduce x:bcp14 element.
3358</t>
3359<t hangText="2006-05-14">
3360  Fix content model for x:blockquote.
3361</t>
3362<t hangText="2006-06-18">
3363  Add box drawing support (x:bt, x:bc, x:bb).
3364</t>
3365<t hangText="2006-06-20">
3366  HTML validity fixes (legal chars in anchors in index).
3367</t>
3368<t hangText="2006-06-24">
3369  Reduce leading empty lines in artwork. Move &lt;dt> style info into CSS.
3370</t>
3371<t hangText="2006-07-14">
3372  Fix rendering of multiple street address entries (missing line break).
3373</t>
3374<t hangText="2006-07-24">
3375  Add extension for deep linking into RFCs, do not generate empty list
3376  items in TOC output, avoid empty &lt;dt> elements for list items
3377  without hangText attribute.
3378</t>
3379<t hangText="2006-08-01">
3380  Allow @anchor on more elements; start work on Relax NG grammar for
3381  extensions. Reduce generated style elements (use CSS classes instead).
3382  Consistently use "id" instead of "name". Change default target for RFC
3383  links to "http://tools.ietf.org/html/rfcNNNN".
3384</t>
3385<t hangText="2006-08-06">
3386  Include appendices defined in &lt;appendix> elements in TOC (please
3387  consider them deprecated anyhow!). Generate links to
3388  "http://tools.ietf.org/html/draft-*" for Internet Drafts.
3389  Replace x:frag by x:rel, allowing any kind of relative reference instead
3390  of just fragments.
3391</t>
3392<t hangText="2006-08-30">
3393  Reduce textual differences between HTML output and what xml2rfc produces
3394  in TXT output mode (section refs/reference targets). Add small workaround
3395  for Opera 9.0.1's problem with node-set().
3396</t>
3397<t hangText="2006-10-29">
3398  Fix problem generating internal links to change markup within references
3399  section. Enhancements when generating numbered references for deleted
3400  references.
3401  Allow inclusion of references into the index (through include-references-in-index
3402  extension).
3403  Fix a bug that caused the newer version of the IETF boilerplate to be
3404  produced rather than the pre-RFC3667 one.
3405  Update to RFC4287 boilerplate.
3406</t>
3407<t hangText="2006-11-11">
3408  Add extension attribute x:for-anchor to &lt;iref&gt; handling.
3409</t>
3410<t hangText="2006-11-26">
3411  Experimental (and limited) support for &lt;x:lt&gt;.
3412</t>
3413<t hangText="2006-12-04">
3414  Fix bugs in processing documents that have both the ipr and the number attribute
3415  set on the rfc root element. Add support for x:fmt='none' on xrefs.
3416  Add different pre style based on artwork type attributes (experimental).
3417</t>
3418<t hangText="2006-12-13">
3419  Add x:fmt='anchor' for xref elements.
3420</t>
3421<t hangText="2007-01-07">
3422  Fix root template for compatibility for the exslt:node-set implementation
3423  in Firefox3.
3424</t>
3425<t hangText="2007-01-29">
3426  Avoid empty table entry in front matter when organization is not specified
3427  for an author.
3428</t>
3429<t hangText="2007-02-10">
3430  Allow change tracking in table rows.
3431</t>
3432<t hangText="2007-03-09">
3433  Add hcard profile URI (<eref target="http://www.w3.org/2006/03/hcard"/>) to head element.
3434  Add warning for misplaced &lt;t> elements (after section).
3435</t>
3436<t hangText="2007-03-21">
3437  Fix internal linking from reference entries in index for some xref types.
3438  Minor CSS tweaks contributed by MTR. Allow turning on text justification through
3439  a PI. Improve iref anchor generation to generate less instable anchors.
3440</t>
3441<t hangText="2007-03-28">
3442  Fixes for numbering of ed:inserted references sections.
3443</t>
3444<t hangText="2007-05-04">
3445  Do not generate anchors for edits in deleted sections. Enhance HTML
3446  conformance.
3447</t>
3448<t hangText="2007-05-19">
3449  Enhance diagnostics when using Saxon (needs Saxon's "-l" command line
3450  parameter to keep line number information). Add warning when symref PI
3451  is missing (default will change in the future).
3452  Add support for overriding computed section numbers (when formatting
3453  historic documents).
3454</t>
3455<t hangText="2007-06-07">
3456  Change default for symrefs PI to "yes" (see change in xml2rfc 1.33pre4).
3457  Warn about docName attributes that appear to contain a file extension.
3458</t>
3459<t hangText="2007-06-26">
3460  Workaround author/@initials values without trailing dot, as in xml2rfc.tcl.
3461</t>
3462<t hangText="2007-07-14">
3463  Enhance index generation for references that use @x:sec attribute.
3464</t>
3465<t hangText="2007-09-09">
3466  Fix: sortrefs is a nop when symrefs=no.
3467</t>
3468<t hangText="2007-10-17">
3469  Work in progress: add support for referencing sections in sibling
3470  documents by anchor name.
3471</t>
3472<t hangText="2007-10-17">
3473  Work in progress (continued): support for referencing sections in sibling
3474  documents by anchor name.
3475</t>
3476<t hangText="2007-12-31">
3477  Emit warning when updating/obsoleting stuff that's not referenced.
3478</t>
3479<t hangText="2008-02-03">
3480  Support xml2rfc-1.33pre5's suppress-title attribute on texttable and figure.
3481</t>
3482<t hangText="2008-02-06">
3483  Extension: allow &lt;eref> below &lt;cref>.
3484</t>
3485<t hangText="2008-02-17">
3486  Extensions: add x:span and x:length-of.
3487</t>
3488<t hangText="2008-02-20">
3489  Add new RFC boilerplate (as changed in 2007-08).
3490</t>
3491<t hangText="2008-02-27">
3492  Improve diagnostics for artwork width problems; add defaulting of publication
3493  dates (requires XSLT processor supporting exslt:date, or msxml).
3494</t>
3495<t hangText="2008-02-29">
3496  Enhance CSS for link elements in the front header, update rules for
3497  generating "Acknowledgment" statement.
3498</t>
3499<t hangText="2008-03-01">
3500  Use line numbers in diagnostics in Saxon8/9 as well.
3501</t>
3502<t hangText="2008-03-02">
3503  Fix a bug in the logic choosing the boilerplate, resulting in obsolete
3504  text being inserted into IDs.
3505</t>
3506<t hangText="2008-04-01">
3507  Add support for superscript element.
3508</t>
3509<t hangText="2008-06-28">
3510  Add sanity checks for email addresses, allow multiple email elements.
3511</t>
3512<t hangText="2008-07-06">
3513  Add x:abnf-char-sequence.
3514</t>
3515<t hangText="2008-08-21">
3516  Add x:note.
3517</t>
3518<t hangText="2008-09-06">
3519  Add experimental support for SVG images.
3520</t>
3521<t hangText="2008-09-17">
3522  Add experimental support for x:author. Fix xref/@format=none.
3523</t>
3524<t hangText="2008-10-10">
3525  Fix a huge bug, causing text content after an XML comment to be ignored.
3526</t>
3527<t hangText="2009-02-24">
3528  Use table/caption when needed.
3529</t>
3530<t hangText="2009-03-07">
3531  Fix bug that caused text to disappear in the output in presence of
3532  processing instructions.
3533</t>
3534<t hangText="2009-03-12">
3535  Make inlined comments bookmarkable.
3536</t>
3537<t hangText="2009-04-09">
3538  Upgrade to DC-HTML from RFC 2731 (affects head/@profile).
3539</t>
3540<t hangText="2009-07-08">
3541  Remove table/@summary in output; the value getting inserted was just
3542  repeating stuff that appeared in the preamble.
3543</t>
3544<t hangText="2009-08-01">
3545  Implement table alignment (HTML output only for now).
3546</t>
3547<t hangText="2009-08-18">
3548  Replicate Dublin Core "abstract" metadata into meta/@name=description
3549  (search engines do use it).
3550</t>
3551<t hangText="2009-09-02">
3552  Fix default/left alignment of table columns, remove silly table summmary
3553  attributes.
3554</t>
3555<t hangText="2009-09-24">
3556  Support double-sided layout using CSS page:left/right selectors.
3557</t>
3558<t hangText="2009-11-27">
3559  Generate unordered lists instead of broken definition lists for list style empty.
3560</t>
3561      </list></t>
3562    </section>
3563    <section title="rfc2629toFO.xslt">
3564      <t><list style="hanging">
3565<t hangText="2003-11-16">
3566    Initial release.
3567</t>
3568<t hangText="2003-11-29">
3569    Enhance handling of unknown list styles.
3570</t>
3571<t hangText="2004-04-04">
3572    Update reference section handling.
3573</t>
3574<t hangText="2004-04-17">
3575    Use XSL-WD-1.1-style fo:bookmark and index handling and add postprocessors for
3576    existing implementations. Unify PDF info generation by using XEP (postprocessors)
3577    will convert.
3578</t>
3579<t hangText="2004-04-20">
3580    Add experimental cref support.
3581</t>
3582<t hangText="2004-06-14">
3583    Set correct index-item defaults.
3584</t>
3585<t hangText="2004-07-18">
3586    Add list style=letters.
3587</t>
3588<t hangText="2004-09-03">
3589    Make URLs in text break where they are allowed to break by inserting
3590    zero-width spaces.
3591</t>
3592<t hangText="2004-09-26">
3593    Fix letter-style inside nested lists.
3594</t>
3595<t hangText="2004-10-31">
3596    Update handling of artwork.
3597</t>
3598<t hangText="2004-11-13">
3599    Fix handling of references inside ed:* markup.  Fix whitespace handling
3600    in artwork.
3601</t>
3602<t hangText="2004-11-27">
3603    Irefs in artwork generate monospaced entries in index.
3604</t>
3605<t hangText="2005-01-31">
3606    Fix TOC generation that was broken after changes in main XSLT.
3607</t>
3608<t hangText="2005-02-05">
3609    Bring in sync with cosmetic changes in rfc2629.xslt.
3610</t>
3611<t hangText="2005-05-07">
3612    Minor fix for change tracking in document title.  Support for table
3613    styles.
3614</t>
3615<t hangText="2005-06-18">
3616    Fix references to tables.
3617</t>
3618<t hangText="2005-10-15">
3619    Process t/@anchor.
3620</t>
3621<t hangText="2006-02-11">
3622    References: add "work in progress" for Internet Drafts.
3623</t>
3624<t hangText="2006-06-02">
3625    Use XSL 1.1 WD Feb 2006.
3626</t>
3627<t hangText="2007-03-21">
3628    Support optional text justification.
3629</t>
3630<t hangText="2007-05-19">
3631    Various improvements in spacing; also allow overriding the automatic
3632    list indentation via list/x:indent.
3633</t>
3634<t hangText="2009-04-08">
3635    Fix spacing in headers; add support for formatting for double-sided printing.
3636</t>
3637<t hangText="2009-08-01">
3638    Remove surplus empty pages when not generating double-sided output.
3639</t>
3640     </list></t>
3641    </section>
3642
3643    <section title="xsl11toAn.xslt">
3644    <t><list style="hanging">
3645<t hangText="2004-05-17">
3646     Initial release.
3647</t>
3648<t hangText="2006-06-02">
3649    Use XSL 1.1 WD Feb 2006.
3650</t>
3651    </list></t>
3652    </section>
3653
3654    <section title="xsl11toFop.xslt">
3655    <t><list style="hanging">
3656<t hangText="2010-08-25">
3657    Switch to Apache FOP 1.0.
3658</t>
3659<t hangText="2009-09-12">
3660    Support for FOP 0.20.5 and FOP 0.93 removed. Please use FOP 0.95.
3661</t>
3662<t hangText="2008-03-15">
3663    Add a workaround to the fo:inline workaround (sigh).
3664</t>
3665    </list></t>
3666    </section>
3667
3668    <section title="xsl11toXep.xslt">
3669    <t><list style="hanging">
3670<t hangText="2004-05-17">
3671     Initial release.
3672</t>
3673<t hangText="2004-09-04">
3674     Fix xep:index-item attributes.
3675</t>
3676<t hangText="2006-06-02">
3677    Use XSL 1.1 WD Feb 2006.
3678</t>
3679    </list></t>
3680    </section>
3681  </section>
3682
3683</back>
3684</rfc>
Note: See TracBrowser for help on using the repository browser.