json-schema-openc-fork 0.0.1

checksums.yaml

@@ -0,0 +1,15 @@
+---
+!binary "U0hBMQ==":
+  metadata.gz: !binary |-
+    MDQ1ZDEyOTcxZmRjYmU4MmU5YzE1NmUzODJhZjI5MzYxODk2MzI0MQ==
+  data.tar.gz: !binary |-
+    ODU3N2JiZjVkMGZiZDUwZjYzYmY2ZmViYjc1ZTViZTRmMzg2MTM0ZA==
+SHA512:
+  metadata.gz: !binary |-
+    YTc2NGY3YmNiMTNiYzMwYTJiNWIyZGQwMjA0N2MxNzczMTFjZWJiMGI0OTY1
+    MDg0MzBkOTRiMWYwNzZkNGExZGRiMDM1Y2Y5NjAyOGJkMGMwYmNiMmM3NmU3
+    NDlkMDkzZjE4NDM0OTI3NjA1NWIyOGMwNGVkZWYzMjI2OWJlM2Q=
+  data.tar.gz: !binary |-
+    ZGQ5ZjhmNTcyZGU5YTE3MGIxNTcwNjgwZTQ4MTBlMzk0YmYwMjkwODcwNTIx
+    Mjc4NjM1OTZkYjgwZjU5OGUxZWYzNWUzZThhOTcxNzU0YmI1ZWE0M2FkZjI1
+    YzRiN2M2ZWU5MmEyNjVhOGQwZGYyYzRiMTY0ZDJiZjllNjdlZjM=

data/LICENSE.md

@@ -0,0 +1,19 @@
+Copyright (c) 2010-2011, Lookingglass Cyber Solutions
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.textile

@@ -0,0 +1,452 @@
+!https://travis-ci.org/ruby-json-schema/json-schema.svg?branch=master!:https://travis-ci.org/ruby-json-schema/json-schema
+!https://codeclimate.com/github/ruby-json-schema/json-schema/badges/gpa.svg!:https://codeclimate.com/github/ruby-json-schema/json-schema
+
+h1. Ruby JSON Schema Validator
+
+This library is intended to provide Ruby with an interface for validating JSON objects against a JSON schema conforming to "JSON Schema Draft 4":http://tools.ietf.org/html/draft-zyp-json-schema-04. Legacy support for "JSON Schema Draft 3":http://tools.ietf.org/html/draft-zyp-json-schema-03, "JSON Schema Draft 2":http://tools.ietf.org/html/draft-zyp-json-schema-02, and "JSON Schema Draft 1":http://tools.ietf.org/html/draft-zyp-json-schema-01 is also included.
+
+h2. Additional Resources
+
+* "Google Groups":https://groups.google.com/forum/#!forum/ruby-json-schema
+* #ruby-json-schema on chat.freenode.net
+
+h2. Version 2.0.0 Upgrade Notes
+
+Please be aware that the upgrade to version 2.0.0 will use Draft-04 *by default*, so schemas that do not declare a validator using the <code>$schema</code> keyword will use Draft-04 now instead of Draft-03. This is the reason for the major version upgrade.
+
+h2. Installation
+
+From rubygems.org:
+
+<pre>
+gem install json-schema
+</pre>
+
+From the git repo:
+
+<pre>
+$ gem build json-schema.gemspec
+$ gem install json-schema-2.5.0.gem
+</pre>
+
+
+h2. Usage
+
+Three base validation methods exist: <code>validate</code>, <code>validate!</code>, and <code>fully_validate</code>. The first returns a boolean on whether a validation attempt passes and the second will throw a <code>JSON::Schema::ValidationError</code> with an appropriate message/trace on where the validation failed. The third validation method does not immediately fail upon a validation error and instead builds an array of validation errors return when validation is complete.
+
+All methods take two arguments, which can be either a JSON string, a file containing JSON, or a Ruby object representing JSON data. The first argument to these methods is always the schema, the second is always the data to validate. An optional third options argument is also accepted; available options are used in the examples below.
+
+By default, the validator uses the "JSON Schema Draft 4":http://tools.ietf.org/html/draft-zyp-json-schema-04 specification for validation; however, the user is free to specify additional specifications or extend existing ones. Legacy support for Draft 1, Draft 2, and Draft 3 is included by either passing an optional <code>:version</code> parameter to the <code>validate</code> method (set either as <code>:draft1</code> or <code>draft2</code>), or by declaring the <code>$schema</code> attribute in the schema and referencing the appropriate specification URI. Note that the <code>$schema</code> attribute takes precedence over the <code>:version</code> option during parsing and validation.
+
+h3. Validate Ruby objects against a Ruby schema
+
+For further information on json schema itself refer to <a href="http://spacetelescope.github.io/understanding-json-schema/">Understanding JSON Schema</a>.
+
+<pre>
+require 'rubygems'
+require 'json-schema'
+
+schema = {
+  "type" => "object",
+  "required" => ["a"],
+  "properties" => {
+    "a" => {"type" => "integer"}
+  }
+}
+
+data = {
+  "a" => 5
+}
+
+JSON::Validator.validate(schema, data)
+</pre>
+
+h3. Validate a JSON string against a JSON schema file
+
+<pre>
+require 'rubygems'
+require 'json-schema'
+
+JSON::Validator.validate('schema.json', '{"a" : 5}')
+</pre>
+
+h3. Validate a list of objects against a schema that represents the individual objects
+
+<pre>
+require 'rubygems'
+require 'json-schema'
+
+data = ['user','user','user']
+JSON::Validator.validate('user.json', data, :list => true)
+</pre>
+
+h3. Strictly validate an object's properties
+
+With the <code>:strict</code> option, validation fails when an object contains properties that are not defined in the schema's property list or doesn't match the <code>additionalProperties</code> property. Furthermore, all properties are treated as <code>required</code> by default.
+
+<pre>
+require 'rubygems'
+require 'json-schema'
+
+schema = {
+  "type" => "object",
+  "properties" => {
+    "a" => {"type" => "integer"},
+    "b" => {"type" => "integer"}
+  }
+}
+
+JSON::Validator.validate(schema, {"a" => 1, "b" => 2}, :strict => true)            # ==> true
+JSON::Validator.validate(schema, {"a" => 1, "b" => 2, "c" => 3}, :strict => true)  # ==> false
+JSON::Validator.validate(schema, {"a" => 1}, :strict => true)                      # ==> false
+</pre>
+
+h3. Catch a validation error and print it out
+
+<pre>
+require 'rubygems'
+require 'json-schema'
+
+schema = {
+  "type" => "object",
+  "required" => ["a"],
+  "properties" => {
+    "a" => {"type" => "integer"}
+  }
+}
+
+data = {
+  "a" => "taco"
+}
+
+begin
+  JSON::Validator.validate!(schema, data)
+rescue JSON::Schema::ValidationError
+  puts $!.message
+end
+</pre>
+
+
+h3. Fully validate against a schema and catch all errors
+
+<pre>
+require 'rubygems'
+require 'json-schema'
+
+schema = {
+  "type" => "object",
+  "required" => ["a","b"],
+  "properties" => {
+    "a" => {"type" => "integer"},
+    "b" => {"type" => "string"}
+  }
+}
+
+data = {
+  "a" => "taco"
+}
+
+errors = JSON::Validator.fully_validate(schema, data)
+
+# ["The property '#/a' of type String did not match the following type: integer in schema 03179a21-197e-5414-9611-e9f63e8324cd#", "The property '#/' did not contain a required property of 'b' in schema 03179a21-197e-5414-9611-e9f63e8324cd#"]
+</pre>
+
+h3. Fully validate against a schema and catch all errors as objects
+
+<pre>
+require 'rubygems'
+require 'json-schema'
+
+schema = {
+  "type" => "object",
+  "required" => ["a","b"],
+  "properties" => {
+    "a" => {"type" => "integer"},
+    "b" => {"type" => "string"}
+  }
+}
+
+data = {
+  "a" => "taco"
+}
+
+errors = JSON::Validator.fully_validate(schema, data, :errors_as_objects => true)
+
+# [{:message=>"The property '#/a' of type String did not match the following type: integer in schema 03179a21-197e-5414-9611-e9f63e8324cd#", :schema=>#<URI::Generic:0x103a76198 URL:03179a21-197e-5414-9611-e9f63e8324cd#>, :failed_attribute=>"Type", :fragment=>"#/a"}, {:message=>"The property '#/' did not contain a required property of 'b' in schema 03179a21-197e-5414-9611-e9f63e8324cd#", :schema=>#<URI::Generic:0x103a76198 URL:03179a21-197e-5414-9611-e9f63e8324cd#>, :failed_attribute=>"Properties", :fragment=>"#/"}]
+
+</pre>
+
+h3. Validate against a fragment of a supplied schema
+
+<pre>
+  require 'rubygems'
+  require 'json-schema'
+
+  schema = {
+    "type" => "object",
+    "required" => ["a","b"],
+    "properties" => {
+      "a" => {"type" => "integer"},
+      "b" => {"type" => "string"},
+      "c" => {
+        "type" => "object",
+        "properties" => {
+          "z" => {"type" => "integer"}
+        }
+      }
+    }
+  }
+
+  data = {
+    "z" => 1
+  }
+
+  JSON::Validator.validate(schema, data, :fragment => "#/properties/c")
+</pre>
+
+h3. Validate a JSON object against a JSON schema object, while also validating the schema itself
+
+<pre>
+require 'rubygems'
+require 'json-schema'
+
+schema = {
+  "type" => "object",
+  "required" => ["a"],
+  "properties" => {
+    "a" => {"type" => "integer"}  # This will fail schema validation!
+  }
+}
+
+data = {
+  "a" => 5
+}
+
+JSON::Validator.validate(schema, data, :validate_schema => true)
+</pre>
+
+h3. Validate a JSON object against a JSON schema object, while inserting default values from the schema
+
+With the :insert_defaults option set to true any missing property that has a
+default value specified in the schema will be inserted into the validated data. The inserted default value is validated hence catching a schema that specifies an invalid default value.
+
+<pre>
+require 'rubygems'
+require 'json-schema'
+
+schema = {
+  "type" => "object",
+  "required" => ["a"],
+  "properties" => {
+    "a" => {"type" => "integer", "default" => 42},
+    "b" => {"type" => "integer"}
+  }
+}
+
+# Would not normally validate because "a" is missing and required by schema,
+# but "default" option allows insertion of valid default.
+data = {
+  "b" => 5
+}
+
+JSON::Validator.validate(schema, data)
+# false
+
+JSON::Validator.validate(schema, data, :insert_defaults => true)
+# true
+# data = {
+#   "a" => 42,
+#   "b" => 5
+# }
+
+</pre>
+h3. Validate an object against a JSON Schema Draft 2 schema
+
+<pre>
+require 'rubygems'
+require 'json-schema'
+
+schema = {
+  "type" => "object",
+  "properties" => {
+    "a" => {"type" => "integer", "optional" => true}
+  }
+}
+
+data = {
+  "a" => 5
+}
+
+JSON::Validator.validate(schema, data, :version => :draft2)
+</pre>
+
+h3. Explicitly specifying the type of the data
+
+By default, json-schema accepts a variety of different types for the data parameter, and it will try to work out what to do with it dynamically. You can pass it a string uri (in which case it will download the json from that location before validating), a string of JSON text, or simply a ruby object (such as an array or hash representing parsed json). However, sometimes the nature of the data is ambiguous (for example, is "http://github.com" just a string, or is it a uri?). In other situations, you have already parsed your JSON, and you don't need to re-parse it.
+
+If you want to be explict about what kind of data is being parsed, JSON schema supports a number of options:
+
+<pre>
+require 'rubygems'
+require 'json-schema'
+
+schema = {
+  "type" => "string"
+}
+
+# examines the data, determines it's a uri, then tries to load data from it
+JSON::Validator.validate(schema, 'https://api.github.com') # returns false
+
+# data is already parsed json - just accept it as-is
+JSON::Validator.validate(schema, 'https://api.github.com', :parse_data => false) # returns true
+
+# data is parsed to a json string
+JSON::Validator.validate(schema, '"https://api.github.com"', :json => true) # returns true
+
+# loads data from the uri
+JSON::Validator.validate(schema, 'https://api.github.com', :uri => true) # returns false
+</pre>
+
+h3. Extend an existing schema and validate against it
+
+For this example, we are going to extend the "JSON Schema Draft 3":http://tools.ietf.org/html/draft-zyp-json-schema-03 specification by adding a 'bitwise-and' property for validation.
+
+<pre>
+require 'rubygems'
+require 'json-schema'
+
+class BitwiseAndAttribute < JSON::Schema::Attribute
+  def self.validate(current_schema, data, fragments, processor, validator, options = {})
+    if data.is_a?(Integer) && data & current_schema.schema['bitwise-and'].to_i == 0
+      message = "The property '#{build_fragment(fragments)}' did not evaluate  to true when bitwise-AND'd with  #{current_schema.schema['bitwise-or']}"
+      raise JSON::Schema::ValidationError.new(message, fragments, current_schema)
+    end
+  end
+end
+
+class ExtendedSchema < JSON::Schema::Validator
+  def initialize
+    super
+    extend_schema_definition("http://json-schema.org/draft-03/schema#")
+    @attributes["bitwise-and"] = BitwiseAndAttribute
+    @uri = URI.parse("http://test.com/test.json")
+  end
+
+  JSON::Validator.register_validator(self.new)
+end
+
+schema = {
+  "$schema" => "http://test.com/test.json",
+  "properties" => {
+    "a" => {
+      "bitwise-and" => 1
+    },
+    "b" => {
+      "type" => "string"
+    }
+  }
+}
+
+data = {
+  "a" => 0
+}
+
+data = {"a" => 1, "b" => "taco"}
+JSON::Validator.validate(schema,data) # => true
+data = {"a" => 1, "b" => 5}
+JSON::Validator.validate(schema,data) # => false
+data = {"a" => 0, "b" => "taco"}
+JSON::Validator.validate(schema,data) # => false
+</pre>
+
+h3. Custom format validation
+
+The JSON schema standard allows custom formats in schema definitions which should be ignored by validators that do not support them. JSON::Schema allows registering procs as custom format validators which receive the value to be checked as parameter and must raise a <code>JSON::Schema::CustomFormatError</code> to indicate a format violation. The error message will be prepended by the property name, e.g. "The property '#a'":
+
+<pre>
+require 'rubygems'
+require 'json-schema'
+
+format_proc = -> value {
+  raise JSON::Schema::CustomFormatError.new("must be 42") unless value == "42"
+}
+
+# register the proc for format 'the-answer' for draft4 schema
+JSON::Validator.register_format_validator("the-answer", format_proc, ["draft4"])
+
+# omitting the version parameter uses ["draft1", "draft2", "draft3", "draft4"] as default
+JSON::Validator.register_format_validator("the-answer", format_proc)
+
+# deregistering the custom validator
+# (also ["draft1", "draft2", "draft3", "draft4"] as default version)
+JSON::Validator.deregister_format_validator('the-answer', ["draft4"])
+
+# shortcut to restore the default formats for validators (same default as before)
+JSON::Validator.restore_default_formats(["draft4"])
+
+# with the validator registered as above, the following results in
+# ["The property '#a' must be 42"] as returned errors
+schema = {
+  "$schema" => "http://json-schema.org/draft-04/schema#",
+  "properties" => {
+    "a" => {
+      "type" => "string",
+      "format" => "the-answer",
+    }
+  }
+}
+errors = JSON::Validator.fully_validate(schema, {"a" => "23"})
+
+</pre>
+
+h2. Controlling Remote Schema Reading
+
+In some cases, you may wish to prevent the JSON Schema library from making HTTP calls or reading local files in order to resolve <code>$ref</code> schemas. If you fully control all schemas which should be used by validation, this could be accomplished by registering all referenced schemas with the validator in advance:
+
+<pre>
+schema = JSON::Schema.new(some_schema_definition, Addressable::URI.parse('http://example.com/my-schema'))
+JSON::Validator.add_schema(schema)
+</pre>
+
+If more extensive control is necessary, the <code>JSON::Schema::Reader</code> instance used can be configured in a few ways:
+
+<pre>
+# Change the default schema reader used
+JSON::Validator.schema_reader = JSON::Schema::Reader.new(:accept_uri => true, :accept_file => false)
+
+# For this validation call, use a reader which only accepts URIs from my-website.com
+schema_reader = JSON::Schema::Reader.new(
+  :accept_uri => proc { |uri| uri.host == 'my-website.com' }
+)
+JSON::Validator.validate(some_schema, some_object, :schema_reader => schema_reader)
+</pre>
+
+The <code>JSON::Schema::Reader</code> interface requires only an object which responds to <code>read(string)</code> and returns a <code>JSON::Schema</code> instance. See the "API documentation":http://www.rubydoc.info/github/ruby-json-schema/json-schema/master/JSON/Schema/Reader for more information.
+
+h2. JSON Backends
+
+The JSON Schema library currently supports the <code>json</code> and <code>yajl-ruby</code> backend JSON parsers. If either of these libraries are installed, they will be automatically loaded and used to parse any JSON strings supplied by the user.
+
+If more than one of the supported JSON backends are installed, the <code>yajl-ruby</code> parser is used by default. This can be changed by issuing the following before validation:
+
+<pre>
+JSON::Validator.json_backend = :json
+</pre>
+
+Optionally, the JSON Schema library supports using the MultiJSON library for selecting JSON backends. If the MultiJSON library is installed, it will be autoloaded.
+
+h2. Notes
+
+The 'format' attribute is only validated for the following values:
+
+* date-time
+* date
+* time
+* ip-address (IPv4 address in draft1, draft2 and draft3)
+* ipv4 (IPv4 address in draft4)
+* ipv6
+* uri
+
+All other 'format' attribute values are simply checked to ensure the instance value is of the correct datatype (e.g., an instance value is validated to be an integer or a float in the case of 'utc-millisec').
+
+Additionally, JSON::Validator does not handle any json hyperschema attributes.