Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TIO - The Tickets Ontology #16

Open
elf-pavlik opened this issue Jul 28, 2014 · 7 comments
Open

TIO - The Tickets Ontology #16

elf-pavlik opened this issue Jul 28, 2014 · 7 comments

Comments

@elf-pavlik
Copy link

Tickets ontology which includes various transport related concepts
http://www.heppnetz.de/ontologies/tio/ns#

Classes

  • tio:ActualTicket
  • tio:CoachService
  • tio:DiscountType
  • tio:Event
  • tio:Flight
  • tio:POI
  • tio:ScopeOfAccess
  • tio:SeatingLayout
  • tio:SeatOrSeatCategory
  • tio:ServiceLevel
  • tio:Stop
  • tio:Taxi
  • tio:Ticket
  • tio:TicketPlaceholder
  • tio:TrainService
  • tio:TransportationService
@pietercolpaert
Copy link
Member

Regarding adding links from GTFS to tio discussion:

GTFS at this moment doesn't have a class for something called a Ticket. It does however have a class for a FareClass which can be applied on certain parts of the schedule using FareRules.

@elf-pavlik
Copy link
Author

IMO a trip planing app will need a way to show which tickets one can use to take given trip

@mfhepp how do you see gtfs:FareClass and gtfs:FareRules mapping to TIO?

We could also try out 15 days on InterRail use case: http://www.interrail.eu/interrail-passes/global-pass#adult

@pietercolpaert
Copy link
Member

In fact... I was wrong before... A gtfs:FareClass could be a similar class as tio:TicketPlaceholder

@elf-pavlik
Copy link
Author

@mfhepp do you now of a way to include in a ticket features offered by particular vehicle used in the trip?

e.g.

  • power plugs (+which standard)
  • internet / wlan
  • toilet
  • sleeping beds

etc.

@mfhepp
Copy link

mfhepp commented Mar 26, 2015

I think the new schema:additionalProperty pattern will fit, for a preview see http://sdo-property-value-and-cars.appspot.com/additionalProperty

@elf-pavlik
Copy link
Author

@mfhepp I don't see need to limit ourselves to capacities of schema.org vocab. I thought that you work on some vehicle related vocabularies which may already have properties for describing such features. Ticket could reference a particular vehicle (similar to http://schema.org/IndividualProduct ) which would have all the information about power plugs, wlan etc.

@mfhepp
Copy link

mfhepp commented Mar 26, 2015

The most comprehensive, GoodRelations-compliant vocabulary for describing vehicles is the new schema.org branch for vehicles. It defines standard properties for many characteristics of cars and supersedes the VSO ontology. In combination with schema:additionalProperty, you should find everything you need. See

http://sdo-property-value-and-cars.appspot.com/Car
http://sdo-property-value-and-cars.appspot.com/additionalProperty
http://www.w3.org/wiki/WebSchemas/Vehicles (not perfectly in sync with the latest version of the extension).

Older approaches, mostly reflected in this, are

http://www.heppnetz.de/ontologies/vso/ns
http://www.volkswagen.co.uk/vocabularies/vvo/ns
http://ontologies.makolab.com/uco/ns.html

Martin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants