Peter Van den Bosch

WG discussion: invalidStructure e.g. checksum invalidPeriod: bc two inputs (start+end) that may be split in query parameters outOfRange : e.g. page number more than total of pages Should we return...

I've tried to summarize the discussion in https://github.com/belgif/rest-guide/wiki/Input-validation-issue-types IMO, the issue types `referencedResourceNotFound`, `replacedSsin` and `canceledSsin` would require the least discussion to standardize. For rest-problem-java, we'll have to discuss whether...

The page https://github.com/belgif/rest-guide/wiki/Input-validation-issue-types was briefly presented on the WG. Feedback welcome, discussion will continue next WG meeting.

> Other: payload is not valid to content-type (e.g. no valid JSON payload for content-type application/json) > -> doesn't that fall under `urn:problem-type:belgif:input-validation:schemaViolation`? You don't need to have the OpenAPI...

> > Maybe some middle ground can be found, e.g. `belgif:validation-ext` issue types that MAY be used (instead of SHOULD) and for which we don't provide much forward stability guarantees...

WG agrees upon adding `referencedResourceNotFound` Only generic issue types should be in REST guide Issue types specific to business domains, should be aligned with their openapi modules and managed outside...

WG conclusions: * keep schemaViolation separate from other non-schema programmatic validation issues * new issue type that covers broadly programmatic input validation issues, for which a client is expected to...

title for Schemas should probably be avoided, because they override the Schema name in the SwaggerUI view

there's already a rule for description (and avoid title) on schemas: [[oas-descr]](https://www.belgif.be/specification/rest/api-guide/#rule-oas-descr) I'll check if absence of title property is verified by the validator

Absence of title property is added in new release of validator >= 1.3.0 (though validator not yet open-sourced)