Clarifications on api-name, filenames and servers object #332
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
Missing guideline for file names of API definition files, indirect definition of
api-name
variable.This PR adds the definition of api-name to Common Vocabulary and Acronyms and clarifies the name of API definition files and servers object content
Which issue(s) this PR fixes:
Fixes #298 #284
Does this PR introduce a breaking change?
Special notes for reviewers:
Do we need similar definition of 'api-version'?
JSON format is not currently used in any subproject, should the file extension .json be removed?
Changelog input
Additional documentation