-
Notifications
You must be signed in to change notification settings - Fork 12
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
Switches for accessibility information #291
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is OK.
What I miss in this pull request is the actual 'result structure' for example I want to know what happens if the realtime status would not be available. |
@skinkie To answer your question as I understand it: IncludeAccessFeatureStatus (in this PR) is used to request or not real time information about access features. As for the result, see PR #238 - there is AccessFeatureStatus (and AccessFeatureStatusText and SituationFullRef) to provide the real time status. If some data is not available, this can be signalled using AccessFeatureWithUnknownAvailability. Additionally, there is the problem code TRIP_REALTIMEINCOMPLETE that could be used, It should probably also be used by TripRefineRequest, shouldn't it? |
0f6cda8
to
0e21b03
Compare
# Conflicts: # docs/generated/index.html
# Conflicts: # docs/generated/index.html
From the meeting: adding the ability (OJP_TripRequest) to specify the accessibility-related information to return as it may differ depending on the user profile and on what data will be used and presented.