# from Ovid
# on Thursday 21 August 2008 09:28:
>> (2) YAML is better suited for complex serialization than JSON.
>1. YAML is prettier.
>2. JSON, unlike YAML, is stable.
>
>Let's not forget that the debated requirement for diagnostics is that
> the generators and consumers speak the same language
Does it have to be just one? Now and forever?
Is the specification for either of these going to be part of the TAP
spec?
Can the spec simply specify the identifier and start/end sentinels of
the diagnostic and leave the details of the content up to the two ends?
The consumer doesn't even need to grok the diagnostic if it's e.g.
jpeg -- it just needs to reliably preserve it and save it in a file or
hand it to a viewer.
I guess you could put your xml, jpeg, or svg in a JSON value, but I
think that would make it harder to specify any communication between
the emitter and consumer -- starting with "under which key?", a debate
which has already been shown to be endless.
--Eric
--
Speak softly and carry a big carrot.
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
