---
# System prepended metadata

title: Meeting Notes WG GOV DSBC 20220218

---

# Meeting Notes WG GOV DSBC 20220218

## We like to have a tooling for good collaboration and help AISBL staff with note taking etc.
Interim wise we want to use hacmmd.io today and find proper tooling to collaborate later

## Protocols and working documents to be found within Gaia-X AISBL tooling community.gaia-x.eu
* Every member has reading access, WG members will get additional rights
* Folder for this WG is https://community.gaia-x.eu/f/5218488

## The slide on "Compliance with applicable competition law and Antitrust Guidelines" is read - everyone agrees

## Introduction by (Co-) Chair 
* Last week's meeting was successful and agile, we'll get more focused now
* Presentation of today's agenda (see slide deck)
    * presentation of a data space initiative (either Martine oder Herman)
    * understand requirements of members better 
    * sharpen deliverables (if time allows)

## Next steps
It is being discussed the working model of this group. Also detailling the deliverables, such as Policy Paper or Whitepaper/Handbook. 

### Suggestion of a model in order to structure our work 
Consider a simple input - output model as working model of the WG governance
* Find input sources based on existing work done elsewhere, law, existing governance standards or functional or operational models of data spacess
* Define deliverables and target audiences needed to establish a working governance
* Discussions, alignments and work to take all inputs into deliverables and an alignment will be learned by the team as we go on


Presentation of must reads, which should be read by all participants on the weekend and that form initial input documents (see the list in the slide deck)

(Suggestion to upload those as PDF into the work folder of the WG and provide a pre defined, initial folder structure - Michael L. can support)

## Presentation and proposition of four different layers (as already discussed last week): A, B, C, D
* A - Common building blocks and common (EU) framework for data spaces
* B - Domain specific building blocks, governance, agreements 
* C - Data space specific governance
* D - Operation of a data space

Discussion which layers to focus on. Suggestion is to focus on C and B (discuss layer B, take inspiration from layer C) and maybe give recommendations for A, but with a lead by Gaia-X Board/PRC. 

We need to understand how Data User, Data Provider, Data Holder and data subject as well as providers and participaters and their requirements are captured, as well as the business mechanics + value created for parties.

Data space members are not yet clearly visible in the model. 

We should start with the functional business problem we want to solve (instead of starting from comprehensive framework). Layers surely influence each other, especially top down (problem -> data space solution). 

Suggestion to add 'layer 0' with value creation, definition of terms to the model.
Need to understand how the lower levels are limited.

Understanding of dataspace (within Gaia-X) is tightly linked to the work of this WG. 

Let us look where Gaia-X may add value to current developments: e.g. the interconnection between dataspaces - create a general data spaces governance. To determine the needs from a governance perspective, the understanding of a Gaia-X Data Space is a pre-requisite. 
Closed - domain-specific - data spaces is being worked upon by several initiatives. 
Gaia-X strives in abstracting the requirements to - on the long run - and enable interactions between such domain-specific data spaces.
Thus, key should be the painpoints for such an overarching data space rather than repeating work that is already covered elsewhere. 

## Presentation of SCSN by Herman Pals (Smart Connected Supplier Networks)- see the slides https://community.gaia-x.eu/f/14309994

## Discussion about SCSN - Website: https://smart-connected.nl/en
* Smart Connector Supplier Network
* Connected Factories
* Goal to standardize interfaces to exchange information and enable interoperability.
* Similar connector model for Service Providers
* A monthly fee is paid to the Service Provider that delivers IDS Connector- TNO provides the basic elements.
* SCSN is a foundation - the Service Providers are members of the Foundation, so they can influence the requirements and the roadmap.
* You have to comply with the rules to be admitted as Service Provider

### Chat Comments related
* Question raised from Herman Pals - TNO via Chat: 
Here are a few questions, triggered from an earlier SCSN presentation to Gaia-X: Your info indicates that various service providers have to sign a participation agreement, but there is nothing about what the end users/providers have to commit to (by way of agreements covering participation, or specific transactions).  These would be interest to understand...
Another question (perhaps more technical) -- you have build a specialized data standard on UBL to support the specific message types of SCSN -- is this extensible or very limited to the SCSN context?


### Chat Comments related
* Text comment by Lars Nagel - Chair / IDSA: The SCSN principles could be an inspiration for other data spaces - we should study them.
* Text question raised by Mark Dietrich - EGI: a follow-up to my 1st question: can a Chinese supplier join SCSN?  (just to be provocative)
* Text question raised by Michael Leibfried - Redhat: 
Sounds for my like another Catena-X - what is the relation between both initiatives, please
* Text question raised by Michael Leibfried - Redhat: If you take part, are you also signing agreements with SCSN or only with a provider? What are the legal relations or committments from all parties?
  * Legal relation will be established only between participants and providers (also for scalability issues)
* Text comment by Frank Ingenrieth - SRIW: Thinking out loud and abstracting the matters that might to be addressed: technical interoperability, legal (licence, purpose....) compatibility, governance (change management) compatibility....
Any of those areas will likely have general painpoints, that can be determined (are determined elsewhere already) and thus, Gaia-X might determine its expectations to resolve such painpoints. Resolving in a comp-neutral way, i.e., defining the objective, but not unduly limit the actual implementations, provided defined compatibility requirements will be met.

Question raised by Sebastian Schlosser - BMW: Who is going to issue the certificate?

Question raised by Frank Ingenrieth - SRIW: and what is in scope of this certification and what is the methodology of issuing - my understanding is the technical aspects (interoperability) but not the legal / governance aspects. Is my understanding correct?


Suggestion by Michael to index relevant information: how do we capture what we have 

### Follow up topics raised related to the presentation
* consider legal, contractual relations, boundaries and committments in the SCSN model

# How to proceed - working plan for the group:
## Proposal to form two groups: 
* 1 Focused on horizontal criteria for Governance (Michael Leibfried and Mark Dietrich are available to join)
* 2.Focused lighthouse projects and initiatives as a starting point

As a result of the as a result of the work, it is expected to derive organisational options

Work also needs to be done on the different levels of governance 

## Dominik Rohrmus, CCO is requesting proper house keeping at the level of WG Mission Document: define mission, purpose/targets for the year and timelines.

The Mission Document has to be the first and most urgent deliverable for the working group. 

