[BUG] OperationResultValueOnly differs in API and Metamodel

[BirgitBoss]

Describe the bug
In
Schema for Value-Only Serialization the result object is defined as follows:

  "OperationResultValueOnly": {
      "executionState": {
        "type": "string",
        "enum": ["Initiated", "Running", "Completed", "Canceled",
                 "Failed", "Timeout"]
      },

looks different to result as defined in

https://app.swaggerhub.com/apis/Plattform_i40/SubmodelServiceSpecification/V3.1.2_SSP-001#/Submodel%20API/InvokeOperationSync-ValueOnly

[BirgitBoss]

see also https://industrialdigitaltwin.io/aas-guides-antora/AAS_SAMM_Guideline/1.0/smt2samm.html#_operation and https://industrialdigitaltwin.io/aas-guides-antora/AAS_SAMM_Guideline/1.0/samm2smt.html#samm:Operation

[mjacoby]

You are correct that there are deviations, however, your initial statement is incorrect as the definition of the Schema for Value-Only Serialization you provided is incomplete. The source you provide gives the following definition

"OperationResultValueOnly": {
      "executionState": {
        "type": "string",
        "enum": ["Initiated", "Running", "Completed", "Canceled",
                 "Failed", "Timeout"]
      },
      "inoutputArguments": {
        "$ref": "#/definitions/ValueOnly"
      },
      "outputArguments": {
        "$ref": "#/definitions/ValueOnly"
      },
      "additionalProperties": false
    }

So the only properties missing are messages and success.

My proposal would be to add those two properties in the ValueOnly JSON Schema definition. The reasoning would be that the message structure would be the same as for the normal serialization only with valueOnly serialization for all AAS elements - the meta data should be the same for both serialization modes. This would be in line with what SAMM is doing.