Page Comparison

Authorization

Optional

String

MUST contain an OAuth 2.0 authorization based on bearer token. MUST contain “Bearer " + access token value. This parameter is optional and may be used by data service providers who wish to use an access token as authorization information for their data service.

Data service consumers can request access tokens via the /token endpoint. See Access Token for more information.

broker_evidence

Optional

Object

MUST contain a broker_token object containing DSGO broker evidence regarding the data service broker. This parameter is optional and may be used by data service brokers who request a data service on behalf of data service consumers they service.

Data service brokers can obtain broker evidence via the /brokers endpoint. See Datadienstbrokers for more information.

Note, broker_evidence MUST be used in combination with the client_assertion parameter. If broker_evidence is used, the accessSubject in the brokerEvidence object MUST be validated to match the client_id in the client_assertion. If this matches, the policyIssuer in the brokerEvidence MUST be considered the data service consumer.

Note, broker_evidence MAY NOT be used in combination with delegation_evidence.

client_assertion

Optional

Object

MUST contain a signed DSGO JSON Web Token. This parameter may contain a DSGO Authenticatie JWT used for of the data service consumer. Alternatively this parameter may contain a DSGO Onweerlegbaarheid JWT used by data service consumers or required by data service providers who wish to ensure for non-repudiation of the data service request. If this parameter contains a Onweerlegbaarheid JWT, the Digest header must also be included.

See Authenticatie and Onweerlegbaarheid for more information.

delegation_evidence

Optional

Object

MUST contain a delegation_token object containing delegation evidence regarding the requested service. This parameter is optional and may be used by data service providers who wish to enable data entitled parties to delegate their rights in regard to the data service to (potential) data service consumers.

Data service consumers can obtain delegation evidence via the /delegation endpoint. See Delegation for more information.

Note, delegation_evidence MUST be used in combination with the client_assertion parameter. If delegation_evidence is used, the accessSubject in the delegationEvidence object MUST be validated to match the client_id in the client_assertion. If this matches, the policyIssuer in the delegationEvidence MUST be considered the data service consumer.

Note, delegation_evidence MAY NOT be used in combination with broker_evidence.

Digest

Optional

String

MUST contain a SHA256 hash (according to RFC 3230) of the HTTP body with the matching algorithm identifier S256as defined in ETSI TS 119 182-1. This parameter is optional and may be used by data service consumers or required by data service providers who wish to ensure for non-repudiation of the data service request.

See Onweerlegbaarheid for more information.

LicensePurpose

Optional

String

MUST contain a reference to the legal document under which the data service is made available. MUST be equal to one or more of the licence codes, prepended with a “DSGO." prefix. This parameter describes the purpose of the licence the data service consumer request for the data in the data service response.

See Licenties for more information.