You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 3, 2026. It is now read-only.
How do we present (as in EPIP) specific additions (rule, constraint, etc.) for the profile. versus elements that should not be used versus elements used in some use cases and not in others?
Navigation of references as in EPIP, example:
The TARIFF ZONE to members SCHEDULED STOP POINT relation is navigable in both directions, so in NeTEx the references that implement may be held by the elements on either or both ends (i.e. on TariffZone or ScheduledStopPoint).
In EPIP the reference should only be on the ScheduledStopPoint.
GroupOfTariffZones is at this time only available in SiteFrame, missing in FareFrame, and there is no GroupOfFareZones
e.g purposeOfGrouping should be concrete types in the profile
Which Frames can be used for exchanging FareZones
How do we present (as in EPIP) specific additions (rule, constraint, etc.) for the profile. versus elements that should not be used versus elements used in some use cases and not in others?
Navigation of references as in EPIP, example:
The TARIFF ZONE to members SCHEDULED STOP POINT relation is navigable in both directions, so in NeTEx the references that implement may be held by the elements on either or both ends (i.e. on TariffZone or ScheduledStopPoint).
In EPIP the reference should only be on the ScheduledStopPoint.
GroupOfTariffZones is at this time only available in SiteFrame, missing in FareFrame, and there is no GroupOfFareZones
e.g purposeOfGrouping should be concrete types in the profile