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

Review Draft Publication: June 2019 #767

Merged
merged 1 commit into from Jun 19, 2019
Merged

Conversation

annevk
Copy link
Member

@annevk annevk commented Jun 17, 2019

A Review Draft for this Workstream will be published shortly, by merging this pull request.

Under the WHATWG IPR Policy, Participants may, within 45 days after publication of a Review Draft, exclude certain Essential Patent Claims from the Review Draft Licensing Obligations. See the IPR Policy for details.

@domenic domenic merged commit b5eac4d into master Jun 19, 2019
@domenic domenic deleted the review-draft-2019-06-17 branch June 19, 2019 05:08
@domenic
Copy link
Member

domenic commented Jun 19, 2019

@foolip
Copy link
Member

foolip commented Mar 2, 2020

This URL will be updated in-place, so since we don't have the build output in version control I've made sure the Wayback Machine has a copy:
https://web.archive.org/web/20200302174446/https://dom.spec.whatwg.org/review-drafts/2019-06/

It (add id_ to URL) currently matches the live URL byte-for-byte.

@foolip
Copy link
Member

foolip commented Mar 10, 2020

https://dom.spec.whatwg.org/review-drafts/2019-06/ has been updated in-place now, thanks @sideshowbarker!

@domenic
Copy link
Member

domenic commented Mar 10, 2020

Hmm. The logo ordering and fonts don't match the agreement.

@annevk
Copy link
Member Author

annevk commented Mar 10, 2020

The agreement doesn't spell out an ordering as far as I can tell. The sample has them (WHATWG DOM, W3C) and this publication has them (W3C, WHATWG DOM), but I think either is okay per the agreement.

@domenic
Copy link
Member

domenic commented Mar 10, 2020

True, I meant the sample, which is linked to as part of the agreement.

@sideshowbarker
Copy link
Contributor

sideshowbarker commented Mar 10, 2020

The logo ordering was simply due to the way I initially appended the W3C logo in from the Python script I wrote. I think that’s just how it ended up when I did the first pass, and it seemed to look fine — and it had the effect of not moving the DOM logo but instead just leaving in the same position relative to the margins — so I just kept it like that in the https://domspec.herokuapp.com/ output that I gave to the W3C as the basis for the CR transition request, and there was no request from the W3C side about moving it. So it ended up just staying there.

But anyway in hindsight I should’ve somewhere noted that as a difference from the MoU sample.

Going forward, for the HTML CR draft, I can ensure that the logos follow the order in the MoU sample. Or else if we actually prefer the logos in the same order was what we ended up with for DOM, we can make them follow that order for HTML, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants