Re: EARL vs. our desired test results format

> So... I suggest we jump to a simpler, custom-built XML format like the
> one we sketched last week. I don't think it's because EARL is
> deficient, but because we have pretty detailed test output needs, and
> also because it's RDF-ness just adds complexity here that doesn't help
> -- well, that's the view from my brain, which has never really
> "gotten" the point of RDF.
Agreed!
If we (or someone) want/needs EARL output,
we can add a transformation from out custom-build XML to EARL.

  Roland