Fields in JSON

[sethfri]

In /mobile/BEACON_ID.json, the physical_expiration_date is given, but the training_completion_date and permit_expiration_date are not. Is this what Public Works is expecting?

I remember someone talking about showing the users how long the driver has been a cab driver, meaning instead of training_completion_date, we might want to add a calculated property - like years_as_driver - based on the training_completion_date and put that in the JSON so that the client doesn't have to spend time calculating it.

What's the difference between physical_expiration_date and permit_expiration_date? I'm not sure which we should be including in the JSON.

[brollb]

Those fields were taken from the list of fields used currently. We should
see if they are necessary and what they are.

Brian
On Feb 27, 2014 4:08 AM, "Seth Friedman" notifications@github.com wrote:

In /mobile/BEACON_ID.json, the physical_expiration_date is given, but
the training_completion_date and permit_expiration_date are not. Is this
what Public Works is expecting?

I remember someone talking about showing the users how long the driver has
been a cab driver, meaning instead of training_completion_date, we might
want to add a calculated property - like years_as_driver - based on the
training_completion_date and put that in the JSON so that the client
doesn't have to spend time calculating it.

What's the difference between physical_expiration_date and
permit_expiration_date? I'm not sure which we should be including in the
JSON.

Reply to this email directly or view it on GitHubhttps://github.com//issues/32
.