adiwg-mdjson_schemas 2.8.0 → 2.9.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: eebc6cb500f846a0e9836ff4eaf540ab17005e97979e2ba4475f1428c2aa94cf
-  data.tar.gz: d42baac44598a3a8911e91c6c463d23177a825c0ea2f40237c0ebaa390239718
+  metadata.gz: fa2772ea2ae6a21d680e1405fb074828e78bc4f2c61f76aa1e0912f36080bd3b
+  data.tar.gz: 0f48447823dd6be78973116ff44ce4bf270e4c64a6cacf8e4cf9c3ca5efafe16
 SHA512:
-  metadata.gz: fb4870e51ad1a29ab063e0d4e9d1578f9bf254da0f83fa4649624ea9689f3379a80474dbfc4c356633cd60691bd6b6cdbb6ba43c2c741a1cf1e2f41c633381b3
-  data.tar.gz: 15b997f7a3aec2f44d5ad54f4ec83fcdab0195151a80b621e7b989da7a4fb3d81939067484b5149e3dc2be89d12baa22fffcd0e1cdd0a9598cfad8e12d10d6ff
+  metadata.gz: 23d4b2a087a926628b04c61ebc9a27517aefecc2f53dfd15c29dd98d72eba3b96c8a696a376cb77b87cbbe10d137d7677a2b69cf5fa9469f9c1a0fa5e7b653d8
+  data.tar.gz: f8d5573196a9efd700b3d0bad92c1f90ae6fc3dbc46e7871bf231763c65fb4f416b5fb08f396fd4ed90f439473e611cc7e3e57d82185e1a8ae5e1ea937284493

data/.gitignore

@@ -18,3 +18,5 @@ tmp
 .project
 node_modules
 resources/js
+
+.DS_Store

data/README.md

@@ -5,7 +5,6 @@
 
 # mdJson-schemas
 
-
 JSON schemas for the ADIwg project and data metadata standard
 
 ## Ruby Gem
@@ -26,12 +25,6 @@ Or install it yourself as:
 
     $ gem install adiwg-json_schemas
 
-## Bower
-
-Install:
-
-    $ bower install mdjson-schemas
-
 ## npm
 
 Install:
@@ -40,10 +33,9 @@ Install:
 
     const Schemas = require('../resources/js/schemas.js');
 
-
 ### Usage
 
-The main schema file is `schema/schema.json`.  Load that file in your [validator](http://json-schema.org/implementations.html#libraries).
+The main schema file is `schema/schema.json`. Load that file in your [validator](http://json-schema.org/implementations.html#libraries).
 
 **NOTE**: The schemas use relative addresses for `$ref` paths. If this causes a problem
 with the [ruby-json-schema/json-schema](https://github.com/ruby-json-schema/json-schema) gem,
@@ -56,3 +48,7 @@ as a workaround you can pre-load all of the schemas by calling `ADIWG::MdjsonSch
 3. Commit your changes (`git commit -am 'Add some feature'`)
 4. Push to the branch (`git push origin my-new-feature`)
 5. Create new Pull Request
+
+### Ignore anything below this line
+
+Just making changes to make changes to something. Trying to resolve merge conflicts.

data/adiwg-json_schemas.gemspec

@@ -20,7 +20,7 @@ Gem::Specification.new do |spec|
 
   spec.add_development_dependency "bundler", "~> 2"
   spec.add_development_dependency "rake", ">= 0"
-  spec.add_development_dependency "json-schema", "~> 2.8.0"
+  spec.add_development_dependency "json-schema", "~> 2.8.1"
   spec.add_development_dependency "minitest", "~>5"
-  spec.add_development_dependency "adiwg-mdcodes", "~> 2.7.5"
+  spec.add_development_dependency "adiwg-mdcodes", "~> 2.9.0"
 end

data/examples/rangeElementDescription.json

@@ -0,0 +1,10 @@
+{
+    "rangeElementDescription":
+       [
+          {
+             "name": "example name",
+             "definition": "example definition",
+             "rangeElement": [ "elem1", "elem2" ]
+          }
+       ]
+}

data/lib/adiwg/mdjson_schemas/version.rb

@@ -1,6 +1,6 @@
 module ADIWG
     module MdjsonSchemas
         # Current schema version number
-        VERSION = "2.8.0"
+        VERSION = "2.9.0"
     end
 end