-
Notifications
You must be signed in to change notification settings - Fork 46
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
Revert #478, remove inconsistent wording about special characters #548
Comments
Dear @Dave-Allured Thanks for raising this issue. It is relevant to #528 and discussion 323, so I've flagged it in both. Since the proposal to add this sentence was accepted as an Best wishes Jonathan |
@JonathanGregory, thanks for switching the label. That is fine with me. |
I supported inclusion of the text now suggested to be removed. The anticipated main use case that was to create a mechanism for adding localization language tags to attribute names. But as the conversation over in that issue has moved forward in a different issue see here and subsequent comments. Hence I support this proposal to remove the sentence rather than trying to improve it. This has the advantage variable names and attribute names will use the same character set. |
I too support this proposal, for the same reasons as Lars. This issue has sufficient support to be accepted in three weeks, on 30th November, if no-one raises concerns by then. |
Moderator
TBD
Associated pull request
#549
Detailed Proposal
Revert PR #478. Remove this single line from section 2.3, Naming Conventions:
"ASCII period (.) and ASCII hyphen (-) are also allowed in attribute names only."
This line was based on my misunderstanding of an earlier version of 2.3 paragraph 1. That paragraph was later clarified by PR #526, which now says that character restrictions are a recommendation, not a requirement. Therefore this new sentence is redundant and confusing.
The text was updated successfully, but these errors were encountered: