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

changes for process 2021 style #307

Merged
merged 4 commits into from
Oct 26, 2021
Merged

changes for process 2021 style #307

merged 4 commits into from
Oct 26, 2021

Conversation

himorin
Copy link
Contributor

@himorin himorin commented Oct 5, 2021


Preview | Diff

@himorin himorin self-assigned this Oct 5, 2021
@himorin
Copy link
Contributor Author

himorin commented Oct 5, 2021

w3cid : The editors'/authors' names must be listed, with attribute data-editor-id="@@".
from https://www.w3.org/pubrules/doc/rules/?profile=WG-NOTE#editorSection

@r12a
Copy link
Contributor

r12a commented Oct 5, 2021

I believe that the id has to be present ONLY for those people who are likely to actually publish the document, rather than for all editors (which probably means just you and me). Do you know of any other reason for posting people's ids?

@himorin
Copy link
Contributor Author

himorin commented Oct 6, 2021

I totally have no idea on w3cid restriction...

@r12a
Copy link
Contributor

r12a commented Oct 6, 2021

I'll ask Denis for clarification.

@himorin
Copy link
Contributor Author

himorin commented Oct 14, 2021

discussed with @kidayasuo for a while,,, how about to move ones actively worked at the development of 2nd edition to authors?

@r12a
Copy link
Contributor

r12a commented Oct 14, 2021

Mm. Then we'd have the possibly tricky problem of deciding in some cases who is an author and who is an editor, unless everyone is added to the author list, and editors (defined as people who work on the HTML) are added to both lists.

I originally thought we could keep things simple by not adding unnecessary information to the source, but i fear that splitting the information would only increase the administrative work for us. Maybe it's best just to add everyone's w3cid, after all, and leave things as they are?? I don't imagine that we have to worry about anyone on the list unexpectedly publishing the document.

@kidayasuo
Copy link
Contributor

@r12a I tend to agree. I do not like the idea of dividing people based on if they have w3cid. Can we change the document system if it mandates the w3cid that not necessarily all have? What is the benefit of the work of finding past editors' contact emails, writing them and asking a favour of creating a w3cid which was not necessary at the time they participated? They might not be reachable or they do not respond to the email quickly.

@r12a
Copy link
Contributor

r12a commented Oct 15, 2021

Let me check with the webmaster.

@himorin
Copy link
Contributor Author

himorin commented Oct 18, 2021

confirmed working with pubrules.
remaining errors are followings, both of which are duplicated between en and ja. So I'll add another commit to change ja one like with adding j at the last (e.g. d8e1224j)

  • Duplicate ID “d8e1224”.
  • Duplicate ID “d8e1230”.

@himorin himorin changed the title [WIP] changes for process 2021 style changes for process 2021 style Oct 19, 2021
@himorin himorin requested review from kidayasuo and r12a October 19, 2021 11:57
@himorin
Copy link
Contributor Author

himorin commented Oct 19, 2021

requesting review with this. I confirm this could pass updated pubrules.

Copy link
Contributor

@kidayasuo kidayasuo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good. thank you for updating the document, esp. working on getting w3cid.

@himorin himorin merged commit 645d781 into w3c:gh-pages Oct 26, 2021
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 this pull request may close these issues.

3 participants