...
Parameters | Type | Description | ||||
| Required | String | MUST contain a description of the access policy of the data service which is not covered by the | |||
| Required | Array | MUST contain a (reference to) (one or more) recognised standard to indicate ontologies, semantics, schemes to which the resource in the data service conforms. In order to be machine-readable, this MUST contain an array of URIs (according to RFC3986), if this is not possible, it MAY contain a human-readable description of the standard. | |||
| Required | String | MUST contain a description of the costs that a data service provider charges a data service consumer for using the data service. In order to be machine-readable, this MUST contain a URI (according to RFC3986) to existing models, if this is not possible, it MAY contain a human-readable description of associated costs. | |||
| Required | Array | MUST contain a URI (according to RFC3986) to a machine-readable description of the endpoint and possible operations related to the endpoint(s) of the data service. Examples include an OpenAPI (Swagger) description, or YAML file. Additionally, this array MAY include a URI to a human-readable description of the endpoint, for example a developer portal. | |||
| Required | String | MUST contain a description regarding the policies related to the execution of the data service. In order to be machine-readable, this MUST contain a XCAML description, if this is not possible, it MAY contain a human-readable description of the policies. | |||
| Required | String | MUST contain the level of assurance that a data service consumer must achieve in order to make use of the data service, MUST be indicated in accordance with the eIDAS regulation and be the value of | |||
| Required | Array | 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 /wiki/spaces/AD/pages/215547968 licence codes, prepended with a “ | |||
| Required | String | MUST contain the level of security that a data service consumer must achieve in order to make use of the data service. Note, this is not yet defined in the DSGO, but will be further expanded in the development of the DSGO. | |||
| Required | Object | Service levels which data service consumers can expect regarding the data service. MUST contain an object including the | |||
| Required | Array of objects in | MUST contain a range of timestamps indicating the weekly availability window of the data service. In order to be machine-readable, this MUST contain a JSON structure as presented below, if this is not possible, it MAY contain a human-readable description of the availability window.
| |||
| Required | string in | Performance indicators of the data service. MUST contain a string describing the performance, limited to a maximum of 500 characters. | |||
| Required | String | Version indicator of the data service, MUST be formatted as a.b.c. inline with the versioning guidelines for the trust framework |
...