About Me

Intro – Born and raised in northern Germany I moved to the beautiful south as soon as school was out. There in the “Tuscany of Germany” Freiburg I did my diploma in Computer Science. During that time I created K3b – the KDE CD/DVD burning application – and saw it become the de-facto standard for optical media in Linux. After receiving my diploma in 2006 Mandriva brought me into the European research project Nepomuk to establish an open-source community connection. Since 2012 I am working on the OpenLink Data Spaces project.

IT Skills – I have more than 12 years of experience in C/C++, with a focus on QT and KDE development (Nokia Certified Qt Specialist). Semantic Web/Desktop technologies such as RDF and SPARQL are my day-to-day tools. I am experienced in Java, Python, HTML, and XML and know my way around database systems such as Virtuoso, Oracle, or MySQL. I have a deep knowledge of Linux systems.

Personal Skills – Working in a team comes natural to me as I managed different developers in the open-source projects I maintain. In Google’s Summer of Code 2009, 2010, and 2011 I successfully mentored a total of seven students. I gained experience in user support through the K3b and Nepomuk projects. In 2009 I organized two Nepomuk workshops in Freiburg with participants from all over Europe. I am very enthusiastic about my work and am able to comprehend new technologies very quickly.

Personal – In my spare time I like to do sports like rock climbing and jogging. I am passionate about cinema and my 2 daughters.
Contact – Sebastian Trüg – trueg@kde.org – trueg@jabber.org -View Sebastian Trüg's profile on LinkedIn

Recent Posts

TPAC 2012 – Who Am I (On the Web)?

Last week I attended my first TPAC ever – in Lyon, France. Coming from the open-source world and such events like Fosdem or the ever brilliant Akademy I was not sure what to expect. Should I pack a suite? On arrival all my fears were blown away by an incredibly well organized event with a lot of nice people. I felt very welcome as a newbie, there was even a breakfast for the first-timers with some short presentations to get an overview of the W3C‘s work in general and the existing working groups. So before getting into any details: I would love this to become a regular thing (not sure it will though, seeing that next year the TPAC will be in China).

My main reason for going to the TPAC was identity on the Web, or short WebID. OpenLink Software is a strong supporter of the WebID identification and authentication system. Thus, it was important to be present for the meeting of the WebID community group.

The meeting with roughly 15 people spawned some interesting discussions. The most heatedly debated topic was that of splitting the WebID protocol into two parts: 1. identification and 2. authentication. The reason for this is not at all technical but more political. The WebID protocol which uses public keys embedded in RDF profiles and X.509 certificates which contain a personal profile URL has always had trouble being accepted by several working groups and people. So in order to lower the barrier for acceptance and to level the playing field the idea was to split the part which is indisputable (at least in the semantic web world) from the part that people really have a problem with (TLS).

This lead to a very simple definition of a WebID which I will repeat in my own words since it is not written in stone yet (or rather “written in spec”):

A WebID is a dereferencable URI which denotes an agent (person, organization, or software). It resolves to an RDF profile document uniquely identifying the agent.

Here “uniquely identify” simply means that the profile contains some relation of the WebID to another identifier. This identifier can be an email address (foaf:mbox), it can be a Twitter account, an OpenID, or, to restore the connection to the WebID protocol, a public key.

The nice thing about this separation of identity and authentication is that the WebID is now compatible with any of the authentication systems out there. It can be used with WebID-Auth (this is how I call the X.509 certificate + public key in agent profile system formally known as WebID), but also with OpenID or even with OAuth. Imagine a service provider like Google returning a WebID as part of the OAuth authentication result. In case of an OpenID the OpenID itself could be the WebID or another WebID would be returned after successful authentication. Then the client could dereference it to get additional information.

This is especially interesting when it comes to WebACLs. Now we could imagine defining WebACLs on WebIDs from any source. Using mutual owl:sameAs relations these WebIDs could be made to denote the same person which the authorizing service could then use to build a list of identifiers that map the one used in the ACL rule.

In any case this is a definition that should pose no problems to such working groups as the Linked Data Protocol. Even the OpenID or OAuth community should wee the benefits of identifying people via URIs. In the end the Web is a Web of URIs…

  1. And Now For Something Completely Different: Resizable Bootstrap Modals 4 Replies
  2. Digitally Sign Emails With Your X.509 Certificate in Evolution 7 Replies
  3. Use an X.509 certificate for SSH Login 3 Replies
  4. Virtuoso 6.1.6 and KDE 4.9 6 Replies
  5. Debugging Nepomuk/Virtuoso’s CPU usage 1 Reply
  6. Nepomuk Tasks: KActivityManager Crash 11 Replies
  7. Nepomuk Tasks: Let The Virtuoso Inferencing Begin 8 Replies
  8. Akonadi, Nepomuk, and A Lot Of CPU 13 Replies
  9. Nepomuk Tasks – Sponsor a Bug or Feature 60 Replies