-
Notifications
You must be signed in to change notification settings - Fork 40
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' of https://github.com/TOMP-WG/TOMP-API
- Loading branch information
Showing
20 changed files
with
396 additions
and
26 deletions.
There are no files selected for viewing
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,27 +1,23 @@ | ||
Transport Operator Mobility-as-a-service Provider (TOMP) API development Github | ||
==== | ||
|
||
Working group meeting in the Netherlands every two weeks with the goal to develop | ||
and specify a generic TOMP-API for use by Transport Operators and Mobility-as-a-service Providers by Jan 1st 2020. | ||
The TOMP working group aims to develop and sustain an internationally governed interoperable open standard for technical communication between Transport Operators and MaaS Providers, by means of definition, improvement, alignment and dissemination. | ||
|
||
I need help, where can I find it? / How do I start implementing TOMP? | ||
--- | ||
If you need help with your TOMP-integration as a Transport Operator or a MaaS-Provider, use the following channels: | ||
1. First look at the [Wiki](https://github.com/TOMP-WG/TOMP-API/wiki), a lot of flows are described there. The wiki relates to the latest API-version. | ||
2. If you have any questions regarding TOMP or how to implement it, please find us in Slack. There are a lot of developers there that can help you. Slack is a chat tool and very easy to use. Use this link to join our Slack space: https://join.slack.com/t/tomp-wg/shared_invite/zt-e3fftun7-qCs8FyXZPPy9pt_opyFw0Q | ||
2. If you have any questions regarding TOMP or how to implement it, please find us in Slack. There are a lot of developers there that can help you. Slack is a chat tool and very easy to use. | ||
|
||
Where can I find the API-documentation? | ||
--- | ||
OpenAPI 3.0 documentation is also available at https://app.swaggerhub.com/apis-docs/TOMP-API-WG/transport-operator_maas_provider_api/ | ||
OpenAPI 3.0 documentation is available at [Swaggerhub](https://app.swaggerhub.com/apis-docs/TOMP-API-WG/transport-operator_maas_provider_api/). | ||
|
||
To document the latest developments, a Blueprint for an Transport Operator to Mobility-as-a-service Provider API is provided | ||
The latest version of this Blueprint is available at: | ||
|
||
https://github.com/TOMP-WG/TOMP-API/tree/master/documents or through dutchmobilityinnovations.com. | ||
The Blueprint for an Transport Operator to Mobility-as-a-service Provider API is available at the [documentation page](https://github.com/TOMP-WG/TOMP-API/tree/master/documents). | ||
|
||
How can I join the TOMP working group? | ||
--- | ||
Please contact Bon Bakermans ([email protected]). He will add you to our mailing lists and will send you the invites for the meetings. | ||
Join our [Slack space](https://join.slack.com/t/tomp-wg/shared_invite/zt-2bmkbwacm-qxJV1tzON6dp3KH261fwrQ) or contact Ayse (aysehilal.ocal@ndw.nu) to be added to our mailing list and to receive invites for the working group meetings. | ||
|
||
The working group meetings take place every month with the goal to develop and specify a generic TOMP-API for use by Transport Operators and Mobility-as-a-service Providers. All reports can be found at the [documentation page](https://github.com/TOMP-WG/TOMP-API/tree/master/documents/working%20group%20reports). | ||
|
||
|
@@ -31,4 +27,4 @@ Code of conduct | |
[Our code of conduct](https://github.com/TOMP-WG/TOMP-API/blob/master/code_of_conduct.md) [](code_of_conduct.md) | ||
|
||
|
||
<img align="center" src="https://github.com/TOMP-WG/website/blob/master/wiki/images/TOMP%20WG%20grey.png" width="300"> | ||
<img align="center" src="https://github.com/TOMP-WG/website/blob/master/wiki/images/TOMP%20WG%20grey.png" width="300"> |
Large diffs are not rendered by default.
Oops, something went wrong.
Binary file not shown.
Binary file added
BIN
+4.02 MB
documents/presentations/230324 Technical and functional analusis of TOMP-API Duquesne.pptx
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
Repository for TOMP-API working group reports | ||
Reports will be added after they have been approved by the working group | ||
|
||
Please contact [email protected] for more information | ||
Please contact [email protected] for more information |
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.