The following four attributes are defined as mandatory for bookings:
from Place{...}
to Place{...}
startTime Timeinteger($int32)
endTime Timeinteger($int32)
Having these four attributes mandatory limits the mobility services that can be booked via the API.
E.g. free floating bike will not have an "to" and "endTime" at the time of booking.
Other example are public transport tickets such as day tickets. From and to does not exist. I suggest lowering the constraints on the attributes.
It should be the intention of the MaaS API to broadly applicable for all kind of services.
The following four attributes are defined as mandatory for bookings:
from Place{...} to Place{...} startTime Timeinteger($int32) endTime Timeinteger($int32)
Having these four attributes mandatory limits the mobility services that can be booked via the API.
E.g. free floating bike will not have an "to" and "endTime" at the time of booking. Other example are public transport tickets such as day tickets. From and to does not exist. I suggest lowering the constraints on the attributes.
It should be the intention of the MaaS API to broadly applicable for all kind of services.