Paul Wille's research while affiliated with Technische Universität Berlin and other places

... Later studies, for instance as in [29], provide an overview and compare the different languages available. Of particular practical relevance are policy languages and accompanying developer toolkits, such as LPL (Layered Privacy Language) [11], TIRA (Transparency in RESTful Architectures) [17], and TILT (Transparency Information Language and Toolkit) [16], that can capture transparency information from modern, constantly evolving, and inherently complex distributed systems [14]. Moreover, consent or preference languages, such as YaPPL (YaPPL is a Privacy Preference Language) [42], GPC (Global Privacy Control ) 4 , and ADPC (Advanced Data Protection Control ) [25], or controversially discussed industry-driven consent management platforms (e.g., IAB Europe Transparency and Consent Framework) [22] are complementary to these, albeit with a different focus on providing legitimacy for processing instead of transparency as the main goal. ...

... When used in proper combination, they may, depending on the type of data, the context, and the party receiving the data, even allow to render data non-personal from the regulatory perspective. At the same time, the practical application of these techniques in real-world Web APIs is -like for other privacy / data protection principles and technologies [12,18] -hindered by a lack of easily adoptable technical solutions that smoothly integrate into established technology stacks and development practices [13]. ...