Skip to content

Commit

Permalink
Supply missing changes metadata
Browse files Browse the repository at this point in the history
  • Loading branch information
@michaelhkay
michaelhkay committed Nov 12, 2024
1 parent 5f488b2 commit adf6237
Show file tree
Hide file tree
Showing 2 changed files with 81 additions and 17 deletions.
65 changes: 48 additions & 17 deletions specifications/xpath-functions-40/src/function-catalog.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3120,7 +3120,8 @@ format-number(12345, '0,###^0', {
</fos:example>
</fos:examples>
<fos:changes>
<fos:change><p>The decimal format name can now be supplied as a value of type <code>xs:QName</code>,
<fos:change issue="780" PR="925" date="2024-01-09"><p>The decimal format name can now be supplied
as a value of type <code>xs:QName</code>,
as an alternative to supplying a lexical QName as an instance of <code>xs:string</code>.</p>
</fos:change>
<fos:change issue="340 1138" PR="1049 1151" date="2024-03-05"><p>Decimal format parameters
Expand Down Expand Up @@ -4884,7 +4885,9 @@ translate(value := '٢٠٢٣', replace := '٠١٢٣٤٥٦٧٨٩', with := '01234
</fos:example>
</fos:examples>
<fos:changes>
<fos:change><p>The function has been expanded in scope to handle comparison of values other than strings.</p></fos:change>
<fos:change issue="893" PR="909" date="2024-01-10">
<p>The function has been expanded in scope to handle comparison of values other than strings.</p>
</fos:change>
</fos:changes>
</fos:function>
<fos:function name="codepoint-equal" prefix="fn">
Expand Down Expand Up @@ -9042,7 +9045,7 @@ return ($value - unix-dateTime()) div seconds(0.001)</eg>
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="959" date="2024-08-01"><p>New in 4.0</p></fos:change>
<fos:change issue="959" PR="1358" date="2024-08-01"><p>New in 4.0</p></fos:change>
</fos:changes>
</fos:function>

Expand Down Expand Up @@ -9777,7 +9780,7 @@ return ($value - unix-dateTime()) div seconds(0.001)</eg>
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="1448">
<fos:change issue="1448" PR="1481" date="2024-10-08">
<p>The function has been extended to handle other Gregorian types such as <code>xs:gYearMonth</code>.</p>
</fos:change>
</fos:changes>
Expand Down Expand Up @@ -9849,7 +9852,7 @@ return ($value - unix-dateTime()) div seconds(0.001)</eg>
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="1448">
<fos:change issue="1448" PR="1481" date="2024-10-08">
<p>The function has been extended to handle other Gregorian types such as <code>xs:gYearMonth</code>.</p>
</fos:change>
</fos:changes>
Expand Down Expand Up @@ -9921,7 +9924,7 @@ return ($value - unix-dateTime()) div seconds(0.001)</eg>
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="1448">
<fos:change issue="1448" PR="1481" date="2024-10-08">
<p>The function has been extended to handle other Gregorian types such as <code>xs:gMonthDay</code>.</p>
</fos:change>
</fos:changes>
Expand Down Expand Up @@ -10009,7 +10012,7 @@ return ($value - unix-dateTime()) div seconds(0.001)</eg>
</fos:examples>

<fos:changes>
<fos:change issue="1448">
<fos:change issue="1448" PR="1481" date="2024-10-08">
<p>The function has been extended to handle other types including <code>xs:time</code>.</p>
</fos:change>
</fos:changes>
Expand Down Expand Up @@ -10070,7 +10073,7 @@ return ($value - unix-dateTime()) div seconds(0.001)</eg>
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="1448">
<fos:change issue="1448" PR="1481" date="2024-10-08">
<p>The function has been extended to handle other types including <code>xs:time</code>.</p>
</fos:change>
</fos:changes>
Expand Down Expand Up @@ -10187,7 +10190,7 @@ return ($value - unix-dateTime()) div seconds(0.001)</eg>
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="1448">
<fos:change issue="1448" PR="1481" date="2024-10-08">
<p>The function has been extended to handle other types such as <code>xs:gYearMonth</code>.</p>
</fos:change>
</fos:changes>
Expand Down Expand Up @@ -14072,7 +14075,7 @@ return empty($break)
</fos:example>
</fos:examples>
<fos:changes>
<fos:change><p>New in 4.0</p></fos:change>
<fos:change issue="1542" PR="1547 1551"><p>New in 4.0</p></fos:change>
</fos:changes>

</fos:function>
Expand Down Expand Up @@ -14412,7 +14415,7 @@ return error((), 'Duplicate IDs found: ' || string-join($ids, ', '))</eg>
</fos:example>
</fos:examples>
<fos:changes>
<fos:change date="2022-09-20"><p>New in 4.0</p></fos:change>
<fos:change date="2022-09-20" issue="858"><p>New in 4.0</p></fos:change>
</fos:changes>
</fos:function>
<fos:function name="insert-before" prefix="fn">
Expand Down Expand Up @@ -14850,7 +14853,7 @@ for-each($input, fn($item, $pos) {
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="2 868" date="2022-09-27"><p>New in 4.0</p></fos:change>
<fos:change issue="2 868" PR="1504" date="2022-09-27"><p>New in 4.0</p></fos:change>
</fos:changes>
</fos:function>

Expand Down Expand Up @@ -16823,6 +16826,10 @@ declare function equal-strings(

</fos:examples>
<fos:changes>
<fos:change issue="930" PR="933" date="2024-01-16">
<p>When comments and processing instructions are ignored, any text nodes either side of the
comment or processing instruction are now merged prior to comparison.</p>
</fos:change>
<fos:change issue="934 1167" PR="1191" date="2024-05-21">
<p>The <code>$options</code> parameter has been added,
absorbing the <code>$collation</code> parameter.</p>
Expand Down Expand Up @@ -17126,6 +17133,14 @@ declare function equal-strings(
code="0006"/>. </p>
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="866" PR="881" date="2023-12-06">
<p>The way that <code>fn:min</code> and <code>fn:max</code> compare numeric values of different types
has changed. The most noticeable effect is that when these functions are applied to a sequence of
<code>xs:integer</code> or <code>xs:decimal</code> values, the result is an <code>xs:integer</code> or
<code>xs:decimal</code>, rather than the result of converting this to an <code>xs:double</code></p>
</fos:change>
</fos:changes>
</fos:function>


Expand Down Expand Up @@ -17270,6 +17285,14 @@ declare function equal-strings(
code="0006"/>. </p>
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="866" PR="881" date="2023-12-06">
<p>The way that <code>fn:min</code> and <code>fn:max</code> compare numeric values of different types
has changed. The most noticeable effect is that when these functions are applied to a sequence of
<code>xs:integer</code> or <code>xs:decimal</code> values, the result is an <code>xs:integer</code> or
<code>xs:decimal</code>, rather than the result of converting this to an <code>xs:double</code></p>
</fos:change>
</fos:changes>
</fos:function>
<fos:function name="sum" prefix="fn">
<fos:signatures>
Expand Down Expand Up @@ -18101,6 +18124,14 @@ return tokenize(normalize-space($s), ' ')[. castable as xs:IDREF]</eg>
not able to guarantee that the result of the function will be deterministic, and the
user has not indicated that an unstable result is acceptable.</p>
</fos:errors>
<fos:changes>
<fos:change issue="898" PR="905" date="2024-01-09">
<p>The rule that multiple calls on <code>fn:doc</code>
supplying the same absolute URI must return the same document node has been clarified;
in particular the rule does not apply if the dynamic context for the two calls requires
different processing of the documents (such as schema validation or whitespace stripping).</p>
</fos:change>
</fos:changes>
</fos:function>
<fos:function name="doc-available" prefix="fn">
<fos:signatures>
Expand Down Expand Up @@ -27699,7 +27730,7 @@ array:of-members(
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="868" date="2024-10-29">
<fos:change issue="868" PR="1504" date="2024-10-29">
<p>Optional <code>$separator</code> added.</p>
</fos:change>
</fos:changes>
Expand Down Expand Up @@ -27954,7 +27985,7 @@ array:fold-left($array, (), fn($indices, $member, $pos) {
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="114" date="2022-12-13"><p>New in 4.0</p></fos:change>
<fos:change issue="114" PR="258" date="2022-12-13"><p>New in 4.0</p></fos:change>
<fos:change issue="1171" PR="1182" date="2024-05-07">
<p>The <code>$predicate</code> callback function may return an empty sequence (meaning <code>false</code>).</p>
</fos:change>
Expand Down Expand Up @@ -28905,7 +28936,7 @@ array:build(
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="97"><p>New in 4.0</p></fos:change>
<fos:change issue="97" PR="250"><p>New in 4.0</p></fos:change>
</fos:changes>
</fos:function>

Expand Down Expand Up @@ -28965,7 +28996,7 @@ return deep-equal(
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="29 113 314"><p>New in 4.0</p></fos:change>
<fos:change issue="29 113 314" PR="360 476"><p>New in 4.0</p></fos:change>
</fos:changes>
</fos:function>

Expand Down Expand Up @@ -29096,7 +29127,7 @@ fold-left($input, [], fn($array, $record) {
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="29 113 314"><p>New in 4.0</p></fos:change>
<fos:change issue="29 113 314" PR="360 476"><p>New in 4.0</p></fos:change>
</fos:changes>
</fos:function>

Expand Down
33 changes: 33 additions & 0 deletions specifications/xpath-functions-40/src/xpath-functions.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2781,6 +2781,14 @@ string conversion of the number as obtained above, and the appropriate <var>suff
</div3>
<div3 id="html-ascii-case-insensitive-collation" diff="chg" at="issue668">
<head>The HTML ASCII Case-Insensitive Collation</head>

<changes>
<change issue="668" PR="680" date="2023-09-05">
The case-insensitive collation is now defined normatively within this specification, rather than
by reference to the HTML "living specification", which is subject to change. The collation can now
be used for ordering comparisons as well as equality comparisons.
</change>
</changes>

<p>The collation URI <code>http://www.w3.org/2005/xpath-functions/collation/html-ascii-case-insensitive</code> must be recognized
by every implementation. It is <phrase diff="chg" at="issue668">designed to be compatible with</phrase>
Expand Down Expand Up @@ -3027,6 +3035,12 @@ string conversion of the number as obtained above, and the appropriate <var>suff
<?local-function-index?>
<div3 id="regex-syntax">
<head>Regular expression syntax</head>
<changes>
<change issue="999" PR="1022" date="2024-02-20">
Regular expressions can include comments (starting and ending with <code>#</code>)
if the <code>c</code> flag is set.
</change>
</changes>
<p>The regular expression syntax used by these functions is defined in terms of
the regular expression syntax specified in XML Schema (see <bibref ref="xmlschema-2"/>), which in turn is based on the established conventions of
languages such as Perl. However, because XML Schema uses regular expressions
Expand Down Expand Up @@ -3675,6 +3689,12 @@ It is recommended that implementers consult <bibref ref="UNICODE-TR18"/> for inf
<div3 id="duration-conformance" diff="add" at="issue931">
<head>Limits and precision</head>

<changes>
<change issue="931" PR="932" date="2024-01-16">
The specification now prescribes a minimum precision and range for durations.
</change>
</changes>

<p>All conforming processors
<rfc2119>must</rfc2119> support duration values in which:</p>
<ulist>
Expand Down Expand Up @@ -8603,6 +8623,12 @@ There is no constructor function for <code>xs:NOTATION</code>. Constructors are
<div2 diff="add" at="issue617" id="id-constructors-for-record-tests">
<head>Constructor functions for named record tests</head>

<changes>
<change issue="617" PR="953" date="2024-02-20">
Constructor functions for named record types have been introduced.
</change>
</changes>

<p>For every named item type in the static context (See <xspecref spec="XP31"
ref="static_context"/>) whose expansion is a record test, there is a
constructor function whose name is the same as the name of the
Expand Down Expand Up @@ -11779,6 +11805,13 @@ ISBN 0 521 77752 6.</bibl>

<div1 id="schemata">
<head>Schemas</head>

<changes>
<change issue="648" PR="924" date="2024-01-09">
Rules have been added clarifying that users should not be allowed to change the schema for
the <code>fn</code> namespace.
</change>
</changes>
<p>Two functions in this specification, <code>fn:analyze-string</code> and
<code>fn:json-to-xml</code>, produce results in the form of an XDM node tree that must conform
to a specified schema, defined in this appendix.
Expand Down

0 comments on commit adf6237

Please sign in to comment.