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.

Sign up for GitHub

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

Jump to bottom

Ruby Markup Coordination #14

Merged
merged 17 commits into from
Feb 10, 2022
Merged

Ruby Markup Coordination #14

Show file tree
Hide file tree
Changes from 11 commits
Commits
Show all changes
17 commits
Select commit Hold shift + click to select a range
e294152
Copy text from https://github.com/whatwg/sg/issues/184#issuecomment-9…
frivoal Jan 16, 2022
eee3c7f
Line break the text for easier editing
frivoal Jan 16, 2022
94bae1f
Minor tweaks to adjust the text to its new context
frivoal Jan 16, 2022
a8159b6
Add hyperlinks and abbr title
frivoal Jan 16, 2022
0528c9d
Convert to HTML
frivoal Jan 16, 2022
450d562
Link to the ruby agreement from the README
frivoal Jan 16, 2022
4b19b99
Replace third paragraph
frivoal Jan 20, 2022
38ea6fd
Clarify the goal of pull requests
frivoal Jan 26, 2022
68c5be5
Phrasing tweak on merging PRs
frivoal Jan 26, 2022
7058941
Clarify that this is based on the PR instead of being defined by the PR
frivoal Jan 26, 2022
d654a1d
Phrasing tweak about using the REC track
frivoal Jan 26, 2022
9f476af
Fix typo
frivoal Jan 27, 2022
8e5b44e
Update date in presumed URL
Feb 1, 2022
5fefa6f
Convert leftover markdown to actual html
frivoal Feb 6, 2022
3f67a42
Adopt the rewording proposed by foolip
frivoal Feb 6, 2022
1f3830a
Credit both sources of this work
frivoal Feb 9, 2022
bc3b69a
Merge second and third paragraphs
frivoal Feb 9, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,4 @@

* [Memorandum of Understanding Between W3C and WHATWG](https://www.w3.org/2019/04/WHATWG-W3C-MOU.html)
* [Update, 30 June 2021](https://www.w3.org/2021/06/WHATWG-W3C-MOU_2021_update.html)
* [Agreement on HTML Ruby Markup](https://www.w3.org/2022/01/ruby-agreement)
5 changes: 5 additions & 0 deletions ruby/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# Agreement on HTML Ruby Markup

This directory contains:

* an exact copy of the Agreement on HTML Ruby Markup
43 changes: 43 additions & 0 deletions ruby/ruby-agreement.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
<!doctype html>
<html lang="en">
<meta charset="utf-8">
<meta name="viewport" content="width=device-width">
<title>Agreement on HTML Ruby Markup</title>
<style>
body {
max-width: 50em;
margin: auto;
font-family: sans-serif;
}
</style>

<h1>Agreement on HTML Ruby Markup</h1>

<p>
The W3C will specify extended HTML Ruby markup
Copy link
Member

Choose a reason for hiding this comment

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

This should read:

The W3C has the option to specify extended HTML Ruby markup

since we can't commit to do this without proper AC Review of the charter and HTML Working Group approval.

Copy link

Choose a reason for hiding this comment

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

@plehegar Can we just switch “will” to “may” here rather than complicating the phrasing?

Copy link
Member

Choose a reason for hiding this comment

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

sure

Copy link
Contributor Author

Choose a reason for hiding this comment

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

See #15

(based on in <a href="https://github.com/whatwg/html/pull/6478">PR#6478</a>)
frivoal marked this conversation as resolved.
Show resolved Hide resolved
under the <a href="https://www.w3.org/Consortium/Process/#rec-track">REC track</a>.
The W3C and WHATWG believe this is within the bounds of our <a href="https://www.w3.org/2019/04/WHATWG-W3C-MOU">MoU</a>,
and while it is not the ideal outcome
(having Ruby documented in two places),
we understand that it serves the goals for the W3C’s constituencies and existing implementations
to have an easily referencable document
as well as honoring the strict <a href="https://whatwg.org/working-mode#additions">requirements of the WHATWG</a>
that the living standard not contain new additions
that don’t have multi-browser-engine implementer commitments.

<p>
The <abbr title="Status Of This Document">SOTD</abbr> section of the W3C Ruby Extension spec
will state our joint intention
that the extended ruby markup definitions be fully integrated into the <a href="https://html.spec.whatwg.org/multipage/">WHATWG HTML specification</a>
once they <a href="https://whatwg.org/faq#adding-new-features">meet WHATWG’s inclusion criteria</a>
under section <a href="https://www.w3.org/2019/04/WHATWG-W3C-MOU#forking">10.2 of the 2019 MOU</a>.

<p>
W3C editors may offer pull requests to keep the HTML spec in sync,
both technically and editorially,
for the subset of features defined in both specs,
so that readers of both specs can benefit from any improvements.
WHATWG HTML editors will review these contributions in good faith,
and merge those they deem acceptable
under the WHATWG [working mode](https://whatwg.org/working-mode).