Changeset 308 for rfc2629xslt/rfc2629xslt.xml
- Timestamp:
- 10/08/08 14:19:14 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
rfc2629xslt/rfc2629xslt.xml
r285 r308 30 30 </author> 31 31 32 <date month=" July" year="2008"/>32 <date month="August" year="2008"/> 33 33 <keyword>RFC2629</keyword> 34 34 <keyword>xml2rfc</keyword> … … 55 55 <t>outputting HTML (<xref target="output.html"/>) and XHTML (<xref target="output.xhtml"/>),</t> 56 56 <t>outputting CHM (Compiled Microsoft Help, <xref target="output.chm"/>),</t> 57 <t>outputting PDF through XSL-FO (<xref target="output.pdf"/>) and</t> 57 <t>outputting PDF through XSL-FO (<xref target="output.pdf"/>),</t> 58 <t>extensions to the xml2rfc vocabulary (<xref target="extensions"/>).</t> 58 59 <t>various utilities (<xref target="utilities"/>).</t> 59 60 </list> 60 61 </t> 62 <t> 63 The full distribution is available at <eref target="http://greenbytes.de/tech/webdav/rfc2629xslt.zip"/>. 64 </t> 61 65 </section> 62 66 … … 68 72 <section title="Extension elements"> 69 73 <t> 70 In addition, <spanx style="verb">rfc2629.xslt</spanx> supports a set of extension elements, using elements 71 and attributes in the namespace "http://greenbytes.de/2002/rfcedit". They 72 are used for 73 <list style="symbols"> 74 <t>simple issue tracking and change tracking and</t> 75 <t>adding additional metadata to the generated documents (such as HTML LINK 76 elements to related documents, see <xref target="html.link"/>).</t> 77 </list> 78 </t> 79 <t> 80 Note that these extensions are experimental. Please email the author in case 74 <spanx style="verb">rfc2629.xslt</spanx> supports two kind of extension 75 elements, using different XML namespaces. 76 </t> 77 <t> 78 The first set contains (hopefully) generally useful extensions, see 79 <xref target="extensions"/>. 80 </t> 81 <t> 82 The second set is used for change and issue tracking and currently is not 83 documented here. Please email the author in case 81 84 you're interested in using these extensions. 82 85 </t> … … 969 972 </section> 970 973 974 <section title="Extensions to Xml2rfc <rfc> element" anchor="ext-rfc2629.rfc"> 975 <t> 976 The extension attributes below are allowed on the standard <rfc> element: 977 <list style="symbols"> 978 <t>grddl:transformation can be used to reference a GRDDL transform.</t> 979 <t>x:maturiy-level can be used to specify the IETF Standards Track 980 Maturity Level of "proposed", "draft" or "internet" (see <xref target="RFC2026" x:fmt="of" x:sec="4.1"/>).</t> 981 </list> 982 </t> 983 </section> 984 971 985 <section title="Extensions to Xml2rfc <section> element" anchor="ext-rfc2629.section"> 972 986 <t> … … 1042 1056 If the document is supposed to be published on the IETF standards track, 1043 1057 the desired level can be specified using the parameter <spanx style='verb'>intended-level</spanx> 1044 as 'PROPOSED', 'DRAFT' or 'STANDARD'. 1058 as 'proposed', 'draft' or 'internet'. Alternatively, it can be specified 1059 inside the document using the attribute x:maturity-level on the <rfc> element. 1045 1060 </t> 1046 1061 <t> … … 1250 1265 <references title="Informative References"> 1251 1266 1267 <reference anchor='RFC2026'> 1268 <front> 1269 <title abbrev='Internet Standards Process'>The Internet Standards Process -- Revision 3</title> 1270 <author initials='S.' surname='Bradner' fullname='Scott O. Bradner'> 1271 <organization>Harvard University</organization> 1272 <address> 1273 <email>sob@harvard.edu</email> 1274 </address> 1275 </author> 1276 <date year='1996' month='October' /> 1277 </front> 1278 <seriesInfo name='BCP' value='9' /> 1279 <seriesInfo name='RFC' value='2026' /> 1280 </reference> 1281 1252 1282 <reference anchor="RFC2119"> 1253 1283 <front> 1254 1284 <title abbrev="RFC Key Words">Key words for use in RFCs to Indicate Requirement Levels</title> 1255 1285 <author initials="S." surname="Bradner" fullname="Scott Bradner"> 1256 <organization>Harvard University</organization> 1257 <address> 1258 <email>sob@harvard.edu</email> 1259 </address></author> 1286 <organization>Harvard University</organization> 1287 <address> 1288 <email>sob@harvard.edu</email> 1289 </address> 1290 </author> 1260 1291 <date month="March" year="1997"/> 1261 1292 </front> … … 1738 1769 <spanx># Extend attribute set for <rfc></spanx> 1739 1770 attlist.rfc &= 1740 attribute grddl:transformation { ATEXT }? 1771 attribute grddl:transformation { ATEXT }?, 1772 attribute x:maturity-level { "proposed" | "draft" | "internet" } 1741 1773 1742 1774 <spanx># Extend attribute set for <section> (see <xref target="ext-rfc2629.section"/>)</spanx> … … 2035 2067 Initial release. 2036 2068 </t> 2037 <t hangText="2003-11-16">2038 Initial release.2039 </t>2040 2069 <t hangText="2004-05-11"> 2041 2070 Add document status; print references type. … … 2068 2097 <t hangText="2008-07-12"> 2069 2098 Add XSLT2-based link target checking. 2099 </t> 2100 <t hangText="2008-08-10"> 2101 Change keywords for "intended-level" to proposed/draft/internet, 2102 optionall extract intended level from /rfc/@x:maturity-level attribute. 2070 2103 </t> 2071 2104 </list></t>
Note: See TracChangeset
for help on using the changeset viewer.