Skip to content

Commit

Permalink
Updated profiles
Browse files Browse the repository at this point in the history
  • Loading branch information
roll committed Apr 12, 2018
1 parent 60393ef commit cf511a3
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions tableschema/profiles/table-schema.json
Expand Up @@ -1540,7 +1540,6 @@
},
"missingValues": {
"type": "array",
"minItems": 1,
"items": {
"type": "string"
},
Expand All @@ -1550,7 +1549,8 @@
"description": "Values that when encountered in the source, should be considered as `null`, 'not present', or 'blank' values.",
"context": "Many datasets arrive with missing data values, either because a value was not collected or it never existed.\nMissing 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.\nThe `missingValues` property provides a way to indicate that these values should be interpreted as equivalent to null.\n\n`missingValues` are strings rather than being the data type of the particular field. This allows for comparison prior to casting and for fields to have missing value which are not of their type, for example a `number` field to have missing values indicated by `-`.\n\nThe default value of `missingValue` for a non-string type field is the empty string `''`. For string type fields there is no default for `missingValue` (for string fields the empty string `''` is a valid value and need not indicate null).",
"examples": [
"{\n \"missingValues\": [\n \"-\",\n \"NaN\",\n \"\"\n ]\n}\n"
"{\n \"missingValues\": [\n \"-\",\n \"NaN\",\n \"\"\n ]\n}\n",
"{\n \"missingValues\": []\n}\n"
]
}
},
Expand Down

0 comments on commit cf511a3

Please sign in to comment.