- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Jan 2021 19:40:37 +0000
- To: public-hydra-logs@w3.org
I've changed the approach with this issue this time. This time I've dropped the resource specification and I didn't got towards request specification neither. All I did was a slight modification of `returnsHeader` and `expectsHeader` so it is possible to provide possible header values. This way it would be possible to describe an expected resource to be any of provided `Content-Type` header values for upload or possible `Content-Type` serializations of the resource. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/186#issuecomment-765641669 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 22 January 2021 19:40:39 UTC