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.

Sign up for GitHub

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

Jump to bottom

valid Respones, fix Order (PARENT) #209

Open
TO-mdv opened this issue Jan 20, 2025 · 1 comment
Open

valid Respones, fix Order (PARENT) #209

TO-mdv opened this issue Jan 20, 2025 · 1 comment

Comments

@TO-mdv
Copy link

TO-mdv commented Jan 20, 2025

Making sure, Serivce Deliveries are valid. Also check for correct order of the elements.
@TO-mdv TO-mdv moved this to Development in OJP 2.0 Backend Issues Jan 20, 2025
@TO-mdv TO-mdv changed the title Response valid - Orders valid Respones, fix Order (PARENT) Jan 20, 2025
@TO-mdv TO-mdv moved this from Development to Ready for Testing in OJP 2.0 Backend Issues Feb 10, 2025
@TO-mdv TO-mdv added decision-needed Needs to be addressed in the bi-weekly and removed decision-needed Needs to be addressed in the bi-weekly labels Feb 11, 2025
@TO-mdv TO-mdv moved this from Ready for Testing to Release Candidate in OJP 2.0 Backend Issues Feb 13, 2025
@TO-mdv
Copy link
Author

TO-mdv commented Feb 13, 2025 •
edited
Loading

@r3to Könnt ihr prüfen, ob die Änderung an der Sortierung der Element (nun XSD konform) bei euch zu Problemen führt?
Ausserdem wurde in der TripResponse das Element </ConventionalModeOfOperation> entfernt, da dieses keinen Mehrwert bringt (ist optional und hatte bisland immer den Wert scheduled).

Die Version ist nun auf INT für euch zum Testen verfügbar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
OJP 2.0 Backend Issues
Status: Release Candidate
Milestone
No milestone
Development

No branches or pull requests
1 participant
@TO-mdv