[Psidev-qc-dev] Handcrafted JSON file

[Bittremieux W. <wou...@ua...>]

Dear colleagues,

I have now made a handcrafted JSON file as well, which you can find here: https://gist.github.com/bittremieux/52d215895d3bdf4e8ca3483c107491a6

I tried to give a few examples and tried to remove some (unnecessary?) extra levels of encapsulation that were caused by a direct translation from XML to JSON. See the comments throughout the file for some of my reasoning.

Some things are represented differently in my file versus Dave's file or Mathias's file. This is logical as we'll need to settle on a uniform way of representing our data in JSON, but I feel that by cutting back on the verbosity this example is already more readable than our previous XML files. Instead of a direct translation of the previous XML schema I deviated a bit in some places to take advantage of the additional flexibility JSON gives us.

@Dave: Your JSON file seems reasonably ok compared to Mathias's example. I have done a few things differently which I think could be advantageous, but we'll have to discuss that.
One major thing that will change is how multiple values are encoded. You added those as a string value after the "__text" key, but that obviously doesn't take advantage of the fact that we have a full JSON object and don't need to encoded our JSON values as a string anymore. Instead this should become a native JSON object. The current string encoding in yours and Mathias's file comes from a naive conversion of the previous XML schema. However, if we have a native JSON format we can directly encode values in JSON.

Best,
Wout

> On 22 May 2018, at 00:34, David Tabb <dt...@su...> wrote:
> 
> Hi, folks.
> 
> I've made a first effort at JSON output for QuaMeter IDFree.  You can
> find it here:
> https://github.com/HUPO-PSI/qcML-development/blob/master/schema/v0_0_10/examples/20180403-1091_Pool_start_v0.1.qc.json.
> 
> Unlike my prior attempt at a qcML output, this example spans only two
> metrics.  I feel considerably less sure of myself in how these should be
> formatted, but at least it seems to be legit JSON, courtesy of the
> validator at jsonlint.com.
> 
> Your feedback and guidance on what goes where would be welcome!
> 
> Thanks,
> Dave
> [http://cdn.sun.ac.za/100/ProductionFooter.jpg]<http://www.sun.ac.za/english/Pages/Water-crisis.aspx>
> 
> The integrity and confidentiality of this email is governed by these terms. Disclaimer<http://www.sun.ac.za/emaildisclaimer>
> Die integriteit en vertroulikheid van hierdie e-pos word deur die volgende bepalings gereël. Vrywaringsklousule<http://www.sun.ac.za/emaildisclaimer>
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Psidev-qc-dev mailing list
> Psi...@li...
> https://lists.sourceforge.net/lists/listinfo/psidev-qc-dev