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.

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

SIRI Lite ET/SX response entry possibility for XML or JSON #6412

Open
Jouca opened this issue Jan 29, 2025 · 1 comment
Open

SIRI Lite ET/SX response entry possibility for XML or JSON #6412

Jouca opened this issue Jan 29, 2025 · 1 comment

Comments

@Jouca
Copy link

Jouca commented Jan 29, 2025

Is your feature request related to a problem? Please describe.
Currently, SIRI lite ET/SX is taking an XML, however based on the documentation of OTP said on chapter XML - JSON conversion rules for SIRI responses, it's possible to have a case that JSON could be taken.

Goal / high level use-case
As a developer using OTP and using a SIRI ET/SX Lite feed from an operator, it would be useful to have a way to select a XML or a JSON response type on the router.

Describe the solution you'd like
A solution that could be done is to use a new field adapter that we could select between json and xml the response type for SIRI ET/SX Lite data.

@Jouca Jouca changed the title SIRI Lite ET/SX response possibility for XML or JSON SIRI Lite ET/SX response entry possibility for XML or JSON Jan 29, 2025
@t2gran
Copy link
Member

t2gran commented Jan 30, 2025

We discussed this in a developer meeting today. In general we do not think it is a good idea, because we cannot see any big benefits for providing support for JSON. None of the "core" developers on OTP wanted this, but you may implement it as long as you also maintain it. I am not sure how much extra code it would be to do it. If possible this should be put in a OTP Sandbox.

Points mentioned:

  • More difficult to validate the data against the schema (not sure if a JSON schema exist for this). And the mapping from XML/XSD to JSON/JSON Schema can be tricky.
  • Higher maintenance cost
  • Increased complexity - our primary implementation target XML, and the JSON support is secondary

Feel free to elaborate on why you need it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants