We at the Open Transport initiative have been asked how our two different API specifications are actually an Open Standard. This is a fair question, as not many people will understand the lengths we have taken to ensure our work is truly open and available for all.
- They are free to adopt
Meaning there is no initial charge or ongoing license fee for them being used as they are. (The only thing we ask is that when they are adopted the Open Transport is given a public credit somewhere, such as in a ‘Terms & Conditions’ or ‘About Us’ page, that’s all)
- They are free to adapt
Meaning that either standard can be taken as they are and changed in any way required. (Any official changes to the current published standard must happen through Open Transport’s modification process)
- They have been designed from a wide collaboration of contributors
Meaning they are the output from many interested organisations and parties (transport providers, private consultants, public sector stakeholders), not just individual suppliers.
- They have been ratified by a clear and communicated peer review process
This has allowed feedback and further contribution by subject matter experts. Plus our outputs and intentions have been widely publicised across the transport and mobility industry
- There is a transparent and published feedback and modification process
This is there to ensure the future ongoing quality and amendments to the standards.
If you would like to suggest further changes or enhancements of either, initially email email@example.com.