You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specification: for example "Can you send me your specification?" (may be abbreviated less formally as "spec")
It seems like this either refers to an older use of terms when it was ok to call a "definition" a "specification". Or if it really means that I am asking somebody to send me the OpenAPI specification, then this may not be the most helpful example. What about:
Specification: for example "My OpenAPI document conforms to the OpenAPI specification version 3.1.0"
The text was updated successfully, but these errors were encountered:
We should definitely add "OpenAPI Description" (OAD) to the style guide as that's what we settled on calling the things that people write that conform to the OpenAPI Specification (OAS). We have an official glossary that defines these terms and the style guide should match its usage. The 3.0.4, 3.1.1, and 3.20 releases will use OpenAPI Description and OAD in their text.
Currently the README contains this:
It seems like this either refers to an older use of terms when it was ok to call a "definition" a "specification". Or if it really means that I am asking somebody to send me the OpenAPI specification, then this may not be the most helpful example. What about:
The text was updated successfully, but these errors were encountered: