Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing assertion markup in 7.3.2? #348

Closed
mmccool opened this issue Jun 14, 2022 · 1 comment
Closed

Missing assertion markup in 7.3.2? #348

mmccool opened this issue Jun 14, 2022 · 1 comment

Comments

@mmccool
Copy link
Contributor

mmccool commented Jun 14, 2022

The following sentence in section 7.3.2 is not marked as an assertion:

If the missing feature is to customize existing functionality of an API,
the server will respond with 501 (Not Implemented) HTTP status.

Not being marked as an assertion seems out of place, and the use of "will" sounds like it should be "MUST".

@mmccool mmccool changed the title Missing assertion markup? Missing assertion markup in 7.3.2? Jun 14, 2022
@mmccool
Copy link
Contributor Author

mmccool commented Jun 27, 2022

There is normative content elsewhere in the doc that covers what this says, so this is not an assertion itself. Closing, nothing needs to be changed (although maybe we can clean up the wording in an editorial pass later).

@mmccool mmccool closed this as completed Jun 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant