source: rfc2629xslt/rfc2629xslt.xml @ 2080

Last change on this file since 2080 was 2027, checked in by julian.reschke@…, 7 years ago

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

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