The format of the data that comes in and out of the API is currently dictated by the columns in the table that has the data. This means that if other agencies (who might not have the same column names) try to use this, the format of the data will be different for each agency, making it complex for any client that wants to consume the data.
A standard format for the data should be determined such that it will work for most or all agencies who use Express Lanes and wish to publish the toll data.
This data standard should at minimum:
- allow each toll corridor to be identified by the agency who controls it
- provide a unique ID for each toll corridor
- provide the time at which the toll was updated
- provide the current price of the toll
- allow for an arbitrary message to be displayed
- secure the publication of toll data using keys
The API should at minimum:
- allow for multiple agencies to publish data for multiple tolls
- provide a way to get the toll data for all or some of the toll corridors
- support for HTTP and HTTPS
- support both AJAX and WebSockets
The format of the data that comes in and out of the API is currently dictated by the columns in the table that has the data. This means that if other agencies (who might not have the same column names) try to use this, the format of the data will be different for each agency, making it complex for any client that wants to consume the data.
A standard format for the data should be determined such that it will work for most or all agencies who use Express Lanes and wish to publish the toll data.
This data standard should at minimum:
The API should at minimum: