Darrel

The specific API that does this determines which response is going to come back based on whether the target document exists or not. A client cannot know this in advance....

CSDL cannot describe this currently, therefore we are going to defer the work on this. Currently there are no open requests from the community for this.

To pile onto this conversation, we also need to think about the consequences of supporting different media types for structured formats. Normally, if multiple media types are supported for a...

Can we clarify why we want to describe containment in an API description? While I do think it is an important concept to understand while designing an API, it is...

Unless you plan on supporting different charsets for RSDL then application/rsdl is the right choice.

The `info.version` property is defined as the version of the "Description" which could be composed of multiple documents. In OpenAPI the info.version is defined as the version of the document....

The literals description includes `string` but the table does not. It would be good to clarify whether single and/or double quotes are supported for strings. https://github.com/OAI/sig-workflows/blob/main/versions/1.0.0.md#literals

It appears that in the OpenAPI spec we did a particularly bad job of specifying how to use $statusCode in an expression. Most of the examples in workflows treat statusCode...

https://github.com/OAI/sig-workflows/blob/main/versions/1.0.0.md#fixed-fields-4 The successCriteria property is a list of Criterion Objects that all must be satisfied. It might be worthwhile providing some guidance as to when to use an AND (&&)...

Is this ``` - condition: $statusCode == 200 ``` the same as ``` - context: $statusCode condition: 200 type: simple ``` ? If so, what is the value of `type`...