RDM 1.37-5 Schema "different_pid" used in QUEUED_MESSAGE not part of Schema

[Qasi_]

While implementing 1.37-5 i found this.
if i validate QUEUED_MESSAGE with the Schema of 1.0.0
it prompt me an Exception, because the Enum "different_pid" is not specified in the Schema.
Currently in the Schem its defined like:

"enum": [
"get_request",
"get_response",
"set_request",
"set_response"
]


but should be

"enum": [
"get_request",
"get_response",
"set_request",
"set_response",
"different_pid"
]

[shawn]

None of the examples are normative because there are some outliers. QUEUED_MESSAGE is one of them. The response to GET:QUEUED_MESSAGE can change depending on what the message is, so there isn’t a specific way to define the message body. The “different_pid” value is just a placeholder.

I’m curious, at which link did you find the examples?

[Qasi_]

I found it related from the Spec 1.37-5 Duckument.
https://gitlab.com/esta-cpwg/e137-5/-/blob/main/examples/1.0.0/e1.20/QUEUED_MESSAGE.json?ref_type=heads

https://gitlab.com/esta-cpwg/e137-5/-/blob/main/schemas/1.0.0/schema.json?ref_type=heads

If i cant validate the QUEUED_MESSAGE withe the schema to validate thees json-defines then something is not completely thought through.

[shawn]

From that (and my) perspective, QUEUED_MESSAGE itself is ill-defined. Suggestions on how to improve the schema for this case are welcome.