Aaron Trevena writes: > I don't have a clean-room data set I can use as an example right now, > but essentially I'm parsing json, making a note of the names and > hierarchy of the fields, using dot-notation (i.e. like mongo) to name > nested fields, infer their type (i.e. ip address, mac address, epoch > time, etc) from data, and get a sample of the data. From that I can > then output a JSON::Schema or other documentation describing the data > itself.
If your module is Json-specifiec and there already exists a JSON:: top-level namespace, then I think it's much better to put it somewhere under JSON:: than Data::, which is so generic it tells users very little about the module's purpose. How about JSON::Schema::Inferred? Smylers -- http://twitter.com/Smylers2
