Interoperability - Universal and Open

Short URL to here:


Track page:


General Programme Team Slides:

Dimensions of interoperability

Sitra IHAN®: Human-driven data economy

Identity management in the IHAN® world

Consent in Action

Semantic Interoperability and Transparency

Standards for Delivering on the MyData Principles

Interoperability and Decentralisation: Part I

Interoperability and Decentralisation: Part II

Interoperability - Universal and Open

Making MyData as interoperable as the web itself

Our digital world is full of intentionally built walls and impenetrable wastelands of unintentional incompatibilities. We envision a future the digital person can roam without such barriers, where the cost of engagement is low, and where new innovations benefiting humanity are readily integratable with the existing ecosystems. We believe that maximising user choice and accelerating the power of market competition will bring forth a more inclusive and human-centered world where interoperable MyData is a natural part of our lives.

What are the various layers and dimensions of interoperability? We will look into the various innovations, progressions and challenges happening the scope of MyData interoperability. We hope to gain awareness of the relevant open standards and possible solutions to the big interoperability questions, like semantics of data, impact of regulations and governance of global networks.

Old text (to be removed):

We envision a future, where people have self-sovereign (not controlled by anybody else) digital identities and freedom to use their data without any constraints.

What are the minimum interoperability requirements of making different personal data solutions work together in an ecosystem? We look into challenges that the builders of these solutions are facing and solving today. We hope to gain awareness of the relevant open standards and possible solutions to the big interoperability questions, like semantics of data, impact of regulations and governance of global networks.

Contributions to this track may include:

  • Examples of personal data initiatives that have built interoperability between them. (i.e. two platforms connecting, cross-standard data porting etc.)
  • Clarifying presentations into different aspects of interoperability of personal data. What needs to be understood, when multiple systems operate with humans in the middle?
  • Interoperability efforts from other personal data related standardisation etc. communities. If your project can contribute to making the human centric personal data flow, let us know!
  • Posters on particular standards (interactive poster session). How they work towards accomplishing the goals of the MyData Declaration.

Keywords: interoperability, standards, legal, network, cross-border, data sharing, semantics, ontology

Links to external resources:

Decentralized Identity Foundation

Decentralized Identifiers (DIDs)

The New European Interoperability Framework – ISA²

W3C Data Privacy Controls and Vocabularies

NIEM | National Information Exchange Model

W3C Credentials Community Group

Dimensions of interoperability

Wednesday: Kultsa

10:45 - 12:00


Geoff Revill, Cagla Salmensuu, Petteri Kivimäki, Antti Kettunen, Joss Langford


During this first session we will introduce the interoperability track and give the big picture of different dimensions of interoperability. We will define what interoperability means for MyData and how this is supported by the interoperability sessions in the conference.

We will start off the interoperability track with some of the most important topics of MyData interoperability. We will begin with how machines handling MyData understand interoperability. Then we will dive into the legal issues to be understood in interoperability, and finish with how interoperability can work at a  national level in the X-Road architecture. 

<b>Dimensions of Interoperability</b>

Joss Langford, Coelition

An overview of the role of interoperability in the MyData ecosystem - person, data source, data using service and operator. We will highlight the key dimensions of interoperability with reference to existing models and show how these connect to the various sessions in the interoperability track for MyData 2018.

<b>The Language of Machines - from Syntax to Semantics</b>

Geoff Revill, Krowdthink Ltd

For large-scale MyData integration our approach to building software needs a fundamental rethink. We are imposing on machines our human-scale communication methods instead of seeking to enable machines to freely converse. Unleashing the power of MyData means making it meaningfully interoperable with systems that have never seen or processed it before!

<b>Interoperability: what needs to be understood from the legal side</b>

Cagla Salmensuu, Tieto

The presentation will look at the regulatory landscape against which the MyData vision for interoperability is going to work. There are a number of instruments at the EU level which need to be known and understood in the field of interoperability for a meaningful implementation: the revised Directive on the reuse of Public Sector Information, the INSPIRE Directive, and the eIDAS Regulation as well as the new EU initiatives, such as the European Cloud Initiative, the EU eGovernment Action Plan 2016-2020; and the envisaged ones, such as the Single Digital Gateway Regulation.

<b>X-Road as a platform to exchange MyData</b>

Petteri Kivimäki, Nordic Institute for Interoperability Solutions (NIIS)

X-Road is an open source data exchange layer solution used by the national governments in Estonia and Finland. This presentation explains a concept how the X-Road could be used technically as a platform to exchange MyData. In addition to the technology, I’m also going to discuss the common principles and guidelines required by the concept.

Session is moderated by: Antti Kettunen

Start        :                        10:45

Opening:                        10:45 (2 minutes, Antti Kettunen)                 

Presenter 1:                        10:47 (8 minutes, Joss Langford)

Intro of presenter 2:                10:55 (1 minute, Antti Kettunen)

Presenter 2:                        10:56 Geoff Revill (15min)

Q&A for presenter 2:        11:11 (5min)

Intro of presenter 3:                11:16 (1 minute, Antti Kettunen)

Presenter 3:                        11:17 Cagla Salmensuu (15min)

Q&A for presenter 3:        11:32 (5min)

Intro of presenter 4                11:37 (1 minute, Antti Kettunen)

Presenter 4:                        11:38 Petteri Kivimäki (15min)

Q&A for presenter 4:        11:53 (5min)

Closing:                        11:58 (2 minutes, Antti Kettunen)

End:                                12:00

Sitra IHAN®: Human-driven data economy 

(changed to Business track 16.08.2018. Below info is outdated!)

Wednesday: Kultsa

12:00 - 13:15


Jaana Sinipuro, Risto Tornivaara


What is human-driven economy? Sitra's IHAN® project will create the missing building blocks for fair and functioning data economy. By creating an international protocol between end users, data providers and service providers we can enable a data ecosystem where everybody wins: service providers can start to create and capture value by providing relevant services to end users by using data from one or more data sources with the consent of the individual – giving people control over how and what their data is being used for.

This session will focus on global identity and consent mechanism. We will discuss the main questions of how the data economy will create new business opportunities and benefit also the individual.

This lunch session is moderated by Jaana Sinipuro and Risto Tornivaara

Start        :                        12:00

Opening:                        ..                 

Closing:                        13:10

End:                                13:15

Identity management in the IHAN® world

Wednesday: Kultsa

13:15 - 14:30


Antti Larsio, Juhani Luoma-Kyyny, Jyrki Suokas


<b>Identity management in the IHAN® world</b>

Sitra's IHAN® project will create the missing building blocks for fair and functioning data economy. By creating an international protocol between end users, data providers and service providers we can enable a data ecosystem where everybody wins: service providers can start to create and capture value by providing relevant services to end users by using data from one or more data sources with the consent of the individual – giving people control over how and what their data is being used for.

During the next three years we are launching and funding pilot projects in which various technologies and mechanisms are tested against IHAN requirements. Right now we are building awareness and engaging people across Europe.

Help us crack the toughest nut in the world right now - Identity management! In this workshop we will focus on these three IHAN components:

  ·     IHAN Number – What is the best mechanism to connect you with your data?

  ·     eIDAS identity management – What is the role of eIDAS in the IHAN ecosystem?

  ·     Identity wallet – You have hundreds of identities (accounts) today. How will you manage them tomorrow?

Check out the stories below and choose your favorite session.

<b>IHAN Number</b>

Antti Larsio, Sitra

The IHAN Number is an identifier to uniquely combine you and your data - globally. This all-new approach will change the way we used to handle our precious data in various services. The IHAN number is the new standard! In this workshop we will cover the mathematical and technical background and discuss how this new tool can be utilized to create bullet-proof mechanisms to protect your valuable assets.

<b>eIDAS identity management</b>

Juhani Luoma-Kyyny, Sitra

eIDAS is establishing an EU-wide legal framework for electronic signatures and a range of newly defined electronic “trust services”. In this session we will search the areas where eIDAS and IHAN will support each other and also discover the challenges that are already recognized. So if you are familiar with eIDAS implementations, come and help us!

<b>Identity Wallet</b>

Jyrki Suokas, Sitra

The challenge of managing multiple identities is a common problem, that has so far been resolved in closed environments. What if you could manage all your identities or have them managed for you - globally? If you are interested in identity management, come to this workshop either to get the latest info or to share your ground-breaking ideas to resolve known issues.

Session is moderated by: Jyrki Suokas

Start        :                        13:15

Opening:                        ..                 

Closing:                        14:25

End:                                14:30

Consent in Action

Wednesday: Kultsa

15:00 - 16:15


Alex Cash, Martin Sandren, Andrew Hughes, John Wunderlich, Joss Langford


Interoperability in the management of consent will allow safe, seamless sharing of personal data for individuals. In this session we will explore the role of consent in the GDPR, the practical implications of compliance and see standards-based approaches to consent management in action.

<b>GDPR: How to Tackle Consent and Preference Management</b>

Alex Cash, OneTrust

Consent is an active area that many organizations are currently struggling with in GDPR (and ePrivacy). Consent impacts both B2B and B2C marketing activities, as well as deeper business activities that may require consent such as automatic decision making, processing special categories of data, or cross-border data transfers. This session will help clarify why consent is so unique in GDPR, when you do (and don’t) need consent, and practical case studies of how to tackle consent, re-consent, and preference management in practice.

<b>Consent management in practise</b>

Martin Sandren, Nixu Oyj

We start by figuring out what an informed consent is and the story behind it, to the points why it is so centric and why it should be planned with care.  The practical approach brings in the Basics of implementing consent management for services and the standardization work around it. Also some of the different models available for solving the issue are handled.

<b>Replace Terms & Conditions with Information Sharing Agreements</b>

John Wunderlich, JLINC

The JLINC protocol and software enable individuals to control how information about them is used or shared. Instead of a web server offering “take it or leave it”-options the JLINC protocol enables a negotiation of terms between Data Subject and Data Controller and then vests ongoing control of the data with the Data Subject - enabling a dynamic and flexible relationship.

<b>Consent Receipt - An Interoperability Demo </b>

Andrew Hughes, Kantara Initiative

The goal of this demo is showing how using the Kantara Consent Receipt spec. provides the basis for allowing the different Company receipts to be shared between different entities. The participating companies are:, Consentua, Open Consent, Trunomi, UNLOQ, Ubisecure.

Session is moderated by: Joss Langford

Start        :                        15:00

Opening:                        15:02 (3 minutes, moderator)                 

Alex Cash:                        15:05 (10 minutes)

Questions:                        15.15 (2 minutes)

Martin Sandren:                15:17 (10 minutes)

Questions:                        15:27 (2 minutes)

John Wunderlich:                15:29 (10 minutes)

Questions:                        15:39 (2 minutes)

Andrew Hughes et al.:        15:41 (20 minutes)

Questions:                        16:01 (12 minutes)

Closing:                        16:13 (2 minutes, moderator)

End:                                16:15

Semantic Interoperability and Transparency

Thursday: Henrik

10:00 - 11:15


Axel Polleres, Christoph Fabianek, Elmar Kiesling, Joss Langford


Harmonised semantics and standardised vocabularies for personal data are essential for portability, informed consent, notice and transparency of personal data processing. In this session will we will focus on how we can integrate semantic schemes in both subject-centric approaches and at the enterprise level. We will show how academia, industry and standards bodies are working together for regulatory compliance and the wider benefits of interoperability.

<b>Privacy and Transparency Interoperability</b>

Axel Polleres & Ben Whittam Smith

We report on the recent W3C workshop in Vienna on Privacy and Transparency interoperability, standards and vocabularies as well as the current status of the use cases from the SPECIAL EU project that is building a scalable policy-aware linked data architecture for privacy.

<b>Sharing personal data through semantic containers</b>

Christoph Fabianek & Elmar Kiesling

In this talk we propose a framework to share personal data in a secure way, track and control the usage of that data, as well as allow to bill any data access. The approach uses semantic annotation to describe data and processing capabilities and uses container technology to provide easy deployability.

Session is moderated by: Joss Langford

Start        :                        10:00

Opening:                        10:02 (5 minutes, moderator)                 

Axel Polleres &

Ben Whittam Smith:        10:07 (20 minutes)

Questions:                        10.27 (5 minutes)

Christoph Fabianek                10:32 (20 minutes)

& Elmar Kiesling

Questions:                        10:52 (5 minutes)

Open floor:                        10:57 (15 minutes)        

Closing:                        11:12 (3 minutes, moderator)

End:                                11:15

Standards for Delivering on the MyData Principles

Thursday: Arkki

10:00 - 11:15


Colin Wallis, Drummon Reed, Kai Kuikkaniemi


Delivering on the MyData principles
Colin Wallis, Kantara

This presentation takes each of the MyData 6 Principles and gives examples of Kantara's work supporting those - from the specifications that the Kantara community curates through member implementations of those specifications to Trust Mark evidenced conformity via Kantara's Trust Framework and Assurance programme.

Delivering on the MyData principles
Drummond Reed, Evernym and Sovrin Foundation

Drummond will give an update on how we are making rapid progress on four emerging open standards for self-sovereign identity (SSI): DID (Decentralized Identifiers), DKMS (Decentralized Key Management System), DID Auth (how you authenticate using DIDs), and Verifiable Credentials (interoperable digital credentials), and how together these open standards are laying an SSI foundation for MyData.

Session is moderated by: Kai Kuikkaniemi

During your session calls, please talk also about the practical needs, and fill in if needed!

Start        :                        10:00

Opening:                        10:02 (5 minutes, moderator)                 

Intro of presenter 1:                10:07 (3 minutes, moderator)

Presenter 1:                        10:10 (XX minutes)

Q&A for presenter 1:                10:30 (X minutes)

Intro of presenter 2:                10:37

Presenter 2:                        10:40

Q&A for presenter 2:        11:00

Join Q&A                        11:07

Closing:                        (3 minutes, moderator)

End:                                11:15

Interoperability and Decentralisation: Part I

Friday: Studio

10:45 - 12:00


Kimberly Hamilton Duffy, Benjamin Goering, Markus Sabadello


We give an overview of existing interoperability-focused standards and protocols useful to the MyData audience, covering their history, the classic centralized and federated approaches, and the new set of decentralized and self-sovereign ones. We’ll talk about where each approach is appropriate, how the various standards can interact, and what possible upgrade paths could be.

Categories of technologies include: Identity (e.g. DIDs) and Verifiable Credentials, Authentication (e.g. DID-Auth), Access Control, Aggregation and Federation (e.g. the new W3C ActivityPub and ActivityStreams2 specs), and Personal Data Store APIs (e.g. Solid).

<b>Decentralized Identifiers, DID methods, and BTCR Method Specification demo</b>

Kimberly Hamilton Duffy

<b>ActivityPub: a W3C Technical Recommendation for Federated Social Networking</b>
Benjamin Goering

In January of 2018, the World Wide Web Consortium Social Web Working Group published the final versions of two standards: (1) ActivityStreams vocabulary for describing social data and activities on the web and (2) ActivityPub protocol for federated social networking. Both were quickly adopted by Mastodon, an open source TweetDeck-style web application. Come learn about how what these standards say, how they work together, and how you can implement them to break down the silos of the closed-source social networks.

Session is moderated by: Markus Sabadello

Start        :                        10:45

Opening:                        10:47 (5 minutes, moderator)                 

Intro of presenter 1:                10:50 (3 minutes, moderator)

Presenter 1:                        ..

Q&A for presenter 1:                ..

Intro of presenter 2:                ..

Presenter 2:                        ..

Q&A for presenter 2:        ..

Closing:                        11:55 (5 minutes, moderator)

End:                                12:00

Interoperability and Decentralisation: Part II

Friday: Studio

13:15 - 14:30


Adrian Gropper, Rouven Heck, Markus Sabadello


There are lots of new and exciting developments going on in the decentralized & self-sovereign world of MyData. After offering a general overview to standards and protocols in the morning Part I session, this Part II will focus on concrete projects that are already underway. We will explore examples where decentralized technologies are being used, how they help interoperability, and how they integrate with existing infrastructure.

<b>Standards for a Self-Sovereign Technology Stack</b>
Adrian Gropper

HIE of One Trustee® innovates in two aspects of personal data management: decentralized governance and a standards-based self-sovereign technology stack, using blockchain self-sovereign decentralized identifiers (DID), W3C Verifiable Credentials, and User Managed Access (UMA) authorization standards. Decentralized governance and self-sovereign tech are linked in the sense that governance groups compete for subjects that have a choice of governance group because the infrastructure is standardized. These concepts stand in contrast to first-generation personal information management that is typically not standards-based nor decentralized in governance.

<b>Self-Sovereign Identity Meets Portable Data</b>

Rouven Heck, Consensys and uPort

Blockchain based systems built on public ledgers like Ethereum enable entirely new ways for humanity to own, control and share their identity attributes, claims and any data associated with them. However, how can publicly accessible immutable ledgers be compatible with new data regulation like GDPR and the right to be forgotten? uPort is an open-source protocol that has been in development for over two years and is currently implemented in more than 10 decentralized applications (DApps), as well as in a live production use case in the City of Zug in Switzerland. With uPort, individuals can anchor their identity on a blockchain but retain all their data in a GDPR compliant way in an off-chain environment. Users and organisations can issue, sign data in a secure and interoperable way and selectively disclose it. All this happens via a mobile app. A secure, self-sovereign GDPR compliant identity at the tip of a fingertip. In our talk, we'd like to showcase the protocol's architecture and perform a life demonstration.

Session is moderated by: Markus Sabadello

Start        :                        13:15 (0 minutes)

Opening:                        13:15 (5 minutes, moderator)                 

Intro of presenter 1:                

Presenter 1:                        13:20 (10 minutes)

Q&A for presenter 1:        13:20 (5 minutes)

Intro of presenter 2:        

Presenter 2:                        13:25 (10 minutes).

Q&A for presenter 2:        14:35 (5 minutes)

Intro of presenter 3:        

Presenter 3:                        14:40 (10 minutes)

Q&A for presenter 3:        14:50 (5 minutes)

Questions:                        14:55 (15 minutes)

Closing:                        14:55 (5 minutes, moderator)

End:                                14:30

SALLA: Saving this thread randomly here ! one eIDAS presenter (TBD)



Here is a good academic paper with a different perspective and therefore levels (technical, syntactic, semantic, dynamic, conceptual)

Geoff Revill described this at the conference last year (slides & video)

European Interoperability Framework found here:

Especially I would recommend taking a look at the infographic here:

Joss’s presentation from last year (slides & video)

17.4.2018 What is the MyData definition of the interoperability?


PART 1: We look at interoperability from the perspective of the four roles defined in the MyData Declaration: persons, data sources, data using services and operators. What are the expectations and requirements towards interoperability of these roles?

Person (identity holder)

  • Able to use the service from anywhere, any country
  • Interoperability of identities
  • Common patterns to enhance usability

Data source

  • Capability to ?? → syntactic and semantic
  • Easy integration with existing systems. No need to completely overhaul their whole technology stack, legacy bindings
  • Technology neutrality, interface specifications
  • Access & control
  • Ability to “pull the plug” and stopping some access (shady activity)
  • In some cases give access to state organisations
  • → log of permissions (metadata… timestamps etc.)

Data using service

  • What is the difference of between sources and data users?
  • Burden of data storage → they may want to use, but not store the data (limit the responsibility) → they may require granularity
  • Access only
  • Interoperability of the permissioning (consent etc.) → log of permissions (metadata… timestamps etc.)


  • Interoperability of identities
  • Operators offer interoperability for other roles
  • Commercial side ( see Patrik notes)
  • Natural language requirement → turning the machine readable stuff into human readable

PART 2 (not done yet): We then map the requirements to the generally acknowledged layers of interoperability: legal, technical (x2), semantic (x2), organisational, syntactic, dynamic, pragmatic, conceptual.

Notes Folke


Notes Patrik

Commercial side criterias needs to be carefully stated such as the business agreements align with MyData definition:

  • Supporting frameworks
  • Sharing of data, state-of-the API economy. What is the standpoint on access to raw data? (Open data?)
  • Interoperability standards: emerging within new (eco)system or adopt already available one

Technology wise it is fairly easy to solve integration with the MyData definition but the commercial agreements need to fit in. In some cases be incentivised to push/pull for adoption.  

Notes Markus


Notes Antti K.

Interoperability is the multi-layered defining factor that enables me as an identity holder to be at the center of all things MyData. Interoperability extends MyData to include the relationships and surrounding infrastructures, so that MyData becomes more than just the defining personal attributes.

Notes Joss

Mapping the interoperability space (v1)

Changes for v2:

  • Add language
  • Add specifications
  • Add semantic, syntactic & data portability
  • Add testing & certification

Layers from the models: legal, technical (x2), semantic (x2), organisational, syntactic, dynamic, pragmatic, conceptual.

Notes Jogi

1) Interoperability from the roles of the declaration

I suggest that we move one part of what was last week written to “why interoperability” part to here, namely the starting point of looking interoperability and scoping it from the the perspective of the four roles in the declaration:

2) Separation of technical interoperability on semantics vs. transaction layer (see in Slack)

The *semantic interoperability* of the data content is a big challenge.

The other big challenge are the *standards for transactions* including identity, consent, usage policies etc.

If we have good *standards for transactions* it is easy and seamless to do secure sharing of data between services.  If not, then clumsy point-to-point integrations and/or manual download-uploads is needed and scaling effects are hard to reach.

If we have good *semantic interoperability* it is easy and seamless to use data once you get it.  If not, then clumsy and error prone data format manipulations need to be done when data is used.

→ Both are needed!

10.4.2018 Why is interoperability important for the MyData Community?


Interoperability is the key factor in making MyData happen and making it right.

Interoperability drives practical global adoption and wider markets (making it happen):

  • Reusability of technologies        faster and cheaper to implement
  • Less friction in data flow → new categories of services become viable
  • Substitutability of services → systemic trust (no need to trust in any single provider) and easier decision making for organizations and individuals
  • Network effects drive faster adoption

Interoperability enables open ecosystem and drives innovation (make it right):

  • Open technologies → lower entry barrier for new service providers
  • Customers are not locked in with their data to the existing services → possibility to compete with new innovations

In the MyData Declaration it says: “Interoperability decreases friction in the data flow from data sources to data using services, while eliminating the possibilities of data lock-in.”

Interoperability should be thought also from the perspective of other roles in the MyData ecosystem, what it means for people (person) and for operators. For individuals interoperability offers seamless user experience also when dealing with multiple organisations and field tested standard solutions will be safer, present fewer technical risks and have fewer unintended consequences.

MyData community’s role in supporting interoperability:

  • We curate from the existing standards and technologies the ones that are aligned and support the MyData principles.
  • We create clear guidance for the implementers on what technologies and standards to choose.
  • We drive the adoption of standards by reaching out to different bodies and promoting the use of standards and the tools that have interoperability in their core.

Notes from Joss

The flow of data provides opportunities for innovation, enterprise and personal freedom.

The European Interoperability Framework (EIF) defines interoperability as “the ability of organisations to interact towards mutually beneficial goals, involving the sharing of information and knowledge between these organisations, through the business processes they support, by means of the exchange of data between their ICT systems.” Where is the individual in the MyData definition?

Interoperability creates a level playing field ...

The importance of reusability of solutions is recognised by the EIF. The ability to use standardised approaches to solve engineering problems is fundamental to the advancement of technology and the dissemination of knowledge. In addition to being faster and cheaper to implement, a solution that has been tested and iterated repeatedly in the field will be safer, present fewer technical risks and have fewer unintended consequences.

Technology neutrality is critical - specify the interface for as many channels as possible, not the technical means of delivering the interface.

Simplicity. As complicated as it need to be and no more.

[note: we need to understand and communicate the risks/barriers and benefits of increased interoperability to organisations as well as individuals (e.g. disclosure of commercial IP & accidental disclosure).]

Notes from Jogi

Why Interoperability:

  • No lock-in = Substitutability of service providers → Systemic trust → Wider markets and faster adoption
  • I don’t need to trust one service provider, since I can always change to new provider
  • Competition → innovation
  • Standards → Market for tools and solutions → faster, cheaper, better implementations → Wider markets and faster adoption

Why MyData promoting interoperability (isn’t it done by others already):

  • Standards are done by others, but there is nobody guiding the personal data management services and use-cases on which standards to use and how.
  • Risk that the PDM field gets overly fragmented and therefore dies out (no stable market)
  • Companies are investing in different technologies and standards, a neutral community is needed to discuss and agree the approaches that are recommended.

Notes from Antti K

  • MyData is not only about enabling access to personal data. MyData is about enabling beneficial reuse of that MyData with the consent and for the benefit of the identity holder. In order to make that happen, it’s critical to establish interoperability understanding for MyData.
  • There are different layers of interoperability, and they all need to be solved in order to enable efficient global, cross-border MyData flows.
  • Interoperability (in general) is the first thing that needs to be solved, when we want to move from talking about MyData and making MyData happen.
  • “MyData is not happening” when we do MyData by ourselves or just with few parties between each other. That’s not interoperability, that point-to-point integration.
  • MyData Community should raise up awareness and visibility of “MyData-friendly” interoperability frameworks, and call out for providing solutions to those interoperability levels.
  • By driving interoperability-centric implementations, the MyData Community will enable network effects to grow for MyData

Call memo in Slack

Feb 20th

*Next call*

• Tue 6th 3.30PM CET

From now on all we will speak all time zones in CET

*Point of contact for the track*

• Antti K. will be steering the substance development for example by leading the discussion in the track calls, no other extra duties for him.
Jogi will prepare the discussion points in advance, take notes etc.

*Marketing Plan for the track*

• See separate thread on this topic.

• Important is that we are all active and remember to mention the call for proposals to all directions.

• After brainstorming the marketing ideas we should move from general “all standardisation organisations” to actionable “which venue, which channel, which person and email address”

•Markus will promote the CfP in the Rebooting Web of Trust and IIW conferences

*Our own ideas for track content / who to invite*

• Antti: Kim Cameron

• Patrik: Possibly a domain specific interoperability session in some area like transport, health, insurance or education. Involve people at least from Sweden and Finland and possibly from other countries as well. In transport for example the digital driver’s license and geo-fencing are interesting topics where there is development in Sweden.

• Markus: cases demonstrating interoperability, we have this in the CfP, but need to be also proactive in getting these -- Markus asks cases from DIF

• Folke: will list findings and leads resulting from his standards and specifications readings. This could be invitation list for the poster session.

* Meetup in Turin 12-13. April*

• If there are more people from the interoperability track who can participate in Turin then we should use the opportunity and have a workshop. Now the status is Folke (no), Markus (maybe), Patrik (maybe), Antti (?), Jogi (yes). Let’s see how this looks like in our next call.

*Other News*

• Jogi: I have been in discussions with Christopher Allen about bringing *Rebooting web of Trust* workshop to the conference

• Jogi: There is also ongoing discussion of possibility to arrange 1 day external event on the day before the conference with Sovrin.

• Markus: Kaliya had suggested that there could be also DIF meetup in the conference.

• There is some overlap with people, but not much in DIF and rebooting web of trust, these both could take place and good if they are not on top of each others. Conference can help in arranging meeting space etc.

*What could be the goal/mission of the Interoperability Track?*

Call memos in Slack

Jan 24th & 26th

*What could be the goal/mission of the Interoperability Track?*

  • Adopt a big vision: interoperability meaning something that works for everybody
  • Build the missing identity layer to the Internet / Internet of Identity (Phil Windley)
  • Understand the limitations, on this track we can not expect to create the perfect white paper defining the ultimate solutions, since many people with bigger efforts are trying the same, not a small task. --> Scope down.
  • Look at different standardisation efforts, share the key points and understand how they might relate to each others (example. IEEE ethics, w3c personal data semantics, DIDs and verifiable claims etc.)
  • Consider also the end user perspective, what does the interoperability mean for the people?
  • Keep the big picture in mind... Ideally people could use their data without borders. Nowadays when ever humans are interacting with data they are dealing with silos.
  • Bring together the terrific work in standards etc. that is already happening.
  • MyData mentioned globally in the biggest projects that have to do with personal data. Offer something so useful in terms of interoperability, that people behind these projects will know us.

*What kind of programme contributions we would like to see coming from the open call for proposals?*

  • Concrete examples of “pairs of initiatives” that have build interoperability between them, what has worked and what has been challenging?
  • Get surprising parties involved: Something new outside from the usual suspects (like the NIEM for example)
  • What are the global (outside of Europe) pieces of the puzzle to make the human centric personal data flow happen?
  • Bridge over to other orgs like GSMA and UN (align with the sustainability goals) and find synergies.

*Other notes*

  • Track team is well connected to for example Sovrin circles --> key question is how to get the message to other circles (like for example uPort, which is involved in DID and aligned with our intentions). Next week I will run here in Slack a simple stakeholder mapping exercise to get over this challenge.
  • US national information exchange model ( ) is very interesting project to replicate. We could benchmark the process and governance.


Our digital world infrastructure is full of intentionally build walls and un-penetrable wastelands of unintentional incompatibilities. We envision better data future, where people have freedom to use their data without any borders. Interoperability means something that works for everybody, incompatible technologies only create silos that lock people in. MyData movement looks interoperability from the human perspective, how individuals could be the connection points regarding their own data and digital identity in a rich and heterogeneous world of digital services. In order to make that happen we share a vision of a "universal identity layer" for the Internet that everyone can build on and that works as well as the web itself.

Interoperability is a multi headed beast that people have been working over decades. We have experience of “data exchange”, “open systems interconnection” etc. in the 70´s to what is the state of the art today. In this conference track we cannot expect to create the perfect white paper defining the ultimate solutions (why would anybody adopt those solutions anyways).

INTEROPERABILITY FOR MYDATA? : What is most needed in order to make the different personal data solutions work together in an ecosystem? We will collectively scope what are the requirements and possible solutions to the big interoperability questions of MyData. Real use cases feed into the interoperability discussions. We look into legal and technical challenges that the builders of these solutions are facing and solving today.

LEARN FROM EXAMPLES: We want to build upon commonly accepted standards and bring together the terrific work in technical approaches, protocols and specifications, that is already happening (example. IEEE ethics, w3c personal data semantics, DIDs and verifiable claims, trust models, data models, open APIs etc.).

INITIATE ENRICHING COLLABORATION: Interoperability should not be an afterthought of individual projects. It should be an attitude of open mind, collaboration and learning from others. Such collaboration needs right environment and we want to create such. The aim is to develop concrete and actionable roadmap to the future interoperability work in the MyData community. At the end of the conference we should gather a summary of the findings and discussions, and highlight areas that would require additional focus, or that are ready for practical application.

What kind of programme contributions we would like to see coming from the open call for proposals?

Concrete examples of “pairs of initiatives” (i.e. separate personal data platforms connecting or cross standard data porting etc.) that have build interoperability between them, what has worked and what has been challenging?

Proposals that look into different aspects of interoperability. What needs to be understood, when multiple previously unknown systems operate with personal data and humans in the middle?

Examples of interoperability initiatives, standards and projects all around the world. If you think that your project could contribute in making to making the human centric personal data flow happen, let us know!



The track should make clear that interoperability should not be an afterthought of individual projects ("now that I'm done building my app/service/etc., I'll see if it can somehow connect to others"). Incompatible technologies only become another kind of silo that locks people in. The audience of the track should share a vision of a "universal identity layer" for the Internet that everyone can build on and that works as well as TCP/IP or the web itself.

It would be nice if we can have sessions in the programme that illustrate concrete examples of related technologies, and explore in some detail  why they work or do not work with each other. E.g. can my Meeco app connect to my CozyCloud, can I share claims between a Sovrin user and a uPort user, can I port personal data between Blockstack and a DIF Hub, etc…...


This track will try to explain the requirements and possible solutions to the big interoperability questions of MyData. We will present an overview of what facets/areas MyData interoperability has and present what kind of approaches have we found to the requirements. Among other things, we will look into standards, specifications, legal challenges, trust models and technical capabilities that MyData interoperability has so far faced. 

At the end of the conference we should gather a summary of the findings and discussions, and highlight areas that would require additional focus, or that are ready for practical application.

We would like to receive proposals that look into different aspects of interoperability. What needs to be understood, when multiple previously unknown systems operate with personal data and humans in the middle.


  • A shared data model
  • The interoperability between organisations using a reference architecture
  • Solutions to enable semantic synergies and ideas on how the terminology will be designed and governed

I am into this due to my interest for interoperability has increased during the recent years of studying management and economics of innovation. I see the potential of web 3.0, semantics and technologies of the fourth industrial revolution has thresholds and where the information converge between different systems and needs. I want to align the ideas by using systems thinking and create a platform for future concepts to be realized. These platforms could be a network of actors that can utilize the effects of synergies in using common protocols, standards and frameworks to their mutual benefit with a focus on the individual. By increasing trust and security in sharing information a higher effect can be achieved in the end, with the goal of expanding the reward instead of creating more vertical silos of information, data lakes etc.



Newcomer as I am, I started to fill the gap between my earlier experience of “data exchange”, “open systems interconnection” etc in the 70´s to what is the state of the art today. Among all theoretical discussions, debates, conflicts I found one very good example where one sector (HealthIT) is touching the interoperability quest nicely. Starting with the US  Office of the National Coordinator for Health Information Technology and their vision and their interoperability roadmap. Here I especially like the Guiding Principles for Nationwide Interoperability (p.xiii), D. Verifiable Identity and Authentication of All Participants(p. 11) and H. Consistent Data Semantics (p.25). I then ended up in a NIST paper: Standards for Interoperability: Life and Death Implications in Health IT by Sheryl Taylor, Rob Snelick, Systems Interoperability Group, NIST. Perhaps an interesting Use case?


The purpose of interoperability is to decrease friction in the data flow from data sources to data using services, while eliminating the possibilities of data lock-in. It should be achieved by continuously driving towards common business practices and technical standards.

In order to maximise the positive effects of open ecosystems, we will continuously work towards interoperability of data, open APIs, protocols, applications and infrastructure, so that all personal data are portable and reusable, without losing user control. We will build upon commonly accepted standards, ontologies, libraries and schemas, or help develop new ones if necessary.

curating standards for reaching minimum of interoperability between different personal data solutions. We will form “use cases” and “interoperability” working groups, that will overlap with the corresponding topic tracks in the MyData 2018 conference. The two tracks are interlinked, for instance use cases feed into the interoperability discussions, where the aim is to develop concrete and actionable support material for the MyData Declaration.