[tap-l] questions regarding draft standard compliance

[EBo]

Sorry, I was a bit more tired that I realized when I wrote this.  

> One of the bugs I discovered in my consumer when reparsing
Test-Harness's
> output was a test description which contained a \# -- which is not a
> Safe-String:
> 
>   ok 36 - Perl->can_handle( \#!...perl )
> 
> I also noticed that the the directives SKIP and TODO are in lower case
> instead of upper.  Are the string safety and case sensitivity going to
be
> part of the draft standard?

I would like to rephrase the questions as:

1) is the draft standard for the SKIP and TODO directives to be case
sensitive?

2) Should I report here, to tap-l, discrepancies from Test-Harness
divinations from the draft standard?  Or should I take that off-list to
the
maintainers?  The case in point is a descriptive string in Test-Harness
which is not Safe-String compliant.  Normally, I would take this directly
to the maintainers, but it is my understanding that Test-Harness is the
exemplar for the IETF draft standard, and thought these issues fodder for
general discussion.

  EBo --