-
Notifications
You must be signed in to change notification settings - Fork 0
/
model_checksums.go
17 lines (16 loc) · 1.57 KB
/
model_checksums.go
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
/*
* Data Repository Service
*
* GET request: - Fetch a DrsObject from the database by sending a unique ID through the request - Fetch an access url to the data which the object refers to - Fetch DrsObjects by doing a search on the aliases POST request: - Create a non-existing DrsObject in the database by giving an identifier DELETE request: - Delete a DrsObject from the database by unique identifier PUT request: - Update an existing DrsObject by unique identifier and the changes in the body
*
* API version: 1.2.0
* Contact: [email protected]
* Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
*/
package drs_api
type Checksums struct {
// The hex-string encoded checksum for the data
Checksum string `json:"checksum"`
// The digest method used to create the checksum. The value (e.g. ```sha-256```) SHOULD be listed as ```Hash Name String``` in the https://www.iana.org/assignments/named-information/named-information.xhtml#hash-alg[IANA Named Information Hash Algorithm Registry]. Other values MAY be used, as long as implementors are aware of the issues discussed in https://tools.ietf.org/html/rfc6920#section-9.4[RFC6920]. GA4GH may provide more explicit guidance for use of non-IANA-registered algorithms in the future. Until then, if implementors do choose such an algorithm (e.g. because it's implemented by their storage provider), they SHOULD use an existing standard ```type``` value such as ```md5```, ```etag```, ```crc32c```, ```trunc512```, or ```sha1```.
Type_ string `json:"type"`
}