Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Will the agency API replace the provider API ? #148

Closed
HenriJ opened this issue Oct 23, 2018 · 2 comments
Closed

Will the agency API replace the provider API ? #148

HenriJ opened this issue Oct 23, 2018 · 2 comments
Labels
question Further information is requested

Comments

@HenriJ
Copy link

HenriJ commented Oct 23, 2018

I don't know if this point has already been clarified, but it might be interesting to add some clarification in the README about the future of both APIs.
Should both the Agency & Provider APIs live side-by-side while the Agency API would be a superset of the Provider API ? Or is the Provider API a temporary stream that will be deprecated at some time and replacer by the Agency API ?
@HenriJ HenriJ mentioned this issue Oct 23, 2018
Closed
@thekaveman
Copy link
Collaborator

I think the answer here is a definitive no; agency and provider are focused on entirely different perspectives of the data.

It seems like there have been enough questions about this that some clearer documentation would be useful here. TLDR:

  • provider is all about what already happened, the historical view of operations (e.g. how many trips yesterday?)

  • agency is all about what may (and may not) happen, the future control mechanism (e.g. can I park here?)

@thekaveman thekaveman added the question Further information is requested label Oct 23, 2018
@HenriJ
Copy link
Author

HenriJ commented Oct 23, 2018

Ok, thank you @thekaveman , that is very clear and makes perfect sense.

@HenriJ HenriJ closed this as completed Oct 23, 2018
hunterowens added a commit that referenced this issue Oct 23, 2018
@hunterowens
Agency vs Provider Clarification. [#148]
ff54842
black-tea pushed a commit that referenced this issue Oct 31, 2018
@hunterowens @black-tea
Agency vs Provider Clarification. [#148] (#150)
23e19be 
* Agency vs Provider Clarification. [#148]

* clean up wording
hunterowens added a commit that referenced this issue Dec 4, 2018
@hunterowens
Merge branch '0.2.1'
253aaa9 
* 0.2.1: (61 commits)
  updating release notes for 0.2.x
  fix for required properties in generated schema
  add WIND as a dockless mobility provider (#185)
  add Spin as a dockless mobility provider (#184)
  Reverts PR #146, moving Timestamp change into future release (#180)
  wheels (#177)
  adding info about mailing list. (#175)
  Adding Release guidelines (#147)
  Update providers.csv (#174)
  Add `next` link requirement (#166)
  Add OAauth client_credentials auth guidelines section
  update JUMP provider URL (#164)
  allowing null for links.next (#162)
  Agency vs Provider Clarification. [#148] (#150)
  Add LADOT Guidelines for the Handling of MSP Data (#154)
  allowing for null links properties
  Suggestion: Add Clarification to Propulsion Types
  fix versions
  remove oneOf when required is being added
  regenerate the schemas
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@HenriJ @thekaveman