Unit for barometer is wrong (hPA instead of hPa) (rev. 13) about schema HOT 8 CLOSED

You're obviously right.

@rnestler @dns2utf8 @rorist would this be a breaking change in an already published spec if we change the capitalization of one of multiple valid values? Does this need to go into the v14 draft?

from schema.

I just crawled the entire directory. Right now a single space is providing barometer data:

https://hskrk-spacemon.herokuapp.com/

from schema.

Hi, maybe we could simplify the sensors. Because now it's almost always an array of objet with value, unit, location, and desc. We could write the specs so its' backward compatible with the detailed sensors, and remove them all, so people can add their own sensors. And still provide examples of sensors.

from schema.

Hm, I think some of the sensors should be standardized, e.g. people now present.

But simplification might be an option.

from schema.

I have no clue how the specification is handled.

For v13 it might be an option to just add "hPa" as enum value in addition to "hPA", and then drop "hPA" in v14. That way it is possible for hackspaces (our hackspace in Siegen actually provides a barometric value of "null" - grgh) to deliver the sensor value correctly without breaking the other hackspaces.

from schema.

I think it would be a breaking change.
But since it would only apply to two spaces, we could also change both endpoints.

What do you think @HackerspaceKRK @simon-budig ?

from schema.

We don't know whether there are other applications that will consider hPa as invalid. After all, it should be considered invalid according to the published spec. Since it doesn't hurt anyone, I'd actually stick with the wrong writing and fix it in v0.14.

See #3 for v0.14 discussion.

@simon-budig what do you think? :)

from schema.

This issues is about to be resolved in #7. Please comment there.

from schema.