Clarify the exact error type (#162)

Author: sebastien-rosset

GRAMMAR.ABNF

@@ -341,7 +341,7 @@ slice-expression  = [number] ":" [number] [ ":" [number] ] ;; ## Slices
 ;; - If no `stop` position is given, it is assumed to be the length of the array or string if the given `step` is greater than `0` or `0` if
 ;;   the given `step` is less than `0`.
 ;; - If the given `step` is omitted, it it assumed to be `1`.
-;; - If the given `step` is `0`, an error MUST be raised.
+;; - If the given `step` is `0`, an `invalid-value` error MUST be raised.
 ;; - If the element being sliced is not an array or a string, the result is `null`.
 ;; - If the element being sliced is an array or string and yields no results, the result MUST be an empty array.
 ;;

function_schema.yml

@@ -109,6 +109,7 @@ definitions:
     type: string
     enum:
       - invalid-arity
+      - invalid-value
       - invalid-type
       - not-a-number
       - syntax

functions/abs.yml

@@ -12,7 +12,7 @@ returns:
 desc: |
   Returns the absolute value of the provided argument.  The signature indicates
   that a number is returned, and that the input argument `$value` **must**
-  resolve to a number, otherwise a `invalid-type` error is triggered.
+  resolve to a number, otherwise an `invalid-type` error is triggered.
 
   Below is a worked example.  Given:
 

functions/group_by.yml

@@ -23,7 +23,7 @@ desc: |
   This includes objects for which applying the `$expr` expression evaluates to `null`.
 
   If the result of applying the `$expr` expression against the current array element
-  results in type other than `string` or `null`, a type error MUST be raised.
+  results in type other than `string` or `null`, an `invalid-type` error MUST be raised.
 examples:
   group_by:
     context:

functions/sort_by.yml

@@ -18,7 +18,7 @@ desc: |
   resulting value is used as the key used when sorting the `elements`.
 
   If the result of evaluating the `expr` against the current array element
-  results in type other than a `number` or a `string`, a type error will
+  results in type other than a `number` or a `string`, an `invalid-type` error will
   occur.
 
   Below are several examples using the `people` array (defined above) as the

jep-003-functions.md

@@ -189,7 +189,7 @@ number abs(number $value)
 
 Returns the absolute value of the provided argument.  The signature indicates
 that a number is returned, and that the input argument `$value` **must**
-resolve to a number, otherwise a `invalid-type` error is triggered.
+resolve to a number, otherwise an `invalid-type` error is triggered.
 
 Below is a worked example.  Given:
 

jep-003a-functions.md

@@ -195,7 +195,7 @@ number abs(number $value)
 
 Returns the absolute value of the provided argument.  The signature indicates
 that a number is returned, and that the input argument `$value` **must**
-resolve to a number, otherwise a `invalid-type` error is triggered.
+resolve to a number, otherwise an `invalid-type` error is triggered.
 
 Below is a worked example.  Given:
 

jep-005-array-slices.md

@@ -86,7 +86,7 @@ the given step is greater than 0 or 0 if the given step is less than 0.
 5. If the given step is omitted, it it assumed to be 1.
 
 
-6. If the given step is 0, an error must be raised.
+6. If the given step is 0, an `invalid-value` error must be raised.
 
 
 7. If the element being sliced is not an array, the result must be `null`.

jep-018-grouping.md

@@ -30,7 +30,7 @@ Objects that do not match the group criteria are discarded from the output.
 This includes objects for which applying the `$expr` expression evaluates to `null`.
 
 If the result of applying the `$expr` expression against the current array element
-results in type other than `string` or `null`, a type error MUST be raised.
+results in type other than `string` or `null`, an `invalid-type` error MUST be raised.
 
 ### Examples