On 2013-05-10 14:31, Joakim Hove wrote:
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?
I have sufficiently worn angle brackets on my keyboard that I would have
to chime in and say that I personally prefer JSON over XML for a
"property-based" purpose (where text is only at single leaf nodes),
which I gather this would be.
The reason is purely aestethic; such files tends to still be inspected
by humans using regular text editors, so there is a desire to keep the
visual distractions low.
JSON libraries may be considered to be "less mature" than XML at this
point; however, that can also be read as "less over-engineered". :-) Due
to the less verbosity it is more used in the mobile space, so I think it
will improve.
Regarding Alf's question about interchanging TinyXML with JSON: This
should certainly be possible considering the conceptual similarities
(just witness boost::property_tree, which is capable of reading from
*both* formats), but I don't know enough about the Opm::parameters code
to know if this is a large undertaking.
--
Roland.
_______________________________________________
Opm mailing list
[email protected]
http://www.opm-project.org/mailman/listinfo/opm
