"Query-input" term no longer in Schema.org

[rebeccaringuette]

The guidelines for accessing data for a service endpoint shows use of the "query-input" term:

    "query-input": [
      {
        "@type": "PropertyValueSpecification",
        "valueName": "format",
        "description": "The desired format requested either 'application/x-netcdf' or 'text/tab-separated-values'",
        "valueRequired": true,
        "defaultValue": "application/x-netcdf",
        "valuePattern": "(application\/x-netcdf|text\/tab-separated-values)"
      },

However, the term no longer exists in Schema.org. The resulting schema.org json-ld record still validates in the Schema.org validator. A quick search suggests that query and actionProcess might be reasonable replacements. Query only accepts text, but actionProcess is of type HowTo which has much more structure. What should the updated term and structure be for potentialActions requiring the additional information that used to live in "query-input"?
@Kurokio

[mbjones]

@rebeccaringuette This seems to be the issue: https://stackoverflow.com/a/27150008

[rebeccaringuette]

Interesting. So it isn't "wrong", and apparently Schema.org has updated their validator to not break for it. So, do we need to update the guidance on this, or is this fine as is?

[rebeccaringuette]

If we leave this as is, a sentence or two just after the example containing "query-input" describing this will help reduce questions.

[mbjones]

Makes sense to me.

[smrgeoinfo]

yes, the SOSO recs are based on https://schema.org/docs/actions.html. query-input has never appeared in the schema.org vocabulary pages except there...