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

Errata link should be optional; can be inline #1665

Closed
svgeesus opened this issue Nov 2, 2022 · 3 comments · Fixed by #1680
Closed

Errata link should be optional; can be inline #1665

svgeesus opened this issue Nov 2, 2022 · 3 comments · Fixed by #1680
Assignees

Comments

@svgeesus
Copy link
Contributor

svgeesus commented Nov 2, 2022

Pubrules requires an errata link for Recommendations:

Errata - URI to an errata document for any errors or issues reported since publication. See also suggestions on errata page structure in the Manual of Style. Note: Do not put the errata document in TR space as the expectation is that we will not modify document in TR space after publication; see the policy for in-place modification of W3C Technical Reports.

However, we now have the option of Recommendation with Candidate/Proposed Corrections, which are effectively inline Errata.

@frivoal suggested to me that it should be possible to use alternate wording:

Yeah, that’s annoying. Do you think you could file a bug against pubrules, to get them to accept a sentence like ”<a href="https://www.w3.org/Consortium/Process/#errata">errata will be tracked inline in this document” as an alternative to the link?

@jennyliang220
Copy link
Contributor

Hi @plehegar , is it ok for Pubrules to add the errata description?
cc @deniak

@deniak
Copy link
Member

deniak commented Nov 3, 2022

We actually have a way to distinguish regular RECs to RECs with Candidate/Proposed changes. I think it makes sense to make the errata optional for the latter.

@plehegar
Copy link
Member

This makes sense to me.

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.

4 participants