-
RFC7807 has a couple of options that should be clarified in the Profile.
Open questions include:
- Should we permit XML formats?
- Should we permit HTML strings?
- Should we permit "about:blank"?
…
-
Currently, `Message` is only an instance of `Stringable`: https://github.com/CuyZ/Valinor/blob/396f64a5246ccfe3f6f6d3211bac7f542a9c7fc6/src/Mapper/Tree/Message/Message.php#L9-L11
When using this li…
-
### Situation Description
Currently, Sormas Rest API is handling a small range of errors which can be reported to the front(or service which is interrogating REST endpoints).
If appear a scenario wh…
-
## Background and Motivation
API Controllers have a mechanism to auto generated `Problem Details` (https://datatracker.ietf.org/doc/html/rfc7807) for API Controller `ActionResult`. The mechanis…
-
This issue has been inspired by [Problem Details for HTTP APIs - RFC7807](https://tools.ietf.org/html/rfc7807) and blog post [Structuring validation errors in REST APIs](https://medium.com/engineering…
Sibyx updated
2 years ago
-
Currently:
> A Designated Expert reviews and approves registration requests, as per {{RFC8126, Section 4.5}}. A specification document is appreciated, but not required.
That doesn't seem like a …
-
Results of localization self-review for WoT.
Answers to short i18n review checklist [(from here)](http://w3c.github.io/i18n-activity/reviews/shortchecklist).
1. [x] _If the spec (or its implemen…
-
This has been requested a number of times but so far has been deferred to Spring Boot which supports error response details. The corresponding https://github.com/spring-projects/spring-boot/issues/195…
-
https://mailarchive.ietf.org/arch/msg/core/7_Oqt82j4tl69IG6--FrSoRN8uQ/
```
[Section 1.1]
* Please add the usual remark "Readers are expected to be familiar with ..."
[Section 2]
* The …
-
In HydraCG/Specifications#178 we have been working on making the response in the case of an API error compatible with RFC 7807. Since Hydra is based on JSON-LD, and RFC 7807 does not provide an offici…