search

International-Data-Spaces-Association / ids-specification

The Dataspace Protocol is a set of specifications designed to facilitate interoperable data sharing between entities governed by usage control and based on Web technologies. These specifications define the schemas and protocols required for entities to publish data, negotiate Agreements, and access data in a data space
https://docs.internationaldataspaces.org/dataspace-protocol/
Apache License 2.0
34 stars 16 forks source link

TBD: Versioning #15

Closed juliapampus closed 8 months ago

juliapampus commented 1 year ago

Resolve TBD in catalog.binding.https.md.

ssteinbuss commented 1 year ago

@ssteinbuss will add an editorial info box. We need to discuss on the item itself 3.2 Versioning Versioning will be done via URLs. TBD.

ssteinbuss commented 11 months ago

The section 3.2 Versioning is missing text:

ssteinbuss commented 11 months ago

@jimmarino and @sebbader-sap could you sketch a solution?

jimmarino commented 11 months ago

Some thoughts:

  1. Define a generic JSON response type, and each binding document will provide the mechanics for obtaining the metadata (e.g., well-known for HTP)
  2. Each version can specify an endpoint

An example:

{
   "versions": [
       { "1.0" : "https://example.com/catalog/v1"},
       { "2.0" : "https://example.com/catalog/v2"},
    ]
}

This should be part of #167.

ssteinbuss commented 9 months ago

fixed in #184

sebbader-sap commented 8 months ago

Explanation already introduced at https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/common/common.binding.https.md

sebbader-sap commented 8 months ago

Together with #225 and the linked explanation above, I'd say this issue is solved. Can somebody else confirm?

ssteinbuss commented 8 months ago

Agree.