Merge pull request #121 from opengeospatial/chris-little-domain-definition

Update clause_4_terms_and_definitions.adoc

Author: chris-little

standard/annex-bibliography.adoc

@@ -8,3 +8,5 @@
 [2] Blower, J., Riechert, M., Roberts, B.: Overview of the CoverageJSON format, https://www.w3.org/TR/covjson-overview/
 
 [3] W3C JSON-LD 1.1, JSON-based Serialization for Linked Data, W3C Recommendation 2020-07-16, https://www.w3.org/TR/json-ld11/
+
+[4] Baumann, P., Hirschorn, E., Masó, J.: OGC Coverage Implementation Schema with Corrigendum, Version: 1.1.1,  http://docs.opengeospatial.org/is/09-146r8/09-146r8.html 

standard/clause_4_terms_and_definitions.adoc

@@ -12,6 +12,8 @@ feature that acts as a function to return values from its range for any direct p
 === *Domain*
 well-defined set [ISO19123]
 
+Note: Commonly, a set of n-dimensional direct positions, usually including space and time, for which a coverage provides values of properties
+
 === *i18n object*
 string in multiple languages with tags as defined in [BCP 47](http://tools.ietf.org/html/bcp47), and the value is the string in that language.
 The special language tag `"und"` can be used to identify a value whose language is unknown or undetermined. [IETF BCP47]

standard/clause_specification_text.adoc

@@ -1,4 +1,4 @@
-== Specification: Normative with Informative Examples
+== CoverageJSON Encoding: Normative with Informative Examples
 
 //## 1. Introduction
 === Introduction