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

Define WebDriver as living #930

Merged
merged 1 commit into from Nov 2, 2018

Conversation

Projects
None yet
5 participants
@andreastt
Copy link
Contributor

andreastt commented Oct 6, 2018

WebDriver exists in two versions:

  1. as a W3C recommendation published at https://www.w3.org/TR/webdriver/, also known as WebDriver Level 1,
  2. and as a living document published at https://w3c.github.io/webdriver/, known as WebDriver, which is what browser vendors implement.

@andreastt andreastt force-pushed the andreastt:webdriver-url branch from b8d1d10 to 4259b18 Oct 7, 2018

@ExE-Boss
Copy link
Contributor

ExE-Boss left a comment

🤦🏻‍♂️ The W3C doesn’t publish Living Standards, that’s the WHATWG’s job.

Show resolved Hide resolved macros/SpecData.json
"url": "https://w3c.github.io/webdriver/",
"status": "Living"
},
"WebDriver Level 1": {

This comment has been minimized.

@ExE-Boss

ExE-Boss Oct 17, 2018

Contributor

This is just WebDriver.

This comment has been minimized.

@andreastt

andreastt Oct 17, 2018

Contributor

There’s a difference between https://www.w3.org/TR/webdriver1/ and https://w3c.github.io/webdriver/, and it’s useful to be able to reference both.

The former recommendation is a timestamped dump for legal reasons and does not reflect the reality of existing implementations. The latter is an evolving document that accurately tracks and reflects reality in WebDriver implementations.

This comment has been minimized.

@Elchi3

Elchi3 Nov 1, 2018

Member

The former recommendation is a timestamped dump for legal reasons and does not reflect the reality of existing implementations.

How relevant is such a document to web developers then? I've heard from different standards people that MDN should stop referencing outdated specs. Why should we do this for WebDriver?

This comment has been minimized.

@andreastt

andreastt Nov 1, 2018

Contributor

I’m not aware of anyone referencing level 1 on MDN.

This comment has been minimized.

@Elchi3

Elchi3 Nov 1, 2018

Member

Then we shouldn't add this here so that people can't reference it. Or am I misunderstanding something?

This comment has been minimized.

@andreastt

andreastt Nov 1, 2018

Contributor

I thought this was a bibliography of specifications you could reference, like https://www.specref.org/, but if you want to limit the selection for MDN I can remove the level 1 entry?

This comment has been minimized.

@Elchi3

Elchi3 Nov 1, 2018

Member

This spec list is not meant to be exhaustive like specref. My understanding is that it only collects the specs that can and should be referenced from MDN pages. We have removed dated specs in the past. See #284 and #220 for previous efforts to get rid of outdated specs. I'd like to avoid the situation in which we have to edit lots of wiki pages to remove dated specs by not allowing them in the first place.

So, yes, imo, we should remove the level 1 entry.

@andreastt

This comment has been minimized.

Copy link
Contributor

andreastt commented Oct 17, 2018

🤦🏻‍♂️ The W3C doesn’t publish Living Standards, that’s the WHATWG’s job.

W3C does allow WGs to publish living documents. These are timestamped and dumped into www.w3.org/TR/ when we put a snapshot through the recommendation track.

The “Editor’s Draft” banner on https://w3c.github.io/webdriver/ is misleading because it no longer contains the “Living Document” subtitle. This is a mistake which I’ve rectified in https://github.com/w3c/webdriver/pull/1318/files.

@andreastt andreastt force-pushed the andreastt:webdriver-url branch 2 times, most recently from 4b91901 to baf9efb Oct 19, 2018

@andreastt

This comment has been minimized.

Copy link
Contributor

andreastt commented Oct 25, 2018

I got a confirmation from Mike Smith at W3C today that there is no reason WebDriver is marked as “Editor’s Draft”, and that we should file relevant bugs to introduce a “Living Standard” badge into ReSpec.

@wbamberg wbamberg added the json-data label Oct 26, 2018

@andreastt

This comment has been minimized.

Copy link
Contributor

andreastt commented Oct 30, 2018

w3c/webdriver#1327 has now also landed on WebDriver, which marks it as a Living Document (LD) in ReSpec as well. The effect of this is that it dumps the Editor’s Draft banner on the left hand side.

cc @sideshowbarker

@sideshowbarker

This comment has been minimized.

Copy link
Contributor

sideshowbarker commented Nov 1, 2018

🤦🏻‍♂️ The W3C doesn’t publish Living Standards, that’s the WHATWG’s job.

Not true

@sideshowbarker

This comment has been minimized.

Copy link
Contributor

sideshowbarker commented Nov 1, 2018

🤦🏻‍♂️ The W3C doesn’t publish Living Standards, that’s the WHATWG’s job.

W3C does allow WGs to publish living documents. These are timestamped and dumped into www.w3.org/TR/ when we put a snapshot through the recommendation track.

Correct

@andreastt andreastt force-pushed the andreastt:webdriver-url branch from baf9efb to 457c1e7 Nov 1, 2018

@andreastt andreastt changed the title Define WebDriver as living and add entry for level 1 rec Define WebDriver as living Nov 1, 2018

@Elchi3

Elchi3 approved these changes Nov 2, 2018

Copy link
Member

Elchi3 left a comment

Thanks @andreastt 👍 Looks good to me now.

@Elchi3 Elchi3 merged commit ce062cb into mdn:master Nov 2, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment