I saw AEP-193 got added somewhat recently. I ran into this with one of my specs:
812:18 warning aep-193-error-response-schema "type" property must have required property "format" components.schemas.ConflictProblem.properties.type
I see that comes from here:
02097ae#diff-22d42c0ff22b239c4fc7114a4d98a5f52b6ee2a817f50858202d2794b9973c6eR17
I don't have a problem with adding this to my spec, but it's not mentioned on AEP-193.
I checked RFC 9457. It strongly encourages URI format, but doesn't mention needing to document whether it is a URI or string, (or empty which is valid and assumed to be about:blank).
I think requiring format makes sense for AEP, but if we are going to ask people to do it, we should probably add it to the AEP. Unless I'm missing something?
I saw AEP-193 got added somewhat recently. I ran into this with one of my specs:
I see that comes from here:
02097ae#diff-22d42c0ff22b239c4fc7114a4d98a5f52b6ee2a817f50858202d2794b9973c6eR17
I don't have a problem with adding this to my spec, but it's not mentioned on AEP-193.
I checked RFC 9457. It strongly encourages URI format, but doesn't mention needing to document whether it is a URI or string, (or empty which is valid and assumed to be about:blank).
I think requiring format makes sense for AEP, but if we are going to ask people to do it, we should probably add it to the AEP. Unless I'm missing something?