Data Terminology Catalogue
BOLD Capitalised is the Term being described in a standards context.
RED is used to highlight the common language used by the public.
Inclusive period within which the SERVICE runs
As a minimum, an OperatingPeriod requires a StartDate.
For BODS where the last date of operation of the services is known (for example, because the service is terminating in the near future, there is an impending change, or because the service being described only operates for a limited period), then an EndDate shall also be provided. If the service is expected to run “until further notice” then the EndDate shall be omitted.
In TXC-PTI, the use of an EndDate in the far distant future to represent an effective “until further notice” operation shall not be permitted. An EndDate shall only describe the actual end date of a service.
Between these (inclusive) start and end dates, the default operation is described by the OperatingProfile. In standard TXC documents, this is predominantly used in one of two ways:
a) To describe the overall operation of the service, e.g. “Mondays to Sundays” for a seven-day service, even though different timetables may operate Mondays to Fridays, Saturdays, and Sundays; or
b) To describe the majority of trips e.g. “Mondays to Fridays” even though there are also trips which run on Saturdays and on Sundays.
OrganisationCode is mandated by the schema. There is a recommendation in the schema that this should be the reference number of the school, as allocated by the administrations in the devolved governments, however this is not required by TXC-PTI. Firstly, a textual code can be more meaningful (e.g. COWA = College of West Anglia), a set of dates could cover multiple organisations.