On 24 October 2016 at 09:49, Smylers <smyl...@stripey.com> wrote: > 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.
The main idea/purpose isn't json specific - this could apply to mongo or any other nosql data source, I'm using it for postgres jsonb data in this project. This is an implementation of extracting a metadata structure, example data and schema from schema-less data, in this case JSON. > How about JSON::Schema::Inferred? JSON::Schema was just an example of the output, the simplest use case in this case, but there's no reason it couldn't later output RDF, Dublin Core or even HTML documentation using TT. If I was looking for a way to get RDF or other metadata from mongo I wouldn't be looking for JSON::Schema::Inferred. A. -- Aaron J Trevena, BSc Hons http://www.aarontrevena.co.uk LAMP System Integration, Development and Consulting
