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: https://volkerkrause.eu/2018/08/19/kde-itinerary-introduction.html KDE Akademy 2018 presentation (slides and video recording): https://conf.kde.org/en/Akademy2018/public/events/22

1. vkrause@kde.org
@VolkerKrause
Volker Krause
KDE Itinerary
A privacy by design travel assistant
Paris Open Transport Meetup, 22 November 2018

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. Can we do better?
●
Privacy by design
●
Free software, open data
●
Budget: a bit of spare time

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. Booking Data
●
De-facto standard data model: schema.org
●
Email
– Structured data (JSON-LD, Microdata)
– Unstructured data (text, HTML, PDF)
●
Apple Wallet passes
●
Barcodes (IATA BCBP, UIC 918.3, etc)

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. 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. So much for the theory...

9. Data Extraction
●
KItinerary library
– C++/Qt
– schema.org data model
– Structured data extraction
– Unstructured data extraction
– Augmentation with Wikidata knowledge
– Consumes HTML, MIME, PDF, iCal, text, pkpass

10. KMail
●
Data extraction plug-in and calendar
integration

11. KDE Itinerary App
●
Trip timeline and boarding pass access

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. Thank you!
Questions?

14. References
●
Project overview: https://phabricator.kde.org/project/profile/280/
●
Source code
– kpkpass: https://phabricator.kde.org/source/kpkpass/
– kitinerary: https://phabricator.kde.org/source/kitinerary/
– KDE Itinerary: https://phabricator.kde.org/source/itinerary/
– KMail plug-in: https://phabricator.kde.org/source/kdepim-addons/
●
Blogs
– Motivation: https://volkerkrause.eu/2018/08/19/kde-itinerary-introduction.html
– Overview: https://volkerkrause.eu/2018/08/25/kde-itinerary-overview.html
– Data extraction: https://volkerkrause.eu/2018/09/01/kde-itinerary-data-extraction.html
●
Provider support: https://community.kde.org/KDE_PIM/KItinerary/Supported_Providers
●
Nightly APKs: https://binary-factory.kde.org/job/Itinerary_android/