operations schema not valid OpenAPI?

[edeutsch]

Hi, as reported here: NCATSTranslator/ReasonerAPI#301 by @vdancik
the operations schema does not appear to be valid OpenAPI 3.0 schema.
I think it would be fixed if we changed all instances of :

      "properties": {
        "unique": true,

to:

      "properties": {
        "unique": {
          "type": "boolean",
          "default": true
        },

Can you do that?

I think the problem is that you can't define a class to have a property that is merely defined as true (i.e. being true, rather than being a boolean with a value of true)

Making this change seems to fix the validation problems that I'm seeing.
I don't know if there is other code that somehow uses this "unique" property in some creative way that might be affected though. Is there? Can that be fixed?

[cbizon]

Thanks @edeutsch . It sounds like we should implement a validation check as part of the operations release as well.

[edeutsch]

yes, that would be very helpful, thanks!