Editorial: Define and consistently use a "ISO 8601 / RFC 9557 string" term

Author: gibson042

spec/abstractops.html

@@ -1016,8 +1016,8 @@ <h1>
   <emu-clause id="sec-temporal-iso8601grammar">
     <h1>RFC 9557 / ISO 8601 grammar</h1>
     <p>
-      Several operations in this section are intended to parse RFC 9557 strings representing a date, a time, a duration, or a combined date and time.
-      For the purposes of these operations, a valid RFC 9557 string is defined as a string that can be generated by one of the goal elements of the following grammar.
+      Several operations in this section are intended to parse strings representing a date, a time, a duration, or a combined date and time.
+      For the purposes of these operations, a valid <dfn variants="ISO 8601 / RFC 9557 strings">ISO 8601 / RFC 9557 string</dfn> is defined as a string that can be generated by one of the goal elements of the following grammar.
     </p>
     <p>This grammar is adapted from the ABNF grammar of ISO 8601 that is given in appendix A of <a href="https://tools.ietf.org/html/rfc3339#appendix-A">RFC 3339</a>, augmented with the grammar of annotations in section 4.1 of <a href="https://datatracker.ietf.org/doc/html/rfc9557#name-abnf">RFC 9557</a></p>
     <p>
@@ -1582,7 +1582,7 @@ <h1>
     <dl class="header">
       <dt>description</dt>
       <dd>
-        It parses the argument either as an RFC 9557 string or bare calendar type, and returns the calendar type.
+        It parses the argument either as an ISO 8601 / RFC 9557 string or bare calendar type, and returns the calendar type.
         The returned string is syntactically a valid calendar type, but not necessarily an existing one.
       </dd>
     </dl>
@@ -1711,7 +1711,7 @@ <h1>
     <dl class="header">
       <dt>description</dt>
       <dd>
-        It parses the argument as either a time zone identifier or an RFC 9557 string.
+        It parses the argument as either a time zone identifier or an ISO 8601 / RFC 9557 string.
         The returned Record's fields are set as follows:
         <ul>
           <li>If _timeZoneString_ is a named time zone identifier, then [[Name]] is _timeZoneString_ and [[OffsetMinutes]] is ~empty~.</li>

spec/calendar.html

@@ -779,7 +779,7 @@ <h1>
       <dl class="header">
         <dt>description</dt>
         <dd>
-          It returns a string with a calendar annotation suitable for concatenating to the end of an RFC 9557 string.
+          It returns a string with a calendar annotation suitable for concatenating to the end of an ISO 8601 / RFC 9557 string.
           Depending on the given _id_ and value of _showCalendar_, the string may be empty if no calendar annotation need be included.
         </dd>
       </dl>

spec/mainadditions.html

@@ -508,7 +508,7 @@ <h1>Time Zone Offset String <del>Format</del><ins>Formats</ins></h1>
       <p>[...]</p>
 
       <emu-note type="editor">
-        The grammar in this section should be deleted; it is replaced by the ISO 8601 / RFC 9557 String grammar in <emu-xref href="#sec-temporal-iso8601grammar"></emu-xref>.
+        The grammar in this section should be deleted; it is replaced by the ISO 8601 / RFC 9557 string grammar in <emu-xref href="#sec-temporal-iso8601grammar"></emu-xref>.
       </emu-note>
     </emu-clause>
 

spec/plaindate.html

@@ -836,7 +836,7 @@ <h1>
       </h1>
       <dl class="header">
         <dt>description</dt>
-        <dd>It formats _temporalDate_ to an RFC 9557 string.</dd>
+        <dd>It formats _temporalDate_ to an ISO 8601 / RFC 9557 string.</dd>
       </dl>
       <emu-alg>
         1. Let _year_ be PadISOYear(_temporalDate_.[[ISODate]].[[Year]]).

spec/plaindatetime.html

@@ -896,7 +896,7 @@ <h1>
       </h1>
       <dl class="header">
         <dt>description</dt>
-        <dd>It formats an ISO Date-Time Record into an RFC 9557 string, to the precision specified by _precision_.</dd>
+        <dd>It formats an ISO Date-Time Record into an ISO 8601 / RFC 9557 string, to the precision specified by _precision_.</dd>
       </dl>
       <emu-alg>
         1. Let _yearString_ be PadISOYear(_isoDateTime_.[[ISODate]].[[Year]]).

spec/plainmonthday.html

@@ -350,7 +350,7 @@ <h1>
       </h1>
       <dl class="header">
         <dt>description</dt>
-        <dd>It formats _monthDay_ into an RFC 9557 string.</dd>
+        <dd>It formats _monthDay_ into an ISO 8601 / RFC 9557 string.</dd>
       </dl>
       <emu-alg>
         1. Let _month_ be ToZeroPaddedDecimalString(_monthDay_.[[ISODate]].[[Month]], 2).

spec/plainyearmonth.html

@@ -566,7 +566,7 @@ <h1>
       </h1>
       <dl class="header">
         <dt>description</dt>
-        <dd>It formats _yearMonth_ as an RFC 9557 string.</dd>
+        <dd>It formats _yearMonth_ as an ISO 8601 / RFC 9557 string.</dd>
       </dl>
       <emu-alg>
         1. Let _year_ be PadISOYear(_yearMonth_.[[ISODate]].[[Year]]).

spec/zoneddatetime.html

@@ -902,7 +902,7 @@ <h1>
             In the case of more than one possible exact time, or no possible exact time, an answer is determined using _offsetBehaviour_, _disambiguation_ and _offsetOption_.
           </p>
           <p>
-            As a special case when parsing RFC 9557 strings which are only required to specify time zone offsets to minutes precision, if _matchBehaviour_ is ~match minutes~, then a value for _offsetNanoseconds_ that is rounded to the nearest minute will be accepted in those cases where _offsetNanoseconds_ is compared against _timeZone_'s offset.
+            As a special case when parsing ISO 8601 / RFC 9557 strings which are only required to specify time zone offsets to minutes precision, if _matchBehaviour_ is ~match minutes~, then a value for _offsetNanoseconds_ that is rounded to the nearest minute will be accepted in those cases where _offsetNanoseconds_ is compared against _timeZone_'s offset.
             If _matchBehaviour_ is ~match exactly~, then this does not happen.
           </p>
         </dd>
@@ -1052,7 +1052,7 @@ <h1>
       <dl class="header">
         <dt>description</dt>
         <dd>
-          It returns an RFC 9557 string representation of its argument, including a time zone name annotation and calendar annotation, which are extensions to the ISO 8601 format.
+          It returns an ISO 8601 / RFC 9557 string representation of its argument, including a time zone name annotation and calendar annotation, which are extensions to the ISO 8601 format.
         </dd>
       </dl>
       <emu-alg>