Update README.md

Author: Julian

README.md

@@ -6,8 +6,8 @@ validation libraries can use to test their validators.
 
 It is meant to be language agnostic and should require only a JSON parser.
 
-The conversion of the JSON objects into your test framework of choice (say,
-an `xUnit`) is still the job of the validator implementor.
+The conversion of the JSON objects into tests within your test framework of choice
+is still the job of the validator implementor.
 
 Structure of a Test
 -------------------
@@ -19,15 +19,17 @@ Inside that directory is a subdirectory for each draft or version of the
 schema. We'll use `draft3` as an example.
 
 If you look inside the draft directory, there are a number of `.json` files,
-which logically group a set of test cases together.
+which logically group a set of test cases together. Often the grouping is by
+property under test, but not always, especially within optional test files
+(discussed below).
 
 Inside each `.json` file is a single array containing objects. It's easiest to
 illustrate the structure of these with an example:
 
 ```json
     {
         "description": "the description of the test case",
-        "schema": "the schema that should be validated against",
+        "schema": {"the schema that should" : "be validated against"},
         "tests": [
             {
                 "description": "a specific test of a valid instance",
@@ -50,11 +52,9 @@ they should be valid or invalid.
 Coverage
 --------
 
-The coverage of this suite is actively growing. The first order of business is
-to have a full-coverage draft 3 test suite.
+Currently, draft 3 should have essentially full coverage for the core schema.
 
-Ultimately, when it's done, the idea is to attempt to have it included on [the
-JSON Schema website](http://www.json-schema.org).
+The beginnings of draft 4 are underway.
 
 Who Uses the Test Suite
 -----------------------
@@ -71,18 +71,4 @@ the list :).
 Contributing
 ------------
 
-I need help! If you'd like to contribute, please fork this repository. I'd love
-to have your pull requests sent over.
-
-Right now, the way I'm compiling the tests is by porting over a test suite
-that I'd written for a Python validator. The tests (in a messy format) can be
-found [here](https://github.com/Julian/jsonschema/blob/master/tests.py#L100).
-
-There are also other JSON Schema test suites for various other validators, and
-it would certainly be nice to merge all of them as well. In particular, [this
-validator](https://github.com/fge/json-schema-validator/tree/master/src/test/resources/keyword)
-contains a set of tests already written in JSON which will be useful.
-
-I'm perfectly fine with contributions either porting from one of those, or
-being written from scratch, so feel free to do what you're comfortable with as
-long as the tests are easy to understand and correct :).
+If you see something missing or incorrect, a pull request is most welcome!