bareNumber to interpret -$1000 as -1000

[Stephen-Gates]

The current spec doesn't support the bareNumber edge case to interpret -$1000 as -1000.

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.

Reword the spec to handle this (changes in bold)...

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) unless the non-numeric character is - or +. 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, EUR 95, -AUD$100, or ¥-100. Note that it is entirely up to implementors what, if anything, they do with stripped text.

[Stephen-Gates]

Probably should say something about only one - or + being used to handle --$1000.

Also what about +/-$1000

Mmm... Starts to get tricky

[rufuspollock]

@Stephen-Gates it does get quite tricky quickly ...