* Ovid <[EMAIL PROTECTED]> [2008-08-21T12:28:52] > Let's not forget that the debated requirement for diagnostics is that the > generators and consumers speak the same language, not that the *consumer* > emit anything in particular. If you prefer the appearance of YAML to JSON, > have the consumer transform the JSON to YAML and print that. Problem solved.
Right. It's very nice that TAP is easy to read, but it's a protocol, and the harness provides a presentation layer. Schwern argued (on #perl-qa) that JSON will not be sufficient when more strongly-typed languages want to use TAP, and cannot serialize to JSON because it lacks tags and references. That would make TAP not even machine-*writeable* for those languages. When emitting have/want for something that can't be represented as native JSON, YAML will work... as long as there is a serializer for that language to serialize that kind of datum to YAML. I don't think that's a really big win, given the adoption rate of YAML, and given that in the end it's easy to implement tags and references as semantics atop JSON. -- rjbs
