Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Prez kde itinerary_meetup_open_transport_paris_221118


Published on

KDE Itinerary - A privacy by design travel assistant
Volker Krause (KDE)
Getting your itinerary presented in a unified, well structured and always up to date fashion rather than as advertisement overloaded HTML email monstrosities or countless vendor-specific apps has been established by services like TripIt, and with the integration of this into the Google platform it has become part of the de-facto standard feature set for digital assistants. While very useful and convenient, it comes at a heavy privacy cost, a price not everyone is willing to pay. But is it possible to to build a free and privacy-respecting alternative for this? The KDE community has been exploring this question in the past couple of months, resulting in a number of building blocks and the "KDE Itinerary" application. We will look at what has been built, and how, and what's still missing. More information on this subject: blog series: KDE Akademy 2018 presentation (slides and video recording):

Published in: Travel
  • Be the first to comment

  • Be the first to like this

Prez kde itinerary_meetup_open_transport_paris_221118

  1. 1. @VolkerKrause Volker Krause KDE Itinerary A privacy by design travel assistant Paris Open Transport Meetup, 22 November 2018
  2. 2. Digital Travel Assistants ● TripIt, Google, Apple, etc. – Extract booking information from email – Show unified itinerary – Calendar integration – Monitor for delays/changes ● Price: “free” (ie.: your privacy)
  3. 3. Can we do better? ● Privacy by design ● Free software, open data ● Budget: a bit of spare time
  4. 4. What would we need? ● This is more about data than code ● Personal data – Booking emails ● Static data – Where is airport “CDG”? ● Dynamic data – Is flight EZY5673 on time?
  5. 5. Booking Data ● De-facto standard data model: ● Email – Structured data (JSON-LD, Microdata) – Unstructured data (text, HTML, PDF) ● Apple Wallet passes ● Barcodes (IATA BCBP, UIC 918.3, etc)
  6. 6. Static Data ● Freely available, comprehensive collections – Wikidata (almost everything imaginable) – OpenStreetMap (timezone maps) – Unicode CLDR (localized country/region information) ● Problematic – Terminal maps, coach/platform maps, seat maps
  7. 7. Dynamic Data ● No free data sources ● Few de-facto standard formats/API – GTFS (backend only) – Apple Wallet (leaks user identification) ● Vendor-specific REST APIs – varying terms and conditions – API keys required
  8. 8. So much for the theory...
  9. 9. Data Extraction ● KItinerary library – C++/Qt – data model – Structured data extraction – Unstructured data extraction – Augmentation with Wikidata knowledge – Consumes HTML, MIME, PDF, iCal, text, pkpass
  10. 10. KMail ● Data extraction plug-in and calendar integration
  11. 11. KDE Itinerary App ● Trip timeline and boarding pass access
  12. 12. Conclusion ● It’s possible! ● It’s necessary: a lot of personal data involved ● Forget those privacy concerns for a minute, we need test data ;-) – Flights, trains, rental cars, hotels, buses, event tickets, restaurants, etc. ● More integration needed
  13. 13. Thank you! Questions?
  14. 14. References ● Project overview: ● Source code – kpkpass: – kitinerary: – KDE Itinerary: – KMail plug-in: ● Blogs – Motivation: – Overview: – Data extraction: ● Provider support: ● Nightly APKs: