v0.6.0

This is a major release recommended for all users.

Functionality

• The schema SDK has been updated, which introduces new schemas like omh:geoposition:1.0 and omh:speed:1.0.

All shims

• All shims that support calories burned and step count now serve omh:calories_burned:2.0 and omh:step_count:2.0 data points, respectively, which require effective time frames to be time intervals.

  Jawbone mappers aren't being updated until it's clear what will happen to the company's products and APIs.

• All shims that support sleep duration now serve omh:sleep_duration:2.0 data points, which requires effective time frames to be time intervals and whose start and end times ignore the latency to sleep onset and the latency to arising.

Google Fit

• A mapper and endpoint have been added to serve omh:geoposition:1.0 data points, which serve location data from Android and Google Fit data streams.
• A mapper and endpoint have been added to serve omh:speed:1.0 data points.

Misfit

• A mapper and endpoint have been added to serve omh:sleep-episode:1.0 data points.

Moves

• The endpoint names have been fixed to be consistent with other shims. See the migration instructions below for more details. (#91)

Withings

• A mapper and endpoint have been added to serve omh:body-temperature:1.0 data points.
• A mapper and endpoint have been added to serve omh:sleep-episode:1.0 data points.
• The endpoints have been updated following Nokia's acquisition of Withings. (thank you for the PR @rbidanta)
• Time zone offsets in mapped data have been updated to match the time zone information sent by Withings, instead of being transformed to UTC.
• The device attribute "Pulse" included in mapped data has been changed to "Activity tracker", as sent by Withings.
• The external ID included in mapped data has been changed to a String for consistency.

Documentation

• The supported mapping list in the documentation has been updated to include the new mappers and schema versions.

Migration instructions

The following breaking changes have been made.

• When API endpoints were made consistent with Open mHealth schema names and with one another in 0.6.0, Moves was missed. This has been rectified, so you will now need to point to the step_count and physical_activity endpoints if you use the Moves shim.