Bug Report
Describe the Bug
The did document registration schema allows DataService and CatalogService as links to discover DSP endpoints. The former for version-independent discovery, the latter for a specific versioned Catalog-endpoint. Only in the latter case, the Provider must register the serviceEndpoint to end in /catalog. In the former case, it must end on /.well-known/dspace-version. This isn't reflected in schema.
Type: normative
Expected Behavior
a oneOf block that binds the pattern in serviceEndpoint to the type
Observed Behavior
Both types have to end on /catalog
Notes
https://github.com/eclipse-dataspace-protocol-base/DataspaceProtocol/blob/main/artifacts/src/main/resources/common/did-service-schema.json#L29-L41
Bug Report
Describe the Bug
The did document registration schema allows
DataServiceandCatalogServiceas links to discover DSP endpoints. The former for version-independent discovery, the latter for a specific versioned Catalog-endpoint. Only in the latter case, the Provider must register theserviceEndpointto end in/catalog. In the former case, it must end on/.well-known/dspace-version. This isn't reflected in schema.Type:
normativeExpected Behavior
a
oneOfblock that binds the pattern inserviceEndpointto thetypeObserved Behavior
Both types have to end on
/catalogNotes
https://github.com/eclipse-dataspace-protocol-base/DataspaceProtocol/blob/main/artifacts/src/main/resources/common/did-service-schema.json#L29-L41