I ran a diff on our schema and the one in the datapackage repo. The only difference was that they use the unicode glyph for the euro symbol whereas we use the unicode code:
|
"description": "a boolean field with a default of `true`. If `true` the physical contents of this field must follow the formatting constraints already set out. If `false` the contents of this field may contain leading and/or trailing non-numeric characters (which implementors MUST therefore strip). The purpose of `bareNumber` is to allow publishers to publish numeric data that contains trailing characters such as percentages e.g. `95%` or leading characters such as currencies e.g. `\u20ac95` or `EUR 95`. Note that it is entirely up to implementors what, if anything, they do with stripped text.", |
Since this just occurs in an example it doesn't matter much, but maybe we want to change to match? Maybe also good to keep in mind for the future in terms of how the schema is update so a similar error is not introduced in a meaningful field.
