Transfer Legs and local transport

[ralfbayer-db]

How would local transport with separate ticket (purchaseable locally) be modelled?

(e.g. Metro in Paris - Leg 1: Frankfurt-Paris, Leg 2: Metro from Gare de l'Est to Gare Montparnasse, Leg 3: Paris-Rennes)

(Note: when we send a Transfer Leg as part of the journey, we don't get an offer from Sqills S3)

I remember we previously had a flag somewhere in the offer response which said "ticket only available locally".

[ralfbayer-db]

It seems, Sqills is not expecting transferLegs. If a transferLeg is part of a tripSpecification, no offers are returned.
One the hand, it is clear that a transfer is not priced. On the other hand, it is part of a trip.
That's why we have the following question:
How should we handle transferLegs in the tripSpecification for a offer request?
Should we include them, or not?

[ralfbayer-db]

Add to LegAttribute structure documentation that the attributes are actually the "Service Attributes" from the Catalog of Code Lists. --> Ralf to provide patch. The Metro case would have the attribute "BOOKING_ON_LOCAL_STATION_ONLY".

So, in some cases this is part of the trip information.

On the other hand, in some instances it depends on who makes the offer, so one distributor may return an offer for all legs, where another distributor may return an offer for legs 1 and 3 (where 2 is the Metro leg).