2024-06-05

This meeting is part of the quarterly CAB meeting schedule.

This page concerns the CAB meeting held at Jun 5, 2024 at 15:00 CET.

RFC042: Harmonise terminology - we have reconsidered naming and would like to inform you on the naming that we will be implementing with this RFC
RFC031: Preperation of iSHARE DID method. The method name will probably be changed.
We expect to publish a new version of the framework and development documentation with the next release. This will impact all existing direct links to parts of the framework. The update is required to improve version handling and change management. Demonstration will be given in the meeting.

More detailed meeting notes are available upon request.

RFC047: Respecification of the capabilities endpoint: CAB advises to start implementation of the prepared RFC and impact analysis.
RFC055: Allow conditions in delegations: CAB advises to not start implementation, but instead spend more time in deep dives, specifically on the interoperability concerns between data spaces and the value that the RFC brings compared to the impact on complexity. Ideally owners of the business value are present at the deep dive meetings.
RFC052: Applicability of service levels under Adhering parties contract should be applicable only to parties providing services: CAB advises to start implementation of the prepared RFC and impact analysis.

RFC042: Harmonise terminology: CAB suggests to add mapping to IDSA and provide extra information on the conclusion that a one-on-one mapping with terminology used in other initiatives is not possible. Also producing a supporting document that explains the mapping would help the community to better understand meaning and comparison of the mapping.
RFC031: Introduce iSHARE-ID and allow multiple identifiers using DID, preparation of iSHARE DID method: CAB advises to organise more in depth sessions on this topic, focusing on how the iSHARE DID method would work outside iSHARE and inviting more experts to address the topic and assess the created iSHARE DID method.

Owners of a use case or the business value that has led to the creation of an RFC should preferably take part in the deep dive sessions, to make them more practical and less theoretical.
All feedback to RFCs must be provided in Gitlab to make things more transparent.
iSHARE Foundation will make sure that summaries of deep dive discussions (or possibly transcripts) will be made available through Gitlab.
iSHARE Foundation will look into ways of making the last version of an impact analysis more easily accessible, without requiring in depth knowledge of Gitlab.
RFC040: Verifiable Credentials support was discussed and decided to put on on hold, awaiting input from the Eclipse Data Space Working Group.

Last updated 1 year ago

This meeting is part of the quarterly CAB meeting schedule.

This page concerns the CAB meeting held at Jun 5, 2024 at 15:00 CET.

RFC042: Harmonise terminology - we have reconsidered naming and would like to inform you on the naming that we will be implementing with this RFC
RFC031: Preperation of iSHARE DID method. The method name will probably be changed.
We expect to publish a new version of the framework and development documentation with the next release. This will impact all existing direct links to parts of the framework. The update is required to improve version handling and change management. Demonstration will be given in the meeting.

More detailed meeting notes are available upon request.

RFC047: Respecification of the capabilities endpoint: CAB advises to start implementation of the prepared RFC and impact analysis.
RFC055: Allow conditions in delegations: CAB advises to not start implementation, but instead spend more time in deep dives, specifically on the interoperability concerns between data spaces and the value that the RFC brings compared to the impact on complexity. Ideally owners of the business value are present at the deep dive meetings.
RFC052: Applicability of service levels under Adhering parties contract should be applicable only to parties providing services: CAB advises to start implementation of the prepared RFC and impact analysis.

RFC042: Harmonise terminology: CAB suggests to add mapping to IDSA and provide extra information on the conclusion that a one-on-one mapping with terminology used in other initiatives is not possible. Also producing a supporting document that explains the mapping would help the community to better understand meaning and comparison of the mapping.
RFC031: Introduce iSHARE-ID and allow multiple identifiers using DID, preparation of iSHARE DID method: CAB advises to organise more in depth sessions on this topic, focusing on how the iSHARE DID method would work outside iSHARE and inviting more experts to address the topic and assess the created iSHARE DID method.

Owners of a use case or the business value that has led to the creation of an RFC should preferably take part in the deep dive sessions, to make them more practical and less theoretical.
All feedback to RFCs must be provided in Gitlab to make things more transparent.
iSHARE Foundation will make sure that summaries of deep dive discussions (or possibly transcripts) will be made available through Gitlab.
iSHARE Foundation will look into ways of making the last version of an impact analysis more easily accessible, without requiring in depth knowledge of Gitlab.
RFC040: Verifiable Credentials support was discussed and decided to put on on hold, awaiting input from the Eclipse Data Space Working Group.

Last updated 1 year ago