CenterForDigitalHumanities / CenterForDigitalHumanities/deer-LR
Profile Header for 1.0 Requests
- Dominant language
- HTML
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
For a response which is processed using the v1 1.0 profile expectation (ex reading `new_obj_state`), the request must contain a Profile header request for the response under the v1.1 profile.
This happens in the function `quicklyAddToCollection()`.
Ex.
```HTTP
Request:
POST /v1/create HTTP/1.1
Content-Type: application/json
Profile: http://storedev.rerum.io/profile1.0
body {"hello":"world"}
Response:
HTTP/1.1 201 Created
Content-Type: application/json
Accept-Profile: http://storedev.rerum.io/profile1.0
body {"@id":"https://example.item/id/123", "hello":"world", "new_obj_state":{...}}
```
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.