Merge pull request #588 from frictionlessdata/fix/empty-missing-values

[#578] Allow empty missing values
frictionlessdata · Mar 21, 2018 · 0e900fc · 0e900fc
2 parents 768048b + 861a800
commit 0e900fc
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 2 deletions.
diff --git a/schemas/dictionary/tableschema.yml b/schemas/dictionary/tableschema.yml
@@ -204,7 +204,6 @@ tableSchemaFalseValues:
   default: [ "false", "False", "FALSE", "0" ]
 tableSchemaMissingValues:
   type: array
-  minItems: 1
   items:
     type: string
   default:
@@ -228,6 +227,10 @@ tableSchemaMissingValues:
           ""
         ]
       }
+  - |
+      {
+        "missingValues": []
+      }
 tableSchemaFieldString:
   type: object
   title: String Field

diff --git a/specs/table-schema.md b/specs/table-schema.md
@@ -527,7 +527,9 @@ In additional to field descriptors, there are the following "table level" proper
 Many datasets arrive with missing data values, either because a value was not collected or it never existed. Missing values may be indicated simply by the value being empty in other cases a special value may have been used e.g. `-`, `NaN`, `0`, `-9999` etc.
 
 `missingValues` dictates which string values should be treated as `null` values. This conversion to `null` is done before any other attempted type-specific string conversion.
-The default value `[ "" ]` means that empty strings will be converted to null before any other processing takes place.
+The default value `[ "" ]` means that empty strings will be converted to null before any other processing takes place. 
+Providing the empty list `[]` means that no conversion to null will be done, on any value. 
+
 
 `missingValues` MUST be an `array` where each entry is a `string`.