Merge pull request opengeospatial#746 from jerstlouis/patch-9

1-scope: Fixed restrction -> restriction (my typo)
jerstlouis · Jul 19, 2022 · 686f719 · 686f719
2 parents 8e8ce60 + 76147cc
commit 686f719
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/cql2/standard/clause_1_scope.adoc b/cql2/standard/clause_1_scope.adoc
@@ -8,4 +8,4 @@ This document defines
 * A JSON encoding for a CQL2 filter.
 
 NOTE: The CQL2 grammar contains all the necessary language elements of a general purpose expression language, including support for spatio-temporal values.
-The focus of this version of the language are boolean-valued filter expressions. It is planned to potentially remove this restriction, while maintaining backward compatibility, allowing expressions that result in values of other data types, including geometries. Such expressions could be used, for example, in a styling language to specify parameter values, or to define derived properties. In this case, a particular use of CQL2 could specify the boolean-valued restrction separately, for example when used as a filter predicate expression, or as a styling rule selector. The usability of such an expression language, especially in the context of geometry types, would also greatly benefit from standardizing additional functions and/or operators e.g., to compute the geometry resulting from buffering or intersecting operations.
+The focus of this version of the language are boolean-valued filter expressions. It is planned to potentially remove this restriction, while maintaining backward compatibility, allowing expressions that result in values of other data types, including geometries. Such expressions could be used, for example, in a styling language to specify parameter values, or to define derived properties. In this case, a particular use of CQL2 could specify the boolean-valued restriction separately, for example when used as a filter predicate expression, or as a styling rule selector. The usability of such an expression language, especially in the context of geometry types, would also greatly benefit from standardizing additional functions and/or operators e.g., to compute the geometry resulting from buffering or intersecting operations.