source: rfc2629xslt/rfc2629xslt.xml @ 1426

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

bump up document dates; update to latest version of rfc2629.xslt, refresh appendices.

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