diff --git a/lib/superstudio.rb b/lib/superstudio.rb
index 859c10f..f06fc24 100644
--- a/lib/superstudio.rb
+++ b/lib/superstudio.rb
@@ -63,6 +63,15 @@ def interpret_json_schema(json_hash, depth = 0, path_array = [], expected_mappin
           end
         end
 
+        if key == "required"
+          # this will be especially important since according to http://spacetelescope.github.io/understanding-json-schema/reference/object.html
+          # each required string must be unique - which gives us an opportunity to use much shorter
+        end
+
+        if key == "patternProperties"
+          # this will let this library output uniquely keyed properties - which will be especially useful if we want to create ID keyed hashes
+        end
+
         if json_hash[key].is_a?(Hash)
           new_path_array = path_array.dup
           new_depth = depth
@@ -228,7 +237,8 @@ def clean_data_types(row_hash, template_types)
 
 # version 0.6.x - support arrays of objects
 # version 0.7.x - automatically generate data maps with all expected variables
-# version 0.8.x - support all settings for current draft of json schema
+# version 0.8.x - support patternProperties
+# version 0.9.x - support all settings for current draft of json schema
 # version 1.0.x - test suite
 
 # At some point I will address the problem of referencing schemas that define a node to be used, and of using references that are not on the same server
diff --git a/superstudio.gemspec b/superstudio.gemspec
index c8811b2..fde87f6 100644
--- a/superstudio.gemspec
+++ b/superstudio.gemspec
@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name        = 'superstudio'
-  s.version     = '0.6.1'
+  s.version     = '0.6.2'
   s.date        = '2016-01-04'
   s.summary     = "An alternative way of thinking about creating JSON output: life without creating ruby objects."
   s.description = ""