This links a tio:ScopeOfAccess node to one or more gr:OpeningHoursSpecifications that indicate the times of access.
Note: The times of access for a particular ticket may be more constrained than the opening hours of the location, event, or transportation service. Use tio:openingHours for specifying the overall opening hours or hours of operation.
eligibleTimes (0..*)
A special form of electronic ticket delivery, mainly for flight tickets
Etix (gr:DeliveryMethod)
The eligible duration of uninterrupted attendance or access.
Typical unit code(s): HUR for hours, DAY for days, WEE for weeks, MON for months, ANN for years
durationOfAccess (0..1)
This indicates the location, time of arrival, and time of departure for an intermediate stop.
Note: When the object of the statement is a tio:Stop, one can indicate the exact date and time for a single connection.
If such a level of detail is not needed, you can directly link to a point of interest, e.g. an instance of tio:POI.
via (0..*)
This links a tio:ScopeOfAccess node to the tio:DiscountType for which the specified access is granted.
eligibleAudience (0..*)
TIO: The TIckets Ontology
A vocabulary for describing tickets for events, transportation, or points of interest for e-commerce.
Vocabulary: http://purl.org/tio/ns#
Namespace: http://purl.org/tio/ns#
The Tickets Ontology is designed to be used in combination with GoodRelations, a standard vocabulary for the commercial aspects of offers of tickets.
See http://purl.org/goodrelations/ for more information.
V 1.0, Release 2010-11-17
Some class and property definitions are inspired by or based on abstracts from Wikipedia, the free encyclopedia.
Martin Hepp
TIO: The TIckets Ontology for Semantic Web-based E-Commerce
The Tickets Ontology is available under the Creative Commons Attribution 3.0 Unported license; see http://creativecommons.org/licenses/by/3.0/.
In a nutshell, you are free to copy, distribute and transmit the work; to remix/adapt the work (e.g. to import the ontology and create specializations of its elements),
as long as you attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work).
E-Commerce, E-Business, GoodRelations, Ontology, Tickets, Transportation, Events, Concerts, Museums
Tickets Ontology
This indicates the location of a tio:Stop.
at (1..1)
The date and time for which the event is scheduled to end
Note: You can attach the time and date of the event using tio:starts and tio:ends as simple datatype properties,
even if lode:Event and event:Event recommend other, more sophisticated ways of modeling the temporal aspects of events.
ends (0..1)
A regular or individual service to transport passengers or cargo from one location to another location by means of an aircraft
Note: By design, the Tickets Ontology does not provide mechanisms for modeling rules for recurring patterns of transportation services (e.g. every Monday at 8:00). Instead, it expects that you materialize each individual connection on a given day.
Most flight schedule applications are complex databases, so they will have to be exposed as SPARQL endpoints anyway.
Flight
A point or area of interest, e.g. a museum, a train station, an airport, a bus stop, a store, a box office, etc.
Note 1: Use existing vocabularies like vcard or geo to attach address and geoposition (lat/long) details to the location.
Note 2: You can safely re-use any existing location, area, or point of interest from other data sources, e.g. DBPedia.
POI (gr:LocationOfSalesOrServiceProvisioning)
The initial, final, or any intermediate point in time and space of a particular tio:TransportationService,
characterized by its location (tio:at), arrival time (tio:arrives), and departure time (tio:departs).
Each tio:TransportationService has at least one tio:Stop for the point and time of departure and another one for the final destination.
Stop
This property specifies the ending of the validity of the access or right that the ticket grants.
It can be attached to the tio:Ticket (if meant for the ticket as a whole) and to individual tio:ScopeOfAccess entities (if meant for just a particular part of the access rights).
A time-zone should be specified. For a time in GMT/UTC, simply add a "Z" following the time:
2010-11-15T09:30:10Z.
Alternatively, you can specify an offset from the UTC time by adding a positive or negative time following the time:
2010-11-15T09:30:10-09:00
or
2010-11-15T09:30:10+09:00.
validThrough (0..1)
The date and time at which the transportation service will arrive at the respective tio:Stop
arrives (0..1)
A regular or individual service to transport passengers or cargo from one location to another location by means of a train, subway, or other railroad vehicle
Note: By design, the Tickets Ontology does not provide mechanisms for modeling rules for recurring patterns of transportation services (e.g. every Monday at 8:00). Instead, it expects that you materialize each individual connection on a given day.
Most train schedule applications are complex databases, so they will have to be exposed as SPARQL endpoints anyway.
TrainService
This is a conceptual entity that collates all properties defining the type of access a ticket provides to a particular event, location, or transportation.
ScopeOfAccess
This links a tio:Ticket to the tio:ScopeOfAccess node or nodes that are included in the ticket.
Note: For simple scenarios, you can also directly use tio:accessTo.
scope (0..*)
The flight number (or numbers, in case of codeshare flights)
flightNo (0..*)
This indicates the service level(s) or fare class(es) to which the tio:Ticket entitles.
eligibleServiceLevel (0..*)
This indicates that a particular area includes another area or points of interest.
Note: Modeling geo-spatial relationships is non-trivial. This property is a very simple approach, sufficient for e.g. grouping all train stations in a particular fare area.
includes (0..*)
First class as a service level / fare class for transportation by aircraft
Note: The exact character of a particular fare class may vary by carrier or country.
You can create individual instances of tio:ServiceLevel for a particular fare class for a particular airline.
FirstClass (tio:ServiceLevel)
This indicates the seat or seat category.
seat (0..*)
Business class as a service level / fare class for transportation by aircraft
Note: The exact character of a particular fare class may vary by carrier or country.
You can create individual instances of tio:ServiceLevel for a particular fare class for a particular airline.
BusinessClass (tio:ServiceLevel)
A ticket is a tradeable right to access a particular event or location, or to use a particular transportation service.
Ticket (gr:ProductOrService)
An event, e.g. a concert, a show, etc. You can also safely use the following external classes for describing the respective event:
http://linkedevents.org/ontology/Event (lode:Event)
http://purl.org/NET/c4dm/event.owl#Event (event:Event)
http://www.loa-cnr.it/ontologies/DUL.owl#Event (dul:Event)
Note: You can attach the time and date of the event using tio:starts and tio:ends as simple datatype properties, even if lode:Event and event:Event recommend other, more sophisticated ways of modeling the temporal aspects of events.
Event
A unique identifier for a particular ticket or ticket type.
ticketID (0..1)
This indicates the location or locations of a tio:Event.
takesPlaceAt (0..*)
The date and time for which the event is scheduled to begin
Note: You can attach the time and date of the event using tio:starts and tio:ends as simple datatype properties,
even if lode:Event and event:Event recommend other, more sophisticated ways of modeling the temporal aspects of events.
starts (0..1)
A ticket placeholder is a dummy for multiple tickets that are themselves not exposed as data.
TicketPlaceholder (gr:ProductOrService)
This indicates the business entity that actually operates the vessel used for a transportation service.
operatedBy (0..1)
This indicates the available seating layouts for a tio:POI.
availableLayouts (0..*)
The class of qualitative values indicating a service level oder fare class (e.g. Business Class).
ServiceLevel (gr:QualitativeValue)
The total number of tickets of this category that will be issued for the event
total (0..1)
This indicates the destination and time of arrival.
Note: When the object of the statement is a tio:Stop, one can indicate the exact date and time for a single connection.
If such a level of detail is not needed, you can directly link to a point of interest, e.g. an instance of tio:POI.
to (1..1)
This indicates the service level(s) or fare class(es) available for the particular tio:TransportationService.
availableServiceLevel (0..*)
An actual ticket is single, identifiable right to access a particular event, location, or transportation service.
ActualTicket (gr:ProductOrService)
The class of qualitative values indicating a seat position (e.g. the seat 4B in a given plane) or a seat category (e.g. window seat).
Note that the same vessel or building may have multiple seating layouts.
SeatOrSeatCategory (gr:QualitativeValue)
A regular or individual service to transport passengers or cargo from one location to another location by means of a coach or bus.
CoachService
The number of times the respective participant(s) is/are allowed to enter the event, POI, or transportation service
Typical unit code(s): C62 for times
noOfEntrances (0..1)
This links a tio:Ticket or a tio:ScopeOfAccess node to the tio:POI, tio:Event, or tio:TransportationService for which the tio:Ticket grants access.
Note: When used to link a tio:Ticket directly to a tio:POI, tio:Event, or tio:TransportationService, you cannot specify the various details of a tio:ScopeOfAccess node.
accessTo (0..*)
A service to transport passengers or cargo from one location to another location, with optionally intermediate stops
Note: By design, the Tickets Ontology does not provide mechanisms for modeling rules for recurring patterns of transportation services (e.g. every Monday at 8:00). Instead, it expects that you materialize each individual connection on a given day.
Most timetable applications are complex databases, so they will have to be exposed as SPARQL endpoints anyway.
TransportationService
The number of participants that are allowed to enter the event, POI, or use transportation service
Typical unit code(s): C62 for persons
participants (0..1)
A taxi service to transport passengers from one location to another location
Taxi
The class of qualitative values indicating a discount type, audience, or group type - e.g. students, military personnel, etc.
Note: Discount types that solely represent age ranges (e.g. children, senior citizens, ...) are better expressed using tio:ageRange.
DiscountType (gr:QualitativeValue)
Economy class as a service level / fare class for transportation by aircraft
Note: The exact character of a particular fare class may vary by carrier or country.
You can create individual instances of tio:ServiceLevel for a particular fare class for a particular airline.
Economy (tio:ServiceLevel)
A seating layout for a particular location, vessel, or single transportation service
SeatingLayout
The eligible age range or age ranges for admission to the revent, POI, or transportation service
Typical unit code(s): ANN for year (less frequently used: MON for months, WEE for weeks)
ageRange (0..*)
The number of tickets of this category still available at the time of publishing the data
available (0..1)
This indicates the location of origin and time of departure.
Note: When the object of the statement is a tio:Stop, one can indicate the exact date and time for a single connection.
If such a level of detail is not needed, you can directly link to a point of interest, e.g. an instance of tio:POI.
from (1..1)
This indicates the opening hours for a point of interest.
Note: The opening hours of the location and the time-windows for which a particular ticket is eligible may differ. Use tio:eligibleTimes for the latter.
openingHours (0..*)
This property specifies the beginning of the validity of the access or right that the ticket grants.
It can be attached to the tio:Ticket (if meant for the ticket as a whole) and to individual tio:ScopeOfAccess entities (if meant for just a particular part of the access rights).
A time-zone should be specified. For a time in GMT/UTC, simply add a "Z" following the time:
2010-11-15T09:30:10Z.
Alternatively, you can specify an offset from the UTC time by adding a positive or negative time following the time:
2010-11-15T09:30:10-09:00
or
2010-11-15T09:30:10+09:00.
validFrom (0..1)
The date and time at which the transportation service will depart from the respective tio:Stop
departs (0..1)
This indicates the individual seats for a given seating layout.
availableSeats (0..*)
The number of tickets of this category already sold at the time of publishing the data
sold (0..1)