Actually, we do already have an investment in using XML in other code bases 
too, while JSON is new to me. However, we are at a point in the OPM code base 
where we have room to make the right decisions with respect to what 
infrastructure we want to use. I am afraid I know very little about JSON, so I 
hope some of you who have looked into this can share a bit more thoughts. In 
particular, please elaborate on the following:
-Is it natural for JSON to replace XML in OPM, that would we get rid of the 
TinyXML dependence?
-How common is JSON today, will the value chain surrounding it strengthen as 
time goes?
-What technical advantages does JSON have over XML?

Cheers,
Alf

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Atgeirr Rasmussen
Sent: 12. mai 2013 18:12
To: OPM Mailing List
Subject: Re: [OPM] Xml / json

I had no idea about JSON before this, so I won't exactly claim to be an expert, 
but:
 - JSON looks good, and simpler than XML.
 - There are multiple C++ libraries available with free licenses.
So my first question is: what library do you plan to use, or do you want to 
write your own?
 - We already have an XML dependency in opm-core (satisfied by embedding 
TinyXML).
Would you similarly embed the JSON lib or have it as an external dependency? 
(Actually, opm-core can use TinyXML as an external dependency as well, but 
since the code is embedded that is just a convenient possibility).

Overall, I think JSON looks good, feel free to use what you think is best for 
your particular purpose. Have you sketched how you would like to use it? That 
would be interesting to see!

Atgeirr


Den 11. mai 2013 kl. 14:02 skrev Bård Skaflestad:

> I'll second what Andreas said.  I much prefer JSON to XML for extensibility 
> (and configuration data for that matter).
> ________________________________________
> From: [email protected] [[email protected]] on
> behalf of Joakim Hove [[email protected]]
> Sent: 10 May 2013 14:31
> To: [email protected]
> Subject: [OPM] Xml / json
>
> Hello,
>
> the Eclipse parser we are writing should be run-time extendable, and to 
> achieve that we need to load semantic information from a file. Personally I 
> would prefer using json, but maybe there is a strong xml presedence? Any 
> opinions?
>
> Joakim
>
> Sendt fra min HTC
>
>
>
> -------------------------------------------------------------------
> The information contained in this message may be CONFIDENTIAL and is
> intended for the addressee only. Any unauthorised use, dissemination
> of the information or copying of this message is prohibited. If you
> are not the addressee, please notify the sender immediately by return
> e-mail and delete this message.
> Thank you
>
> _______________________________________________
> Opm mailing list
> [email protected]
> http://www.opm-project.org/mailman/listinfo/opm


_______________________________________________
Opm mailing list
[email protected]
http://www.opm-project.org/mailman/listinfo/opm

-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you

_______________________________________________
Opm mailing list
[email protected]
http://www.opm-project.org/mailman/listinfo/opm

Reply via email to