integers vs decimals and units

[diatomsRcool]

In the Observation element do we need to worry about integers vs decimals? We might need integers for things like scores that are always a whole number. Do we want to force a "0.0" here? Does it matter? Should the attribute be value_number instead?
What about units? Some variables, like ratios and percentages don't have units. Do we need a separate attribute for numbers that don't have units? How do we require units where we need to and not where we don't?

[bfurner]

It is a good point. I suggest that we add a value_integer attribute to the Quantity class to handle cases where the value is an integer as placing integers into a decimal with a .0 at the end implies a level of precision that isn't necessarily there.

Percentages will have UCUM units (i.e. %). I wonder how many ratios may already be represented in UCUM. Now, for cases where there are no units supplied by the source and we're not sure, there may need to be flavors of null added to the enum for units (e.g. 'Unknown', 'Not applicable')

[diatomsRcool]

I would say go ahead and add value_integer. Also, missing units can possibly be handled the same way N3C handled them via their "data rescue" methods.

[bfurner]

will do, thanks

[bfurner]

OK, I merged PR #66 to address this. Feel free to close if you feel this is resolved.