source: rfc2629xslt/rfc2629xslt.xml @ 1327

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

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

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