Coerce strings to #uuids
post from :data field for consistency with GET
Simplifying away the old/new in PUT as we may not need it with the new masking stuff?
get the ctor from the spec that was fetched from the item itself, not the optional arg
inspect-spec gives  a json-friendly nested map of a spec.
enum values are now normal specs; enums are now effectively union types.
Added to/from json functions that explicitly tag the structure with the spec type (needed for knowing which enum value to construct)
Had to comment out a bunch of un-fixed restify tests for now.
masks and inspection now handle enums
added depth-n masks
whoops. Misunderstood why these tests were failing: a namespace collision error with another project
complete masks were returning values for nonextant keys
datomic tests for storing/retrieving enums
some wrong arities on get-eid
new-components-mask
subtle bug where we our transactions cause overwriting, but we don't notice it because get-eid doesn't find anything.
Problem is that datomic uses identity OR uniqueness to fix entitys for updating, not just identity.
schema generation helper
don't have misleading non-?'d names in the placeholder comment
recursively remove db-refs from a sp
need to get-eid recursively on recursive fields, as they may fix a unique instance.
[WIP] nils on "recursive" properties should imply a retraction.
Not convinced this is 100% correct -- needs more testing.
optionally provide a resource path when inspecting
sending/receiving through json now adds a "spec-tacular-spec"~"specTacularSpec" keyword to tag what type each object is.
This explicit tag is peeled off again on the put/posts