Replied to: github.com

So investigating Micropub and mf2 syntax to test out in this app, it looks like we’d use h-measure which is a proposed property.

Essentially Apple stores the “energy burned”, “exercise time”, and “stand count” separately from the goals.

We would essentially need to send 6 separate attributes to the server. I think this is best done as 3 separate Micropub requests.

Each Micropub request would cover a “type” (energy, exercise, stand) with the “current” value and the “goal” value.

I’m not sure what the top level item would be (h-entry? Something else?)

If h-entry, it could contain a p-name of “Stand”, “Energy” or “Exercise Time”.

Then embed two h-measures into h-entry, the current value as an h-measure and the goal value as an h-measure.

This is my first brainstorm and will probably be refined.