source: rfc2629xslt/rfc2629xslt.xml @ 1443

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

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

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