Info |
---|
Deze pagina’s zijn in het engels ten behoeve van mogelijk internationale ontwikkelaars |
...
This endpoint must MUST be implemented by the following roles:
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
This endpoint may MAY be implemented by the following roles:
...
Used to obtain information about the capabilities of participants in the DSGO from the trust framework catalogue (provided by the DSGO Trust framework authority). The /capabilities
endpoint is used by all parties providing services within the context of the DSGO (data service providers, market facilities and the trust framework catalogue) to provide information about features provided. In the DSGO, a data service can be considered as a specific feature.
Excerpt | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
|
...
Parameters | Type | Description | ||||
---|---|---|---|---|---|---|
| Required | String | Unique identifier of the party, MUST be a valid Organisation ID, containing an EORI or KvK number. | |||
| Required | Array of objects | MUST be an object containing an array of | |||
| Required | String in | MUST be the party role. Available values are | |||
| Array of objects | Contains information about supported version endpoints for each version. MUST contains | ||||
| Required | String in | MUST be the version of the system which is under support | |||
| Required | Array of objects in | Contains a list of supported features. MUST contains | |||
| Optional | Array of objects in | MUST Contain a list of public features ( | |||
| Required | String in | Unique identifier of the data service, MUST be a unique identifier distributed by the DSGO Trust framework authority, when no identifier is received yet, field MUST be | |||
| Required | String in | Friendly name of the data service, MUST be limited to a maximum of 100 characters | |||
| Required | String in | Short description of the data service, MUST be limited to a maximum of 1000 characters | |||
| Required | String in | URL to the data service, MUST be according to RFC3986 | |||
| Optional | String in | URL where access token for the feature could be retrieved, MUST be according to RFC3986. This is optional because if | |||
| Required | object in | Data service specification, MUST contain a valid | |||
| Optional | Array of objects in | MUST contain supported restricted features. The structure and parameters are exactly the same as defined in |
* these parameters are DSGO specific and have been added on top of the parameters defined in iSHARE (v2.0).
...
the /parties
endpoint follows the generic technical requirements, as well as the requirements specified for specific methods. The figure below gives an overview of the HTTP methods that are supported by the /parties
endpoint. These methods are further detailed and specified in the pages below:
...