Changes to endpoints PUT and GET for ticket active status
Description
Attachments
3
- 30 Sep 2020, 12:15 PM
- 09 Apr 2020, 10:43 AM
- 09 Apr 2020, 10:43 AM
Activity
Show:
Former user December 9, 2020 at 3:03 PM
Merged to the BoB-standard 2020-12-09
Close
Former user November 13, 2020 at 10:12 AM
Approved at CAB 2020-11-10
Former user October 1, 2020 at 2:54 PM
Fixed
Details
Details
Assignee
Unassigned
UnassignedReporter
Former user
Former user(Deactivated)Versioning
Patch
Change risk
Medium
Priority
Who's Looking?
Open Who's Looking?
Created April 6, 2020 at 1:50 PM
Updated December 9, 2020 at 3:03 PM
Resolved November 12, 2020 at 6:27 AM
Who's Looking?
Background
During the work within the VSB-project and implementation of OpenBoB, Samtrafiken is analyzing the BoB-specifications to both understand what to implement but also for the management of the standard to seek consistency, improvements and clarity.
Problem
The endpoints mention active and active status for ticket but refers to freeze and thaw as concepts for deactivation or activation of a ticket?
In GET-method it refers to ticket is active when ticketActiveStatus is true but mentions freeze and thaw in the PUT-method.
The response code 200 has a description “Successful operation, ticket is now inactive” but that statement is not true if ticketActiveStatus = true is sent in the request.
Need
Consequent endpoint definition and a clear description of why and when to use it.
Motivation
Clear and unambiguous descriptions of endpoints and parameters.
Relevant response code descriptions.
Suggestion
See Pull request for the specific changes.
Changes
Change freeze and thaw to deactivate and activate in descriptions
Update descriptions to fit changes