Script updating gh-pages from 79719bb. [ci skip]

draft-ietf-sedate-datetime-extended.html

@@ -1037,7 +1037,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Sharma &amp; Bormann</td>
-<td class="center">Expires 15 April 2024</td>
+<td class="center">Expires 19 April 2024</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1053,12 +1053,12 @@
 <a href="https://www.rfc-editor.org/rfc/rfc3339" class="eref">3339</a> (if approved)</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2023-10-13" class="published">13 October 2023</time>
+<time datetime="2023-10-17" class="published">17 October 2023</time>
     </dd>
 <dt class="label-intended-status">Intended Status:</dt>
 <dd class="intended-status">Standards Track</dd>
 <dt class="label-expires">Expires:</dt>
-<dd class="expires"><time datetime="2024-04-15">15 April 2024</time></dd>
+<dd class="expires"><time datetime="2024-04-19">19 April 2024</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1119,7 +1119,7 @@ <h2 id="name-status-of-this-memo">
         time. It is inappropriate to use Internet-Drafts as reference
         material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
 <p id="section-boilerplate.1-4">
-        This Internet-Draft will expire on 15 April 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 19 April 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -1499,7 +1499,7 @@ <h3 id="name-background">
 earlier in <span><a href="https://rfc-editor.org/rfc/rfc2822#section-3.3" class="relref">Section 3.3</a> of [<a href="#RFC2822" class="cite xref">RFC2822</a>]</span>.
 This email header convention is in actual use, while its adaptation into
 <span>[<a href="#RFC3339" class="cite xref">RFC3339</a>]</span> always was
-handicapped by the fact that <span>[<a href="#ISO8601-2000" class="cite xref">ISO8601:2000</a>]</span> and later versions do not actually allow <code>-00:00</code>.<a href="#section-2.1-2" class="pilcrow">¶</a></p>
+compromised by the fact that <span>[<a href="#ISO8601-2000" class="cite xref">ISO8601:2000</a>]</span> and later versions do not actually allow <code>-00:00</code>.<a href="#section-2.1-2" class="pilcrow">¶</a></p>
 <p id="section-2.1-3">Implementations that needed to express the semantics of <code>-00:00</code>
 therefore tended to use <code>Z</code> instead.<a href="#section-2.1-3" class="pilcrow">¶</a></p>
 </section>
@@ -1512,7 +1512,7 @@ <h3 id="name-update-to-rfc-3339">
 <p id="section-2.2-1">This specification updates <span><a href="https://rfc-editor.org/rfc/rfc3339#section-4.3" class="relref">Section 4.3</a> of [<a href="#RFC3339" class="cite xref">RFC3339</a>]</span>, aligning it with the actual
 practice of interpreting the offset <code>Z</code> to mean the same as<code>-00:00</code>:
 "the time in UTC is known, but the offset to local time is unknown".<a href="#section-2.2-1" class="pilcrow">¶</a></p>
-<p id="section-2.2-2">A revised <span><a href="https://rfc-editor.org/rfc/rfc3339#section-4.3" class="relref">Section 4.3</a> of [<a href="#RFC3339" class="cite xref">RFC3339</a>]</span> with the update could read as follows:<a href="#section-2.2-2" class="pilcrow">¶</a></p>
+<p id="section-2.2-2"><span><a href="https://rfc-editor.org/rfc/rfc3339#section-4.3" class="relref">Section 4.3</a> of [<a href="#RFC3339" class="cite xref">RFC3339</a>]</span> is revised to read as follows:<a href="#section-2.2-2" class="pilcrow">¶</a></p>
 <blockquote id="section-2.2-3">
           <p id="section-2.2-3.1">If the time in UTC is known, but the offset to local time is unknown,
    this can be represented with an offset of "Z".

draft-ietf-sedate-datetime-extended.txt

@@ -6,7 +6,7 @@ Serialising Extended Data About Times and Events               U. Sharma
 Internet-Draft                                              Igalia, S.L.
 Updates: 3339 (if approved)                                   C. Bormann
 Intended status: Standards Track                  Universität Bremen TZI
-Expires: 15 April 2024                                   13 October 2023
+Expires: 19 April 2024                                   17 October 2023
 
 
  Date and Time on the Internet: Timestamps with additional information
@@ -60,7 +60,7 @@ Status of This Memo
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on 15 April 2024.
+   This Internet-Draft will expire on 19 April 2024.
 
 Copyright Notice
 
@@ -303,7 +303,7 @@ Table of Contents
    information in email headers, described in Section 3.3 of [RFC5322]
    and introduced earlier in Section 3.3 of [RFC2822].  This email
    header convention is in actual use, while its adaptation into
-   [RFC3339] always was handicapped by the fact that [ISO8601:2000] and
+   [RFC3339] always was compromised by the fact that [ISO8601:2000] and
    later versions do not actually allow -00:00.
 
    Implementations that needed to express the semantics of -00:00
@@ -316,8 +316,7 @@ Table of Contents
    00:00: "the time in UTC is known, but the offset to local time is
    unknown".
 
-   A revised Section 4.3 of [RFC3339] with the update could read as
-   follows:
+   Section 4.3 of [RFC3339] is revised to read as follows:
 
    |  If the time in UTC is known, but the offset to local time is
    |  unknown, this can be represented with an offset of "Z".  (The