W3C home > Mailing lists > Public > public-browser-tools-testing@w3.org > April to June 2012

CfC: publish FPWD of WebDriver; deadline June 27

From: Michael[tm] Smith <mike@w3.org>
Date: Wed, 20 Jun 2012 14:51:01 +0900
To: public-browser-tools-testing@w3.org
Cc: Simon Stewart <shs@google.com>, David Burns <dburns@mozilla.com>, Philippe Le Hegaret <plh@w3.org>, Wilhelm Joys Andersen <w@wja.no>
Message-ID: <20120620055058.GA10338@sideshowbarker>
This is a Call for Consensus (CfC) to publish a First Public Working Draft
(FPWD) of the WebDriver specification:


Please send all responses, questions, or comments regarding this CfC to the
public-browser-tools-testing@w3.org mailing list by June 27. Note that
silence will be considered agreement with the proposal to publish.

If you support publication, a positive response on the mailing list (e.g.,
"I/My organization supports FPWD publication of this spec.") is preferred
and encouraged, but not required.


  This specification defines the WebDriver API, a platform-and
  language-neutral interface that allows programs or scripts to introspect
  into, and control the behaviour of, a web browser. The WebDriver API is
  primarily intended to allow developers to write tests that automate a
  browser from a separate controlling process, but may also be implemented
  in such a way as to allow in-browser scripts to control a (separate?)

  The WebDriver API is defined by a set of interfaces to discover and
  manipulate DOM elements on a page, and to control the behaviour of the
  containing browser.

  This specification also includes a non-normative reference serialisation
  (to JSON) of the interface's invocations and responses that may be useful
  for browser vendors.

This CfC satisfies the group's requirement to "record the group's  
decision to request advancement".

By publishing this FPWD, the group sends a signal to the community to 
begin reviewing the document. The FPWD reflects where the group is on 
this specification at the time of publication; it does not necessarily 
mean there is consensus on the specification's contents.


Michael[tm] Smith http://people.w3.org/mike
Received on Wednesday, 20 June 2012 05:51:14 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 12 February 2015 15:39:01 UTC