create table schemas (
  ref text,
  format text references format_types,
  title text,
  description text,
  default text,
  multiple_of bigint,
  maximum bigint,
  exclusive_maximum boolean,
  minimum bigint,
  exclusive_minimum boolean,
  max_length integer,
  min_length integer,
  pattern text,
  max_items integer,
  min_items integer,
  unique_items boolean,
  max_properties integer,
  min_properties integer,
  required ,
  enum ,
  type ,
  items ,
  all_of ,
  properties ,
  additional_properties ,
  discriminator text,
  read_only boolean,
  xml ,
  external_docs ,
  example text
);

comment on column schemas.ref is '
  TODO: Needs to be named '$ref'
';
comment on column schemas.items is '
  TODO: figure out if this also needs to support boolean (http://json-schema.org/latest/json-schema-validation.html#rfc.section.5.9). It's possible that a uni-directional approach may allow us to avoid supporting this odd type.
';
comment on column schemas.additional_properties is '
  TODO: figure out if this also needs to support boolean (http://json-schema.org/latest/json-schema-validation.html#rfc.section.5.18). It's possible that a uni-directional approach may allow us to avoid supporting this odd type.
';