-
Notifications
You must be signed in to change notification settings - Fork 200
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
Add boilerplate for Browser Testing and Tools Working Group #1682
Add boilerplate for Browser Testing and Tools Working Group #1682
Conversation
This is intended to match the existing wording and links in https://w3c.github.io/webdriver/ exactly.
This is to enable w3c/webdriver#1462. However, I have my doubts that LD is a status we should use here. It results in https://www.w3.org/StyleSheets/TR/2016/W3C-LD being used as stylesheet, and that's 404. @AutomatedTester @sideshowbarker what should be the statuses of tip-of-tree https://w3c.github.io/webdriver/ and https://w3c.github.io/webdriver-bidi/? I'd like to include the template text for those statuses at least. |
My best guess is Editor's Draft and Unofficial Draft, respectively. |
That could be considered WD since the same revision of the document is also auto-published to https://www.w3.org/TR/webdriver/ Personally, I would label it Editor’s Draft. I don’t know what the difference between Editor’s Draft and Unofficial Draft is supposed to be, but as far as I can see, there is no policy at the W3C for labeling anything as an Unofficial Draft — and we have many precedents of the label Editor’s Draft being used for documents which haven’t yet been formally adopted as deliverables by any working groups, nor published yet as Working Drafts. |
Yeah, UD is (unofficially, appropriate enough) often used as an "even less official" editor's draft, for things that shouldn't be read as having any blessing from the WG.
Whatever the stylesheet is that should be used for LDs, we can fix that in bikeshed. What URL shoudl it use? |
I've updated to have WD and ED templates instead now. Note that this depends on w3c/webdriver#1511 for the "WD matches https://www.w3.org/TR/webdriver/" claim in the description to be 100% true, as the placement of |
@AutomatedTester, @sideshowbarker and I discussed a bit on IRC and concluded that the ED+WD boilerplate is OK, no need for LD. I'll squash the PR to clean up the history. |
Per discussion in speced/bikeshed#1682. This is mainly to minimize changes in #1462.
Per discussion in speced/bikeshed#1682. This is mainly to minimize changes in #1462.
WD matches https://www.w3.org/TR/webdriver/ ED matches wording and order of many other status-ED.include
eb40872
to
bb19275
Compare
No need to squash the PR, btw; I squash at the merge anyway. |
As a side, the Process CG just started to get interested in designing the boilerplates for Process 2020 documents, especially the CR Draft and CR Snapshot), which may be used the LD-like documents. So, if the CG ends up with some of the required boilerplates that is inappropriate for a LD-type document, please don't hesitate to say so. |
WD matches https://www.w3.org/TR/webdriver/
ED matches wording and order of many other status-ED.include