LogoLogo
How to Build Dataspaces?Main IDSA AssetsOther ResourcesManifesto for International Data Spaces
Dataspace Protocol
Dataspace Protocol
  • Overview
    • Dataspace Protocol 2024-1
    • Terminology
    • Information Model
  • Common Functionalities
    • Specification
    • Binding: HTTPS
  • Catalog
    • Specification
    • Binding: HTTPS
  • Contract Negotiation
    • Specification
    • Binding: HTTPS
  • Transfer Process
    • Specification
    • Binding: HTTPS
  • List of Files
    • Common
    • Figures
    • Messages
    • Schemes
    • Shapes
  • Best Practices
    • Introduction
    • Related Documents
Powered by GitBook

Links:

  • IDSA Website
  • IDSA Github
  • Legal Notice
  • Privacy Policy

© 2016 – 2025 | All Rights Reserved | International Data Spaces Association

On this page
Edit on GitHub
  1. Common Functionalities

Specification

Last updated 1 year ago

1 Exposure of Dataspace Protocol Versions

implementing the Dataspace Protocol may operate on different versions. Therefore, it is necessary that they can discover the supported versions of each other reliably and unambiguously. Each must expose information of at least one Dataspace Protocol Version it supports. The specifics of how this information is obtained its defined by specific protocol bindings.

A must respond to a respective request by providing a JSON-LD object containing an array of supported versions with at least one item. The item connects the version tag (version attribute) with the absolute URL path segment of the root path for all endpoints of this version. The following example specifies that this offers version 1.0 endpoints at <host>/some/path/v1.

{
    "@context": "https://w3id.org/dspace/2024/1/context.json",
    "protocolVersions": [
       {
            "version": "1.0",
            "path": "/some/path/v1" 
       }
   ]
}

This data object must comply to the and the .

The requesting may select from the endpoints in the response. If the can't identify a matching Dataspace Protocol Version, it must terminate the communication.

JSON Schema
SHACL Shape
Connectors
Connector
Connector
Connector
Connector
Connector