The following example illustrates the importance of a common language for key terminologies:
A network of European railway companies aims to create a seamless mobility data space enabling users to book trips across Europe in one transaction, such as from Berlin to Lisbon. However, achieving this requires a unified understanding of key terms, like "billing information". Player A defines it classically as account details, such as IBAN and Direct Debit mandates. Player B does not consider any such information relevant, as it requires pre-payments. Player C takes a progressive approach and does not allow for account details or direct debit, allowing only for modern payment platforms or credit cards.
Problem: Divergent understandings lead to data-sharing inefficiencies and/or legal ambiguities. In this scenario, different definitions of billing information result in more complex transactions, which undermine the goal of creating a unified data space while they inherently involve varying levels of additional effort for users.
Solution: Develop a Common GDPR Glossary standardizing key terms and definitions.
Benefits:
- Clear Definitions: Ensure both parties have a consistent understanding of "billing information".
- Improved Compliance: Align interpretations with GDPR standards.
- Enhanced Communication: Minimize misunderstandings and streamline collaboration.
- Efficient Processes: Establish robust procedures with complete and accurate data.
Visit SRIW’s website for more information on the group’s approach and participation opportunities. If we’ve sparked your interest, we'd love for you to join us!
