


RFC2629 through XSLT                                          J. Reschke
                                                              greenbytes
                                                           November 2004


            Transforming RFC2629-formatted XML through XSLT


Table of Contents

   1.   Introduction . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.   Supported RFC2629 elements . . . . . . . . . . . . . . . . .   3
     2.1  Extension elements . . . . . . . . . . . . . . . . . . . .   3
   3.   Processing Instructions  . . . . . . . . . . . . . . . . . .   4
     3.1  Supported xml2rfc-compatible PIs . . . . . . . . . . . . .   4
     3.2  Unsupported xml2rfc-compatible PIs . . . . . . . . . . . .   5
     3.3  Extension PIs  . . . . . . . . . . . . . . . . . . . . . .   6
   4.   Anchors  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   5.   Supported XSLT engines . . . . . . . . . . . . . . . . . . .   8
     5.1  Standalone Engines . . . . . . . . . . . . . . . . . . . .   8
     5.2  In-Browser Engines . . . . . . . . . . . . . . . . . . . .   8
   6.   Transforming to HTML . . . . . . . . . . . . . . . . . . . .   9
     6.1  HTML compliance  . . . . . . . . . . . . . . . . . . . . .   9
     6.2  Standard HTML LINK elements  . . . . . . . . . . . . . . .   9
     6.3  Standard HTML metadata . . . . . . . . . . . . . . . . . .  10
     6.4  Dublin Core (RFC2731) metadata . . . . . . . . . . . . . .  10
   7.   Transforming to XHTML  . . . . . . . . . . . . . . . . . . .  11
   8.   Transforming to CHM (Microsoft Compiled Help)  . . . . . . .  12
   9.   Transforming to PDF via XSL-FO . . . . . . . . . . . . . . .  13
     9.1  Extension feature matrix . . . . . . . . . . . . . . . . .  13
     9.2  Example: producing output for Apache FOP . . . . . . . . .  14
   10.  Utilities  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     10.1   Checking References  . . . . . . . . . . . . . . . . . .  15
     10.2   Producing reference entries for books  . . . . . . . . .  15
     10.3   Down-converting to RFC2629bis DTD  . . . . . . . . . . .  16
   11.  Informative References . . . . . . . . . . . . . . . . . . .  16
        Author's Address . . . . . . . . . . . . . . . . . . . . . .  17
        Index  . . . . . . . . . . . . . . . . . . . . . . . . . . .  18













Reschke                                                         [Page 1]

Documentation             RFC2629 through XSLT             November 2004


1.  Introduction

   This document describes a set of XSLT transformations that can be
   used to transform RFC2629-compliant XML (see [RFC2629]) to various
   output formats, such as HTML and PDF.  The main topics are
   o  compliance to the xml2rfc XML element set (Section 2),
   o  support for xml2rfc processing instructions (Section 3),
   o  the names of anchor elements generated in HTML and PDF output
      (Section 4),
   o  various XSLT engines that can be used (Section 5),
   o  outputting HTML (Section 6) and XHTML (Section 7),
   o  outputting CHM (Compiled Microsoft Help, Section 8),
   o  outputting PDF through XSL-FO (Section 9) and
   o  various utilities (Section 10).





































Reschke                                                         [Page 2]

Documentation             RFC2629 through XSLT             November 2004


2.  Supported RFC2629 elements

   "rfc2629.xslt" supports both all RFC2629 grammar elements and the
   extensions implemented in xml2rfc 1.21.

2.1  Extension elements

   In addition, "rfc2629.xslt" supports a set of extension elements,
   using elements and attributes in the namespace
   "http://greenbytes.de/2002/rfcedit".  They are used for
   o  simple issue tracking and change tracking and
   o  adding additional metadata to the generated documents (such as
      HTML LINK elements to related documents, see Section 6.2).

   Note that these extensions are experimental.  Please email the author
   in case you're interested in using these extensions.



































Reschke                                                         [Page 3]

Documentation             RFC2629 through XSLT             November 2004


3.  Processing Instructions

   All PIs can be set as XSLT parameter as well, overriding any value
   that is found in the source file to be transformed.

   Using processing instructions:

   <?rfc toc="yes"?>
   <?rfc-ext support-rfc2731="no"?>

   Using XSLT parameters:

   saxon foo.xml rfc2629.xslt xml2rfc-toc=yes \
     xml2rfc-ext-support-rfc2731=no > result.hzml


3.1  Supported xml2rfc-compatible PIs

   +------------+------------+-------------+-------------+-------------+
   | PI target  | PI         | XSLT        | default     | comment     |
   |            | pseudo-att | parameter   |             |             |
   |            | ribute     | name        |             |             |
   +------------+------------+-------------+-------------+-------------+
   | rfc        | background | xml2rfc-bac | (not set)   |             |
   |            |            | kground     |             |             |
   |            |            |             |             |             |
   | rfc        | compact    | xml2rfc-com | "no"        | only        |
   |            |            | pact        |             | applies to  |
   |            |            |             |             | HTML output |
   |            |            |             |             | method when |
   |            |            |             |             | printing    |
   |            |            |             |             |             |
   | rfc        | comments   | xml2rfc-com | (not set)   |             |
   |            |            | ments       |             |             |
   |            |            |             |             |             |
   | rfc        | editing    | xml2rfc-edi | "no"        |             |
   |            |            | ting        |             |             |
   |            |            |             |             |             |
   | rfc        | footer     | xml2rfc-foo | (not set)   |             |
   |            |            | ter         |             |             |
   |            |            |             |             |             |
   | rfc        | header     | xml2rfc-hea | (not set)   |             |
   |            |            | der         |             |             |
   |            |            |             |             |             |
   | rfc        | inline     | xml2rfc-inl | (not set)   |             |
   |            |            | ine         |             |             |
   |            |            |             |             |             |
   | rfc        | iprnotifie | xml2rfc-ipr | "no"        |             |



Reschke                                                         [Page 4]

Documentation             RFC2629 through XSLT             November 2004


   |            | d          | notified    |             |             |
   |            |            |             |             |             |
   | rfc        | linkmailto | xml2rfc-lin | "yes"       |             |
   |            |            | kmailto     |             |             |
   |            |            |             |             |             |
   | rfc        | private    | xml2rfc-pri | (not set)   |             |
   |            |            | vate        |             |             |
   |            |            |             |             |             |
   | rfc        | sortrefs   | xml2rfc-sor | "no"        |             |
   |            |            | trefs       |             |             |
   |            |            |             |             |             |
   | rfc        | symrefs    | xml2rfc-sym | "no"        |             |
   |            |            | refs        |             |             |
   |            |            |             |             |             |
   | rfc        | toc        | xml2rfc-toc | "no"        |             |
   |            |            |             |             |             |
   | rfc        | tocdepth   | xml2rfc-toc | 99          |             |
   |            |            | depth       |             |             |
   |            |            |             |             |             |
   | rfc        | topblock   | xml2rfc-top | "yes"       |             |
   |            |            | block       |             |             |
   +------------+------------+-------------+-------------+-------------+


3.2  Unsupported xml2rfc-compatible PIs

   +----------------------+----------------------+---------------------+
   | PI target            | PI pseudo-attribute  | comment             |
   +----------------------+----------------------+---------------------+
   | rfc                  | include              | incompatible with   |
   |                      |                      | XML/XSLT processing |
   |                      |                      | model               |
   |                      |                      |                     |
   | rfc                  | needLines            |                     |
   |                      |                      |                     |
   | rfc                  | slides               |                     |
   |                      |                      |                     |
   | rfc                  | strict               |                     |
   |                      |                      |                     |
   | rfc                  | subcompact           |                     |
   |                      |                      |                     |
   | rfc                  | tocindent            | (defaults to "yes") |
   |                      |                      |                     |
   | rfc                  | tocompact            |                     |
   +----------------------+----------------------+---------------------+






Reschke                                                         [Page 5]

Documentation             RFC2629 through XSLT             November 2004


3.3  Extension PIs

   +------------+------------+-------------+-------------+-------------+
   | PI target  | PI         | XSLT        | default     | description |
   |            | pseudo-att | parameter   |             |             |
   |            | ribute     | name        |             |             |
   +------------+------------+-------------+-------------+-------------+
   | rfc-ext    | allow-mark | allow-marku | "no"        | Enables     |
   |            | up-in-artw | p-in-artwor |             | support for |
   |            | ork        | k           |             | specific    |
   |            |            |             |             | elements    |
   |            |            |             |             | inside      |
   |            |            |             |             | abstract    |
   |            |            |             |             | elements    |
   |            |            |             |             | (using this |
   |            |            |             |             | extension   |
   |            |            |             |             | makes the   |
   |            |            |             |             | document    |
   |            |            |             |             | incompatibl |
   |            |            |             |             | e to the    |
   |            |            |             |             | RFC2629bis  |
   |            |            |             |             | DTD; see    |
   |            |            |             |             | description |
   |            |            |             |             | of          |
   |            |            |             |             | conversion  |
   |            |            |             |             | XSLT in     |
   |            |            |             |             | Section 10. |
   |            |            |             |             | 3).         |
   |            |            |             |             |             |
   | rfc-ext    | parse-xml- | parse-xml-i | "no"        | May be used |
   |            | in-artwork | n-artwork   |             | to enable   |
   |            |            |             |             | parsing of  |
   |            |            |             |             | XML content |
   |            |            |             |             | in figures  |
   |            |            |             |             | (MSXML      |
   |            |            |             |             | only).      |
   |            |            |             |             |             |
   | rfc-ext    | support-rf | xml2rfc-ext | "yes"       | Decides     |
   |            | c2731      | -support-rf |             | whether the |
   |            |            | c2731       |             | HTML        |
   |            |            |             |             | transformat |
   |            |            |             |             | ion should  |
   |            |            |             |             | generate    |
   |            |            |             |             | META tags   |
   |            |            |             |             | according   |
   |            |            |             |             | Section 6.4 |
   |            |            |             |             | .           |
   +------------+------------+-------------+-------------+-------------+



Reschke                                                         [Page 6]

Documentation             RFC2629 through XSLT             November 2004


4.  Anchors

   The transformation automatically generates anchors that are supposed
   to be stable and predictable and that can be used to identify
   specific parts of the document.  Anchors are generated both in HTML
   and XSL-FO content (but the latter will only be used for PDF output
   when the XSL-FO engine supports producing PDF anchors).

   The following anchors get auto-generated:

         +----------------------+----------------------------+
         | Anchor name          | Description                |
         +----------------------+----------------------------+
         | rfc.abstract         | Abstract                   |
         |                      |                            |
         | rfc.authors          | Authors section            |
         |                      |                            |
         | rfc.copyright        | Copyright section          |
         |                      |                            |
         | rfc.copyrightnotice  | Copyright notice           |
         |                      |                            |
         | rfc.figure.n         | Figures (titled)           |
         |                      |                            |
         | rfc.figure.u.n       | Figures (untitled)         |
         |                      |                            |
         | rfc.index            | Index                      |
         |                      |                            |
         | rfc.ipr              | Intellectual Property      |
         |                      |                            |
         | rfc.iref.n           | Internal references        |
         |                      |                            |
         | rfc.note.n           | Notes (from front section) |
         |                      |                            |
         | rfc.references       | References                 |
         |                      |                            |
         | rfc.references.n     | Additional references      |
         |                      |                            |
         | rfc.section.n        | Section n                  |
         |                      |                            |
         | rfc.section.n.p.m    | Section n, paragraph m     |
         |                      |                            |
         | rfc.status           | Status of memo             |
         |                      |                            |
         | rfc.toc              | Table of contents          |
         +----------------------+----------------------------+






Reschke                                                         [Page 7]

Documentation             RFC2629 through XSLT             November 2004


5.  Supported XSLT engines

   The transformation requires a non-standard extension function (see
   exsl:node-set [1]) which is however widely available.  XSLT
   processors that do not support this extension (or a functional
   equivalent) currently are not supported.

5.1  Standalone Engines

   The following XSLT engines are believed to work well:
   o  MSXML3 and MSXML4 (<http://msdn.microsoft.com/xml>; these
      processors do not support exsl:node-set(), but have a similar
      proprietary extension)
   o  Saxon (<http://saxon.sourceforge.net/>)
   o  Xalan (<http://xml.apache.org/xalan-j/>)
   o  xsltproc (libxslt) (<http://xmlsoft.org/XSLT/>, make sure that you
      have a current version)

5.2  In-Browser Engines

   The following browsers seem to work fine:
   o  Internet Explorer 5.5 (Windows version, if MSXML3 is installed)
   o  Internet Explorer 6 (Windows version)

   The following browsers are known not to work properly:
   o  Mozilla (missing extension function - see change request at
      Mozilla Bug 215242 [6])
























Reschke                                                         [Page 8]

Documentation             RFC2629 through XSLT             November 2004


6.  Transforming to HTML

   Transformation to HTML can be done inside the browser if it supports
   XSLT.  To enable this, add the following processing instruction to
   the start of the source file:

     <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

   (and ensure that "rfc2629.xslt" is present).

6.1  HTML compliance

   The transformation result is supposed to conform to the HTML 4.01
   strict DTD [HTML].  This can be checked using the W3C's online
   validator at <http://validator.w3.org>.

6.2  Standard HTML LINK elements

   LINK elements exist since HTML 2.0.  They can be used to embed
   content-independant links inside the document.  Unfortunately, only
   few user agents fully support this element, namely Mozilla where it's
   called "Site Navigation Bar" (by default disabled!).

   The following LINK elements are produced:

   +---------------------------------+---------------------------------+
   | LINK type                       | description                     |
   +---------------------------------+---------------------------------+
   | alternate                       | for RFCs, a link to the         |
   |                                 | authorative ASCII version on    |
   |                                 | the IETF web site               |
   |                                 |                                 |
   | appendic                        | pointer to all top-level        |
   |                                 | appendics                       |
   |                                 |                                 |
   | author                          | pointer to "authors" section    |
   |                                 |                                 |
   | chapter                         | pointer to all top-level        |
   |                                 | sections                        |
   |                                 |                                 |
   | contents                        | pointer to table of contents    |
   |                                 |                                 |
   | copyright                       | pointer to copyright statement  |
   |                                 |                                 |
   | index                           | pointer to index                |
   +---------------------------------+---------------------------------+





Reschke                                                         [Page 9]

Documentation             RFC2629 through XSLT             November 2004


   The figure below shows how Mozilla Firebird displays the Site
   Navigation Bar for rfc2396.xml.

   (LINK elements displayed in Mozilla Firebird for RFC2396.xml)


6.3  Standard HTML metadata

   The following standard HTML META elements are produced:

    +-----------+-------------------------------------------------+
    | META name | description                                     |
    +-----------+-------------------------------------------------+
    | generator | from XSLT engine version and stylesheet version |
    |           |                                                 |
    | keywords  | from keyword elements in front section          |
    +-----------+-------------------------------------------------+


6.4  Dublin Core (RFC2731) metadata

   Unless turned off using the "rfc-ext support-rfc2731" processing
   instruction, the transformation will generate metadata according to
   [RFC2731].

   The following DCMI properties are produced:

   +---------------------------------+---------------------------------+
   | META name                       | description                     |
   +---------------------------------+---------------------------------+
   | DC.Creator                      | from author information in      |
   |                                 | front section                   |
   |                                 |                                 |
   | DC.Date.Issued                  | from date information in front  |
   |                                 | section                         |
   |                                 |                                 |
   | DC.Description.Abstract         | from abstract                   |
   |                                 |                                 |
   | DC.Identifier                   | document URN [RFC2648] from     |
   |                                 | "docName" attribute             |
   |                                 |                                 |
   | DC.Relation.Replaces            | from "obsoletes" attribute      |
   +---------------------------------+---------------------------------+








Reschke                                                        [Page 10]

Documentation             RFC2629 through XSLT             November 2004


7.  Transforming to XHTML

   Transforming to XHTML requires slightly different XSLT output options
   and is implemented by the derived transformation script
   "rfc2629toXHTML.xslt".

   Note: Microsoft Internet Explorer does _not_ support XHTML.
   Therefore it usually makes more sense to generate plain old HTML.











































Reschke                                                        [Page 11]

Documentation             RFC2629 through XSLT             November 2004


8.  Transforming to CHM (Microsoft Compiled Help)

   To generate a CHM file using Microsoft's HTML Help Compiler (hhc),
   three files are required in addition to the HTML file.
   1.  hhc - table of contents file (HTML)
   2.  hhk - index file (HTML)
   3.  hhp - project file (plain text)

   The three files are generated with three specific transformations,
   each requiring the additional XSLT parameter "basename" to specify
   the filename prefix.

   Example:

   saxon rfc2616.xml rfc2629toHhp.xslt basename=rfc2616  > rfc2616.hhp
   saxon rfc2616.xml rfc2629toHhc.xslt basename=rfc2616  > rfc2616.hhc
   saxon rfc2616.xml rfc2629toHhk.xslt basename=rfc2616  > rfc2616.hhk
   hhc rfc2616.hhp

































Reschke                                                        [Page 12]

Documentation             RFC2629 through XSLT             November 2004


9.  Transforming to PDF via XSL-FO

   Transformation to XSL-FO [XSL-FO] format is available through
   "rfc2629toFO.xslt" (which includes "rfc2629.xslt", so keep both in
   the same folder).

   Compared to HTML user agents, XSL-FO engines unfortunately either
   come as open source (for instance, Apache FOP) or feature-complete
   (for instance,  AntennaHouse XSL Formatter), but not both at the same
   time.

   As Apache FOP needs special workarounds (page breaking, table
   layout), and some popular extensions aren't standardized yet, the
   translation produces a generic output (hopefully) conforming to
   [XSL-FO-11-WD].  Specific backends ("xsl11toFop.xslt",
   "xsl11toXep.xslt", "xsl11toAn.xslt") the provide post-processing for
   the individual processors.

9.1  Extension feature matrix

   +------------+------------+-------------+-------------+-------------+
   |            |     PDF    |     PDF     |     PDF     |    Index    |
   |            |   anchors  |  bookmarks  |   document  |   cleanup   |
   |            |            |             | information |             |
   +------------+------------+-------------+-------------+-------------+
   | XSL 1.1 WD |   no, but  |     yes     |   no, but   |     yes     |
   | [8]        |   can be   |             |   uses XEP  |             |
   |            | auto-gener |             |    output   |             |
   |            |  ated from |             |  extensions |             |
   |            |    "id"    |             |             |             |
   |            | attributes |             |             |             |
   |            |            |             |             |             |
   | Antenna    |     no     |   yes [10]  |   yes [11]  |   yes [12]  |
   | House XSL  |            |  (from XSL  |  (from XEP  |  (just page |
   | formatter  |            |     1.1     |   document  |  duplicate  |
   | [9]        |            |  bookmarks) |    info)    | elimination |
   |            |            |             |             |  , from XSL |
   |            |            |             |             |   1.1 page  |
   |            |            |             |             |    index)   |
   |            |            |             |             |             |
   | Apache FOP |     yes    |  yes (from  |      no     |      no     |
   | [13]       |            |   XSL 1.1   |             |             |
   |            |            |  bookmarks) |             |             |
   |            |            |             |             |             |
   | RenderX    |     no     |   yes [15]  |   yes [16]  |   yes [17]  |
   | XEP [14]   |            |  (from XSL  |             |  (from XSL  |
   |            |            |     1.1     |             |   1.1 page  |
   |            |            |  bookmarks) |             |    index)   |



Reschke                                                        [Page 13]

Documentation             RFC2629 through XSLT             November 2004


   +------------+------------+-------------+-------------+-------------+


9.2  Example: producing output for Apache FOP

   Example:

   saxon rfc2616.xml rfc2629toFo.xslt > tmp.fo
   saxon tmp.fo xsl11toFop > rfc2629.fo










































Reschke                                                        [Page 14]

Documentation             RFC2629 through XSLT             November 2004


10.  Utilities

10.1  Checking References

   "check-ietf-references.xslt" can be used to check all references to
   RFC-series IETF publications (note this script requires a local copy
   of <ftp://ftp.isi.edu/in-notes/rfc-index.xml>).  For instance:

   > saxon rfc2518.xml check-ietf-references.xslt
   Normative References:
   RFC1766: [PROPOSED STANDARD] obsoleted by RFC3066 RFC3282
   RFC2277: [BEST CURRENT PRACTICE] (-> BCP0018) ok
   RFC2119: [BEST CURRENT PRACTICE] (-> BCP0014) ok
   RFC2396: [DRAFT STANDARD] ok
   RFC2069: [PROPOSED STANDARD] obsoleted by RFC2617
   RFC2068: [PROPOSED STANDARD] obsoleted by RFC2616
   RFC2141: [PROPOSED STANDARD] ok
   RFC2279: [PROPOSED STANDARD] obsoleted by RFC3629
   Informational References:
   RFC2026: [BEST CURRENT PRACTICE] (-> BCP0009) ok
   RFC1807: [INFORMATIONAL] ok
   RFC2291: [INFORMATIONAL] ok
   RFC2413: [INFORMATIONAL] ok
   RFC2376: [INFORMATIONAL] obsoleted by RFC3023


10.2  Producing reference entries for books

   "amazon-asin.xslt" uses the Amazon web services to generate a
   <reference> element for a given ASIN (ISBN).

   For instance:

   <?xml version="1.0" encoding="utf-8"?>
   <references>
    <reference target="urn:isbn:0134516591">
      <front>
        <title>Simple Book, The: An Introduction to Internet Management,
                  Revised Second Edition</title>
        <author surname="Rose"
                   fullname="Marshall T. Rose" initials="M. T. "/>
        <author surname="Marshall"
                   fullname="Rose T. Marshall" initials="R. T."/>
        <seriesInfo name="Prentice Hall" value=""/>
        <date year="1996" month="March"/>
      </front>
    </reference>
   </references>



Reschke                                                        [Page 15]

Documentation             RFC2629 through XSLT             November 2004


   Note that the resulting XML usually requires checking, in this case
   Amazon's database is playing tricks with Marshall's name...

10.3  Down-converting to RFC2629bis DTD

   "clean-for-DTD.xslt" can be used to down-convert some extensions to a
   format that is supported by the base xml2rfc distribution.  Note that
   these extensions are experimental (feedback appreciated).

   The following mappings are done:
   o  <iref> elements inside <artwork> elements are moved in front of
      the enclosing <figure> element.
   o  <xref> elements inside <artwork> are expanded just like in regular
      text (that is, the marlup is stripped, but the element is replaced
      by the applicable replacement text).

11.  Informative References

   [RFC2629]  Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
              June 1999.

   [RFC2648]  Moats, R., "A URN Namespace for IETF Documents", RFC 2648,
              August 1999.

   [RFC2731]  Kunze, J., "Encoding Dublin Core Metadata in HTML",
              RFC 2731, December 1999.

   [HTML]     Raggett, D., Hors, A. and I. Jacobs, "HTML 4.01
              Specification", W3C REC REC-html401-19991224, December
              1999, <http://www.w3.org/TR/html401/>.

   [XSL-FO]   Adler, S., Berglund, A., Caruso, J., Deach, S., Graham,
              T., Grosso, P., Gutentag, E., Milowski, R., Parnell, S.,
              Richman, J. and S. Zilles, "Extensible Stylesheet Language
              (XSL) Version 1.0", W3C REC REC-xsl-20011015, October
              2001, <http://www.w3.org/TR/2001/REC-xsl-20011015>.

   [XSL-FO-11-WD]
              Berglund, A., "Extensible Stylesheet Language (XSL)
              Version 1.1", W3C REC WD-xsl11-20031217, December 2003,
              <http://www.w3.org/TR/2003/WD-xsl11-20031217>.

   [1]   <http://www.exslt.org/exsl/functions/node-set/exsl.node-set.htm
         l>

   [6]   <http://bugzilla.mozilla.org/show_bug.cgi?id=215242>

   [8]   <http://www.w3.org/TR/2003/WD-xsl11-20031217/>



Reschke                                                        [Page 16]

Documentation             RFC2629 through XSLT             November 2004


   [9]   <http://www.antennahouse.com/>

   [10]  <http://www.antennahouse.com/XSL20/axf-extension.htm>

   [11]  <http://www.antennahouse.com/XSL20/axf-extension.htm>

   [12]  <http://www.antennahouse.com/XSL20/axf-extension.htm>

   [13]  <http://xml.apache.org/fop/>

   [14]  <http://xep.xattic.com/>

   [15]  <http://xep.xattic.com/xep/spec.html>

   [16]  <http://xep.xattic.com/xep/spec.html>

   [17]  <http://xep.xattic.com/xep/spec.html>


Author's Address

   Julian F. Reschke
   greenbytes GmbH
   Salzmannstrasse 152
   Muenster, NW  48159
   Germany

   Phone: +49 251 2807760
   Fax:   +49 251 2807761
   Email: julian.reschke@greenbytes.de
   URI:   http://greenbytes.de/tech/webdav/




















Reschke                                                        [Page 17]

Documentation             RFC2629 through XSLT             November 2004


Index

A
   allow-markup-in-artwork PI pseudo-attribute  6
   alternate HTML LINK element  9
   Anchors
      rfc.abstract  7
      rfc.authors  7
      rfc.copyright  7
      rfc.copyrightnotice  7
      rfc.figure.n  7
      rfc.figure.u.n  7
      rfc.index  7
      rfc.ipr  7
      rfc.iref.n  7
      rfc.note.n  7
      rfc.references  7, 7
      rfc.section.n  7
      rfc.section.n.p.m  7
      rfc.status  7
      rfc.toc  7
   AntennaHouse XSL Formatter  13
   Apache FOP  13
   appendix HTML LINK element  9
   author HTML LINK element  9

B
   background PI pseudo-attribute  4

C
   chapter HTML LINK element  9
   CHM format  12
   comments PI pseudo-attribute  4
   compact PI pseudo-attribute  4
   contents HTML LINK element  9
   copyright HTML LINK element  9
   Creator DCMI property  10

D
   Date.Issued DCMI property  10
   DCMI properties
      Creator  10
      Date.Issued  10
      Description.Abstract  10
      Identifier  10
      Relation.Replaces  10
   Description.Abstract DCMI property  10




Reschke                                                        [Page 18]

Documentation             RFC2629 through XSLT             November 2004


E
   editing PI pseudo-attribute  4

F
   footer PI pseudo-attribute  4

G
   generator HTML META element  10

H
   header PI pseudo-attribute  4
   HTML compliance  9
   HTML LINK elements
      alternate  9
      appendix  9
      author  9
      chapter  9
      contents  9
      copyright  9
      index  9
   HTML META elements
      generator  10
      keywords  10

I
   Identifier DCMI property  10
   include PI pseudo-attribute  5
   index HTML LINK element  9
   inline PI pseudo-attribute  4
   Internet Explorer 5.5  8
   Internet Explorer 6  8
   iprnotified PI pseudo-attribute  4

K
   keywords HTML META element  10

L
   linkmailto PI pseudo-attribute  4

M
   Microsoft Help  12
   Mozilla  8
   MSXML3  8
   MSXML4  8

N
   needLines PI pseudo-attribute  5




Reschke                                                        [Page 19]

Documentation             RFC2629 through XSLT             November 2004


P
   Parameters
      xml2rfc-background  4
      xml2rfc-comments  4
      xml2rfc-compact  4
      xml2rfc-editing  4
      xml2rfc-ext-allow-markup-in-artwork  6
      xml2rfc-ext-parse-xml-in-artwork  6
      xml2rfc-ext-support-rfc2731  6
      xml2rfc-footer  4
      xml2rfc-header  4
      xml2rfc-inline  4
      xml2rfc-iprnotified  4
      xml2rfc-linkmailto  4
      xml2rfc-private  4
      xml2rfc-sortrefs  4
      xml2rfc-symrefs  4
      xml2rfc-toc  4
      xml2rfc-tocdepth  4
      xml2rfc-topblock  4
   parse-xml-in-artwork PI pseudo-attribute  6
   private PI pseudo-attribute  4
   Processing Instruction pseudo attributes
      allow-markup-in-artwork  6
      background  4
      comments  4
      compact  4
      editing  4
      footer  4
      header  4
      include  5
      inline  4
      iprnotified  4
      linkmailto  4
      needLines  5
      parse-xml-in-artwork  6
      private  4
      slides  5
      sortrefs  4
      strict  5
      subcompact  5
      support-rfc2731  6
      symrefs  4
      toc  4
      tocdepth  4
      tocindent  5
      tocompact  5
      topblock  4



Reschke                                                        [Page 20]

Documentation             RFC2629 through XSLT             November 2004


R
   Relation.Replaces DCMI property  10
   rfc.abstract anchor  7
   rfc.authors anchor  7
   rfc.copyright anchor  7
   rfc.copyrightnotice anchor  7
   rfc.figure.n anchor  7
   rfc.figure.u.n anchor  7
   rfc.index anchor  7
   rfc.ipr anchor  7
   rfc.iref.n anchor  7
   rfc.note.n anchor  7
   rfc.references anchor  7
   rfc.references.n anchor  7
   rfc.section.n anchor  7
   rfc.section.n.p.m anchor  7
   rfc.status anchor  7
   rfc.toc anchor  7

S
   Saxon  8
   slides PI pseudo-attribute  5
   sortrefs PI pseudo-attribute  4
   strict PI pseudo-attribute  5
   subcompact PI pseudo-attribute  5
   support-rfc2731 PI pseudo-attribute  6
   symrefs PI pseudo-attribute  4

T
   toc PI pseudo-attribute  4
   tocdepth PI pseudo-attribute  4
   tocindent PI pseudo-attribute  5
   tocompact PI pseudo-attribute  5
   topblock PI pseudo-attribute  4

X
   Xalan  8
   xml-stylesheet PI  9
   xml2rfc-background parameter  4
   xml2rfc-comments parameter  4
   xml2rfc-editing parameter  4, 4
   xml2rfc-ext-allow-markup-in-artwork parameter  6
   xml2rfc-ext-parse-xml-in-artwork parameter  6
   xml2rfc-ext-support-rfc2731 parameter  6
   xml2rfc-footer parameter  4
   xml2rfc-header parameter  4
   xml2rfc-inline parameter  4
   xml2rfc-iprnotified parameter  4



Reschke                                                        [Page 21]

Documentation             RFC2629 through XSLT             November 2004


   xml2rfc-linkmailto parameter  4
   xml2rfc-private parameter  4
   xml2rfc-sortrefs parameter  4
   xml2rfc-symrefs parameter  4
   xml2rfc-toc parameter  4
   xml2rfc-tocdepth parameter  4
   xml2rfc-topblock parameter  4
   xsltproc  8











































Reschke                                                        [Page 22]

