Ignore:
Timestamp:
Apr 1, 2010, 12:49:35 AM (10 years ago)
Author:
julian.reschke@…
Message:

latest versions of rfc2629.xslt and xml2rfc.tcl, bump up document dates

File:
1 edited

Legend:

Unmodified
Added
Removed
  • rfc2629xslt/rfc2629xslt.xml

    r754 r799  
    3030        </author>
    3131     
    32     <date month="January" year="2010"/>
     32    <date month="March" year="2010"/>
    3333
    3434    <keyword>RFC2629</keyword>
     
    19691969  attribute x:indent-with { ATEXT }?
    19701970
    1971 <spanx># Allow anchor attribute on &lt;author></spanx>
     1971<spanx># Allow anchor and x:annotation attributes on &lt;author></spanx>
    19721972attlist.author &amp;=
    1973   attribute anchor { xsd:ID }?
     1973  attribute anchor { xsd:ID }?,
     1974  attribute x:annotation { ATEXT }?
    19741975 
    19751976  <spanx># Extend attribute set for &lt;iref> (see <xref target="ext-rfc2629.iref"/>)</spanx>
     
    19971998attlist.spanx &amp;=
    19981999  attribute anchor { xsd:ID }?
     2000
     2001<spanx># Allow annotation attribute on &lt;uri></spanx>
     2002attlist.uri &amp;=
     2003  attribute x:annotation { ATEXT }?
    19992004
    20002005<spanx># Extend attribute set for &lt;xref> (see <xref target="ext-rfc2629.xref"/>)</spanx>
     
    23502355  for the "Status Of This Memo" and "Copyright Notice" sections on the front
    23512356  page. When submitting an Internet Draft, the "boilerplate" is checked
    2352   for compliance with the current Intellectual Property rules, and thus
     2357  by "Idnits" (<eref target="http://tools.ietf.org/tools/idnits/"/>) for compliance with the current Intellectual Property rules, and thus
    23532358  it's important to set the correct value.
    23542359</t>
    23552360<t>
    2356   As of December 2009, the attribute value can take a long list of values. As
     2361  As of the time of this writing, the attribute value can take a long list of values. As
    23572362  frequently, this is not the result of a grand plan, but simply for historic
    23582363  reasons. Of these values, only a few are currently in use; all others are
     
    23782383<t>
    23792384  The name for these values refers to the "TLP" ("IETF TRUST Legal Provisions Relating
    2380   to IETF Documents"), on effect February 15, 2009 (see <eref target="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-02-16-09.pdf"/>).
    2381   An update to this document was published on September 12, 2009 (<eref target="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf"/>),
     2385  to IETF Documents"), on effect February 15, 2009 (see <eref target="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090215.pdf"/>).
     2386  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"/>)
     2387  and on December 28, 2009 (TLP 4.0, <eref target="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf"/>),
    23822388  modifying the license for code components.
    23832389  The actual text is located in Section 6 ("Text To Be Included in IETF Documents")
     
    23862392<t> 
    23872393  The tools will automatically produce the "right" text depending on the
    2388   document's date information (see above).
    2389 </t>
    2390 <x:note>
    2391   <t>
    2392     <x:h>Note:</x:h> for consistency with Internet Draft generation using
    2393     xml2rfc.tcl, the TLP text effective since December 28, 2009 is currently
    2394     only supported when producing RFCs.
    2395   </t>
    2396 </x:note>
     2394  document's date information (see above):
     2395</t>
     2396<texttable align="left">
     2397  <ttcol>TLP</ttcol><ttcol>URI</ttcol><ttcol>starting with publication date</ttcol>
     2398
     2399  <c>3.0</c>
     2400  <c><eref target="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf"/></c>
     2401  <c>2009-11-01</c>
     2402
     2403  <c>4.0</c>
     2404  <c><eref target="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf"/></c>
     2405  <c>2010-04-01</c>
     2406
     2407</texttable>
     2408
    23972409
    23982410<section title="trust200902" anchor="attribute-ipr-trust200902">
     
    24062418<section title="noModificationTrust200902" anchor="attribute-ipr-noModificationTrust200902">
    24072419<t>
    2408   This produces the additional text from Section 6.c.i of the TLP.
     2420  This produces the additional text from Section 6.c.i of the TLP:
    24092421</t>
    24102422<x:blockquote>
     
    24192431<section title="noDerivativesTrust200902" anchor="attribute-ipr-noDerivativesTrust200902">
    24202432<t>
    2421   This produces the additional text from Section 6.c.ii of the TLP.
     2433  This produces the additional text from Section 6.c.ii of the TLP:
    24222434</t>
    24232435<x:blockquote>
     
    26032615    For RFC generation (not IDs), experimentally support RFC 5741 headers and boilerplate and Trust
    26042616    Legal Provisions 4.0.
     2617</t>
     2618<t hangText="2010-03-31">
     2619    Upgrade to xml2rfc v1.35.
    26052620</t>
    26062621      </list></t>
Note: See TracChangeset for help on using the changeset viewer.