We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the following sections describing abstract roles, it is clear that authors MUST NOT use them in content:
Abstract Roles
Content authors MUST NOT use abstract roles because they are not implemented in the API binding.
List of Abstract Roles
Authors MUST NOT use abstract roles in content.
However, the Note in the definition for each abstract role says "should not" instead of "MUST NOT":
Authors should not use this role in content.
Is there a reason for this inconsistency? Are "Notes" non normative? (and even if they are, wouldn't it be clearer to use "must not" in the Note?)
Another inconsistency:
The text was updated successfully, but these errors were encountered:
Remove text from Note, make consistent
Sorry, something went wrong.
carmacleod
Successfully merging a pull request may close this issue.
In the following sections describing abstract roles, it is clear that authors MUST NOT use them in content:
Abstract Roles
List of Abstract Roles
However, the Note in the definition for each abstract role says "should not" instead of "MUST NOT":
Is there a reason for this inconsistency? Are "Notes" non normative? (and even if they are, wouldn't it be clearer to use "must not" in the Note?)
Another inconsistency:
The text was updated successfully, but these errors were encountered: