`driverJourney` and `passengerJourney` vocabulary & difference `Journey` vs `Trip`

[pierrecamilleri]

I find the names driverJourney and passengerJourney somewhat confusing, and I would like your input before proposing a PR.

Especially, when we look at a DriverJourney object (or more specifically its DriverTrip component), we see attributes like departureToPickupWalkingDistance, which is especially confusing as at first we expect informations about a driver and not a walker given the name.

I suggest searching for better names. The best I could come up with is:

• DriverJourney -> JourneyAsPassenger
• PassengerJourney -> JourneyWithPassenger

EDIT: I also wonder why \driver_regular_trips endpoint is not called \driver_regular_journeys. (Especially as *Journey = *Trip + JourneySchedule, I would expect *RegularJourney = *Trip + Schedules).
Is there a rationale behind the change in vocabulary? Maybe because regular trips are more likely to be round trips than single journeys? or is it common business vocabulary?

2nd EDIT: By writing the spec, I realize that considering that a regular trip can be composed of individual Journeys is pretty useful, so I think I've got it.

[riclage]

DriverJourney means a journey being done by a driver, which a passenger can send a request to, right? That's at least my current understanding of it. See, for example, https://github.com/fabmob/standard-covoiturage/pull/2/files#r832597019

I'm not sure changing it to JourneyAsPassenger disambiguates it. It now makes me think of a journey I'm doing as a passenger, i.e., to me it feels like we are changing the meaning of the term.

I don't remember, though, why we need to qualify the journey. Since a journey will always have a driver and at least one passenger, could we maybe just use the term journey instead?