--- Michael G Schwern <[EMAIL PROTECTED]> wrote: > A. Pagaltzis wrote: > >> If they're really not useful and just complicate matters I'm > >> quite open to being convinced otherwise. > > > > OK; the goal here, I think, is to make TAP as simple as possible > > to generate as well as consume, without limiting expressiveness > > unnecessarily. > > Yep, we're on the same page. > > To make it clear, the use case for TAP datetimes includes both the > TAP meta > information AND use in the TAP diagnostics to describe testing data. > For > example, let's say you're testing some Biblical software and want to > make sure > you got your dates right. > > not ok 1 - age of the Earth > ---- > found: -05000000000-02-12 > wanted: -4004-10-23
Whoa! I missed a memo and now I'm confused. I did think that a lot of this fuss over the date YAML meta information in TAP was going on a bit, but small details can be important. However, date YAML diagnostic information (we need formal names to distinguish between those two) should be up to the app, yes? What if scientific software needs picoseconds? We shouldn't be putting those arbitrary constraints here. A defined format for meta information is important. It is bad for diagnostic information. Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Perl and CGI - http://users.easystreet.com/ovid/cgi_course/ Personal blog - http://publius-ovidius.livejournal.com/ Tech blog - http://use.perl.org/~Ovid/journal/
