NeTEx can support multiple use cases. Here we talk about the Swiss timetable delivery.

The following diagram shows the relevant core classes we will use. In the center is the ServiceJourney.

graph TD
  subgraph TimetableFrame["TimetableFrame"]
    SJ[ServiceJourney]
    DT[DirectionType]
  end

  subgraph ServiceCalendarFrame["ServiceCalendarFrame"]
    AC[AvailabilityCondition]
    UOP[ValidDayBits]
  end

  subgraph ServiceFrame["ServiceFrame"]
    L[Line]
    O[Operator]
    SSP[ScheduledStopPoint]
    PSA[PassengerStopAssignment]
    TL[TimingLink]
    SJP[ServiceJourneyPattern]
    TDT[TimeDemandType]
    SPtJP[StopPointInJourneyPattern]
  end

  subgraph SiteFrame["SiteFrame"]
    SP[StopPlace]
    Q[Quay]
  end

  subgraph OtherStuff["Other stuff"]
    CN[DefaultConnection]
    SI[ServiceJourneyInterchange]
    JP[JourneyPart]
    N[Notice]
    AN[AlternativeName]
    F[ServiceFacilities]
     SJI[ServiceJourneyInterchange]
   
  end

  %% ---------------------
  %% Visible semantic relationships
  SJ --> AC
  SJ --> DT
  SJ --> L
  SJ --> O
  SJ --> SJP
  SJ --> TDT

  TDT --> TL
  TDT --> SSP
  TDT --> SPtJP

  SJP --> L
  SJP --> SPtJP
  SPtJP --> SSP

  PSA ---> SP
  PSA ---> Q
  PSA ---> SSP

  SP ---> Q

  AC --> UOP


  %% ---------------------
  %% Layout hints to force rows and columns (dashed edges used only as hints)

  %% ---------------------
  %% Highlight central nodes in green
  style SJ fill:#e6f9e6,stroke:#2ea44f,stroke-width:2px
  style SJP fill:#e6f9e6,stroke:#2ea44f,stroke-width:2px
  style TDT fill:#e6f9e6,stroke:#2ea44f,stroke-width:2px
  style PSA fill:#e6f9e6,stroke:#2ea44f,stroke-width:2px

  %% Subgraph box styling (may be renderer-dependent)
  style TimetableFrame stroke:#999,stroke-width:1px,fill:none
  style ServiceCalendarFrame stroke:#999,stroke-width:1px,fill:none
  style ServiceFrame stroke:#999,stroke-width:1px,fill:none
  style SiteFrame stroke:#999,stroke-width:1px,fill:none
  style OtherStuff stroke:#999,stroke-width:1px,fill:none

Notes:

  • Every ServiceJourney belongs to one Line and has one Operator. Some more information can be stored in associated ResponsibilitySets (difference between operator and legal “owner”).
  • The pattern of the stops is defined in a ServiceJourneyPattern with additional details about each stop.
  • The timing behaviour is stored in TimeDemandType. They contain run times and where needed wait times. The relevant TimingLinks are mostly based on ScheduledStopPoints and not individual to each ServiceJourneyPattern.
  • The physical stops are modeled as StopPlacee with Quays.
  • ScheduledStopPoints are the “logical” stops.
  • The PassengerStopAssignment associates the physical and the logical stops.
  • DefaultConnection and SiteConnection define transfers based on site elements.
  • ServiceJourneyMeetings are used for splitting and joining of trains and “Durchbindungen”.
  • Notice, ServiceFacility and SiteFacility model almost everything else (especially offers).
  • The operating days are defined through ValidDayBits for the whole timetable year in AvailabilityConditions.