New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bareNumber or stripNonNumeric? #509

Closed
roll opened this Issue Aug 21, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@roll
Member

roll commented Aug 21, 2017

Overview

Type number (http://specs.frictionlessdata.io/table-schema/#number):

bareNumber: 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. €95 or EUR 95. Note that it is entirely up to implementors what, if anything, they do with stripped text.

Type integer (http://specs.frictionlessdata.io/table-schema/#integer):

stripNonNumeric: a boolean field with a default of false. When stripNonNumeric is true, the value of the field MUST have all leading and trailing non-numeric characters stripped from the string before casting.

@roll roll added the Table Schema label Aug 21, 2017

@pwalsh

This comment has been minimized.

Show comment
Hide comment
@pwalsh

pwalsh Aug 21, 2017

Member

bareNumber - pls do a PR on specs too

Member

pwalsh commented Aug 21, 2017

bareNumber - pls do a PR on specs too

@pwalsh pwalsh assigned rufuspollock and roll and unassigned rufuspollock Aug 21, 2017

@pwalsh pwalsh added this to the v1.0 milestone Aug 21, 2017

@roll

This comment has been minimized.

Show comment
Hide comment
@roll

roll Aug 21, 2017

Member

@pwalsh
thanks. ok

Member

roll commented Aug 21, 2017

@pwalsh
thanks. ok

rufuspollock added a commit that referenced this issue Aug 21, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment