brighterplanet/api — comment on commit f05b6483ed9d955b305022ca734f482f95669123
File:  line 0
By rossmeissl:

OK that was a useless comment, sorry

What I mean to say is that the important thing here is not to provide a parallel to `decisions`, but to properly reflect what **Charisma** will be returning. Charisma, remember, is all about `to_s`. So what we need to provide, I think, is the **object** representation of the characteristic value along with its **`to_s`** description via Charisma.

What does the object representation look like? I think [the GH issue](https://github.com/brighterplanet/cm1-rack/issues/1) gets it mostly right, but, on reflection, I think what I have in the first comment for `highway_speed` is wrong. I think---and this combines your proposal above with what is in that issue---this version covers all of our bases:

{ characteristics:
{ highway_speed:
{ object: {
value: 55,
units: "mph" // or maybe we stay in SI units here and leave friendly units to Charisma curation
},
description: "55 mph" // what Charisma says #to_s is
}
}
}

See how that works? It also happily avoids the issue you illustrate above, where you're using `nil` for the "units" on `DFW`. An airport isn't a quantity (scalar plus unit). A speed is.