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

[simple-ruby] Normativeness #2

Closed
r12a opened this issue Feb 13, 2019 · 2 comments · Fixed by w3c/jlreq#202
Closed

[simple-ruby] Normativeness #2

r12a opened this issue Feb 13, 2019 · 2 comments · Fixed by w3c/jlreq#202
Assignees

Comments

@r12a
Copy link
Contributor

r12a commented Feb 13, 2019

The document will be published as a Note, so there is iiuc no normative aspect to the document.

Therefore we should remove the statements about normativeness from the start of sections 2 and 4, and collapse the references into a single section.

@frivoal
Copy link

frivoal commented Feb 18, 2019

On the one hand, you're right. On the other hand, it seemed useful to me to distinguish between the body of the text that describes the logic, and pieces of commentary about it. The normative/non-normative distinction offered by respec (and implied in notes) seemed right for that.

I could removed the informativeness statements in section 2 and 4, but the notes would remain "non-normative", and I think the reference section would therefore not be collapsed.

@r12a
Copy link
Contributor Author

r12a commented Mar 26, 2020

It should be possible to retain a distinction between different types of text without using the normative/non-normative terminology. I don't think that's appropriate here.

frivoal referenced this issue in frivoal/jlreq Apr 3, 2020
The whole document is a note, so nothing is normative. These messages
are therefore confusing.

Closes #25
frivoal referenced this issue in frivoal/jlreq Apr 3, 2020
The whole document is a note, so nothing is normative. These messages
are therefore confusing.

Closes #25
frivoal referenced this issue in w3c/jlreq Apr 3, 2020
The whole document is a note, so nothing is normative. These messages
are therefore confusing.

Closes #25
@r12a r12a transferred this issue from w3c/jlreq Apr 3, 2020
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

Successfully merging a pull request may close this issue.

2 participants