inferral independent of data

docs/odata-url-conventions/odata-url-conventions.html

@@ -1025,7 +1025,7 @@ <h3 id="511-common-expression-syntax"><a name="CommonExpressionSyntax" href="#Co
 </summary>
 <p>The following operators, functions, and literals can be used in <code>$filter</code>, <code>$orderby</code>, and <code>$compute</code> expressions.</p>
 <p>The <a href="#ODataABNF">OData-ABNF</a> <code>commonExpr</code> syntax rule defines the formal grammar of common expressions.</p>
-<p>The following subsections specify situations in which expressions evaluate to <code>null</code> if operands or parameters do not have the types expected by an operator or function. Notwithstanding these rules, if such a type discrepancy can be inferred for an expression that appears in a request, services SHOULD reject the request with an error message explaining the discrepancy. The inferral could be based on, for example, the declared type of a property or the type of a literal value that occurs in the expression.</p>
+<p>The following subsections specify situations in which expressions evaluate to <code>null</code> if operands or parameters do not have the types expected by an operator or function. Notwithstanding these rules, if such a type discrepancy can be inferred for an expression that appears in a request independently of the underlying data, services SHOULD reject the request with an error message explaining the discrepancy. The inferral could be based on, for example, the declared type of a property or the type of a literal value that occurs in the expression.</p>
 <div class="example">
 <p>Example 51: In a search for people above a certain age</p>
 <pre><code>http://host/service/People?$filter=Age gt &#39;50&#39;</code></pre>

docs/odata-url-conventions/odata-url-conventions.md

@@ -1561,7 +1561,8 @@ grammar of common expressions.
 The following subsections specify situations in which expressions evaluate to `null`
 if operands or parameters do not have the types expected by an operator or function.
 Notwithstanding these rules, if such a type discrepancy can be inferred for an expression
-that appears in a request, services SHOULD reject the request with an error message
+that appears in a request independently of the underlying data,
+services SHOULD reject the request with an error message
 explaining the discrepancy. The inferral could be based on, for example, the
 declared type of a property or the type of a literal value that occurs in the
 expression.

odata-url-conventions/5 Query Options.md

@@ -77,7 +77,8 @@ grammar of common expressions.
 The following subsections specify situations in which expressions evaluate to `null`
 if operands or parameters do not have the types expected by an operator or function.
 Notwithstanding these rules, if such a type discrepancy can be inferred for an expression
-that appears in a request, services SHOULD reject the request with an error message
+that appears in a request independently of the underlying data,
+services SHOULD reject the request with an error message
 explaining the discrepancy. The inferral could be based on, for example, the
 declared type of a property or the type of a literal value that occurs in the
 expression.