Submitted by: Peter Bruhn Andersen --------------------------------- Bio I’m a long time Semantic Web / Linked Data proponent (since 2002) now working within the Agency for Digitisation [1] in the Division for Data and Architecture. The agency is in the process of creating a new and better foundation for interoperability between Danish public organizations. One of the strategies we are pursuing is to create a Linked Data environment between it-systems in the public organization. The LD-environment should be able to handle very sensitive data as well as open publicly accessible data. One of the projects in the process is to create a registry for basic data. This Base Registry [2] has the potential to be core in the LD-environment. To proceed with a Linked Data version of the Base Registry we need a solution that can ensure that sensitive data is not exposed in a LD-environment. Name: Peter Bruhn Andersen Mobile: pea@digst.dk Phone: +45 2246 6086 Twitter: @BruhnAndersen LinkedIn: https://www.linkedin.com/in/peter-bruhn-andersen-a9b9b72/ [1] https://en.digst.dk/about-us/ [2] https://en.digst.dk/data-and-it-architecture/basic-data/ --------------------------------- Your goals Our primary goal is to find solutions that makes it possible to use Linked Data between government organizations in a way that provides a dynamic, flexible and automatic data sharing environment and at the same time insures that sensitive data on citizens and businesses is protected. We also would like to use this opportunity to get in contact with other parties who has challenges similar to ours regarding Linked Data security. --------------------------------- Workshop Goals The workshop should focus on recommendations for handling access rights and security in a Linked Data environment with sensitive data. The workshop should be the start of a community that further explores the issues and solutions. --------------------------------- Your interests Please select the rank-order (1 to 10) for the options you think are acceptable (i.e. you can live with it), where 1 is the most preferred, 2 the next best and so on... * Vocabularies to model privacy policies, regulations, and involved (business) processes: [ Ranked 2 ] * Identity management vocabularies: [ Ranked 1 ] * Modeling personal data usage, processing, sharing, and tracking: [ Ranked 7 ] * Interlinking aspects of privacy and provenance: [ Ranked 6 ] * Modeling consent and making it transportable: [ Ranked 3 ] * New ways to put the user in control benefiting from semantic interoperability of policy information: [ Ranked 4 ] * Modeling permissions, obligations, and their scope: [ Ranked 5 ] * Reasoning about formally declared privacy policies: [ Don’t mind ] * Exploring links and synergies using Linked Data vocabularies in the context of related efforts: [ Don’t mind ] * Visualizations of data and policy information to help data self determination: [ Ranked 8 ] --------------------------------- Other Thoughts