How can we present the `geographicalValidity`/`zonalValidity` for an `offer` in an `OfferCollection`?

[jorgenosberg]

When an offer is generated for a single ticket or another product without explicit legs, the client might need to know exactly where that offer is valid or other conditions for the offer. Currently, this is only possible to provide in the summary field for a given offer, but it's not explicitly available in the spec.

Should this be a more explicit field visible to spec consumers?

[edwinvandenbelt]

Hmmm. In the first attempt, there was a "geometry" field (geojson-compatibility) in the offer.... There was some resistance to include it.

[joachse]

This is a tough issue to address in an elegant way I think.

Products in Netex are scoped with a ruleset (GENERIC PARAMETER ASSIGNMENT and SPECIFIC PARAMETER ASSIGNMENT) switch resembles an advanced WHERE-clause from SQL.

Examples could be
authority == Company AND mode == METRO AND fareZone in (A, B, C)
(authority == CompanyA OR authority == CompanyB) AND fareZone (A)

I think we either should use a textual description for customers or an more accurate way so that clients can evaluate the validity against journey/fara data on their own.