RFC047: Respecification of the capabilities endpoint
Background and rationale
The /capabilities endpoint is required for every participant that provides services. The endpoint returns iSHARE capabilities (supported versions & optional features) of the iSHARE party. This way it forms a cornerstone in the technical implementation of the iSHARE Framework.
DSGO is developing a data space for the built environment. The current design of the capabilities object limits its utility within DSGO's data space. Therefore, they recommend modifications for broader generic utility, allowing it to be used in the DSGO and other data spaces.
The DIL programme is developing BDI ("Basis Data Infrastructuur") and is working on implementation in the logistics domain. As part of the programme, Portbase developed a proof of concept. During the proof of concept several possible improvements of the capabilities endpoint have risen.
During the lifetime of iSHARE, new standards have been released. Particularly DCAT version 2 is a relevant standard, which introduced the concept of a Data Service, with a comparable scope as the iSHARE /capabilities endpoint.
Proposed change: purpose
This RFC intends to improve the specification of the capabilities endpoint (more specifically the capabilities_info object) to foster adaptability for data spaces and to improve alignment with new standardisation.
Proposed change: considerations and requirements
Proposed modifications include:
1 - The "ishare_role" parameter should be renamed to "role" with provision for additional values, accommodating data space-specific roles.
2 - Explicitly allow the expansion of the feature object with extra parameters, facilitating the integration of data space-specific functionalities as necessary.
Impact analysis
The final impact analysis of the RFC can be found here.
The work-in-progress version of the impact analysis can be found here.