MDS 2.0 - trip/fare attributes inconsistencies about mobility-data-specification HOT 7 CLOSED

I think 5 was just formatting, fixed here.

6 I think leaving as milliseconds makes sense based on the field name and intention, because it's not the timestamp of when this happened, it's the calculated difference in timestamps.

from mobility-data-specification.

For 1, 2, 5, and 7 you could do a PR.

For 3, the 'may have' refers to the fact that you may have some combination of the following fields.

For 4, in passenger services it's a string because I can be a variety of sources.

For 6, MDS defaults to milliseconds as our common unit. I don't think we use seconds elsewhere.

For 8, instead of currency it should probably be an integer and in cents.

from mobility-data-specification.

I don't see what the issue is with 5?

For 6 I think those should just be renamed timestamp since that's what we use everywhere; and yes, it is milliseconds since Unix epoch.

from mobility-data-specification.

For 2 the name is now consistent here.

from mobility-data-specification.

7 is fixed here with underscore - Kegan does that change it form OpenAPI?

And 1 is fixed here, which also may need an OpenAPI update.

from mobility-data-specification.

These items were all addressed in OpenAPI in openmobilityfoundation/mds-openapi#36

from mobility-data-specification.

Closing this multi-item issue. If you have ideas from this list that weren't addressed, please open a new issue to discuss them. Thanks!

from mobility-data-specification.