Comment on page
Introduction

Abstract
This document presents best practices for the usage of the Dataspace Protocol.
Status of this document
The Best Practices are created and published by the International Data Spaces Association and are not considered to be normative. The specification of the Dataspace Protocol itself is normative. As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative.
The key words MAY, MUST, and MUST NOT in this document are to be interpreted as described in RFC2119 and RFC8174 when, and only when, they appear in all capitals, as shown here.
Introduction
The Dataspace Protocol is under development and the working group is active on this draft. We have reviewed and improved the content multiple times. During the process several aspects were discussed, which are not considered to be part of the specification itself, but important to be documented as support for the users of this specification as best practices. The examples in this document are non-normative.
Users of this specification are invited to provide feedback such as, but not limited to:
What information is missing?
What information, including examples, would you like to see?
What did you like in this document?
Please provide your feedback as Issue in our GitHub repository.
The remainder of the document is structured as follows:
​Related documents: provides useful resources for understanding the overarching concepts of Dataspaces and other foundational documents.
​Extensions: How to extend the Dataspace Protocol.
​Examples: Living examples to foster the understanding of the Dataspace Protocol.
​How to create Bindings​
​Known Implementations of the Dataspace Protocol​
​Security related considerations​
Last modified 1mo ago