Preparation for REC #2554
Preparation for REC #2554
Conversation
|
Obviously, this PR should not be merged until we have a final publication date... |
| <main> | ||
| <!-- The data-erratalabel should include one label that filters the errata --> | ||
| <section data-erratalabel="Spec-Overview"> | ||
| <h1>Open Errata on the “EPUB 3 Overview” Working Group Note</h1> |
There was a problem hiding this comment.
Do we need errata for notes? Isn't it faster to just fix and republish them since they don't have the same involved update process as REC-track documents?
(Just thinking it might make for a less busy page.)
There was a problem hiding this comment.
I am a bit neutral about it... and would like to hear the reaction of the chairs.
My only reason to include it (apart from the fact that it does not cost anything to do it:-) is that, I presume, the new WG will not meet that frequently, so a number of errata may pile up between two calls, and this mechanism may help us keeping track of those.
There was a problem hiding this comment.
the new WG will not meet that frequently, so a number of errata may pile up between two calls
Doesn't the WG have to agree to publish errata, though? I thought the sticking point for REC-track documents was getting them republished, so publishing errata is quicker, whereas notes we can freely revise and republish once we know what needs changing?
There was a problem hiding this comment.
It is all true. But will we look at the possible errata frequently? That is really the issue.
Again, I am not against removing the note references, but I would like to see how Wendy & Co imagine running the show...
There was a problem hiding this comment.
The only notes I see potentially receiving attention are the accessibility related ones, particularly as we approach EAA. I'm ok with errata and keeping track, but we can always revise the process if it becomes arduous?
There was a problem hiding this comment.
Yes, we can touch that whenever we want.
So let us leave it as is now.
|
Should we also do something about https://www.w3.org/publishing/epub3/ ? |
Co-authored-by: Matt Garrish <mattgarrish@users.noreply.github.com>
Yes, we will have to. But that should be a separate issue somwhere; it cannot be handled in a PR on this repository. It is a matter of changing the .htaccess file in the /publishing page (I will have to look at that). |
This is a preparation for the REC publication
Preview | Diff