Comments (3)
I would say moving the request parameters into a query string is probably the correct approach here.
I don't believe there is the need for complex geometric shapes if the base geometry for the particular MDS client is provided as part of the token based auth.
Using a POST
to retrieve data is often considered to be not semantic.
I would recommend keeping /trips
and /status_changes
as GET and clarifying around query parameters. I provided a potential approach in #64.
On the agency
side I think it may be a bit early to deciding if service_areas need support for specific provider_id
or an additional /:id
route. I think both of these are good ideas to keep in mind moving forward but I don't think there should necessarily be an update now without a use case.
Let me know what you think!
from mobility-data-specification.
GET parameters is the right spot for this. Would you be comfortable documenting these using RFC6570-compliant form-style query expansion?
Example: /service_areas{?provider_id}{?service_area_id}
.
from mobility-data-specification.
I think part of the confusion is, these query parameters aren't spelled out anywhere in the spec yet. But I also don't see where it is stated that MDS is expecting GET request bodies? That sounds crazy, I totally agree it is a bad idea @oderby!
I also tend to agree with @asadowns and @migurski here, these are very clearly GET requests (read-only, should be idempotent given the same parameters, etc.). @asadowns did some initial work on defining the query params over on #64 - can we move this discussion to that proposal so we can comment on some actual changes to the language in the spec?
(BTW I also really like the suggestion of tying the geo-area to the auth token (see #60) from @asadowns, thus obviating the need for that data on every request.)
I'm closing this one to hopefully move the discussion over to these ongoing threads. Thanks!
from mobility-data-specification.
Related Issues (20)
- guidance on how to use telemetry data for compliance HOT 3
- What vehicles are included in the MDS 2.0 /vehicles endpoint? HOT 4
- Reports endpoint - description of START_DATE HOT 4
- Add mode in trips and vehicles objects HOT 6
- Data structure with sub-objects for mode-specific attributes complexifies the data ingestion HOT 1
- Adding a field in trip objects to cover cancelled trips easier HOT 2
- Add Provider ID: Nextbike HOT 2
- Error and bulk responses HOT 5
- Add the publication_time field in the telemetry object
- Supporting Advanced Air Mobility (AAM) HOT 1
- Add Provider ID: Starship Technologies HOT 3
- Add operations start and end dates to VEHICLES endpoint HOT 5
- Simplify /vehicles/status HOT 1
- Define conditions for "conditionally required" fields
- Clearer support for AV taxis (Robotaxis) and stop events HOT 2
- Real-time improvements for MDS Policy
- Add Provider ID: Flamingo HOT 2
- Policy API - Rule unit of distance travelled for maintenance use cases
- Add Provider ID: 3km HOT 3
- Clarify that Policy API can require Authorization to access the published material
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mobility-data-specification.