The property `id` is reserved for global object identification with field stability requiring us to use something else for our UUIDs

[simon-wacker]

I decided to go for the naming convention type name followed by Id in camel case as property and also as query parameter name. This does not work though when there is an interface like Data that specifies the property dataId because the type OpticalData implementing this interface has the property dataId instead of opticalDataId. An alternative name would be _id or uuid or whatever. There once was RFC 232 which was rejected because there was no consensus which proposed __id; that is not an option anymore because using two underscores for user-defined properties is forbidden in the latest GraphQL draft.