From tap-bounces@ietf.org  Sun Jan 18 20:41:55 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B0803A67F1;
	Sun, 18 Jan 2009 20:41:55 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 04CC43A67F1
	for <tap@core3.amsl.com>; Sun, 18 Jan 2009 20:41:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5
	tests=[BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id boGqLHcCotPS for <tap@core3.amsl.com>;
	Sun, 18 Jan 2009 20:41:53 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com
	[207.106.133.19])
	by core3.amsl.com (Postfix) with ESMTP id 16D943A6452
	for <tap@ietf.org>; Sun, 18 Jan 2009 20:41:51 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1])
	by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id
	C224A91C13 for <tap@ietf.org>; Sun, 18 Jan 2009 23:41:34 -0500 (EST)
Received: from windhund.local (unknown [216.99.210.236]) (using TLSv1 with
	cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate
	requested)
	by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id
	2732991C12 for <tap@ietf.org>; Sun, 18 Jan 2009 23:41:33 -0500 (EST)
Message-ID: <4974047A.6010407@pobox.com>
Date: Sun, 18 Jan 2009 20:41:30 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tap@ietf.org
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: 736CD0CE-E5E3-11DD-BAE6-5720C92D7133-02258300!a-sasl-fastnet.pobox.com
Subject: [tap] Complete TAP v13 ABNF grammar.  Now run it!
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

I would like to have a meaningful TAP v13 grammar ready before the Birmingham
QA Conference end of March.  To that end, I've picked up Gaurav's ball and
completed the TAP grammar on the wiki.  By "complete" I mean it covers all the
syntax of TAP v13 which is normal TAP, none of the proposed extensions.  I
used TAP::Parser::Grammar for reference.
http://testanything.org/wiki/index.php/TAP_at_IETF:_Draft_Standard

My knowledge of ABNF sucks, I was going from the Wikipedia article.  There's
probably mistakes.  There's probably things I'm forgetting.  There's a small
pile of unresolved issues in the discussions page.  But it's something.

Now what would be interesting is for someone to take that ABNF, make a simple
parser out of it and see what happens.  There is the TAP test suite around
somewhere, it would be interesting to run the grammar through that.


-- 
I have a date with some giant cartoon robots and booze.

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap


From tap-bounces@ietf.org  Sun Jan 18 21:19:02 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C4BCA28C0F7;
	Sun, 18 Jan 2009 21:19:02 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9631628C0F7
	for <tap@core3.amsl.com>; Sun, 18 Jan 2009 21:19:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5
	tests=[AWL=-1.207, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EdrRvDNs77vj for <tap@core3.amsl.com>;
	Sun, 18 Jan 2009 21:19:00 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by core3.amsl.com (Postfix) with SMTP id 22F353A6902
	for <tap@ietf.org>; Sun, 18 Jan 2009 21:18:59 -0800 (PST)
Received: (qmail invoked by alias); 19 Jan 2009 05:18:42 -0000
Received: from dslb-088-075-236-140.pools.arcor-ip.net (EHLO hive)
	[88.75.236.140]
	by mail.gmx.net (mp043) with SMTP; 19 Jan 2009 06:18:42 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX18sJbgROTQsQbIxPaQbY5KIueXT1xdXAChdK1wT6M
	06cjAhloCerJ5K
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Michael G Schwern <schwern@pobox.com>
Date: Mon, 19 Jan 2009 06:18:45 +0100
Message-ID: <lj18n49nr0dcv21bembr37gmj2e63v8agg@hive.bjoern.hoehrmann.de>
References: <4974047A.6010407@pobox.com>
In-Reply-To: <4974047A.6010407@pobox.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.6
Cc: tap@ietf.org
Subject: Re: [tap] Complete TAP v13 ABNF grammar.  Now run it!
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

* Michael G Schwern wrote:
>http://testanything.org/wiki/index.php/TAP_at_IETF:_Draft_Standard

I'm familiar with Internet Draft authoring and ABNF, not so much
familiar with TAP itself, please understand my comments in that light.

>My knowledge of ABNF sucks, I was going from the Wikipedia article.  There=
's
>probably mistakes.  There's probably things I'm forgetting.  There's a sma=
ll
>pile of unresolved issues in the discussions page.  But it's something.

There is an error in the comment production,

  Comment =3D # String EOL

Presumably the '#' is meant to be quoted.

I am not sure why

  Version =3D "T" "A" "P" SP "version" SP Version-Number EOL

Is written like this, that's just the same as

  Version =3D "TAP version " Version-Number EOL

The specification should be explicit about case-sensitivity, normally
ABNF quoted strings imply ascii-insensitivity. If that is intended, it
should be spelled out somewhere. If it's not intended, %... sequences
would have to be used.

The relationship between TAP-line and TAP-stream is unclear. I would
have expected something more like

  TAP-document =3D header plan body [comments]
               / header body plan [comments]

  header       =3D [comments] [version]

  body         =3D *(comment / TAP-line)

  TAP-line     =3D Test-Result / bail-out

This would actually use the TAP-line production and make clear that you
have to have exactly one plan, in addition to being somewhat easier to
read, in my opinion.

Rules like EOL and String should probably be in their own section, at
least putting them alongside Plan is not a good idea.

>Now what would be interesting is for someone to take that ABNF, make a sim=
ple
>parser out of it and see what happens.  There is the TAP test suite around
>somewhere, it would be interesting to run the grammar through that.

My Parse::ABNF (on CPAN) module turns an ABNF grammar into a array/hash
reference structure that should be easy to print out in whatever form is
desired for a given parsing toolkit. That might give a quick and easy
way to do that.
-- =

Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehrma=
nn.de
Am Badedeich 7 =B7 Telefon: +49(0)160/4415681 =B7 http://www.bjoernsworld.de
25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev.d=
e/ =

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap


From tap-bounces@ietf.org  Sun Jan 18 22:54:56 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A1093A6803;
	Sun, 18 Jan 2009 22:54:56 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9B0503A68F9
	for <tap@core3.amsl.com>; Sun, 18 Jan 2009 22:54:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XszitxaSbM2r for <tap@core3.amsl.com>;
	Sun, 18 Jan 2009 22:54:53 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com
	[207.106.133.19])
	by core3.amsl.com (Postfix) with ESMTP id 633933A6803
	for <tap@ietf.org>; Sun, 18 Jan 2009 22:54:51 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1])
	by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id
	173D2913B0; Mon, 19 Jan 2009 01:54:35 -0500 (EST)
Received: from [10.23.42.2] (unknown [69.64.236.3]) (using TLSv1 with cipher
	DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by
	a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 0CB69913AF;
	Mon, 19 Jan 2009 01:54:32 -0500 (EST)
Message-ID: <497423A7.7050705@pobox.com>
Date: Sun, 18 Jan 2009 22:54:31 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <4974047A.6010407@pobox.com>
	<lj18n49nr0dcv21bembr37gmj2e63v8agg@hive.bjoern.hoehrmann.de>
In-Reply-To: <lj18n49nr0dcv21bembr37gmj2e63v8agg@hive.bjoern.hoehrmann.de>
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: 080DC424-E5F6-11DD-93CF-5720C92D7133-02258300!a-sasl-fastnet.pobox.com
Cc: tap@ietf.org
Subject: Re: [tap] Complete TAP v13 ABNF grammar.  Now run it!
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

Bjoern Hoehrmann wrote:
> * Michael G Schwern wrote:
>> http://testanything.org/wiki/index.php/TAP_at_IETF:_Draft_Standard
> 
> I'm familiar with Internet Draft authoring and ABNF, not so much
> familiar with TAP itself, please understand my comments in that light.

Thanks for your fast comments.


>> My knowledge of ABNF sucks, I was going from the Wikipedia article.  There's
>> probably mistakes.  There's probably things I'm forgetting.  There's a small
>> pile of unresolved issues in the discussions page.  But it's something.
> 
> There is an error in the comment production,
> 
>   Comment = # String EOL
> 
> Presumably the '#' is meant to be quoted.

Yep, fixed.


> I am not sure why
> 
>   Version = "T" "A" "P" SP "version" SP Version-Number EOL
> 
> Is written like this, that's just the same as
> 
>   Version = "TAP version " Version-Number EOL
>
> The specification should be explicit about case-sensitivity, normally
> ABNF quoted strings imply ascii-insensitivity. If that is intended, it
> should be spelled out somewhere. If it's not intended, %... sequences
> would have to be used.

You're right, I should have used % sequences.  I specifically wanted to
require TAP in all-caps (this may or may not be a good idea, but that's what I
intended).  The rest of the string literals in the spec can be case sensitive.

Fixed.


> The relationship between TAP-line and TAP-stream is unclear. I would
> have expected something more like
> 
>   TAP-document = header plan body [comments]
>                / header body plan [comments]
> 
>   header       = [comments] [version]
> 
>   body         = *(comment / TAP-line)
> 
>   TAP-line     = Test-Result / bail-out
> 
> This would actually use the TAP-line production and make clear that you
> have to have exactly one plan, in addition to being somewhat easier to
> read, in my opinion.

TAP-Line was really just a way to define Significant-TAP-Line.  You're right,
it's stilted.  Your way is much better.  Fixed.


> Rules like EOL and String should probably be in their own section, at
> least putting them alongside Plan is not a good idea.

I've put them in a section called "Values" along with some discussion.  Just
using String for Description is not entirely correct.  Is there a way to
specify "any character in this set EXCEPT this one"?  Description should be
String without "#".

Is there a way to specify in the grammar that the document has to have a
consistent EOL?  That is, it has to use LF or CRLF but not both?


>> Now what would be interesting is for someone to take that ABNF, make a simple
>> parser out of it and see what happens.  There is the TAP test suite around
>> somewhere, it would be interesting to run the grammar through that.
> 
> My Parse::ABNF (on CPAN) module turns an ABNF grammar into a array/hash
> reference structure that should be easy to print out in whatever form is
> desired for a given parsing toolkit. That might give a quick and easy
> way to do that.

Excellent, I'll look into it.


-- 
package Outer::Space;  use Test::More tests => 9;
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap


From tap-bounces@ietf.org  Sun Jan 18 23:52:10 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 14A913A676A;
	Sun, 18 Jan 2009 23:52:10 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C9AB3A6803
	for <tap@core3.amsl.com>; Sun, 18 Jan 2009 23:52:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[AWL=-4.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wqw-I6U9oZxm for <tap@core3.amsl.com>;
	Sun, 18 Jan 2009 23:52:08 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by core3.amsl.com (Postfix) with SMTP id C77233A676A
	for <tap@ietf.org>; Sun, 18 Jan 2009 23:52:07 -0800 (PST)
Received: (qmail invoked by alias); 19 Jan 2009 07:51:49 -0000
Received: from dslb-088-074-180-017.pools.arcor-ip.net (EHLO hive)
	[88.74.180.17]
	by mail.gmx.net (mp006) with SMTP; 19 Jan 2009 08:51:49 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX193Ub0KuEd3YXzQGDCMR6h4hzqiSiNK8MgkFInzCG
	fvEqXOurWfzlDG
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Michael G Schwern <schwern@pobox.com>
Date: Mon, 19 Jan 2009 08:51:52 +0100
Message-ID: <vgb8n41lgtv8v65b7ovg46cr2s3cscg790@hive.bjoern.hoehrmann.de>
References: <4974047A.6010407@pobox.com>
	<lj18n49nr0dcv21bembr37gmj2e63v8agg@hive.bjoern.hoehrmann.de>
	<497423A7.7050705@pobox.com>
In-Reply-To: <497423A7.7050705@pobox.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.65
Cc: tap@ietf.org
Subject: Re: [tap] Complete TAP v13 ABNF grammar.  Now run it!
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

* Michael G Schwern wrote:
>I've put them in a section called "Values" along with some discussion.  Ju=
st
>using String for Description is not entirely correct.  Is there a way to
>specify "any character in this set EXCEPT this one"?  Description should be
>String without "#".

There is not, other than a prose value like

  foo =3D <a String without any "#" characters>

That's fine for drafts but ultimately makes automatically generating
code from the grammar more difficult as the specification matures.

A better place for prose values would be defining a symbol like

  Extension =3D <string without any EOL and not matching TAP-line> EOL

>Is there a way to specify in the grammar that the document has to have a
>consistent EOL?  That is, it has to use LF or CRLF but not both?

In ABNF there is not. I would not recommend specifying that either. My
personal preference in handling this is doing what the XML specification
does, require processing as if there was a pre-processing step turning
CRLF and bare CR into LF, then use only LF in the grammar as needed.
-- =

Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehrma=
nn.de
Am Badedeich 7 =B7 Telefon: +49(0)160/4415681 =B7 http://www.bjoernsworld.de
25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev.d=
e/ =

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap


From tap-bounces@ietf.org  Mon Jan 19 02:30:24 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 46EDA3A69A3;
	Mon, 19 Jan 2009 02:30:24 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 225453A69A3
	for <tap@core3.amsl.com>; Mon, 19 Jan 2009 02:30:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5
	tests=[BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 60dluCY3zrHJ for <tap@core3.amsl.com>;
	Mon, 19 Jan 2009 02:30:22 -0800 (PST)
Received: from web65708.mail.ac4.yahoo.com (web65708.mail.ac4.yahoo.com
	[76.13.9.100]) by core3.amsl.com (Postfix) with SMTP id E3C473A677C
	for <tap@ietf.org>; Mon, 19 Jan 2009 02:30:21 -0800 (PST)
Received: (qmail 51215 invoked by uid 60001); 19 Jan 2009 10:30:06 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=oFsLBkkqDP9tmNmq1GMIX6ioyO4EOvdvjSN1mhUmEoVLT3VNXTyY4h7SBNeZPRNbgi8KUas/F3c9xEse4ZJhb6IzHUg3Fhf0UshpQAFu6KGaUvEdrFvf4sO91GUqlLi80ITA40mHVTYG31qS7YdHF065E+ed/WcaikgdgFFf84Y=;
X-YMail-OSG: p1kfVN4VM1mxhW3RGbQL4NE9dlm..GlKpDg69PYHbRMulip8QIWSgXHfbVmnPlKS3GyDWMttNFsLtCTJlP48O2XaBxYzMLIZZaa9MAp2S5Nhig7dtvkB6VloHTx1TlUO..WzlAsujOJe97D7ot4BeQbbuAF4Zk08486hOCR7_EU9avty0dEoJduXCZp2M1EF99eTZGLnVxm3mvZDOw--
Received: from [91.85.130.147] by web65708.mail.ac4.yahoo.com via HTTP;
	Mon, 19 Jan 2009 02:30:05 PST
X-Mailer: YahooMailRC/1155.45 YahooMailWebService/0.7.260.1
References: <4974047A.6010407@pobox.com>
Date: Mon, 19 Jan 2009 02:30:05 -0800 (PST)
From: Ovid <publiustemp-tapx@yahoo.com>
To: Michael G Schwern <schwern@pobox.com>, tap@ietf.org
MIME-Version: 1.0
Message-ID: <19524.50385.qm@web65708.mail.ac4.yahoo.com>
Subject: Re: [tap] Complete TAP v13 ABNF grammar.  Now run it!
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

----- Original Message ----

> From: Michael G Schwern <schwern@pobox.com>

> I would like to have a meaningful TAP v13 grammar ready before the Birmingham
> QA Conference end of March.  To that end, I've picked up Gaurav's ball and
> completed the TAP grammar on the wiki.  By "complete" I mean it covers all the
> syntax of TAP v13 which is normal TAP, none of the proposed extensions.  I
> used TAP::Parser::Grammar for reference.
> http://testanything.org/wiki/index.php/TAP_at_IETF:_Draft_Standard

Out of curiosity, what was wrong with my grammar?

Cheers,
Ovid
--
Buy the book         - http://www.oreilly.com/catalog/perlhks/
Tech blog            - http://use.perl.org/~Ovid/journal/
Twitter              - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap


From tap-bounces@ietf.org  Mon Jan 19 14:10:48 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B0A663A693D;
	Mon, 19 Jan 2009 14:10:48 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 15D523A693D
	for <tap@core3.amsl.com>; Mon, 19 Jan 2009 14:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id y11exYeuUfCT for <tap@core3.amsl.com>;
	Mon, 19 Jan 2009 14:10:40 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com
	[207.106.133.19])
	by core3.amsl.com (Postfix) with ESMTP id 6A4493A6944
	for <tap@ietf.org>; Mon, 19 Jan 2009 14:10:39 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1])
	by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id
	547139117E; Mon, 19 Jan 2009 17:10:23 -0500 (EST)
Received: from [10.23.42.2] (unknown [69.64.236.3]) (using TLSv1 with cipher
	DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by
	a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 9F96B9117D;
	Mon, 19 Jan 2009 17:10:21 -0500 (EST)
Message-ID: <4974FA4B.7010603@pobox.com>
Date: Mon, 19 Jan 2009 14:10:19 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Ovid <publiustemp-tapx@yahoo.com>
References: <4974047A.6010407@pobox.com>
	<19524.50385.qm@web65708.mail.ac4.yahoo.com>
In-Reply-To: <19524.50385.qm@web65708.mail.ac4.yahoo.com>
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: F7C39622-E675-11DD-A1E3-5720C92D7133-02258300!a-sasl-fastnet.pobox.com
Cc: tap@ietf.org
Subject: Re: [tap] Complete TAP v13 ABNF grammar.  Now run it!
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

Ovid wrote:
> ----- Original Message ----
> 
>> From: Michael G Schwern <schwern@pobox.com>
> 
>> I would like to have a meaningful TAP v13 grammar ready before the Birmingham
>> QA Conference end of March.  To that end, I've picked up Gaurav's ball and
>> completed the TAP grammar on the wiki.  By "complete" I mean it covers all the
>> syntax of TAP v13 which is normal TAP, none of the proposed extensions.  I
>> used TAP::Parser::Grammar for reference.
>> http://testanything.org/wiki/index.php/TAP_at_IETF:_Draft_Standard
> 
> Out of curiosity, what was wrong with my grammar?

Heh, I never even thought to look at the TAP::Parser::Grammar docs for a
grammar.  I went straight into the code to see how it's actually implemented.

Aside from the technical issue of not being ABNF, it will be worthwhile to
compare the differences between the two to reveal edge cases and strict vs
pragmatic concerns.


-- 
There will be snacks.
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap


From tap-bounces@ietf.org  Mon Jan 19 16:57:04 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1AF5B3A6A24;
	Mon, 19 Jan 2009 16:57:04 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 35F633A6A98
	for <tap@core3.amsl.com>; Mon, 19 Jan 2009 16:57:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5
	tests=[BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CW2jZL-Cvwtk for <tap@core3.amsl.com>;
	Mon, 19 Jan 2009 16:57:01 -0800 (PST)
Received: from mail-bw0-f14.google.com (mail-bw0-f14.google.com
	[209.85.218.14])
	by core3.amsl.com (Postfix) with ESMTP id 034173A6A24
	for <tap@ietf.org>; Mon, 19 Jan 2009 16:57:00 -0800 (PST)
Received: by bwz7 with SMTP id 7so362074bwz.18
	for <tap@ietf.org>; Mon, 19 Jan 2009 16:56:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:date:message-id:subject
	:from:to:content-type:content-transfer-encoding;
	bh=rfiH+0neRZvNWTDksEbSczqzmyNoOMLRzGmjpM/fX7M=;
	b=jiwvZDeTk+OzkLHPKwynAw4wuurMjG9sLhLqtN6BkkmvfLuaYEMFDWBr4DS1ieETh6
	z7bzlPrTxRwHo7sGUKP1TapKomWc31UBGL6G3cs19P1GquLhw79bXPbVfoFb4UVPJNy4
	T1fl4rGhzIJMjm8DwIDRWG1Uf5oaG6xOAO0Cc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:date:message-id:subject:from:to:content-type
	:content-transfer-encoding;
	b=P3iDvuvzLczHqL/ZT3dJSiGaxHhU7LwFl+Nf5kO7F1+rS3/NCGUQFgyg31+c8M5Gnv
	GIX62noljyt0QW2oS4m99JWxcA/UqQ0pSZgDena/pbC3zkT+krrkEgDkhVfSqsFq8zT1
	9XkwVbrM7aCcpga7XP4aPW9+jNfqoyI23QY2M=
MIME-Version: 1.0
Received: by 10.223.126.66 with SMTP id b2mr1599448fas.18.1232413001782; Mon, 
	19 Jan 2009 16:56:41 -0800 (PST)
Date: Tue, 20 Jan 2009 01:56:41 +0100
Message-ID: <a51e610c0901191656u6d20f780mf47a077229d91abd@mail.gmail.com>
From: Leon Timmermans <fawaka@gmail.com>
To: tap@ietf.org
Subject: [tap] Ann: libtap++
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>,
	<mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

SGkgYWxsLAoKSSdtIG5vdCBzdXJlIHRoaXMgaXMgdGhlIHJpZ2h0IHBsYWNlIGZvciBhbm5vdW5j
ZW1lbnRzIGxpa2UgdGhpcywgYnV0CmxhY2tpbmcgYW55IG90aGVy4oCmCgpJJ3ZlIHdyaXR0ZW4g
YSBUQVAgcHJvZHVjaW5nIGxpYnJhcnkgZm9yIEMrKywgY2FsbGVkIGxpYnRhcCsrLiBJdApzdGls
bCBoYXMgc29tZSByb3VnaCBlZGdlcywgYnV0IHRoZSBjb3JlIHBhcnRzIHNlZW0gdG8gd29yayB3
aXRob3V0CmFueSBpc3N1ZXMuIEl0J3MgbWFpbiBhZHZhbnRhZ2Ugb3ZlciB0aGUgQyBsaWJyYXJ5
IGxpYnRhcCBpcyB0aGF0IGl0CnByb3ZpZGVzIHByb3BlciAnJ2lzJycgYW5kICcnaXNudCcnIGZ1
bmN0aW9ucy4gSXQncyBtb3N0bHkgYSBDKysgY2xvbmUKb2YgVGVzdDo6TW9yZSAodG8gdGhlIHBv
aW50IHRoYXQgSSBzdG9sZSBwYXJ0cyBvZiB0aGUgZG9jdW1lbnRhdGlvbiksCndpdGggYSBmZXcg
ZXh0cmFzIHRoYXQgd291bGRuJ3QgbWFrZSBzZW5zZSBpbiBQZXJsIChsaWtlCmlzX2NvbnZlcnRp
YmxlKS4KCllvdSBjYW4gZmluZCB0aGUgY3VycmVudCB2ZXJzaW9uIG9mIGl0IGF0Cmh0dHA6Ly9s
aWJwZXJsLmdvb2dsZWNvZGUuY29tL2ZpbGVzL2xpYnRhcC0wLjAxLnRhci5neiBhbmQgc29tZQpk
b2N1bWVudGF0aW9uIGF0IGh0dHA6Ly9jb2RlLmdvb2dsZS5jb20vcC9saWJwZXJsL3dpa2kvTGli
dGFwLiBUaGUKY29kZSBzaG91bGQgYmUgcG9ydGFibGUsIGJ1dCB0aGUgTWFrZWZpbGUgaXNuJ3Qu
CgpSZWdhcmRzLAoKTGVvbiBUaW1tZXJtYW5zCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fCnRhcCBtYWlsaW5nIGxpc3QKdGFwQGlldGYub3JnCmh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGFwCg==



From tap-bounces@ietf.org  Tue Jan 20 12:58:37 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 837613A67C1; Tue, 20 Jan 2009 12:58:37 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EEB23A68C6 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 12:58:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OpT6-Sf1VJch for <tap@core3.amsl.com>; Tue, 20 Jan 2009 12:58:35 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by core3.amsl.com (Postfix) with ESMTP id 28DE63A67C1 for <tap@ietf.org>; Tue, 20 Jan 2009 12:58:34 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 16AC092E02 for <tap@ietf.org>; Tue, 20 Jan 2009 15:58:17 -0500 (EST)
Received: from [10.23.42.2] (unknown [69.64.236.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 0E85092E00 for <tap@ietf.org>; Tue, 20 Jan 2009 15:58:15 -0500 (EST)
Message-ID: <49763AE1.5@pobox.com>
Date: Tue, 20 Jan 2009 12:58:09 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tap@ietf.org
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: 0F86E024-E735-11DD-9B7F-5720C92D7133-02258300!a-sasl-fastnet.pobox.com
Subject: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org When writing the TAP spec the problem of character sets comes up.  What
character set is TAP going to use?  ASCII?  UTF-8?  Full Unicode?  Sticky.

Fortunately, I have a solution.  TAP will have NO CHARACTER SET!  That's
right, just not going to specify it.  But not in a sniveling "the character
set must be agreed upon by the parties interchanged" way.  We just word it so
the user can use any character set.

The critical observation is this:  there are really only a handful of places
were free-form strings are allowed in TAP.  1) Directive reasons  2)
Descriptions  3) Comments and  4) Ignored lines.  All the rest is fixed
strings which we can strictly specify.  Rather than specifying these things as
what they can be, we can specify them as what they can *not* be.  This handily
lines up with how you'd implement it.

For example, look at a complete TAP test result line.

    ok 3 Basset hounds got long ears # TODO This is a corgi

In order to match the test description you simply look for everything between
the test number and the #.  A test description can contain everything *except*
a "#" or EOL.  Similarly, a directive reason is just anything from the
directive itself to the EOL.  You can put any gibberish in there you like, its
still parsable and can be passed through to the user's display.

This makes the protocol simpler and less restrictive.  It makes it easier to
test non-Unicode apps.  Let's say you're working on a Big5 [1] application,
you'd naturally want to display your test results in Big5.  If TAP went all
Unicode you'd have to translate your Big5 results into Unicode muddying their
value as diagnostics.  Similarly, if you're working on a Big5 application you
probably have your terminal set to handle Big5 thus reading raw TAP output
with Big5 descriptions is most natural.

This solution continues with TAP being able to test ANYTHING.


[1] https://secure.wikimedia.org/wikipedia/en/wiki/Big5

-- 
"I went to college, which is a lot like being in the Army, except when
 stupid people yell at me for stupid things, I can hit them."
    -- Jonathan Schwarz

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 13:13:47 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 73E8C3A6804; Tue, 20 Jan 2009 13:13:47 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6EC9F3A6893 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 13:13:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xSKIpghdrbxk for <tap@core3.amsl.com>; Tue, 20 Jan 2009 13:13:45 -0800 (PST)
Received: from mail.plusthree.com (mail.plusthree.com [70.42.42.197]) by core3.amsl.com (Postfix) with ESMTP id 93E263A67C1 for <tap@ietf.org>; Tue, 20 Jan 2009 13:13:45 -0800 (PST)
Received: from localhost.localdomain (dsl093-241-113.ral1.dsl.speakeasy.net [66.93.241.113]) (authenticated bits=0) by mail.plusthree.com (8.14.2/8.14.2) with ESMTP id n0KL8YGt024378 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jan 2009 16:08:34 -0500
Message-ID: <49763DF7.1080002@plusthree.com>
Date: Tue, 20 Jan 2009 16:11:19 -0500
From: Michael Peters <mpeters@plusthree.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Michael G Schwern <schwern@pobox.com>
References: <49763AE1.5@pobox.com>
In-Reply-To: <49763AE1.5@pobox.com>
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org Michael G Schwern wrote:

> Fortunately, I have a solution.  TAP will have NO CHARACTER SET!  That's
> right, just not going to specify it.  But not in a sniveling "the character
> set must be agreed upon by the parties interchanged" way.  We just word it so
> the user can use any character set.

My head still swims a little when talking about character sets, so I might be wrong, but I don't 
think this will work. Without an agreed upon character set, all you have are meaningless bytes.

> For example, look at a complete TAP test result line.
> 
>     ok 3 Basset hounds got long ears # TODO This is a corgi
> 
> In order to match the test description you simply look for everything between
> the test number and the #.  A test description can contain everything *except*
> a "#" or EOL.  Similarly, a directive reason is just anything from the
> directive itself to the EOL.  You can put any gibberish in there you like, its
> still parsable and can be passed through to the user's display.

But how do you tell if a certain byte (or sequence of bytes) maps to the "#" character. Without an 
encoding you can't tell. "#" is the same byte in Latin1, ASCII, UTF-8 and Big5 but is not the same 
byte (or bytes) in UTF-16, UTF-32, UCS-2 or EBCDIC.

-- 
Michael Peters
Plus Three, LP

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 13:30:26 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 607E63A67C1; Tue, 20 Jan 2009 13:30:26 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C82A73A6893 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 13:30:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.266
X-Spam-Level: 
X-Spam-Status: No, score=-5.266 tagged_above=-999 required=5 tests=[AWL=-2.667, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9AD0R7Vm+N7q for <tap@core3.amsl.com>; Tue, 20 Jan 2009 13:30:24 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 06AF73A67C1 for <tap@ietf.org>; Tue, 20 Jan 2009 13:30:22 -0800 (PST)
Received: (qmail invoked by alias); 20 Jan 2009 21:30:05 -0000
Received: from dslb-088-074-182-112.pools.arcor-ip.net (EHLO hive) [88.74.182.112] by mail.gmx.net (mp064) with SMTP; 20 Jan 2009 22:30:05 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/GjwgIoF/GV94Fcm7CqNxum0J2h5c5SK526B9t0y 9BoXrwChutmJM0
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Michael G Schwern <schwern@pobox.com>
Date: Tue, 20 Jan 2009 22:30:09 +0100
Message-ID: <hsfcn45n5bc2ul9e7lrcs0a1e2adjpvo6a@hive.bjoern.hoehrmann.de>
References: <49763AE1.5@pobox.com>
In-Reply-To: <49763AE1.5@pobox.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.57
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org * Michael G Schwern wrote:
>Fortunately, I have a solution.  TAP will have NO CHARACTER SET!  That's
>right, just not going to specify it.  But not in a sniveling "the character
>set must be agreed upon by the parties interchanged" way.  We just word it=
 so
>the user can use any character set.

That would be problematic as far as the IETF is concerned, as per BCP 18
(currently RFC 2277): "All protocols MUST identify, for all character
data, which charset is in use." So if you do not pick a single encoding,
you have to have some way to identify which encoding is being used.

>In order to match the test description you simply look for everything betw=
een
>the test number and the #.  A test description can contain everything *exc=
ept*
>a "#" or EOL.  Similarly, a directive reason is just anything from the
>directive itself to the EOL.  You can put any gibberish in there you like,=
 its
>still parsable and can be passed through to the user's display.

That is a bit of a stretch, you assume that the user's display accepts
essentially arbitrary byte input, that is not always the case, and may
in fact lead to security problems. Consider the case of generating HTML
based on some TAP stream, you cannot have random byte streams in HTML
documents, you have to convert them to characters first. Otherwise you
have a hard time e.g. to filter out malicious <script> elements.

>This makes the protocol simpler and less restrictive.  It makes it easier =
to
>test non-Unicode apps.  Let's say you're working on a Big5 [1] application,
>you'd naturally want to display your test results in Big5.  If TAP went all
>Unicode you'd have to translate your Big5 results into Unicode muddying th=
eir
>value as diagnostics.  Similarly, if you're working on a Big5 application =
you
>probably have your terminal set to handle Big5 thus reading raw TAP output
>with Big5 descriptions is most natural.

But then of course if you do not have your terminal set to Big5 you get
gibberish, which you may or may not realize, and are less likely to know
how to fix (besides, as the Wikipedia article points out, there are some
variants of Big5, so your terminal's Big5 may be a different one than
the TAP generating application's "Big5").
-- =

Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehrma=
nn.de
Am Badedeich 7 =B7 Telefon: +49(0)160/4415681 =B7 http://www.bjoernsworld.de
25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev.d=
e/ =

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 13:34:16 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A4643A690A; Tue, 20 Jan 2009 13:34:16 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C7EF13A697A for <tap@core3.amsl.com>; Tue, 20 Jan 2009 13:34:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6HKQb4mg4uo0 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 13:34:15 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 8BF4A3A6935 for <tap@ietf.org>; Tue, 20 Jan 2009 13:34:14 -0800 (PST)
Received: (qmail invoked by alias); 20 Jan 2009 21:33:57 -0000
Received: from dslb-088-074-182-112.pools.arcor-ip.net (EHLO hive) [88.74.182.112] by mail.gmx.net (mp039) with SMTP; 20 Jan 2009 22:33:57 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+5/XVDqGO5yVjqjHq41x97VhFbSjOZu8uz0zrkbw Dx+j1gSUiwxFIQ
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Michael Peters <mpeters@plusthree.com>
Date: Tue, 20 Jan 2009 22:34:02 +0100
Message-ID: <ejgcn4ta91de8km1sdg4iblbvpdp15m80d@hive.bjoern.hoehrmann.de>
References: <49763AE1.5@pobox.com> <49763DF7.1080002@plusthree.com>
In-Reply-To: <49763DF7.1080002@plusthree.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.62
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org * Michael Peters wrote:
>But how do you tell if a certain byte (or sequence of bytes) maps to the "=
#" character. Without an =

>encoding you can't tell. "#" is the same byte in Latin1, ASCII, UTF-8 and =
Big5 but is not the same =

>byte (or bytes) in UTF-16, UTF-32, UCS-2 or EBCDIC.

I think the idea is to rule out using those encodings directly. This is
not uncommon, for example, e-mail / MIME messages depend on encodings
being ASCII-compatible (ascii characters map to ascii octets, ascii
octets map to ascii characters). Encodings like UTF-16 can only be used
of additional transformation takes place (e.g. quoted-printable or
base64 encoding).
-- =

Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehrma=
nn.de
Am Badedeich 7 =B7 Telefon: +49(0)160/4415681 =B7 http://www.bjoernsworld.de
25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev.d=
e/ =

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 14:15:33 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E53CC3A688B; Tue, 20 Jan 2009 14:15:33 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D2A053A69FE for <tap@core3.amsl.com>; Tue, 20 Jan 2009 14:15:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7e-z0SchoqmT for <tap@core3.amsl.com>; Tue, 20 Jan 2009 14:15:31 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by core3.amsl.com (Postfix) with ESMTP id 7A33D3A6A50 for <tap@ietf.org>; Tue, 20 Jan 2009 14:15:30 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id ACB93924D5; Tue, 20 Jan 2009 17:15:13 -0500 (EST)
Received: from [10.23.42.2] (unknown [69.64.236.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id F0D32924D3; Tue, 20 Jan 2009 17:15:11 -0500 (EST)
Message-ID: <49764CEE.6080505@pobox.com>
Date: Tue, 20 Jan 2009 14:15:10 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Michael Peters <mpeters@plusthree.com>
References: <49763AE1.5@pobox.com> <49763DF7.1080002@plusthree.com>
In-Reply-To: <49763DF7.1080002@plusthree.com>
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: CF3F0F86-E73F-11DD-834E-5720C92D7133-02258300!a-sasl-fastnet.pobox.com
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org Michael Peters wrote:
> But how do you tell if a certain byte (or sequence of bytes) maps to the
> "#" character. Without an encoding you can't tell. "#" is the same byte
> in Latin1, ASCII, UTF-8 and Big5 but is not the same byte (or bytes) in
> UTF-16, UTF-32, UCS-2 or EBCDIC.

The important grammatical parts are specified as bytes.  We already get that
by using ABNF.  "#" is always going to be the byte x23.  So the grammatical
parts of the spec are unambiguous.

Yes, this means if you output raw TAP on a non-ASCII compatible display it
will look funny, but if you have a non-ASCII display you likely already know
how to cope.

One simple way to cope is to run the TAP through a simple parser which
translates the raw ASCII TAP into your native character set changing, for
example, ASCII "ok" into your native "ok".


-- 
39. Not allowed to ask for the day off due to religious purposes, on the
    basis that the world is going to end, more than once.
    -- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
           http://skippyslist.com/list/
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 14:42:20 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 675AA3A6957; Tue, 20 Jan 2009 14:42:20 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09E6C3A6957 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 14:42:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u45Dc33qmM-Y for <tap@core3.amsl.com>; Tue, 20 Jan 2009 14:42:19 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by core3.amsl.com (Postfix) with ESMTP id C71353A6851 for <tap@ietf.org>; Tue, 20 Jan 2009 14:42:17 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 14EAB92732; Tue, 20 Jan 2009 17:42:01 -0500 (EST)
Received: from [10.23.42.2] (unknown [69.64.236.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 23EB292731; Tue, 20 Jan 2009 17:41:58 -0500 (EST)
Message-ID: <49765335.4090209@pobox.com>
Date: Tue, 20 Jan 2009 14:41:57 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <49763AE1.5@pobox.com> <hsfcn45n5bc2ul9e7lrcs0a1e2adjpvo6a@hive.bjoern.hoehrmann.de>
In-Reply-To: <hsfcn45n5bc2ul9e7lrcs0a1e2adjpvo6a@hive.bjoern.hoehrmann.de>
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: 8D517560-E743-11DD-B35A-5720C92D7133-02258300!a-sasl-fastnet.pobox.com
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org Bjoern Hoehrmann wrote:
> * Michael G Schwern wrote:
>> Fortunately, I have a solution.  TAP will have NO CHARACTER SET!  That's
>> right, just not going to specify it.  But not in a sniveling "the character
>> set must be agreed upon by the parties interchanged" way.  We just word it so
>> the user can use any character set.
> 
> That would be problematic as far as the IETF is concerned, as per BCP 18
> (currently RFC 2277): "All protocols MUST identify, for all character
> data, which charset is in use." So if you do not pick a single encoding,
> you have to have some way to identify which encoding is being used.

Maybe I wasn't being clear, because your comment about a security hole via
<script> I don't get.

It's ASCII (or something ASCII compatible) for the grammatical parts with
reasons and descriptions just being byte streams minus certain bytes
(representing things like ASCII "#" and end of line).

Basically, you can think of descriptions and reasons as just being byte
streams with a special byte saying it's done.  The grammar looks like:

EOL             = LF / CRLF
Test-Result     = Status [SP Test-Number] [SP Description]
                   [SP "#" SP Directive [SP Reason]] EOL
Status          = "ok" / "not ok"       ; Whether the test succeeded or failed
Description     = 1*(%x01-0b %x0c %x0e-22 %x24-7f)
                                        ; Anything but EOL and #
Directive       = "SKIP" / "TODO"
Reason          = 1*(%01-0b %0c %0e-7f) ; Anything but EOL

So a Description is a stream of bytes that goes until a # or EOL.  A Reason
goes until EOL.  How those bytes are interpreted is up to the user.


> I think the idea is to rule out using those encodings directly. This is
> not uncommon, for example, e-mail / MIME messages depend on encodings
> being ASCII-compatible (ascii characters map to ascii octets, ascii
> octets map to ascii characters). Encodings like UTF-16 can only be used
> of additional transformation takes place (e.g. quoted-printable or
> base64 encoding).

And I hate them so much.  It's a kludge to bring an ASCII protocol into a
post-ASCII world.  I'd rather design something straight in.


>> This makes the protocol simpler and less restrictive.  It makes it easier to
>> test non-Unicode apps.  Let's say you're working on a Big5 [1] application,
>> you'd naturally want to display your test results in Big5.  If TAP went all
>> Unicode you'd have to translate your Big5 results into Unicode muddying their
>> value as diagnostics.  Similarly, if you're working on a Big5 application you
>> probably have your terminal set to handle Big5 thus reading raw TAP output
>> with Big5 descriptions is most natural.
> 
> But then of course if you do not have your terminal set to Big5 you get
> gibberish, which you may or may not realize, and are less likely to know
> how to fix (besides, as the Wikipedia article points out, there are some
> variants of Big5, so your terminal's Big5 may be a different one than
> the TAP generating application's "Big5").

That's ok.  If you're reading raw TAP involving Big5 and you weren't expecting
it... why were you reading it in the first place?  This is one of those cases
were I'm perfectly happy to use the ISO 8601 cop out of "will be agreed upon
by the parties involved in the exchange".  This is less odious then
restricting output to UTF-8 or something and have to do MIME encoding (which
I'm not sure how you'd wedge that into a description) if you want your
descriptions in, say, Japanese.

Fortunately, a program to translate raw TAP into your native format is trivial.


-- 
124. Two drink limit does not mean first and last.
    -- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
           http://skippyslist.com/list/
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 14:57:49 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EEE003A6A13; Tue, 20 Jan 2009 14:57:49 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64A593A6A13 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 14:57:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NuAA3IMTfmMp for <tap@core3.amsl.com>; Tue, 20 Jan 2009 14:57:48 -0800 (PST)
Received: from mail.plusthree.com (mail.plusthree.com [70.42.42.197]) by core3.amsl.com (Postfix) with ESMTP id 9689C3A6A33 for <tap@ietf.org>; Tue, 20 Jan 2009 14:57:48 -0800 (PST)
Received: from localhost.localdomain (dsl093-241-113.ral1.dsl.speakeasy.net [66.93.241.113]) (authenticated bits=0) by mail.plusthree.com (8.14.2/8.14.2) with ESMTP id n0KMqXj5026080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jan 2009 17:52:34 -0500
Message-ID: <49765658.5060206@plusthree.com>
Date: Tue, 20 Jan 2009 17:55:20 -0500
From: Michael Peters <mpeters@plusthree.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Michael G Schwern <schwern@pobox.com>
References: <49763AE1.5@pobox.com>	<hsfcn45n5bc2ul9e7lrcs0a1e2adjpvo6a@hive.bjoern.hoehrmann.de> <49765335.4090209@pobox.com>
In-Reply-To: <49765335.4090209@pobox.com>
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org Michael G Schwern wrote:

> It's ASCII (or something ASCII compatible) for the grammatical parts with
> reasons and descriptions just being byte streams minus certain bytes
> (representing things like ASCII "#" and end of line).

So we are specifying a character set. ASCII (or compatible in the lower bytes). And if I understand 
you correctly, you're saying the rest can be in whatever encoding you want. So basically TAP streams 
can be mixed-character sets, right? That sounds like a can of worms to me, especially if you have no 
way to specify what that other character set is.

Also, since we aren't giving any meaning to the bytes, what if the x23 byte (#) is the 2nd byte in a 
multi-byte character? How will our character encoding ignorant parser pick up on this?

-- 
Michael Peters
Plus Three, LP

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 15:00:40 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B69643A6833; Tue, 20 Jan 2009 15:00:40 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 93DF93A6A13 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 15:00:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.178
X-Spam-Level: 
X-Spam-Status: No, score=-1.178 tagged_above=-999 required=5 tests=[AWL=-0.993, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tIs2rr9C5QMo for <tap@core3.amsl.com>; Tue, 20 Jan 2009 15:00:38 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 425BC3A6833 for <tap@ietf.org>; Tue, 20 Jan 2009 15:00:37 -0800 (PST)
Received: (qmail invoked by alias); 20 Jan 2009 23:00:20 -0000
Received: from static-87-79-236-202.netcologne.de (EHLO klangraum) [87.79.236.202] by mail.gmx.net (mp012) with SMTP; 21 Jan 2009 00:00:20 +0100
X-Authenticated: #163624
X-Provags-ID: V01U2FsdGVkX19oT14iM/hoO6UvTVvpseSc53lzicOLkihcfs/UhB IY8PEOlX07DzjU
Date: Wed, 21 Jan 2009 00:00:18 +0100
From: Aristotle Pagaltzis <pagaltzis@gmx.de>
To: tap@ietf.org
Message-ID: <20090120230018.GB1318@klangraum.plasmasturm.org>
Mail-Followup-To: tap@ietf.org
References: <a51e610c0901191656u6d20f780mf47a077229d91abd@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <a51e610c0901191656u6d20f780mf47a077229d91abd@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.78
Subject: Re: [tap] Ann: libtap++
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org KiBMZW9uIFRpbW1lcm1hbnMgPGZhd2FrYUBnbWFpbC5jb20+IFsyMDA5LTAxLTIwIDAyOjAwXToK
PiBJJ20gbm90IHN1cmUgdGhpcyBpcyB0aGUgcmlnaHQgcGxhY2UgZm9yIGFubm91bmNlbWVudHMg
bGlrZQo+IHRoaXMsIGJ1dCBsYWNraW5nIGFueSBvdGhlcuKApgoKVGhpcyBwbGFjZSB3aWxsIGRv
IGp1c3QgZmluZS4gTmljZSB3b3JrIHRvby4KClJlZ2FyZHMsCi0tIApBcmlzdG90bGUgUGFnYWx0
emlzIC8vIDxodHRwOi8vcGxhc21hc3R1cm0ub3JnLz4KX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18KdGFwIG1haWxpbmcgbGlzdAp0YXBAaWV0Zi5vcmcKaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90YXAK

From tap-bounces@ietf.org  Tue Jan 20 15:24:45 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E7753A6A33; Tue, 20 Jan 2009 15:24:45 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 717B828C0D7 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 15:24:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.261
X-Spam-Level: 
X-Spam-Status: No, score=-2.261 tagged_above=-999 required=5 tests=[AWL=0.338,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1mL65mMHxRJk for <tap@core3.amsl.com>; Tue, 20 Jan 2009 15:24:43 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id D90F13A6A33 for <tap@ietf.org>; Tue, 20 Jan 2009 15:24:42 -0800 (PST)
Received: (qmail invoked by alias); 20 Jan 2009 23:24:25 -0000
Received: from static-87-79-236-202.netcologne.de (EHLO klangraum) [87.79.236.202] by mail.gmx.net (mp069) with SMTP; 21 Jan 2009 00:24:25 +0100
X-Authenticated: #163624
X-Provags-ID: V01U2FsdGVkX18jke1n3CEjgXtc33eJxCF/UieRzUky6dsUc7jJaZ 6lEzPLkkSIcWRK
Date: Wed, 21 Jan 2009 00:24:21 +0100
From: Aristotle Pagaltzis <pagaltzis@gmx.de>
To: tap@ietf.org
Message-ID: <20090120232421.GC1318@klangraum.plasmasturm.org>
Mail-Followup-To: tap@ietf.org
References: <49763AE1.5@pobox.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <49763AE1.5@pobox.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.6
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org KiBNaWNoYWVsIEcgU2Nod2VybiA8c2Nod2VybkBwb2JveC5jb20+IFsyMDA5LTAxLTIwIDIyOjAw
XToKPiBXaGVuIHdyaXRpbmcgdGhlIFRBUCBzcGVjIHRoZSBwcm9ibGVtIG9mIGNoYXJhY3RlciBz
ZXRzIGNvbWVzCj4gdXAuIFdoYXQgY2hhcmFjdGVyIHNldCBpcyBUQVAgZ29pbmcgdG8gdXNlPyBB
U0NJST8gVVRGLTg/IEZ1bGwKPiBVbmljb2RlPyBTdGlja3kuCj4KPiBGb3J0dW5hdGVseSwgSSBo
YXZlIGEgc29sdXRpb24uIFRBUCB3aWxsIGhhdmUgTk8gQ0hBUkFDVEVSIFNFVCEKClRoYXTigJlz
IG5vdCBhIHNvbHV0aW9uLCBpdOKAmXMgYSBub24tc29sdXRpb24uCgpKdXN0IHNheWluZyDigJxp
dOKAmXMgYWxsIG9jdGV0cyBhcyBmYXIgYXMgVEFQIGlzIGNvbmNlcm5lZOKAnSB3aWxsCmxlYWQg
dG8gdGhlIHNhbWUgbWVzcyBhcyBVbml4IGZpbGVzeXN0ZW1zIGFyZSBpbjogR1VJcyBjYW5ub3QK
cmVsaWFibHkgZGlzcGxheSBmaWxlbmFtZXMgYmVjYXVzZSB0aGV54oCZcmUganVzdCBvY3RldHMg
YW5kIHRoZQp0ZXh0dWFsIG1lYW5pbmcgZGVwZW5kcyBvbiB0aGUgbG9jYWxlIG9mIHRoZSB1c2Vy
IHdobyBjcmVhdGVkCnRoZSBmaWxlLCBhcyB3ZWxsIGFzIHRoZSBwaGFzZSBvZiB0aGUgbW9vbi4K
CkNvbnNpZGVyIHRyeWluZyB0byBjb2xsZWN0IFRBUCBzdHJlYW1zIG92ZXIgSFRUUCBmcm9tIG1h
bnkKZGlmZmVyZW50IHNvdXJjZXMuIElzIGl0IHNhZmUgdG8gbWl4IHRoZW0gdG9nZXRoZXI/IFdo
byBrbm93cz8KSXTigJlzIGFsbCBvY3RldHMhIEhvdyBkbyBJIGRpc3BsYXkgdGhlbT8gSSBndWVz
cyBJIHNob3VsZCBqdXN0CnNob3cgdGhlIHVzZXIgaGV4ZHVtcHMuIEhvb3JheS4KClBlcnNvbmFs
bHkgSSB3b3VsZCBzYXkgc29tZXRoaW5nIGxpa2Ug4oCcaXTigJlzIGFsbCBVVEYtOCBieSBkZWZh
dWx0CnVubGVzcyB5b3Ugc2lnbmlmeSBvdGhlcndpc2Ugd2l0aCBhIHNwZWNpYWwgZGlyZWN0aXZl
4oCdICh3aGljaCB3ZQp3aWxsIGhhdmUgdG8gaW52ZW50KS4gQSBub3RhdGlvbiBmb3Igcm91bmR0
cmlwcGluZyBhY3R1YWwgbm9uLQp0ZXh0dWFsIG9jdGV0IHNlcXVlbmNlcyB3b3VsZCBiZSB1c2Vm
dWwgYWxzby4gV2UgY291bGQgbWFuZGF0ZQpzb21ldGhpbmcgaW5oZXJlbnRseSBwcm9ncmFtbWVy
LXJlYWRhYmxlIGZvciB0aGlzIHB1cnBvc2UuCgpTb3JyeSwgdGhlcmUgaXMgbm8gd2luZGluZyBv
dXQgb2YgdGhpcyBpc3N1ZS4KClJlZ2FyZHMsCi0tIApBcmlzdG90bGUgUGFnYWx0emlzIC8vIDxo
dHRwOi8vcGxhc21hc3R1cm0ub3JnLz4KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18KdGFwIG1haWxpbmcgbGlzdAp0YXBAaWV0Zi5vcmcKaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90YXAK

From tap-bounces@ietf.org  Tue Jan 20 16:01:03 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24BF73A6403; Tue, 20 Jan 2009 16:01:03 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 874F63A6403 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 16:01:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level: 
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=0.930,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KdR3Jw2QdmdY for <tap@core3.amsl.com>; Tue, 20 Jan 2009 16:01:00 -0800 (PST)
Received: from web65709.mail.ac4.yahoo.com (web65709.mail.ac4.yahoo.com [76.13.9.101]) by core3.amsl.com (Postfix) with SMTP id 7EA5A3A6822 for <tap@ietf.org>; Tue, 20 Jan 2009 16:01:00 -0800 (PST)
Received: (qmail 4826 invoked by uid 60001); 21 Jan 2009 00:00:42 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=sP4Ygnd743p6BjHQlmawGwsoDpVMRG1rHnjtQAI7FU5P084IJeW3m8/tC8JQSAoEgLnNe+nk+t94UL0cBU9jrpnCTZseez/ygGF2vFz97M4HMBQrPgEKBSNDb4wZakKP8p7K9ZadU+GnSSeZbN9WvTGWdXtwok4M1GSBIVgKoIE=;
X-YMail-OSG: TkF.tKsVM1ngdPB9XRUn.rb94IOPAg9H6ADscmlhMxxfTa9FTe9ZqvvqEKrX00qrfsAnPjEb8VD11YZPU8l_cqV5e5O7yxbTBUPEYIKh7ipWokEdzrsSqTdhz1OMbk7PJ..S1mNCBfRoui2hyY352uSeoYLM217cW7Pg2F_tMV7W.0b9CnhdInM1lucsG.ktaANYjZEKa41oL5iyOA--
Received: from [91.85.130.147] by web65709.mail.ac4.yahoo.com via HTTP; Tue, 20 Jan 2009 16:00:41 PST
X-Mailer: YahooMailRC/1155.45 YahooMailWebService/0.7.260.1
References: <49763AE1.5@pobox.com>
Date: Tue, 20 Jan 2009 16:00:41 -0800 (PST)
From: Ovid <publiustemp-tapx@yahoo.com>
To: Michael G Schwern <schwern@pobox.com>, tap@ietf.org
MIME-Version: 1.0
Message-ID: <211200.97046.qm@web65709.mail.ac4.yahoo.com>
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org ----- Original Message ----

> From: Michael G Schwern <schwern@pobox.com>

> When writing the TAP spec the problem of character sets comes up.  What
> character set is TAP going to use?  ASCII?  UTF-8?  Full Unicode?  Sticky.

I wasn't aware that there *was* a problem with character sets.  Why not UTF8?  What's wrong with that?  If you can articulate *why* this is a problem, I can better understand your solution.

 
Cheers,
Ovid
--
Buy the book         - http://www.oreilly.com/catalog/perlhks/
Tech blog            - http://use.perl.org/~Ovid/journal/
Twitter              - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 16:01:52 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3093D3A6822; Tue, 20 Jan 2009 16:01:52 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 83FE63A6887 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 16:01:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level: 
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c-NsjoN8+FQI for <tap@core3.amsl.com>; Tue, 20 Jan 2009 16:01:49 -0800 (PST)
Received: from smtp.kineticode.com (host-201.commandprompt.net [207.173.203.201]) by core3.amsl.com (Postfix) with ESMTP id D6D573A6822 for <tap@ietf.org>; Tue, 20 Jan 2009 16:01:49 -0800 (PST)
Received: from [192.168.1.102] (c-76-105-135-51.hsd1.or.comcast.net [76.105.135.51]) by smtp.kineticode.com (Postfix) with ESMTPSA id A6C5850805B; Tue, 20 Jan 2009 15:57:01 -0800 (PST)
Message-Id: <E63A9E22-DEE6-4F80-B318-68D7AA930795@kineticode.com>
From: "David E. Wheeler" <david@kineticode.com>
To: Aristotle Pagaltzis <pagaltzis@gmx.de>
In-Reply-To: <20090120232421.GC1318@klangraum.plasmasturm.org>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 20 Jan 2009 16:01:32 -0800
References: <49763AE1.5@pobox.com> <20090120232421.GC1318@klangraum.plasmasturm.org>
X-Mailer: Apple Mail (2.930.3)
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="windows-1252"; Format="flowed"; DelSp="yes"
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org On Jan 20, 2009, at 3:24 PM, Aristotle Pagaltzis wrote:

> Personally I would say something like =93it=92s all UTF-8 by default
> unless you signify otherwise with a special directive=94 (which we
> will have to invent). A notation for roundtripping actual non-
> textual octet sequences would be useful also. We could mandate
> something inherently programmer-readable for this purpose.

+1

Encodings are hard. Let's get them right rather than trying to ignore  =

the problem.

Best,

David
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 16:02:52 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F09B3A6822; Tue, 20 Jan 2009 16:02:52 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9687C3A6887 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 16:02:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level: 
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x2nLy9u08bXx for <tap@core3.amsl.com>; Tue, 20 Jan 2009 16:02:49 -0800 (PST)
Received: from smtp.kineticode.com (host-201.commandprompt.net [207.173.203.201]) by core3.amsl.com (Postfix) with ESMTP id E3C853A6822 for <tap@ietf.org>; Tue, 20 Jan 2009 16:02:49 -0800 (PST)
Received: from [192.168.1.102] (c-76-105-135-51.hsd1.or.comcast.net [76.105.135.51]) by smtp.kineticode.com (Postfix) with ESMTPSA id D509E50805B; Tue, 20 Jan 2009 15:58:01 -0800 (PST)
Message-Id: <549EDE68-44E3-4B88-A6A4-1028C1CED488@kineticode.com>
From: "David E. Wheeler" <david@kineticode.com>
To: Ovid <publiustemp-tapx@yahoo.com>
In-Reply-To: <211200.97046.qm@web65709.mail.ac4.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 20 Jan 2009 16:02:33 -0800
References: <49763AE1.5@pobox.com> <211200.97046.qm@web65709.mail.ac4.yahoo.com>
X-Mailer: Apple Mail (2.930.3)
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org On Jan 20, 2009, at 4:00 PM, Ovid wrote:

> I wasn't aware that there *was* a problem with character sets.  Why  
> not UTF8?  What's wrong with that?  If you can articulate *why* this  
> is a problem, I can better understand your solution.

Some people want to use encodings other than UTF-8 in their TAP  
output. Think about a test failure where an exception thrown by the  
app includes an error message written in Big5.

Best,

David

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 16:30:43 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC3443A6822; Tue, 20 Jan 2009 16:30:43 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 882223A6822 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 16:30:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[AWL=-1.600, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SbsVQPtxWVke for <tap@core3.amsl.com>; Tue, 20 Jan 2009 16:30:41 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id E743D3A67B6 for <tap@ietf.org>; Tue, 20 Jan 2009 16:30:40 -0800 (PST)
Received: (qmail invoked by alias); 21 Jan 2009 00:30:22 -0000
Received: from dslb-088-074-182-112.pools.arcor-ip.net (EHLO hive) [88.74.182.112] by mail.gmx.net (mp065) with SMTP; 21 Jan 2009 01:30:22 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+oBItLlfuomGlMoinv8or9xz1rS71r5TUwt8jhM4 TBFVXO4LrWQJSh
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Michael G Schwern <schwern@pobox.com>
Date: Wed, 21 Jan 2009 01:30:26 +0100
Message-ID: <tuocn492urj9grdtlv1bn244u7gu325mmq@hive.bjoern.hoehrmann.de>
References: <49763AE1.5@pobox.com> <hsfcn45n5bc2ul9e7lrcs0a1e2adjpvo6a@hive.bjoern.hoehrmann.de> <49765335.4090209@pobox.com>
In-Reply-To: <49765335.4090209@pobox.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.63
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org * Michael G Schwern wrote:
>Maybe I wasn't being clear, because your comment about a security hole via
><script> I don't get.

So how would you write a general purpose tap2html script that can safely
support untrusted tap streams? For the HTML code you have two options,
either you declare some character encoding, or you declare none. If you
declare none, a browser will try to auto-detect it based on the bytes in
the document. As an attacker would control the bytes, he could smuggle
in a certain sequence that would make the browser guess poorly, and then
another sequence that would do something malicious.

If you do specify an encoding, you may not have accounted for unusual
sequences that would need escaping, in particular, if the tap document
was not in the encoding you specified for the HTML code, there may be
errors. Generally either case could be exploited. So it would be quite
difficult to write a general purpose automated tap2html script, more so
if people are careless and stuff data of varying encodings into a single
tap stream.

To give two simple examples, if you do not declare an encoding, some
browsers may autodetect UTF-7 which is a strange format that maps any
Unicode string into only ascii octets. There are very many ways to en-
code a string like "<script>" in it. Another example, if you declare the
us-ascii encoding, some browsers will treat bytes with the 8th bit set
as if the 8th bit wasn't set, so you have two ways to render <script> in
that encoding.

In contrast, if you'd have some declaration ala

  TAP version 14 encoding big5

You can check that all the strings actually are in Big5 and transcode
them to whatever encoding you need, or just echo it after checking and
proper escaping.

>That's ok.  If you're reading raw TAP involving Big5 and you weren't expec=
ting
>it... why were you reading it in the first place?  This is one of those ca=
ses
>were I'm perfectly happy to use the ISO 8601 cop out of "will be agreed up=
on
>by the parties involved in the exchange".

You are assuming that it is not desirable to have an application that
just takes random tap streams and does something interesting with them
that involves processing the strings. I am unsure how valid that is. For
example, getting meaningful diagnostics from your build system via email
would seem a worthwile functionality. But the writer of the tap2mail
script cannot know you are using big5, or utf8, or whatever, yet the
script needs to know to produce a proper email message from it.
-- =

Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehrma=
nn.de
Am Badedeich 7 =B7 Telefon: +49(0)160/4415681 =B7 http://www.bjoernsworld.de
25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev.d=
e/ =

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 16:46:29 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A8FB3A67B6; Tue, 20 Jan 2009 16:46:29 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 19AD63A6A72 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 16:46:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lL8SECpJSqiV for <tap@core3.amsl.com>; Tue, 20 Jan 2009 16:46:27 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-quonix.sasl.smtp.pobox.com [208.72.237.25]) by core3.amsl.com (Postfix) with ESMTP id 178643A67B6 for <tap@ietf.org>; Tue, 20 Jan 2009 16:46:26 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTP id 5D70A1CDB1; Tue, 20 Jan 2009 19:46:09 -0500 (EST)
Received: from windhund.local (unknown [75.150.41.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 72B231CD7C; Tue, 20 Jan 2009 19:46:05 -0500 (EST)
Message-ID: <49767049.5050403@pobox.com>
Date: Tue, 20 Jan 2009 16:46:01 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <49763AE1.5@pobox.com> <hsfcn45n5bc2ul9e7lrcs0a1e2adjpvo6a@hive.bjoern.hoehrmann.de> <49765335.4090209@pobox.com> <tuocn492urj9grdtlv1bn244u7gu325mmq@hive.bjoern.hoehrmann.de>
In-Reply-To: <tuocn492urj9grdtlv1bn244u7gu325mmq@hive.bjoern.hoehrmann.de>
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: E4D9470C-E754-11DD-B2D5-BE78113D384A-02258300!a-sasl-quonix.pobox.com
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org Bjoern Hoehrmann wrote:
> * Michael G Schwern wrote:
>> Maybe I wasn't being clear, because your comment about a security hole via
>> <script> I don't get.
> 
> So how would you write a general purpose tap2html script that can safely
> support untrusted tap streams? For the HTML code you have two options,
> either you declare some character encoding, or you declare none. If you
> declare none, a browser will try to auto-detect it based on the bytes in
> the document. As an attacker would control the bytes, he could smuggle
> in a certain sequence that would make the browser guess poorly, and then
> another sequence that would do something malicious.

I think the key difference here is I'm talking about "<script>" as bytes 60
115 99 114 105 112 116 62 which just happen to come out as "<script>" in
ASCII.  You're talking about "<script>" as being whatever bytes "<", "s",
etc... turn out to be in the given character set.  I fully agree that the
latter is madness.

There is no guessing about the TAP grammatical elements.  Things like "ok" and
"SKIP" are a fixed series of bytes, full stop.  I'm only talking about the
reasons and descriptions which would be the equivalent of HTML CDATA.


> In contrast, if you'd have some declaration ala
> 
>   TAP version 14 encoding big5
> 
> You can check that all the strings actually are in Big5 and transcode
> them to whatever encoding you need, or just echo it after checking and
> proper escaping.

That's an interesting proposal for an extension.


-- 
24. Must not tell any officer that I am smarter than they are, especially
    if it's true.
    -- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
           http://skippyslist.com/list/
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 17:54:05 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B26783A688F; Tue, 20 Jan 2009 17:54:05 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EB1E3A68AD for <tap@core3.amsl.com>; Tue, 20 Jan 2009 17:54:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXnVAQbsns+J for <tap@core3.amsl.com>; Tue, 20 Jan 2009 17:54:04 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-quonix.sasl.smtp.pobox.com [208.72.237.25]) by core3.amsl.com (Postfix) with ESMTP id 50B423A688F for <tap@ietf.org>; Tue, 20 Jan 2009 17:54:03 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTP id CB9421CE7F for <tap@ietf.org>; Tue, 20 Jan 2009 20:53:46 -0500 (EST)
Received: from windhund.local (unknown [75.150.41.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 7D01B1CE7D for <tap@ietf.org>; Tue, 20 Jan 2009 20:53:46 -0500 (EST)
Message-ID: <49768028.1060309@pobox.com>
Date: Tue, 20 Jan 2009 17:53:44 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tap@ietf.org
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: 57473E26-E75E-11DD-A1C2-BE78113D384A-02258300!a-sasl-quonix.pobox.com
Subject: [tap] Fun with random TAP generation.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org I found a little program that will generate grammatically valid documents from
ABNF grammars, abnfgen.
http://www.quut.com/abnfgen/

On the up side, I haven't seen it produce anything that looks invalid and I
already found a bug in the grammar.  On the down side, allowing such a wide
range of characters is a little disconcerting as it plunks in backspace and
such.  To see what's really going on, consider piping the output through less
-UR.  Or replace Safe-String's definition with 1*VCHAR.

Here's an example.

$ abnfgen -c -r1234567 ~/tmp/tap.abnf
##
#o_^N+|F,h#CDk`OWrPY{&3l(d
TAP version 3816
1..0 TODO 2549769604;
bail out! U
#0?5tA
#ERXe
NOT OK 6 # TODO qu7)y%
#<=bn'
BAIL OUT!
baIL out! z6:9m
#J1\g
#G
ok f
not ok 7
#S
#[aT2Vpj-ws".4x
#vBHM/LI;
#K
#~>$i
#!
BaIL Out!
#8
#*c@Q
#Z

Might be fun to shove that into TAP::Parser and see what happens.


-- 
I do have a cause though. It's obscenity. I'm for it.
    - Tom Lehrer

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 18:09:39 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 519833A682C; Tue, 20 Jan 2009 18:09:39 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ECFBF3A68C5 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 18:09:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id trjUHfovLMOJ for <tap@core3.amsl.com>; Tue, 20 Jan 2009 18:09:37 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-quonix.sasl.smtp.pobox.com [208.72.237.25]) by core3.amsl.com (Postfix) with ESMTP id 191643A682C for <tap@ietf.org>; Tue, 20 Jan 2009 18:09:36 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTP id F0E1C1CE7F for <tap@ietf.org>; Tue, 20 Jan 2009 21:09:19 -0500 (EST)
Received: from windhund.local (unknown [75.150.41.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 71A651CE80 for <tap@ietf.org>; Tue, 20 Jan 2009 21:09:19 -0500 (EST)
Message-ID: <497683CD.4030306@pobox.com>
Date: Tue, 20 Jan 2009 18:09:17 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tap@ietf.org
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: 837B1BBE-E760-11DD-AE13-BE78113D384A-02258300!a-sasl-quonix.pobox.com
Subject: [tap] Grammar errors vs test failure. Can we put pass and fail in the grammar?
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org abnfgen created some nonsense, but grammatically correct, TAP streams.  For
example...

1..0 SKIP foo
ok 1

1..1
not ok 1 # SKIP

1..1
ok 0

1..2 TODO 2 5;
ok 1
not ok 2

1..5 SKIP foo


We can specify all this as being illegal in the grammar.  For example, this
partial grammar specifies that a skip all can not have any test results.

Stream          = Header (Plan Body / Body Plan / Skip-All) Footer
Header          = [Comments] [Version]
Footer          = [Comments]

Plan            = "1.." Number-Of-Tests [SP Plan-Todo] EOL
Skip-All        = "1..0 SKIP" *(SP Reason) EOL
Plan-Todo       = "todo" 1*(SP Test-Number) ";"   ; Obsolete

But now this:

1..0 SKIP foo
ok 1

Is not a parsable, but failing, stream.  It is now unparsable.  It is not TAP.
 A TAP displayer can't do anything with it except spit it back at the user.

So as convenient as it would be to strictly spell out all the ways to produce
nonsense TAP in the grammar, I'm against it if it means making the nonsense
completely unparsable.  However, it would be nice to formally specify what a
passing and failing TAP document is.

What if Stream was split into Passing-Stream and Failing-Stream?  And then we
wrote out all the ways a stream can be considered failing?  Then a TAP parser
simply tries to parse a TAP document with Passing-Stream.  If that works, its
a pass!  If not they verify it's valid TAP with Stream and call it a fail. [1]

Obviously this will produce a much more complicated grammar, but I think
there's huge value here in making it very easy to write a TAP parser.  Much of
the complexity of TAP is in figuring out if it failed.


[1] I predict it's easier to spell out all the ways a TAP stream can pass then
all the ways it can fail.  Thus writing out a Passing grammar as opposed to a
Failing grammar.


-- 
We do what we must because we can.
For the good of all of us,
Except the ones who are dead.
    -- Jonathan Coulton, "Still Alive"

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 18:35:39 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 921C83A67B6; Tue, 20 Jan 2009 18:35:39 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 866D03A6989 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 18:35:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=0.301,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PsuCeqUEF6ze for <tap@core3.amsl.com>; Tue, 20 Jan 2009 18:35:37 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 52CDE3A67B6 for <tap@ietf.org>; Tue, 20 Jan 2009 18:35:36 -0800 (PST)
Received: (qmail invoked by alias); 21 Jan 2009 02:35:19 -0000
Received: from static-87-79-236-202.netcologne.de (EHLO klangraum) [87.79.236.202] by mail.gmx.net (mp063) with SMTP; 21 Jan 2009 03:35:19 +0100
X-Authenticated: #163624
X-Provags-ID: V01U2FsdGVkX1/kdnpSMkzkehThCk/0YmG5KkX8VqSeTwIvbRgjMZ qGM5DKFBHBpW+/
Date: Wed, 21 Jan 2009 03:35:14 +0100
From: Aristotle Pagaltzis <pagaltzis@gmx.de>
To: tap@ietf.org
Message-ID: <20090121023514.GA4093@klangraum.plasmasturm.org>
Mail-Followup-To: tap@ietf.org
References: <49763AE1.5@pobox.com> <hsfcn45n5bc2ul9e7lrcs0a1e2adjpvo6a@hive.bjoern.hoehrmann.de> <49765335.4090209@pobox.com> <tuocn492urj9grdtlv1bn244u7gu325mmq@hive.bjoern.hoehrmann.de> <49767049.5050403@pobox.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <49767049.5050403@pobox.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.62
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org KiBNaWNoYWVsIEcgU2Nod2VybiA8c2Nod2VybkBwb2JveC5jb20+IFsyMDA5LTAxLTIxIDAxOjUw
XToKPiBJJ20gb25seSB0YWxraW5nIGFib3V0IHRoZSByZWFzb25zIGFuZCBkZXNjcmlwdGlvbnMK
ClJpZ2h0LCBhbmQgaWYgdGhlcmUgaXMgbm8gZGVjbGFyZWQgZW5jb2RpbmcgZm9yIHRob3NlLCB0
aGVuIHRoZQpvbmx5ICpzYWZlKiB3YXkgdG8gZGlzcGxheSB0aGVtIGlzIGFzIGEgaGV4ZHVtcC4g
QWZ0ZXIgYWxsIGl04oCZcwpqdXN0IGEgYnVuY2ggb2YgYnl0ZXMgd2l0aCBubyBhc3NvY2lhdGVk
IGVuY29kaW5nLiBUaGF04oCZcyBub3QgdGhlCmhlaWdodCBvZiB1c2VyZnJpZW5kbGluZXNzLgoK
PiB3aGljaCB3b3VsZCBiZSB0aGUgZXF1aXZhbGVudCBvZiBIVE1MIENEQVRBLgoKVGhlcmUgaXMg
bm8gc3VjaCB0aGluZyBhcyBDREFUQSBpbiBIVE1MLiBJdCBvbmx5IGV4aXN0cyBpbiBYTUwuCkFu
ZCBpdOKAmXMgbm90IGVxdWl2YWxlbnQgdGhlbiBlaXRoZXI6IHRoZSBjb250ZW50IG9mIENEQVRB
CnNlY3Rpb25zIGlzIHRleHR1YWwgZGF0YSBpbiB0aGUgc2FtZSBlbmNvZGluZyBhcyB0aGUgcmVz
dCBvZiB0aGUKZG9jdW1lbnQuCgo+ID4gICBUQVAgdmVyc2lvbiAxNCBlbmNvZGluZyBiaWc1Cj4K
PiBUaGF0J3MgYW4gaW50ZXJlc3RpbmcgcHJvcG9zYWwgZm9yIGFuIGV4dGVuc2lvbi4KCkhhdmVu
4oCZdCBJIHNlZW4gdGhpcyBzb21ld2hlcmUgYmVmb3Jl4oCmPyAqaGVhZHNjcmF0Y2gqCgrigKYg
b2ggd2FpdDoKCiAgICA8P3htbCB2ZXJzaW9uPSIxLjAiIGVuY29kaW5nPSJ1dGYtOCI/PgoKOi0p
CgooRXhhY3RseSB0aGUga2luZCBvZiB0aGluZyBJIHdhcyBzYXlpbmcgd2UgbmVlZCwgb2J2aW91
c2x5LikKClJlZ2FyZHMsCi0tIApBcmlzdG90bGUgUGFnYWx0emlzIC8vIDxodHRwOi8vcGxhc21h
c3R1cm0ub3JnLz4KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18KdGFwIG1haWxpbmcgbGlzdAp0YXBAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby90YXAK

From tap-bounces@ietf.org  Tue Jan 20 18:47:16 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A4243A69CC; Tue, 20 Jan 2009 18:47:16 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 731703A6A08 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 18:47:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pk5+uUMwmxQT for <tap@core3.amsl.com>; Tue, 20 Jan 2009 18:47:14 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-quonix.sasl.smtp.pobox.com [208.72.237.25]) by core3.amsl.com (Postfix) with ESMTP id 7A2C83A69CC for <tap@ietf.org>; Tue, 20 Jan 2009 18:47:12 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTP id 07B2F1CE3F; Tue, 20 Jan 2009 21:46:56 -0500 (EST)
Received: from windhund.local (unknown [75.150.41.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 1BEA31C9A1; Tue, 20 Jan 2009 21:46:53 -0500 (EST)
Message-ID: <49768C9C.8000109@pobox.com>
Date: Tue, 20 Jan 2009 18:46:52 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Ovid <publiustemp-tapx@yahoo.com>
References: <49763AE1.5@pobox.com> <211200.97046.qm@web65709.mail.ac4.yahoo.com>
In-Reply-To: <211200.97046.qm@web65709.mail.ac4.yahoo.com>
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: C43035EA-E765-11DD-8B9B-BE78113D384A-02258300!a-sasl-quonix.pobox.com
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org Ovid wrote:
> I wasn't aware that there *was* a problem with character sets.  Why not UTF8?  What's wrong with that?  If you can articulate *why* this is a problem, I can better understand your solution.

As in the Big5 example, if you're testing a program using Big5 (or anything
that's not UTF8 compatible, Latin 1?) but TAP can only output in UTF8, now you
have the awkward problem of translating all your Big5 strings into UTF8 before
outputting them.  This adds unnecessary complexity to the simple case where
TAP producer and parser are run by the same person.  And the translation means
diagnostic information might be lost or distorted.

I think this is one of those issues which we can't enforce.  Whatever
character set we specify for TAP strings is really irrelevant as it's all just
interpretation.  If we adapt the grammar I proposed earlier, where it's just a
byte stream with certain bytes forbidden, you can still throw a Big5 string
into a TAP description and the parser will deal with it just fine.

Language like this should cover it:

"TAP strings must be in UTF8 unless the interchange parties agree otherwise". [1]

This allows any given TAP displayer to assume UTF8 unless told otherwise,
while giving enough wiggle room for non-UTF8 programs to be tested without
violating the TAP spec and without having to do a bunch of translation.  And
it doesn't change the parser one bit.  In fact, it lines up with current
implementation.  TAP::Parser::Grammar matches descriptions as "anything but a #".


[1] That "interchange parties" language being the standard issue cop-out from
ISO 8601.


-- 
I'm pale as formica, social skills stunted small. But I'm accurate
like a pica, I know the capital of Nepal. I'm the nemesis of error,
dreadful diction fears my skills, more inquisitive than Jim Lehrer,
snottier than Beverly Hills.
    -- I.L.O.P. Secret Rap  http://goats.com/archive/020830.html
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 20 19:18:09 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D19E43A682C; Tue, 20 Jan 2009 19:18:09 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 840413A682C for <tap@core3.amsl.com>; Tue, 20 Jan 2009 19:18:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5gZDuTLixXn4 for <tap@core3.amsl.com>; Tue, 20 Jan 2009 19:18:07 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by core3.amsl.com (Postfix) with ESMTP id 99E0B3A6863 for <tap@ietf.org>; Tue, 20 Jan 2009 19:18:05 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 5B27C92D46 for <tap@ietf.org>; Tue, 20 Jan 2009 22:17:49 -0500 (EST)
Received: from windhund.local (unknown [75.150.41.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id C786892D45 for <tap@ietf.org>; Tue, 20 Jan 2009 22:17:48 -0500 (EST)
Message-ID: <497693D7.8090101@pobox.com>
Date: Tue, 20 Jan 2009 19:17:43 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tap@ietf.org
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: 14DDC2EC-E76A-11DD-BA01-5720C92D7133-02258300!a-sasl-fastnet.pobox.com
Subject: [tap] Passing Grammar
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org I made a first cut of a grammar for a passing TAP stream.  You can find it here:
http://testanything.org/wiki/index.php/Talk:TAP_at_IETF:_Draft_Standard#Passing_Grammar

Generating some TAP streams from it, it seems kosher.  The plan is nonsense,
though, and I can't think of a way we can encode a plan or test sequence
violation in the grammar.  For example...

ok 9238
not ok 5 # TODO
1..9085934126779

Each individual test passes, but they're A) out of sequence B) missing tests
and C) didn't run enough tests.

Fortunately, those are relatively easy for the parser to keep track of.  So I
think there's value in a grammar which does a good chunk of the pass checks.
Even if it's just enough to determine if a single line is passing or failing,
like so:

TAP-Line        = (Passing-Line / Failing-Line)
Passing-Line    = (Simple-OK / Passing-TODO / Failing-TODO / Passing-SKIP) EOL
Failing-Line    = (Simple-Fail / Failing-SKIP) EOL

Simple-OK       = "ok" [SP Test-Number] [SP Description]
Simple-Fail     = "not ok" [SP Test-Number] [SP Description]
Passing-TODO    = Simple-OK   SP TODO-Directive
Failing-TODO    = Simple-FAIL SP TODO-Directive
Passing-SKIP    = Simple-OK   SP SKIP-Directive
Failing-SKIP    = Simple-FAIL SP SKIP-Directive
TODO-Directive  = "# TODO" [SP Reason]
SKIP-Directive  = "# SKIP" [SP Reason]

Test-Number     = %x31-39 *DIGIT        ; Starting at 1

Description     = Safe-String           ; Description of this test.
Reason          = String                ; Reason for a directive

EOL             = LF             ; Specific to the system producing the stream
Safe-String     = 1*VCHAR                  ; UTF8 without EOL or "#"
String          = 1*(Safe-String / "#")    ; UTF8 without EOL


I think that would be useful.


-- 
"Clutter and overload are not an attribute of information,
 they are failures of design"
    -- Edward Tufte
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Wed Jan 21 04:32:05 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4318328C0F6; Wed, 21 Jan 2009 04:32:05 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BABDC28C0F6 for <tap@core3.amsl.com>; Wed, 21 Jan 2009 04:32:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WMseXOFUCnOI for <tap@core3.amsl.com>; Wed, 21 Jan 2009 04:32:04 -0800 (PST)
Received: from post.hexten.net (post.hexten.net [75.127.65.154]) by core3.amsl.com (Postfix) with ESMTP id 129103A677E for <tap@ietf.org>; Wed, 21 Jan 2009 04:32:04 -0800 (PST)
Received: from voodoo.ripley (ca93nt.hexten.net [82.152.157.85]) by post.hexten.net (Postfix) with ESMTP id 3A0CD18945C1; Wed, 21 Jan 2009 12:31:42 +0000 (GMT)
Message-Id: <01903BA7-3B0E-4DE9-A9CE-6A765B90A474@hexten.net>
From: Andy Armstrong <andy@hexten.net>
To: Michael Peters <mpeters@plusthree.com>
In-Reply-To: <49763DF7.1080002@plusthree.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 21 Jan 2009 12:31:41 +0000
References: <49763AE1.5@pobox.com> <49763DF7.1080002@plusthree.com>
X-Mailer: Apple Mail (2.930.3)
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org On 20 Jan 2009, at 21:11, Michael Peters wrote:
> But how do you tell if a certain byte (or sequence of bytes) maps to  
> the "#" character. Without an encoding you can't tell. "#" is the  
> same byte in Latin1, ASCII, UTF-8 and Big5 but is not the same byte  
> (or bytes) in UTF-16, UTF-32, UCS-2 or EBCDIC.


What we've implemented is that TAP < v13 is ASCII (or some superset  
thereof) and TAP >= v13 is UTF-8.

I'm working on the assumption that, because UTF-8 is already a  
variable length encoding and has codespace for future expansion, it's  
the most future proof encoding extant. I don't think that's a  
particularly daring assumption :)

-- 
Andy Armstrong, Hexten



_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Wed Jan 21 05:14:14 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC5E83A6924; Wed, 21 Jan 2009 05:14:14 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C0773A6924 for <tap@core3.amsl.com>; Wed, 21 Jan 2009 05:14:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6W7AXFO475eD for <tap@core3.amsl.com>; Wed, 21 Jan 2009 05:14:13 -0800 (PST)
Received: from h132974.serverkompetenz.net (renormalist.net [81.169.141.46]) by core3.amsl.com (Postfix) with ESMTP id CA1993A6853 for <tap@ietf.org>; Wed, 21 Jan 2009 05:14:12 -0800 (PST)
Received: from ss5 by h132974.serverkompetenz.net with local (Exim 4.63) (envelope-from <ss5@renormalist.net>) id 1LPcu0-0003y4-Ii for tap@ietf.org; Wed, 21 Jan 2009 14:13:52 +0100
To: tap@ietf.org
References: <49763AE1.5@pobox.com> <20090120232421.GC1318@klangraum.plasmasturm.org> <E63A9E22-DEE6-4F80-B318-68D7AA930795@kineticode.com>
From: Steffen Schwigon <ss5@renormalist.net>
Date: Wed, 21 Jan 2009 14:13:52 +0100
In-Reply-To: <E63A9E22-DEE6-4F80-B318-68D7AA930795@kineticode.com> (David E. Wheeler's message of "Tue, 20 Jan 2009 16:01:32 -0800")
Message-ID: <87ocy0by3z.fsf@renormalist.net>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.19 (linux)
MIME-Version: 1.0
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1216473714=="
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org --===============1216473714==
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit

"David E. Wheeler" <david@kineticode.com> writes:
> On Jan 20, 2009, at 3:24 PM, Aristotle Pagaltzis wrote:
>
>> Personally I would say something like “it’s all UTF-8 by default
>> unless you signify otherwise with a special directive” (which we
>> will have to invent). A notation for roundtripping actual non-
>> textual octet sequences would be useful also. We could mandate
>> something inherently programmer-readable for this purpose.
>
> +1

+1 me too.

It also nicely fits into what Andy said about the current state beeing
v12 default ASCII, v13 default UTF8, and room for v14 with specified
encoding, eg. like Bjoern suggested.

Kind regards,
Steffen 
-- 
Steffen Schwigon <ss5@renormalist.net>

--===============1216473714==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

--===============1216473714==--

From tap-bounces@ietf.org  Wed Jan 21 06:08:37 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9AEB93A6A95; Wed, 21 Jan 2009 06:08:37 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E50343A6A95 for <tap@core3.amsl.com>; Wed, 21 Jan 2009 06:08:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QQmK9xpWWv4J for <tap@core3.amsl.com>; Wed, 21 Jan 2009 06:08:35 -0800 (PST)
Received: from mail.plusthree.com (mail.plusthree.com [70.42.42.197]) by core3.amsl.com (Postfix) with ESMTP id 19D1C3A6A6E for <tap@ietf.org>; Wed, 21 Jan 2009 06:08:34 -0800 (PST)
Received: from localhost.localdomain (dsl093-241-113.ral1.dsl.speakeasy.net [66.93.241.113]) (authenticated bits=0) by mail.plusthree.com (8.14.2/8.14.2) with ESMTP id n0LE38Yr006492 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jan 2009 09:03:09 -0500
Message-ID: <49772BCD.60802@plusthree.com>
Date: Wed, 21 Jan 2009 09:06:05 -0500
From: Michael Peters <mpeters@plusthree.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Steffen Schwigon <ss5@renormalist.net>
References: <49763AE1.5@pobox.com>	<20090120232421.GC1318@klangraum.plasmasturm.org>	<E63A9E22-DEE6-4F80-B318-68D7AA930795@kineticode.com> <87ocy0by3z.fsf@renormalist.net>
In-Reply-To: <87ocy0by3z.fsf@renormalist.net>
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org U3RlZmZlbiBTY2h3aWdvbiB3cm90ZToKPiAiRGF2aWQgRS4gV2hlZWxlciIgPGRhdmlkQGtpbmV0
aWNvZGUuY29tPiB3cml0ZXM6Cj4+IE9uIEphbiAyMCwgMjAwOSwgYXQgMzoyNCBQTSwgQXJpc3Rv
dGxlIFBhZ2FsdHppcyB3cm90ZToKPj4KPj4+IFBlcnNvbmFsbHkgSSB3b3VsZCBzYXkgc29tZXRo
aW5nIGxpa2Ug4oCcaXTigJlzIGFsbCBVVEYtOCBieSBkZWZhdWx0Cj4+PiB1bmxlc3MgeW91IHNp
Z25pZnkgb3RoZXJ3aXNlIHdpdGggYSBzcGVjaWFsIGRpcmVjdGl2ZeKAnSAod2hpY2ggd2UKPj4+
IHdpbGwgaGF2ZSB0byBpbnZlbnQpLiBBIG5vdGF0aW9uIGZvciByb3VuZHRyaXBwaW5nIGFjdHVh
bCBub24tCj4+PiB0ZXh0dWFsIG9jdGV0IHNlcXVlbmNlcyB3b3VsZCBiZSB1c2VmdWwgYWxzby4g
V2UgY291bGQgbWFuZGF0ZQo+Pj4gc29tZXRoaW5nIGluaGVyZW50bHkgcHJvZ3JhbW1lci1yZWFk
YWJsZSBmb3IgdGhpcyBwdXJwb3NlLgo+PiArMQo+IAo+ICsxIG1lIHRvby4KPiAKPiBJdCBhbHNv
IG5pY2VseSBmaXRzIGludG8gd2hhdCBBbmR5IHNhaWQgYWJvdXQgdGhlIGN1cnJlbnQgc3RhdGUg
YmVlaW5nCj4gdjEyIGRlZmF1bHQgQVNDSUksIHYxMyBkZWZhdWx0IFVURjgsIGFuZCByb29tIGZv
ciB2MTQgd2l0aCBzcGVjaWZpZWQKPiBlbmNvZGluZywgZWcuIGxpa2UgQmpvZXJuIHN1Z2dlc3Rl
ZC4KCisxIGZyb20gbWUgYXMgd2VsbAoKLS0gCk1pY2hhZWwgUGV0ZXJzClBsdXMgVGhyZWUsIExQ
CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwp0YXAgbWFp
bGluZyBsaXN0CnRhcEBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL3RhcAo=

From tap-bounces@ietf.org  Wed Jan 21 06:12:36 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7AEF28C0E4; Wed, 21 Jan 2009 06:12:36 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E250B28C0F3 for <tap@core3.amsl.com>; Wed, 21 Jan 2009 06:12:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GHt7Wdz4+wjM for <tap@core3.amsl.com>; Wed, 21 Jan 2009 06:12:35 -0800 (PST)
Received: from mail.plusthree.com (mail.plusthree.com [70.42.42.197]) by core3.amsl.com (Postfix) with ESMTP id 1852E28C0E4 for <tap@ietf.org>; Wed, 21 Jan 2009 06:12:35 -0800 (PST)
Received: from localhost.localdomain (dsl093-241-113.ral1.dsl.speakeasy.net [66.93.241.113]) (authenticated bits=0) by mail.plusthree.com (8.14.2/8.14.2) with ESMTP id n0LE79lR006610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jan 2009 09:07:10 -0500
Message-ID: <49772CBE.1050303@plusthree.com>
Date: Wed, 21 Jan 2009 09:10:06 -0500
From: Michael Peters <mpeters@plusthree.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <49763AE1.5@pobox.com>	<hsfcn45n5bc2ul9e7lrcs0a1e2adjpvo6a@hive.bjoern.hoehrmann.de>	<49765335.4090209@pobox.com> <tuocn492urj9grdtlv1bn244u7gu325mmq@hive.bjoern.hoehrmann.de>
In-Reply-To: <tuocn492urj9grdtlv1bn244u7gu325mmq@hive.bjoern.hoehrmann.de>
Cc: tap@ietf.org
Subject: Re: [tap] Solution to the character set problem:  Don't solve it.
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org Bjoern Hoehrmann wrote:

> You are assuming that it is not desirable to have an application that
> just takes random tap streams and does something interesting with them
> that involves processing the strings. I am unsure how valid that is. 

Very valid. In fact, this is what Smolder already does. It takes random TAP archives and displays 
them in an interactive web application. If people are going to dump descriptions in some random 
encoding without specifying what that is, there's nothing Smolder can do but show junk.

Any solution that works in a terminal for a live TAP stream, but not for a recorded TAP stream 
(which is what a TAP archive is) is fatally flawed IMO. The recorded stream should be self contained 
enough that it can be parsed without any outside knowledge.

-- 
Michael Peters
Plus Three, LP

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Wed Jan 21 17:04:00 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 828623A63D2; Wed, 21 Jan 2009 17:04:00 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 790973A6784 for <tap@core3.amsl.com>; Wed, 21 Jan 2009 17:03:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r11b75kZWXdq for <tap@core3.amsl.com>; Wed, 21 Jan 2009 17:03:57 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-quonix.sasl.smtp.pobox.com [208.72.237.25]) by core3.amsl.com (Postfix) with ESMTP id A9CA03A63D2 for <tap@ietf.org>; Wed, 21 Jan 2009 17:03:56 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTP id EA75E1CF8A for <tap@ietf.org>; Wed, 21 Jan 2009 20:03:39 -0500 (EST)
Received: from windhund.local (unknown [75.150.41.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 96CB41CF03 for <tap@ietf.org>; Wed, 21 Jan 2009 20:03:39 -0500 (EST)
Message-ID: <4977C5E9.1000605@pobox.com>
Date: Wed, 21 Jan 2009 17:03:37 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tap@ietf.org
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: 817484C0-E820-11DD-ADC9-BE78113D384A-02258300!a-sasl-quonix.pobox.com
Subject: [tap] Passing and Failing
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org I've written up everything I can think of which effects individual test and
suite pass/fail.  Please review and poke full of holes.
http://testanything.org/wiki/index.php/TAP_at_IETF:_Draft_Standard#Passing_and_Failing


-- 
I have a date with some giant cartoon robots and booze.

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Wed Jan 21 18:22:56 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 112F93A6B60; Wed, 21 Jan 2009 18:22:56 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31FC63A6B87 for <tap@core3.amsl.com>; Wed, 21 Jan 2009 18:22:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OruB8lUJ3sVx for <tap@core3.amsl.com>; Wed, 21 Jan 2009 18:22:54 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-quonix.sasl.smtp.pobox.com [208.72.237.25]) by core3.amsl.com (Postfix) with ESMTP id 702EC3A6B60 for <tap@ietf.org>; Wed, 21 Jan 2009 18:22:52 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTP id 8B85D1CFA2 for <tap@ietf.org>; Wed, 21 Jan 2009 21:22:35 -0500 (EST)
Received: from windhund.local (unknown [75.150.41.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 374AA1CF2A for <tap@ietf.org>; Wed, 21 Jan 2009 21:22:34 -0500 (EST)
Message-ID: <4977D869.4000107@pobox.com>
Date: Wed, 21 Jan 2009 18:22:33 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tap@ietf.org
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: 88197758-E82B-11DD-B04F-BE78113D384A-02258300!a-sasl-quonix.pobox.com
Subject: [tap] ABNF alternations and order
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org I'm trying to figure out how to specify "ignored" lines in the TAP grammar.  I
figure it needs something like this:

Body            = *(Comment / TAP-Line / Ignored)
Ignored         = *(%x01-%xFF) EOL

The problem is this:  Are alternatives to be evaluated in order?  If not, then
its possible for a parser to simply consider every line be "Ignored".  In
fact, a clever parser might go for that because it's the interpretation which
involves the least rules. [1]

RFC 5234 doesn't appear to say anything about the order of evaluation of
alternatives.  I suppose we can just specify it, but I'm trying to make the
TAP grammar as complete as possible with as few outside rules as can be managed.


[1] He says, not knowing a damn thing about how BNF parsers are designed.


-- 
Don't try the paranormal until you know what's normal.
    -- "Lords and Ladies" by Terry Prachett

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Wed Jan 21 18:55:18 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C484B3A67C0; Wed, 21 Jan 2009 18:55:18 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 14E283A67D6 for <tap@core3.amsl.com>; Wed, 21 Jan 2009 18:55:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.932
X-Spam-Level: 
X-Spam-Status: No, score=-3.932 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SYYT3aFu53Gg for <tap@core3.amsl.com>; Wed, 21 Jan 2009 18:55:16 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id C7E2E3A67C0 for <tap@ietf.org>; Wed, 21 Jan 2009 18:55:15 -0800 (PST)
Received: (qmail invoked by alias); 22 Jan 2009 02:54:57 -0000
Received: from dslb-088-074-131-204.pools.arcor-ip.net (EHLO hive) [88.74.131.204] by mail.gmx.net (mp044) with SMTP; 22 Jan 2009 03:54:57 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/DpQUBlETDgXGobepVVD9hWoAOisFoMSkiZwYVLr 5b9zGMkPF2KxuT
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Michael G Schwern <schwern@pobox.com>
Date: Thu, 22 Jan 2009 03:54:56 +0100
Message-ID: <b2nfn45adsnv009uprl1hvh4crv2losie0@hive.bjoern.hoehrmann.de>
References: <4977D869.4000107@pobox.com>
In-Reply-To: <4977D869.4000107@pobox.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.64
Cc: tap@ietf.org
Subject: Re: [tap] ABNF alternations and order
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org * Michael G Schwern wrote:
>I'm trying to figure out how to specify "ignored" lines in the TAP grammar=
.  I
>figure it needs something like this:
>
>Body            =3D *(Comment / TAP-Line / Ignored)
>Ignored         =3D *(%x01-%xFF) EOL
>
>The problem is this:  Are alternatives to be evaluated in order?

ABNF does not specify how to resolve conflicts in an ambiguous grammar,
what you can do is make it non-ambiguous as I suggested earlier, by e.g.

  Extension =3D <string without any EOL and not matching ...> EOL

If Comment and TAP-Line are regular, you can of course compute Extension
but it would likely be rather complex and not too useful. I think giving
such a prose description is better than the ultra-liberal Ignored rule
you have above and specifying some other conflict resultion algorithm.
-- =

Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehrma=
nn.de
Am Badedeich 7 =B7 Telefon: +49(0)160/4415681 =B7 http://www.bjoernsworld.de
25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev.d=
e/ =

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Thu Jan 22 13:18:22 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F10FB28C272; Thu, 22 Jan 2009 13:18:21 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48E5D28C262 for <tap@core3.amsl.com>; Thu, 22 Jan 2009 13:18:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.205
X-Spam-Level: 
X-Spam-Status: No, score=-1.205 tagged_above=-999 required=5 tests=[AWL=-0.465, BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LykBy1Gslr6h for <tap@core3.amsl.com>; Thu, 22 Jan 2009 13:18:18 -0800 (PST)
Received: from web65712.mail.ac4.yahoo.com (web65712.mail.ac4.yahoo.com [76.13.9.104]) by core3.amsl.com (Postfix) with SMTP id AD10E28C265 for <tap@ietf.org>; Thu, 22 Jan 2009 13:18:18 -0800 (PST)
Received: (qmail 73655 invoked by uid 60001); 22 Jan 2009 21:18:01 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=ZaVGB6YSC0Nyw1h138QuVmu5NvMzo4fOaSSqo+s7azllV355lA9/XBnSH16Ym/8wu/BTWjQRJgw+hvB3XIqXoiBl0BL9A/FvNztgtuyo0oJPS0/bfpTSJyOuAP5wT2RBJgZoXE88M6t9zoBVysccd0DwoPZySRgz7Rw8owccN4M=;
X-YMail-OSG: dp7gLLoVM1l4dRsayTCylvbsuMIFX.ALOoOTwYJA1F_zyA9t0J.ZiLlXuMhmISmhzHIPEWSr4OKL83WBmJ3V9S9inJjIEP.oC5tO0OnUHLbwpMReAjtp9tNNHP0P6S9qlGndEF76owsdBnan3DOrhYulagBuiHfwuAlkApdmfVLxnn_xEL8Tp2ySlSFKZOpu5SaDj7oZuZdMALoayw--
Received: from [91.85.130.147] by web65712.mail.ac4.yahoo.com via HTTP; Thu, 22 Jan 2009 13:18:01 PST
X-Mailer: YahooMailRC/1155.45 YahooMailWebService/0.7.260.1
References: <497693D7.8090101@pobox.com>
Date: Thu, 22 Jan 2009 13:18:01 -0800 (PST)
From: Ovid <publiustemp-tapx@yahoo.com>
To: Michael G Schwern <schwern@pobox.com>, tap@ietf.org
MIME-Version: 1.0
Message-ID: <818453.73195.qm@web65712.mail.ac4.yahoo.com>
Subject: Re: [tap] Passing Grammar
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org ----- Original Message ----

> From: Michael G Schwern <schwern@pobox.com>

> Generating some TAP streams from it, it seems kosher.  The plan is nonsense,
> though, and I can't think of a way we can encode a plan or test sequence
> violation in the grammar.  For example...
> 
> ok 9238
> not ok 5 # TODO
> 1..9085934126779

On an unrelated note:

Why do we have "1.." in the plan at all?  It implies that "17..23" is allowed.  And why not?  It might be nice to concatenate TAP streams and we could have embedded plans.  xUnit style tests can work nicely, some nested TAP issues might go away and we have a new, possibly useful feature.

The only reason I can think of for having "1.." is because it's legacy.

 
Cheers,
Ovid
--
Buy the book         - http://www.oreilly.com/catalog/perlhks/
Tech blog            - http://use.perl.org/~Ovid/journal/
Twitter              - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Thu Jan 22 16:19:33 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D7543A6806; Thu, 22 Jan 2009 16:19:33 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C5F203A6881 for <tap@core3.amsl.com>; Thu, 22 Jan 2009 16:19:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.584
X-Spam-Level: 
X-Spam-Status: No, score=-1.584 tagged_above=-999 required=5 tests=[AWL=-0.474, BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cg26+mLUmGII for <tap@core3.amsl.com>; Thu, 22 Jan 2009 16:19:24 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 1CBBA3A6806 for <tap@ietf.org>; Thu, 22 Jan 2009 16:19:23 -0800 (PST)
Received: (qmail invoked by alias); 23 Jan 2009 00:19:06 -0000
Received: from static-87-79-236-202.netcologne.de (EHLO klangraum) [87.79.236.202] by mail.gmx.net (mp002) with SMTP; 23 Jan 2009 01:19:06 +0100
X-Authenticated: #163624
X-Provags-ID: V01U2FsdGVkX18zEapdoewz1Tz98pAZl7YlBvYeaGMZvGgKLRlSq4 IliziQtPHL6t+4
Date: Fri, 23 Jan 2009 01:19:02 +0100
From: Aristotle Pagaltzis <pagaltzis@gmx.de>
To: tap@ietf.org
Message-ID: <20090123001902.GF6340@klangraum.plasmasturm.org>
Mail-Followup-To: tap@ietf.org
References: <497693D7.8090101@pobox.com> <818453.73195.qm@web65712.mail.ac4.yahoo.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <818453.73195.qm@web65712.mail.ac4.yahoo.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.78
Subject: Re: [tap] Passing Grammar
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org KiBPdmlkIDxwdWJsaXVzdGVtcC10YXB4QHlhaG9vLmNvbT4gWzIwMDktMDEtMjIgMjI6MjBdOgo+
IFdoeSBkbyB3ZSBoYXZlICIxLi4iIGluIHRoZSBwbGFuIGF0IGFsbD8KCkJlY2F1c2UgaXTigJlz
IDIgY2hhcmFjdGVycyBzaG9ydGVyIHRoYW4gYCJwbGFuICJgLiA7LSkKClJlZ2FyZHMsCi0tIApB
cmlzdG90bGUgUGFnYWx0emlzIC8vIDxodHRwOi8vcGxhc21hc3R1cm0ub3JnLz4KX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdGFwIG1haWxpbmcgbGlzdAp0
YXBAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90YXAK

From tap-bounces@ietf.org  Thu Jan 22 17:10:38 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2B9BE3A696D; Thu, 22 Jan 2009 17:10:38 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B32F93A69E4 for <tap@core3.amsl.com>; Thu, 22 Jan 2009 17:10:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LjkgPsyNBxbS for <tap@core3.amsl.com>; Thu, 22 Jan 2009 17:10:35 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-quonix.sasl.smtp.pobox.com [208.72.237.25]) by core3.amsl.com (Postfix) with ESMTP id D0C3F3A6981 for <tap@ietf.org>; Thu, 22 Jan 2009 17:10:35 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTP id 6F9191D132 for <tap@ietf.org>; Thu, 22 Jan 2009 20:10:17 -0500 (EST)
Received: from windhund.local (unknown [75.150.41.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 1CB111D12F for <tap@ietf.org>; Thu, 22 Jan 2009 20:10:16 -0500 (EST)
Message-ID: <497918F4.4050909@pobox.com>
Date: Thu, 22 Jan 2009 17:10:12 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tap@ietf.org
References: <497693D7.8090101@pobox.com> <818453.73195.qm@web65712.mail.ac4.yahoo.com> <20090123001902.GF6340@klangraum.plasmasturm.org>
In-Reply-To: <20090123001902.GF6340@klangraum.plasmasturm.org>
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: 98CB724E-E8EA-11DD-8475-BE78113D384A-02258300!a-sasl-quonix.pobox.com
Subject: Re: [tap] Passing Grammar
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org QXJpc3RvdGxlIFBhZ2FsdHppcyB3cm90ZToKPiAqIE92aWQgPHB1YmxpdXN0ZW1wLXRhcHhAeWFo
b28uY29tPiBbMjAwOS0wMS0yMiAyMjoyMF06Cj4+IFdoeSBkbyB3ZSBoYXZlICIxLi4iIGluIHRo
ZSBwbGFuIGF0IGFsbD8KPiAKPiBCZWNhdXNlIGl04oCZcyAyIGNoYXJhY3RlcnMgc2hvcnRlciB0
aGFuIGAicGxhbiAiYC4gOy0pCgpZZWFoLCB0aGUgZ3JhbW1hciBuZWVkcyBzb21ldGhpbmcgdG8g
bGF0Y2ggb24gdG8gb3RoZXJ3aXNlIHlvdSdsbCBqdXN0IGhhdmUgYQpudW1iZXIuICBBbmQsIGFz
IE92aWQgcG9pbnRlZCBvdXQsIGl0IG9wZW5zIHVwIHRoZSBvcHBvcnR1bml0eSBmb3IgdGhpbmdz
IGxpa2UKMTguLjIzIGJ1dCBJJ20gbm90IHN1cmUgd2hhdCB0aGUgcHJhY3RpY2FsIHV0aWxpdHkg
b2YgYSBmb3JtYWwgd2F5IHRvCmNvbmNhdGVuYXRlIFRBUCBzdHJlYW1zIGlzLgoKSW4gcmVhbGl0
eSwgSSBzdXNwZWN0IGJlY2F1c2UgaXQgbWlycm9ycyB0aGUgUGVybCByYW5nZSBvcGVyYXRvci4K
CgotLSAKTGlmZSBpcyBsaWtlIGEgc2V3ZXIgLSB3aGF0IHlvdSBnZXQgb3V0IG9mIGl0IGRlcGVu
ZHMgb24gd2hhdCB5b3UgcHV0IGludG8gaXQuCiAgICAtIFRvbSBMZWhyZXIKX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdGFwIG1haWxpbmcgbGlzdAp0YXBA
aWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90YXAK

From tap-bounces@ietf.org  Thu Jan 22 20:52:52 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9348D3A6A04; Thu, 22 Jan 2009 20:52:52 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 073993A6A04 for <tap@core3.amsl.com>; Thu, 22 Jan 2009 20:52:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aqxK0uAtiH5g for <tap@core3.amsl.com>; Thu, 22 Jan 2009 20:52:44 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-quonix.sasl.smtp.pobox.com [208.72.237.25]) by core3.amsl.com (Postfix) with ESMTP id 12CAB3A6A1D for <tap@ietf.org>; Thu, 22 Jan 2009 20:52:43 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTP id 6FF7D1D152 for <tap@ietf.org>; Thu, 22 Jan 2009 23:52:25 -0500 (EST)
Received: from windhund.local (unknown [75.150.41.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTPSA id C41BD1D14C for <tap@ietf.org>; Thu, 22 Jan 2009 23:52:24 -0500 (EST)
Message-ID: <49794D07.4030807@pobox.com>
Date: Thu, 22 Jan 2009 20:52:23 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tap@ietf.org
X-Enigmail-Version: 0.95.7
Content-Type: multipart/mixed; boundary="------------060308070600030306080603"
X-Pobox-Relay-ID: A0E71CB6-E909-11DD-A541-BE78113D384A-02258300!a-sasl-quonix.pobox.com
Subject: [tap] TAP as a Parse::RecDescent grammar
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org This is a multi-part message in MIME format.
--------------060308070600030306080603
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I took a stab at converting TAP to a Parse::RecDescent grammar.  It is
attached, along with the ABNF to RecDescent converter.  I don't really know
RecDescent so someone could please try to parse a TAP document with it and
correct any mistakes.


-- 
Ahh email, my old friend.  Do you know that revenge is a dish that is best
served cold?  And it is very cold on the Internet!


--------------060308070600030306080603
Content-Type: text/plain; x-mac-type="54455854"; x-mac-creator="454D4178";
 name="tap.abnf"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="tap.abnf"

; Overall structure
Stream          = Header (Plan Body / Body Plan) Footer
Header          = [Comments] [Version]
Footer          = [Comments]
Body            = *(Comment / TAP-Line)
TAP-Line        = Test-Result / Bail-Out / Unknown
Unknown         = *(%x01-FF) EOL

; TAP version
Version         = "TAP version" SP Version-Number EOL ; ie. "TAP version 13"
Version-Number  = Positive-Integer

; Plan
Plan            = ( Plan-Simple / Plan-Todo / Plan-Skip-All ) EOL
Plan-Simple     = "1.." Number-Of-Tests
Plan-Todo       = Plan-Simple "todo" 1*(SP Test-Number) ";"  ; Obsolete
Plan-Skip-All   = "1..0" SP "skip" SP Reason
Reason          = String
Number-Of-Tests = 1*DIGIT               ; The number of tests contained in this stream
Test-Number     = Positive-Integer      ; The sequence of a test result

; Test result
Test-Result     = Status [SP Test-Number] [SP Description]
                   [SP "#" SP Directive [SP Reason]] EOL
Status          = "ok" / "not ok"       ; Whether the test succeeded or failed
Description     = Safe-String           ; A description of this test.
Directive       = "SKIP" / "TODO"

; Bail out
Bail-Out        = "Bail out!" [SP Reason] EOL

; Comments
Comment         = "#" String EOL
Comments        = 1*Comment

; Values
EOL              = LF / CRLF             ; Specific to the system producing the stream
Safe-String      = 1*(%x01-09 %x0B-0C %x0E-22 %x24-FF)  ; UTF8 without EOL or "#"
String           = 1*(Safe-String / "#")                ; UTF8 without EOL
Positive-Integer = ("1" / "2" / "3" / "4" / "5" / "6" / "7" / "8" / "9") *DIGIT
SP               = " "
DIGIT            = "0" / "1" / "2" / "3" / "4" / "5" / "6"/ "7" / "8" / "9"

; Overall structure
Passing-Stream  = Header
                  (Plan-With-Tests Passing-Body / Passing-Body Plan-With-Tests / Plan-Skip-All)
                  Footer
Passing-Body    = [Comments] 1*Passing-Line *(Passing-Line / Comment) [Comments]
Passing-Line    = (Simple-OK / Passing-TODO / Failing-TODO / Passing-SKIP) EOL
Failing-Line    = (Simple-Fail / Failing-SKIP) EOL

; Plans that must have tests
Plan-With-Tests = ( Plan-Simple / Plan-Todo )

; Passing and failing test lines
Simple-OK       = "ok" [SP Test-Number] [SP Description]        ; pass
Simple-Fail     = "not ok" [SP Test-Number] [SP Description]    ; fail
Passing-TODO    = Simple-OK   SP TODO-Directive                 ; pass (with warning)
Failing-TODO    = Simple-Fail SP TODO-Directive                 ; pass
Passing-SKIP    = Simple-OK   SP SKIP-Directive                 ; pass
Failing-SKIP    = Simple-Fail SP SKIP-Directive                 ; fail (with warning)
TODO-Directive  = "# TODO" [SP Reason]
SKIP-Directive  = "# SKIP" [SP Reason]

--------------060308070600030306080603
Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0";
 name="tap.rec"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="tap.rec"

Stream:              (Header (Plan Body) | (Body Plan) Footer)
Header:              (Comments(0..1) Version(0..1))
Footer:              Comments(0..1)
Body:                Comment | TAP_Line(0..)
TAP_Line:            Test_Result | Bail_Out | Unknown
Unknown:             (/[\x01-\xFF]/(0..) EOL)
Version:             ('TAP version' SP Version_Number EOL)
Version_Number:      Positive_Integer
Plan:                (Plan_Simple | Plan_Todo | Plan_Skip_All EOL)
Plan_Simple:         ('1..' Number_Of_Tests)
Plan_Todo:           (Plan_Simple 'todo' (SP Test_Number)(1..) ';')
Plan_Skip_All:       ('1..0' SP 'skip' SP Reason)
Reason:              String
Number_Of_Tests:     DIGIT(1..)
Test_Number:         Positive_Integer
Test_Result:         (Status (SP Test_Number)(0..1) (SP Description)(0..1) (SP '#' SP Directive (SP Reason)(0..1))(0..1) EOL)
Status:              'ok' | 'not ok'
Description:         Safe_String
Directive:           'SKIP' | 'TODO'
Bail_Out:            ('Bail out!' (SP Reason)(0..1) EOL)
Comment:             ('#' String EOL)
Comments:            Comment(1..)
EOL:                 LF | CRLF
Safe_String:         (/[\x01-\x09]/ /[\x0B-\x0C]/ /[\x0E-\x22]/ /[\x24-\xFF]/)(1..)
String:              Safe_String | '#'(1..)
Positive_Integer:    ('1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' DIGIT(0..))
SP:                  ' '
DIGIT:               '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9'
Passing_Stream:      (Header (Plan_With_Tests Passing_Body) | (Passing_Body Plan_With_Tests) | Plan_Skip_All Footer)
Passing_Body:        (Comments(0..1) Passing_Line(1..) Passing_Line | Comment(0..) Comments(0..1))
Passing_Line:        (Simple_OK | Passing_TODO | Failing_TODO | Passing_SKIP EOL)
Failing_Line:        (Simple_Fail | Failing_SKIP EOL)
Plan_With_Tests:     Plan_Simple | Plan_Todo
Simple_OK:           ('ok' (SP Test_Number)(0..1) (SP Description)(0..1))
Simple_Fail:         ('not ok' (SP Test_Number)(0..1) (SP Description)(0..1))
Passing_TODO:        (Simple_OK SP TODO_Directive)
Failing_TODO:        (Simple_Fail SP TODO_Directive)
Passing_SKIP:        (Simple_OK SP SKIP_Directive)
Failing_SKIP:        (Simple_Fail SP SKIP_Directive)
TODO_Directive:      ('# TODO' (SP Reason)(0..1))
SKIP_Directive:      ('# SKIP' (SP Reason)(0..1))

--------------060308070600030306080603
Content-Type: text/plain; x-mac-type="54455854"; x-mac-creator="454D4178";
 name="abnf2rec.plx"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="abnf2rec.plx"

#!/usr/bin/perl -w

use Parse::ABNF;
use Parse::RecDescent;

use strict;

my $rules = Parse::ABNF->new->parse(join "", <>);

# Not handled are..
# A /= B
my %ABNF2Rec = (
    Rule        => sub {
        my $rule = shift;

        my $name = fix_name($rule);
        return sprintf "%-20s %s\n", "$name:", value($rule);
    },

    Choice      => sub {
        my $rule = shift;
        return join " | ", value($rule);
    },

    Group       => sub {
        my $rule = shift;
        return sprintf "(%s)", join " ", value($rule);
    },

    Reference => sub {
        my $rule = shift;
        return fix_name($rule);
    },

    Repetition => sub {
        my $rule = shift;

        my($min, $max) = map { defined $_ ? $_ : '' } $rule->{min}, $rule->{max};
        return sprintf "%s(%s..%s)", value($rule), $min, $max;
    },

    Literal => sub {
        my $rule = shift;

        return sprintf qq['%s'], $rule->{value};
    },

    ProseValue => sub {
        my $rule = shift;

        return value($rule);
    },

    String => sub {
        my $rule = shift;

        return sprintf q["%s"], join "", to_hexchars($rule->{type}, $rule->{value});
    },

    Range => sub {
        my $rule = shift;

        return sprintf q{/[%s-%s]/}, to_hexchars($rule->{type}, [$rule->{min}, $rule->{max}]);
    }
);

sub to_hexchars {
    my($type, $values) = @_;

    my $converter = $type eq 'hex'          ? sub { hex $_[0] }         :
                    $type eq 'binary'       ? sub { oct "0b$_[0]" }     :
                    $type eq 'decimal'      ? sub { $_[0] }             :
                                              die "Unknown type: $type" ;

    return map { sprintf '\x%02X', $converter->($_) } @$values;
}

sub value {
    my $rule = shift;
    my @values = ref $rule->{value} eq 'ARRAY' ? @{$rule->{value}} : $rule->{value};

    return map { ref $_ ? convert($_) : $_ } @values;
}

sub convert {
    my $rule = shift;

    return $ABNF2Rec{$rule->{class}}->($rule);
}

# RecDescent only allows /[A-Za-z]\w*/ as rule names.
sub fix_name {
    my $rule = shift;
    my $name = $rule->{name};
    $name =~ s{[^A-Za-z\w*]}{_}g;
    return $name;
}

my $recdescent = join '', map { convert($_) } @$rules;
#my $parser = Parse::RecDescent->new($recdescent);
print $recdescent;



--------------060308070600030306080603
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

--------------060308070600030306080603--

From tap-bounces@ietf.org  Fri Jan 23 18:07:39 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B25B13A67C1; Fri, 23 Jan 2009 18:07:39 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7BDF03A67C1 for <tap@core3.amsl.com>; Fri, 23 Jan 2009 18:07:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 76iaHuq2zcsg for <tap@core3.amsl.com>; Fri, 23 Jan 2009 18:07:37 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-quonix.sasl.smtp.pobox.com [208.72.237.25]) by core3.amsl.com (Postfix) with ESMTP id 95E983A694D for <tap@ietf.org>; Fri, 23 Jan 2009 18:07:36 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTP id A22081D26D for <tap@ietf.org>; Fri, 23 Jan 2009 21:07:19 -0500 (EST)
Received: from windhund.local (unknown [75.150.41.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 1E96A1D26C for <tap@ietf.org>; Fri, 23 Jan 2009 21:07:16 -0500 (EST)
Message-ID: <497A77D0.8070500@pobox.com>
Date: Fri, 23 Jan 2009 18:07:12 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tap@ietf.org
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: BB00A10A-E9BB-11DD-8409-BE78113D384A-02258300!a-sasl-quonix.pobox.com
Subject: [tap] "ok 1 description" vs "ok 1 - description"
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

According to the standard, it's supposed to be this:

ok 9 here is some descriptive text
ok 10 and some more stuff

But Test::More does this:

ok 9 - here is some descriptive text
ok 10 - and some more stuff

Why?  Because it's a whole lot easier to read.  Technically the description is
"- here is a some descriptive text".  I would like that to not be so while
still retraining the spacing.

So, in the interest of human readability, I propose a small change to the
grammar from:

Test-Result     = Status [SP Test-Number] [SP Description]
                   [SP "#" SP Directive [SP Reason]] EOL

to

Test-Result     = Status [SP Test-Number] [SP -] [SP Description]
                   [SP "#" SP Directive [SP Reason]] EOL

The dash is simply ignored if it's there.

Yay or nay?


-- 
87. If the thought of something makes me giggle for longer than 15
    seconds, I am to assume that I am not allowed to do it.
    -- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
           http://skippyslist.com/list/

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 24 01:55:26 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CFF43A67B3; Sat, 24 Jan 2009 01:55:26 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2491B3A68E0 for <tap@core3.amsl.com>; Sat, 24 Jan 2009 01:55:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KoZWKY7jZRNg for <tap@core3.amsl.com>; Sat, 24 Jan 2009 01:55:24 -0800 (PST)
Received: from web65715.mail.ac4.yahoo.com (web65715.mail.ac4.yahoo.com [76.13.9.107]) by core3.amsl.com (Postfix) with SMTP id 37F233A67B3 for <tap@ietf.org>; Sat, 24 Jan 2009 01:55:24 -0800 (PST)
Received: (qmail 22115 invoked by uid 60001); 24 Jan 2009 09:55:06 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=XDFNMUVZVV8p/2PiKVESH+eLUE4EE6+The/30wLqqALQ8WuucZI0RDJwJxoER5X2IqfbTuOgrf8/aGeM0aa+u+0x6XiqNiv2FAgE1jxBk+LzgahRmOjqUk+shuR1I/eIRbFFxeedc/T3c+Fi/2JNcCwpVybG3C919C/6+KWaoSU=;
X-YMail-OSG: sJEToLgVM1n.FNQ_BWxAgfkH8n.GlK.JkRvISA546shbp1anjc7l4X5OFILF_6fpCA43uWADzzAANb3F_Aa.6YkGSZNikmKIcKcs32CLuYow2luPFhtOSD8mUcAGdERudckpVKOgCCn1A.hHpbl.xFztemDAGR.9Knyo_Wj7Iib7xTcO9oxVgJI9.uNirFydFnaPUkccqChKinQCiA--
Received: from [82.153.209.99] by web65715.mail.ac4.yahoo.com via HTTP; Sat, 24 Jan 2009 01:55:06 PST
X-Mailer: YahooMailRC/1155.45 YahooMailWebService/0.7.260.1
References: <497A77D0.8070500@pobox.com>
Date: Sat, 24 Jan 2009 01:55:06 -0800 (PST)
From: Ovid <publiustemp-tapx@yahoo.com>
To: Michael G Schwern <schwern@pobox.com>, tap@ietf.org
MIME-Version: 1.0
Message-ID: <335014.20536.qm@web65715.mail.ac4.yahoo.com>
Subject: Re: [tap] "ok 1 description" vs "ok 1 - description"
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

----- Original Message ----

> From: Michael G Schwern <schwern@pobox.com>

> Test-Result     = Status [SP Test-Number] [SP Description]
>                    [SP "#" SP Directive [SP Reason]] EOL
> 
> to
> 
> Test-Result     = Status [SP Test-Number] [SP -] [SP Description]
>                    [SP "#" SP Directive [SP Reason]] EOL
> 
> The dash is simply ignored if it's there.
> 
> Yay or nay?

So everyone who's written a TAP producer in another language and
didn't see fit to add that dash will now be producing invalid TAP?

 
Cheers,
Ovid
--
Buy the book         - http://www.oreilly.com/catalog/perlhks/
Tech blog            - http://use.perl.org/~Ovid/journal/
Twitter              - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 24 01:57:42 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A78283A67B3; Sat, 24 Jan 2009 01:57:42 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56ED43A67B6 for <tap@core3.amsl.com>; Sat, 24 Jan 2009 01:57:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f7cocSGDL4jj for <tap@core3.amsl.com>; Sat, 24 Jan 2009 01:57:40 -0800 (PST)
Received: from smtp-vbr2.xs4all.nl (smtp-vbr2.xs4all.nl [194.109.24.22]) by core3.amsl.com (Postfix) with ESMTP id 042073A67B3 for <tap@ietf.org>; Sat, 24 Jan 2009 01:57:39 -0800 (PST)
Received: from pc09.procura.nl (procura.xs4all.nl [82.95.216.29]) (authenticated bits=0) by smtp-vbr2.xs4all.nl (8.13.8/8.13.8) with ESMTP id n0O9vHOI082188 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sat, 24 Jan 2009 10:57:18 +0100 (CET) (envelope-from h.m.brand@xs4all.nl)
Date: Sat, 24 Jan 2009 10:57:16 +0100
From: "H.Merijn Brand" <h.m.brand@xs4all.nl>
To: Michael G Schwern <schwern@pobox.com>
Message-ID: <20090124105716.4274e1a0@pc09.procura.nl>
In-Reply-To: <497A77D0.8070500@pobox.com>
References: <497A77D0.8070500@pobox.com>
X-Mailer: Claws Mail 3.7.0 (GTK+ 2.12.0; x86_64-unknown-linux-gnu)
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwEAIAAACI8LKTAAAACXBIWXMAAABIAAAASABGyWs+AAAC JElEQVRo3u2aMY4CMQxFczZ6RItEzRm4DBINDbRUSPRInIRbsNK6+dJfezN4kokn48IaCSjysL8d e9Knoj2fr9f9/gllqQ6U9/vxWK3EdwdIEGjRIVCu18NhuxUfK46SH81+fzrdbuKPx/P5ctHQdAdI TKAgpvV6s9ntBEfXEYSGgMQzIHnuFBBjkshCNJ2KtJZ04hHNAugP8bZr3NIHhbcF0AKoK0CoaHXU LUWBIs1n+jV+Fl8CVqOApEXAwyMO/DSR4XVntoAYDR7eBjQupuYAYTMph8Rj21D4m7MChN02tpqs NSnb/KqU2oHCXu5xDCgflj/RAgBiKBIXnICzAsSjWBsTz5K4/HeXYvb8yK5lY3VGEwPi2aONKT+5 AlcxrTPOwcTiraGRChgMEKJh0bVVifGVTq6qgBiNVl8QE29EsK6VE+YJAOG2wz5AvsqUS6uqgHCA n4NGvBYpnJ64Jgg27sCtxtBk1CJIA4S/GhdWKh07QxUB48jWGhZ4jKamRRr/T8/M0AaEyctry6YB 4dTGj9iWZNs3DahES5kPCJOu0RQbF/fQOBprsB9gaO9JtPDzII9U5ySXX7AnuIt91y54AAW7rPpT LCe5gt3F+CLqr2UarGB3MXvMylWGq4+9RCx3TW1oJq1t3HPQlFs6N1fFNEB4s8dn7Ne7ACSm7TPQ I5quAWmw6qBpulHM33B0Csge4Nd8JTTYG2b1XyRe3lH8x34ABJ6aePuQ2N4AAAAASUVORK5CYII=
Mime-Version: 1.0
X-Virus-Scanned: by XS4ALL Virus Scanner
Cc: tap@ietf.org
Subject: Re: [tap] "ok 1 description" vs "ok 1 - description"
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

On Fri, 23 Jan 2009 18:07:12 -0800, Michael G Schwern
<schwern@pobox.com> wrote:

> According to the standard, it's supposed to be this:
> 
> ok 9 here is some descriptive text
> ok 10 and some more stuff
> 
> But Test::More does this:
> 
> ok 9 - here is some descriptive text
> ok 10 - and some more stuff
> 
> Why?  Because it's a whole lot easier to read.  Technically the description is
> "- here is a some descriptive text".  I would like that to not be so while
> still retraining the spacing.
> 
> So, in the interest of human readability, I propose a small change to the
> grammar from:
> 
> Test-Result     = Status [SP Test-Number] [SP Description]
>                    [SP "#" SP Directive [SP Reason]] EOL
> 
> to
> 
> Test-Result     = Status [SP Test-Number] [SP -] [SP Description]
>                    [SP "#" SP Directive [SP Reason]] EOL
> 
> The dash is simply ignored if it's there.
> 
> Yay or nay?

Yay

-- 
H.Merijn Brand  http://tux.nl      Perl Monger  http://amsterdam.pm.org/
using & porting perl 5.6.2, 5.8.x, 5.10.x, 5.11.x on HP-UX 10.20, 11.00,
11.11, 11.23, and 11.31, SuSE 10.1, 10.3, and 11.0, AIX 5.2, and Cygwin.
http://mirrors.develooper.com/hpux/           http://www.test-smoke.org/
http://qa.perl.org      http://www.goldmark.org/jeff/stupid-disclaimers/
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 24 03:54:54 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B6EB28C22E; Sat, 24 Jan 2009 03:54:54 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E63328C2B6 for <tap@core3.amsl.com>; Sat, 24 Jan 2009 03:54:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4oPeLpPla+8 for <tap@core3.amsl.com>; Sat, 24 Jan 2009 03:54:52 -0800 (PST)
Received: from tiger.h2hosting.com (tiger.h2hosting.com [75.125.147.242]) by core3.amsl.com (Postfix) with ESMTP id 9881A28C22E for <tap@ietf.org>; Sat, 24 Jan 2009 03:54:52 -0800 (PST)
Received: from [84.73.133.27] (helo=wesley.pjcj.net) by tiger.h2hosting.com with esmtp (Exim 4.68) (envelope-from <pjcj@pjcj.net>) id 1LQh5l-0000zy-L1; Sat, 24 Jan 2009 05:54:25 -0600
Received: by wesley.pjcj.net (Postfix, from userid 1000) id DD60EA900BC; Sat, 24 Jan 2009 12:54:27 +0100 (CET)
Date: Sat, 24 Jan 2009 12:54:27 +0100
From: Paul Johnson <paul@pjcj.net>
To: Ovid <publiustemp-tapx@yahoo.com>
Message-ID: <20090124115427.GC9114@pjcj.net>
References: <497A77D0.8070500@pobox.com> <335014.20536.qm@web65715.mail.ac4.yahoo.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <335014.20536.qm@web65715.mail.ac4.yahoo.com>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - tiger.h2hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - pjcj.net
Cc: tap@ietf.org
Subject: Re: [tap] "ok 1 description" vs "ok 1 - description"
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

On Sat, Jan 24, 2009 at 01:55:06AM -0800, Ovid wrote:
> ----- Original Message ----
> 
> > From: Michael G Schwern <schwern@pobox.com>
> 
> > Test-Result     = Status [SP Test-Number] [SP Description]
> >                    [SP "#" SP Directive [SP Reason]] EOL
> > 
> > to
> > 
> > Test-Result     = Status [SP Test-Number] [SP -] [SP Description]
> >                    [SP "#" SP Directive [SP Reason]] EOL
> > 
> > The dash is simply ignored if it's there.
> > 
> > Yay or nay?
> 
> So everyone who's written a TAP producer in another language and
> didn't see fit to add that dash will now be producing invalid TAP?

I don't think so, since the dash is optional.  The only real complication
I can see is if anyone actually does want to start the description with a
dash, in which case they would now need two dashes.  TAP from those
producers you mention above would have any dash prefix in the description
silently eaten.  Still not ideal, but perhaps not the end of the world.

(For values of dash that include appropriate whitespace.)

-- 
Paul Johnson - paul@pjcj.net
http://www.pjcj.net
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 24 10:09:59 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9AD1828C2F0; Sat, 24 Jan 2009 10:09:59 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43DB628C2F4 for <tap@core3.amsl.com>; Sat, 24 Jan 2009 10:09:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0+EzcWZJz4Ef for <tap@core3.amsl.com>; Sat, 24 Jan 2009 10:09:57 -0800 (PST)
Received: from h132974.serverkompetenz.net (renormalist.net [81.169.141.46]) by core3.amsl.com (Postfix) with ESMTP id E7F3A28C2F0 for <tap@ietf.org>; Sat, 24 Jan 2009 10:09:56 -0800 (PST)
Received: from ss5 by h132974.serverkompetenz.net with local (Exim 4.63) (envelope-from <ss5@renormalist.net>) id 1LQmwq-0007do-V5 for tap@ietf.org; Sat, 24 Jan 2009 19:09:36 +0100
To: tap@ietf.org
References: <497A77D0.8070500@pobox.com> <335014.20536.qm@web65715.mail.ac4.yahoo.com> <20090124115427.GC9114@pjcj.net>
From: Steffen Schwigon <ss5@renormalist.net>
Date: Sat, 24 Jan 2009 19:09:36 +0100
In-Reply-To: <20090124115427.GC9114@pjcj.net> (Paul Johnson's message of "Sat, 24 Jan 2009 12:54:27 +0100")
Message-ID: <87vds4podb.fsf@renormalist.net>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.19 (linux)
MIME-Version: 1.0
Subject: Re: [tap] "ok 1 description" vs "ok 1 - description"
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

Paul Johnson <paul@pjcj.net> writes:
> On Sat, Jan 24, 2009 at 01:55:06AM -0800, Ovid wrote:
>> ----- Original Message ----
>> 
>> > From: Michael G Schwern <schwern@pobox.com>
>> 
>> > Test-Result     = Status [SP Test-Number] [SP Description]
>> >                    [SP "#" SP Directive [SP Reason]] EOL
>> > 
>> > to
>> > 
>> > Test-Result     = Status [SP Test-Number] [SP -] [SP Description]
>> >                    [SP "#" SP Directive [SP Reason]] EOL
>> > 
>> > The dash is simply ignored if it's there.
>> > 
>> > Yay or nay?
>> 
>> So everyone who's written a TAP producer in another language and
>> didn't see fit to add that dash will now be producing invalid TAP?
>
> I don't think so, since the dash is optional.  The only real
> complication I can see is if anyone actually does want to start the
> description with a dash, in which case they would now need two
> dashes.  TAP from those producers you mention above would have any
> dash prefix in the description silently eaten.  Still not ideal, but
> perhaps not the end of the world.

IMHO when the TAP grammar changes things that were stable for years
it's near to the end of the world.

I, for instance, evaluate test results via the description over *lots*
of archived TAP streams since nearly years. I don't want to become an
outlaw.

So I'm strongly with Ovid.

And I don't know why the grammar is about to be discussed at
all. Until now I thought we would only think about backwards
compatible extensions that fit into the currently "ignored non-tap"
design space.

It would be ok if we were inventing TAP for the first time, but with
this 20 years old thingie I would be very carefully.

Kind regards,
Steffen 
-- 
Steffen Schwigon <ss5@renormalist.net>
Dresden Perl Mongers <http://dresden-pm.org/>
German Perl-Workshop 2009 <http://www.perl-workshop.de/en/2009>
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 24 13:17:00 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB2E53A6A7C; Sat, 24 Jan 2009 13:17:00 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 634973A6AEC for <tap@core3.amsl.com>; Sat, 24 Jan 2009 13:16:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.449
X-Spam-Level: 
X-Spam-Status: No, score=-1.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_TOOL=2.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DbOLemC5kOW5 for <tap@core3.amsl.com>; Sat, 24 Jan 2009 13:16:58 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by core3.amsl.com (Postfix) with ESMTP id 4708228C0CF for <tap@ietf.org>; Sat, 24 Jan 2009 13:16:57 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 32C31938CB; Sat, 24 Jan 2009 16:16:40 -0500 (EST)
Received: from [10.23.42.2] (unknown [69.64.236.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id BF0EF938CA; Sat, 24 Jan 2009 16:16:37 -0500 (EST)
Message-ID: <497B8530.4080903@pobox.com>
Date: Sat, 24 Jan 2009 13:16:32 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Steffen Schwigon <ss5@renormalist.net>
References: <497A77D0.8070500@pobox.com> <335014.20536.qm@web65715.mail.ac4.yahoo.com> <20090124115427.GC9114@pjcj.net> <87vds4podb.fsf@renormalist.net>
In-Reply-To: <87vds4podb.fsf@renormalist.net>
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: 4AB0723A-EA5C-11DD-BC55-5720C92D7133-02258300!a-sasl-fastnet.pobox.com
Cc: tap@ietf.org
Subject: Re: [tap] "ok 1 description" vs "ok 1 - description"
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

Steffen Schwigon wrote:
> Paul Johnson <paul@pjcj.net> writes:
>> On Sat, Jan 24, 2009 at 01:55:06AM -0800, Ovid wrote:
>>> ----- Original Message ----
>>>
>>>> From: Michael G Schwern <schwern@pobox.com>
>>>> Test-Result     = Status [SP Test-Number] [SP Description]
>>>>                    [SP "#" SP Directive [SP Reason]] EOL
>>>>
>>>> to
>>>>
>>>> Test-Result     = Status [SP Test-Number] [SP -] [SP Description]
>>>>                    [SP "#" SP Directive [SP Reason]] EOL
>>>>
>>>> The dash is simply ignored if it's there.
>>>>
>>>> Yay or nay?
>>> So everyone who's written a TAP producer in another language and
>>> didn't see fit to add that dash will now be producing invalid TAP?
>> I don't think so, since the dash is optional.

Exactly, the dash is optional so if you leave it out that's fine.  Sorry for
not making that abundantly clear, I forget not everyone can read ABNF.

These two lines are semantically equivalent:

ok 1 foo
ok 1 - foo

They are both passing test number 1 with a description of "foo".


>> The only real
>> complication I can see is if anyone actually does want to start the
>> description with a dash, in which case they would now need two
>> dashes.  TAP from those producers you mention above would have any
>> dash prefix in the description silently eaten.  Still not ideal, but
>> perhaps not the end of the world.

It's simple enough to deal with, uncommon enough not to be a worry and if you
screw it up it's just cosmetic (that is, it has no effect on passing or
failing).  So I'm not worried.


> IMHO when the TAP grammar changes things that were stable for years
> it's near to the end of the world.
>
> I, for instance, evaluate test results via the description over *lots*
> of archived TAP streams since nearly years. I don't want to become an
> outlaw.

Out of curiosity, what are you using to create these TAP streams and how do
they format the description?


> So I'm strongly with Ovid.
>
> And I don't know why the grammar is about to be discussed at
> all. Until now I thought we would only think about backwards
> compatible extensions that fit into the currently "ignored non-tap"
> design space.
> 
> It would be ok if we were inventing TAP for the first time, but with
> this 20 years old thingie I would be very carefully.

Seeing as how Test::More is the widest producer of TAP, and it's being doing
"ok 1 - description" for years now, and that the dash is optional so nothing
is being made illegal, all of the above would seem to actually be an argument
in favor of adding the optional dash to the grammar as it better describes
reality.

And it produces a nicer to read TAP moving forward, which is important, too.

As a point of reference, we are discussing the grammar exactly because we're
trying to write down reality.  But reality can be hard to nail down when you
try to formalize conventions.  Little niggling things pop up and assumptions
have to be examined.  Does "# SKIP" have to be capitalized or is "# skip" ok,
too? [1]  Do we allow more than one space between tokens? [2]  What's the
character set? [3]  Is "1..0\n" with no skip a passing test? [4]  Is it even
gramatically correct? [5]  What is the TAP end-of-line sequence? [6]  And, of
course, do we enshrine the "ok 1 - description" convention?

All of these little things suddenly become really important when you're trying
to write it all down, in detail, such that others can repeat your work.

To further drill this point into the ground, I noticed a grammatical ambiguity
when generating valid, but nonsense, TAP.  I came across stuff like this:

ok 8lasdjf;akjd;lfj

Which looked like a mistake in the Test-Number grammar until I realized that
was a Test-Result with no Test-Number.  "8lasdjf;akjd;lfj" was the
Description.  This suggests that the following is ambiguous:

ok 8

Is that test 8 passing?  Or is that a test with no number and a description of
"8"?  How do you produce a test with no number and a description of 8?
Without the dash in the grammar, you can't.  You have to say "ok
8not-a-test-number".  You can't even say "ok 8 not a test number" because
that's test number 8 with the description "not a test number".

Un-numbered tests are not just a curiosity (though numeric test descriptions
probably are).  They are important for unsynchronized, parallel testing such
as threads and forking.  The dash allows the test producer to remove this
ambiguity by saying "ok - 8".

Is this important?  Well, TAP is going from being a public interface, to being
a "published" interface.  I mean that in the sense Martin Fowler gave it to
mean "we no longer have control over all implementations and users" and thus
refactoring becomes impossible and backwards compatibility takes on a whole
new meaning.  It also means that people who have no connection to the TAP
community are going to write TAP parsers and producers based purely on the
spec and do REALLY CRAZY SHIT with any crack we leave in the protocol and then
we have to support it FOREVER. [7]

So I assure you that when I bring these things up, I'm trying to nail down the
Jell-O of reality.  I wholeheartedly agree with all my very being that we need
a spec of the current reality of TAP separate from any proposed extensions.

End of unsolicited rant.


[1] Answer, its case insensitive because it's easier to do that in ABNF and
TAP has traditionally been pretty inconsistent about enforcing case.

[2] Still up in the air.  I'm leaning towards more than one space as it gives
more flexibility in formatting for human readability and most parsers (by
which I mean Test::Harness and TAP::Parser) allow more than one space anyway.

[3] Recent discussion seems pretty strong that it's UTF8.

[4] No, though there's no strong reason it couldn't be.

[5] Yes, it is not a parse error.

[6] Newline?  Carriage return + newline?  Both?  This needs to be nailed down
if we're going to pass TAP streams around from machine to machine.

[7] To see this illustrated, please watch rjbs' brilliant rant against mail
formats, "Email Hates The Living".  Also it's funny.
http://video.google.com/videoplay?docid=7054401183589794595


-- 
'All anyone gets in a mirror is themselves,' she said. 'But what you
gets in a good gumbo is everything.'
    -- "Witches Abroad" by Terry Prachett
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 24 13:43:37 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1B9228C0F6; Sat, 24 Jan 2009 13:43:37 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F65E28C0F6 for <tap@core3.amsl.com>; Sat, 24 Jan 2009 13:43:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level: 
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ahqqWPq5zQhq for <tap@core3.amsl.com>; Sat, 24 Jan 2009 13:43:36 -0800 (PST)
Received: from smtp.kineticode.com (host-201.commandprompt.net [207.173.203.201]) by core3.amsl.com (Postfix) with ESMTP id C418728C0E8 for <tap@ietf.org>; Sat, 24 Jan 2009 13:43:36 -0800 (PST)
Received: from [192.168.1.102] (c-76-105-135-51.hsd1.or.comcast.net [76.105.135.51]) by smtp.kineticode.com (Postfix) with ESMTPSA id E03E1508059; Sat, 24 Jan 2009 13:38:25 -0800 (PST)
Message-Id: <243BC9F0-C50C-4DEE-9812-7A52102AB05F@kineticode.com>
From: "David E. Wheeler" <david@kineticode.com>
To: Ovid <publiustemp-tapx@yahoo.com>
In-Reply-To: <335014.20536.qm@web65715.mail.ac4.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Sat, 24 Jan 2009 13:43:18 -0800
References: <497A77D0.8070500@pobox.com> <335014.20536.qm@web65715.mail.ac4.yahoo.com>
X-Mailer: Apple Mail (2.930.3)
Cc: tap@ietf.org
Subject: Re: [tap] "ok 1 description" vs "ok 1 - description"
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

On Jan 24, 2009, at 1:55 AM, Ovid wrote:

> So everyone who's written a TAP producer in another language and
> didn't see fit to add that dash will now be producing invalid TAP?

I always include the dash in the JavaScript and PostgreSQL ports,  
because that's what Test::More does.

David
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Tue Jan 27 17:27:48 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4A4E3A6B17; Tue, 27 Jan 2009 17:27:48 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5DDCB3A6B17 for <tap@core3.amsl.com>; Tue, 27 Jan 2009 17:27:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a0t11XAEVLFk for <tap@core3.amsl.com>; Tue, 27 Jan 2009 17:27:46 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by core3.amsl.com (Postfix) with ESMTP id 9C4123A696E for <tap@ietf.org>; Tue, 27 Jan 2009 17:27:45 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 96FF9945DD; Tue, 27 Jan 2009 20:27:27 -0500 (EST)
Received: from windhund.local (unknown [75.150.41.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id C8D76945DC; Tue, 27 Jan 2009 20:27:25 -0500 (EST)
Message-ID: <497FB47C.1000805@pobox.com>
Date: Tue, 27 Jan 2009 17:27:24 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tap@ietf.org, "David E. Wheeler" <david@kineticode.com>
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: D2E262E6-ECDA-11DD-9340-CC4CC92D7133-02258300!a-sasl-fastnet.pobox.com
Subject: [tap] TAP presentation at OSCON
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

I'm planning on submitting a presentation on TAP at OSCON this year.  Cover
the protocol, why it's cool, relationship to xUnit (and how they can live
together), adoption by various projects, etc...  Basically a simple
information and advocacy piece.

I've already got three other proposals, so if anyone would like to co-present
come forward and I'll gladly work with you.  Especially if it's someone
outside of Perl to give a fresh perspective and some "this isn't just a Perl
thing" legitimacy.


-- 
Being faith-based doesn't trump reality.
	-- Bruce Sterling

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Wed Jan 28 08:02:41 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A5563A6B2A; Wed, 28 Jan 2009 08:02:41 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D70ED3A6BB4 for <tap@core3.amsl.com>; Wed, 28 Jan 2009 08:02:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOgEfEZsUWUm for <tap@core3.amsl.com>; Wed, 28 Jan 2009 08:02:39 -0800 (PST)
Received: from mail.plusthree.com (mail.plusthree.com [70.42.42.197]) by core3.amsl.com (Postfix) with ESMTP id 0DF5C3A6B2A for <tap@ietf.org>; Wed, 28 Jan 2009 08:02:38 -0800 (PST)
Received: from localhost.localdomain (dsl093-241-113.ral1.dsl.speakeasy.net [66.93.241.113]) (authenticated bits=0) by mail.plusthree.com (8.14.2/8.14.2) with ESMTP id n0SFtGZX011182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2009 10:55:16 -0500
Message-ID: <49808107.1080201@plusthree.com>
Date: Wed, 28 Jan 2009 11:00:07 -0500
From: Michael Peters <mpeters@plusthree.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Michael G Schwern <schwern@pobox.com>
References: <497FB47C.1000805@pobox.com>
In-Reply-To: <497FB47C.1000805@pobox.com>
Cc: tap@ietf.org
Subject: Re: [tap] TAP presentation at OSCON
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

Michael G Schwern wrote:

> I've already got three other proposals, so if anyone would like to co-present
> come forward and I'll gladly work with you. 

I'd be glad to help out.

> Especially if it's someone
> outside of Perl to give a fresh perspective and some "this isn't just a Perl
> thing" legitimacy.

Unfortunately, I'm a Perler :) Feel free to reject me if someone better comes along.

-- 
Michael Peters
Plus Three, LP

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Wed Jan 28 16:20:48 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D8D183A6C05; Wed, 28 Jan 2009 16:20:48 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 828E53A6C18 for <tap@core3.amsl.com>; Wed, 28 Jan 2009 16:20:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.407
X-Spam-Level: 
X-Spam-Status: No, score=-2.407 tagged_above=-999 required=5 tests=[AWL=0.192,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a0r6XAX0nSDc for <tap@core3.amsl.com>; Wed, 28 Jan 2009 16:20:47 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by core3.amsl.com (Postfix) with ESMTP id BE09F3A6C05 for <tap@ietf.org>; Wed, 28 Jan 2009 16:20:46 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id A6FAB941FE; Wed, 28 Jan 2009 19:20:27 -0500 (EST)
Received: from [10.23.42.2] (unknown [69.64.236.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 0A807941FA; Wed, 28 Jan 2009 19:20:23 -0500 (EST)
Message-ID: <4980F645.5080700@pobox.com>
Date: Wed, 28 Jan 2009 16:20:21 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tap@ietf.org
References: <497FB47C.1000805@pobox.com> <49808107.1080201@plusthree.com>
In-Reply-To: <49808107.1080201@plusthree.com>
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: A13ACE7A-ED9A-11DD-AB7E-CC4CC92D7133-02258300!a-sasl-fastnet.pobox.com
Subject: Re: [tap] TAP presentation at OSCON
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

Michael Peters wrote:
> Michael G Schwern wrote:
> 
>> I've already got three other proposals, so if anyone would like to
>> co-present
>> come forward and I'll gladly work with you. 
> 
> I'd be glad to help out.
> 
>> Especially if it's someone
>> outside of Perl to give a fresh perspective and some "this isn't just
>> a Perl
>> thing" legitimacy.
> 
> Unfortunately, I'm a Perler :) Feel free to reject me if someone better
> comes along.

But you are one of the few people doing large scale TAP archiving.

What I'm looking for is breadth of experience with TAP.  I understand it from
the producer and protocol side.  Ovid has volunteered and brings detailed
parser experience.  Michael brings experience using TAP as an archive and test
history.  David Wheeler would bring in using TAP in odd environments via PgTAP
and Javascript showing its flexibility.

What's missing is someone with an xUnit point of view, because that's what
everyone else uses people are going to want to know how it relates.  I can't
really answer those questions.  So if we had someone familiar with xUnit to
help out we'd be all set.


-- 
You know what the chain of command is? It's the chain I go get and beat you
with 'til you understand who's in ruttin' command here.
        -- Jayne Cobb, "Firefly"
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 31 12:18:38 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52AAD3A684F; Sat, 31 Jan 2009 12:18:38 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80D3F3A682D for <tap@core3.amsl.com>; Sat, 31 Jan 2009 12:18:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[AWL=0.164,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5aqzNsALiFhf for <tap@core3.amsl.com>; Sat, 31 Jan 2009 12:18:32 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by core3.amsl.com (Postfix) with ESMTP id 04A5D3A688E for <tap@ietf.org>; Sat, 31 Jan 2009 12:18:30 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 9DAE8955E4 for <tap@ietf.org>; Sat, 31 Jan 2009 15:18:11 -0500 (EST)
Received: from [10.23.42.2] (unknown [69.64.236.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 26B5B955E3 for <tap@ietf.org>; Sat, 31 Jan 2009 15:18:10 -0500 (EST)
Message-ID: <4984B200.6060907@pobox.com>
Date: Sat, 31 Jan 2009 12:18:08 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tap@ietf.org
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: 48506F9A-EFD4-11DD-8921-CC4CC92D7133-02258300!a-sasl-fastnet.pobox.com
Subject: [tap] Parse error vs failure
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

In Oslo, when we came across an edge case that was considered nonsense, the
tendency was to say that its a parse error.  For example, "not ok 4 # SKIP",
because why would you fail a test that didn't run?  Also "1..0" without a
skip, because why would you not run any tests and yet not skip the test?

I think I brought this up earlier, but I want to make sure I have consensus.
I've been calling them failures (with a warning) rather than parse errors.
Why?  Because a parse error means the parser can not extract any information
and can't really tell the user anything but "syntax error at line X".  If your
parser starts guessing at what sort of syntax error it is, well, then it might
as well be grammar at that point.

Worse, a TAP document parser, parsing the full document at once rather than a
traditional line-by-line parser, might invalidate the whole stream and thus
can not extract any information.

If it's just a failure, the parser can get information out of it and has
flexibility about what to do and what action it can suggest the user take.

It complicates the grammar to allow "ok 4 # SKIP" but make "not ok 4 # SKIP" a
syntax error and adds in another special case for the parser.  With "not ok #
SKIP" as normal syntax the skip directive has no effect on the truthiness of
the test.

Consensus?  Generally prefer failure-with-warning over parse error for valid
but sort of nonsense output?


-- 
184. When operating a military vehicle I may *not* attempt something
     "I saw in a cartoon".
    -- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
           http://skippyslist.com/list/

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 31 13:37:54 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4E443A67E9; Sat, 31 Jan 2009 13:37:54 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 261BC3A67E9 for <tap@core3.amsl.com>; Sat, 31 Jan 2009 13:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.285
X-Spam-Level: 
X-Spam-Status: No, score=-2.285 tagged_above=-999 required=5 tests=[AWL=0.314,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Hx-t5HFAaNI for <tap@core3.amsl.com>; Sat, 31 Jan 2009 13:37:52 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id EB7923A69E7 for <tap@ietf.org>; Sat, 31 Jan 2009 13:37:51 -0800 (PST)
Received: (qmail invoked by alias); 31 Jan 2009 21:37:31 -0000
Received: from static-87-79-236-202.netcologne.de (EHLO klangraum) [87.79.236.202] by mail.gmx.net (mp015) with SMTP; 31 Jan 2009 22:37:31 +0100
X-Authenticated: #163624
X-Provags-ID: V01U2FsdGVkX1/zrRZFdv3zoeIeyHfAcVq+PVriIZJDJklipM9j5d jN9N8/acQtep3M
Date: Sat, 31 Jan 2009 22:37:20 +0100
From: Aristotle Pagaltzis <pagaltzis@gmx.de>
To: tap@ietf.org
Message-ID: <20090131213720.GB30031@klangraum.plasmasturm.org>
Mail-Followup-To: tap@ietf.org
References: <4984B200.6060907@pobox.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <4984B200.6060907@pobox.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.77
Subject: Re: [tap] Parse error vs failure
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

* Michael G Schwern <schwern@pobox.com> [2009-01-31 21:20]:
> Generally prefer failure-with-warning over parse error for
> valid but sort of nonsense output?

Basically. I think we should differentiate between syntactical
and semantic errors.

Regards,
-- 
Aristotle Pagaltzis // <http://plasmasturm.org/>
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 31 14:25:26 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4CA963A6A30; Sat, 31 Jan 2009 14:25:26 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F296E3A6A99 for <tap@core3.amsl.com>; Sat, 31 Jan 2009 14:25:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BY3yYty+kL9d for <tap@core3.amsl.com>; Sat, 31 Jan 2009 14:25:10 -0800 (PST)
Received: from h132974.serverkompetenz.net (renormalist.net [81.169.141.46]) by core3.amsl.com (Postfix) with ESMTP id 352833A6A30 for <tap@ietf.org>; Sat, 31 Jan 2009 14:25:09 -0800 (PST)
Received: from ss5 by h132974.serverkompetenz.net with local (Exim 4.63) (envelope-from <ss5@renormalist.net>) id 1LTOGe-0005Ii-Bq for tap@ietf.org; Sat, 31 Jan 2009 23:24:48 +0100
To: tap@ietf.org
References: <497A77D0.8070500@pobox.com> <335014.20536.qm@web65715.mail.ac4.yahoo.com> <20090124115427.GC9114@pjcj.net> <87vds4podb.fsf@renormalist.net> <497B8530.4080903@pobox.com>
From: Steffen Schwigon <ss5@renormalist.net>
Date: Sat, 31 Jan 2009 23:24:48 +0100
Message-ID: <873aezxgen.fsf@renormalist.net>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.19 (linux)
MIME-Version: 1.0
Subject: Re: [tap] "ok 1 description" vs "ok 1 - description"
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

Sorry for the late answer, I seem to be out of sync with the rest of
the world ...

Michael G Schwern <schwern@pobox.com> writes:
> Steffen Schwigon wrote:
>> IMHO when the TAP grammar changes things that were stable for
>> years it's near to the end of the world.
>>
>> I, for instance, evaluate test results via the description over
>> *lots* of archived TAP streams since nearly years. I don't want
>> to become an outlaw.
>
> Out of curiosity, what are you using to create these TAP streams
> and how do they format the description?

They are created within a heterogeneous environment with Perl
Test::More, Python PyTAP, and "echo/print" from Shell or C.

To process the TAP, however, we use the Perl toolchain around
TAP::Parser.


> Seeing as how Test::More is the widest producer of TAP, and it's
> being doing "ok 1 - description" for years now, and that the dash
> is optional so nothing is being made illegal, all of the above
> would seem to actually be an argument in favor of adding the
> optional dash to the grammar as it better describes reality.
>
> And it produces a nicer to read TAP moving forward, which is
> important, too.

I see that the dash was meant optional for TAP. Maybe the
optionality of the dash changed in TAP::Parser 3? Admittedly, I
didn't try.

Anyway, the only useful current processing tool is TAP::Parser and
that slurps the dash as part of the description.

So it's probably not the producers like Test::*, PyTAP and
"print" but the history of the *consumer*, i.e. TAP::Parser,
that I'm worrying about.

Someone(tm) (not me, I know, sorry) could try out what happens
around CPAN (as the largest reference test suite) if the grammar is
changed in TAP::Parser.


> As a point of reference, we are discussing the grammar exactly
> because we're trying to write down reality.

I see. But wasn't the original plan to write down what the only
existing consumer toolchain aka. TAP::Parser does, because else no
one in the world has a toolchain?


Kind regards,
Steffen
-- 
Steffen Schwigon <ss5@renormalist.net>
Dresden Perl Mongers <http://dresden-pm.org/>
German Perl-Workshop 2009 <http://www.perl-workshop.de/en/2009>
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 31 14:30:32 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E0183A67A1; Sat, 31 Jan 2009 14:30:32 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B7143A6A99 for <tap@core3.amsl.com>; Sat, 31 Jan 2009 14:30:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level: 
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qYd2-rZWkEPr for <tap@core3.amsl.com>; Sat, 31 Jan 2009 14:30:30 -0800 (PST)
Received: from smtp.kineticode.com (host-201.commandprompt.net [207.173.203.201]) by core3.amsl.com (Postfix) with ESMTP id 48CFC3A6A30 for <tap@ietf.org>; Sat, 31 Jan 2009 14:30:30 -0800 (PST)
Received: from [192.168.1.100] (c-76-105-135-51.hsd1.or.comcast.net [76.105.135.51]) by smtp.kineticode.com (Postfix) with ESMTPSA id 383CA50805D; Sat, 31 Jan 2009 14:24:38 -0800 (PST)
Message-Id: <8663738C-A8A5-41A9-A065-20BF1C97C2B5@kineticode.com>
From: "David E. Wheeler" <david@kineticode.com>
To: Michael G Schwern <schwern@pobox.com>
In-Reply-To: <4984B200.6060907@pobox.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Sat, 31 Jan 2009 14:30:10 -0800
References: <4984B200.6060907@pobox.com>
X-Mailer: Apple Mail (2.930.3)
Cc: tap@ietf.org
Subject: Re: [tap] Parse error vs failure
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

On Jan 31, 2009, at 12:18 PM, Michael G Schwern wrote:

> It complicates the grammar to allow "ok 4 # SKIP" but make "not ok 4  
> # SKIP" a
> syntax error and adds in another special case for the parser.  With  
> "not ok #
> SKIP" as normal syntax the skip directive has no effect on the  
> truthiness of
> the test.
>
> Consensus?  Generally prefer failure-with-warning over parse error  
> for valid
> but sort of nonsense output?

+1

David
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 31 15:41:29 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90BF33A67D1; Sat, 31 Jan 2009 15:41:29 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1B473A6834 for <tap@core3.amsl.com>; Sat, 31 Jan 2009 15:41:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.455
X-Spam-Level: 
X-Spam-Status: No, score=-2.455 tagged_above=-999 required=5 tests=[AWL=0.144,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pfqmj6sDW7Mj for <tap@core3.amsl.com>; Sat, 31 Jan 2009 15:41:27 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by core3.amsl.com (Postfix) with ESMTP id C4E753A67D1 for <tap@ietf.org>; Sat, 31 Jan 2009 15:41:25 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id A743C951EA; Sat, 31 Jan 2009 18:41:05 -0500 (EST)
Received: from [10.23.42.2] (unknown [69.64.236.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 7DF9C951E7; Sat, 31 Jan 2009 18:41:03 -0500 (EST)
Message-ID: <4984E18D.7000606@pobox.com>
Date: Sat, 31 Jan 2009 15:41:01 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Steffen Schwigon <ss5@renormalist.net>
References: <497A77D0.8070500@pobox.com> <335014.20536.qm@web65715.mail.ac4.yahoo.com> <20090124115427.GC9114@pjcj.net> <87vds4podb.fsf@renormalist.net> <497B8530.4080903@pobox.com> <873aezxgen.fsf@renormalist.net>
In-Reply-To: <873aezxgen.fsf@renormalist.net>
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: A09BA342-EFF0-11DD-B098-CC4CC92D7133-02258300!a-sasl-fastnet.pobox.com
Cc: tap@ietf.org
Subject: Re: [tap] "ok 1 description" vs "ok 1 - description"
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

Steffen Schwigon wrote:
>> Seeing as how Test::More is the widest producer of TAP, and it's
>> being doing "ok 1 - description" for years now, and that the dash
>> is optional so nothing is being made illegal, all of the above
>> would seem to actually be an argument in favor of adding the
>> optional dash to the grammar as it better describes reality.
>>
>> And it produces a nicer to read TAP moving forward, which is
>> important, too.
> 
> I see that the dash was meant optional for TAP. Maybe the
> optionality of the dash changed in TAP::Parser 3? Admittedly, I
> didn't try.

The last version of Test::Harness 2 before TAP::Parser strips the dash if its
there, you can see the code in Test::Harness::Point->from_test_line().
http://cpansearch.perl.org/src/PETDANCE/Test-Harness-2.64/lib/Test/Harness/Point.pm

But earlier versions of TH2 do not.

TAP::Parser (aka Test::Harness 3) does not strip the dash.

So we've already got some waffling around how the description is handled.  We
survived with hardly anyone noticing.


>> As a point of reference, we are discussing the grammar exactly
>> because we're trying to write down reality.
> 
> I see. But wasn't the original plan to write down what the only
> existing consumer toolchain aka. TAP::Parser does, because else no
> one in the world has a toolchain?

What the existing consumers and producers do is being written down.  Within
that limit, the human readability and machine parsability of TAP and its
ability to extend in the future are being protected.

Presumably the consumers and producers are in sync, but in the case of the
description Test::More and TAP::Parser aren't.  Test::More intends it to be
stripped, TAP::Parser doesn't do the stripping.  Nobody really uses it for
anything but human readable display, and they probably strip as to their
preference, so it hasn't been a big deal.

It's important to remember that TAP::Parser was written based on what
Test::Harness 2, Test::More and Test.pm do.  Test::More was written based on
what Test::Harness 1 and Perl's core t/TEST TAP parser handled.  Test::Harness
1 was written based on t/TEST which was written to support the Perl core
tests.  Parsers effect consumers, consumers effect parsers.

TAP::Parser was the first attempt to try and make sense of all that historical
cruft from scratch, and this is the first attempt to formalize it.  I'd like
to not just enshrine whatever it is we're doing at the moment we write the
draft and actually put some thought into it.

As mentioned before, the interpretation of the description is open to some
interpretation because it's just an identifier for the human.  It doesn't
effect pass or fail.  For one legacy parser to interpret it as "- foo" and
another to say "foo" doesn't make much difference.  Going forward is what does.

In addition, the existence of the dash removes some ambiguities.  How is this
interpreted?

ok 1      foo

Is that "foo" or "     foo"?  Its an open question.  Because of the tendency
of TAP::Parser to use \s+ (ie. one or more whitespace characters) to separate
tokens it's probably interpreted as "foo".  I doubt that was by design but
rather an expedient way to write the regexes.  If we just went with what
TAP::Parser does we'd be left with no way to have a machine readable leading
space in a description.

As another example, some people like to indent sub tests.  Without a dash it
would come out like this:

ok 1 thing() didn't blow up
ok 2   it returned the right thing
ok 3   they lived happily ever after

Do we count the leading spaces as part of the description?  The dash removes
this ambiguity.

ok 1 - thing() didn't blow up
ok 2 -   it returned the right thing
ok 3 -   they lived happily ever after

The details of how a description is handled has a lot ambiguity and wiggle
room both in current implementation and in definition.  It is not yet boxed in
by what TAP::Parser currently does.


-- 
I am somewhat preoccupied telling the laws of physics to shut up and sit down.
	-- Vaarsuvius, "Order of the Stick"
           http://www.giantitp.com/comics/oots0107.html
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 31 16:49:06 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA6623A68CB; Sat, 31 Jan 2009 16:49:06 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F59B3A68CB for <tap@core3.amsl.com>; Sat, 31 Jan 2009 16:49:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sOoCV1oY6WVX for <tap@core3.amsl.com>; Sat, 31 Jan 2009 16:49:04 -0800 (PST)
Received: from mail.plusthree.com (mail.plusthree.com [70.42.42.197]) by core3.amsl.com (Postfix) with ESMTP id AB1563A6A8D for <tap@ietf.org>; Sat, 31 Jan 2009 16:49:04 -0800 (PST)
Received: from localhost.localdomain (cpe-024-211-145-096.nc.res.rr.com [24.211.145.96]) (authenticated bits=0) by mail.plusthree.com (8.14.2/8.14.2) with ESMTP id n110ekcQ017017 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tap@ietf.org>; Sat, 31 Jan 2009 19:40:49 -0500
Message-ID: <4984F0E4.8090001@plusthree.com>
Date: Sat, 31 Jan 2009 19:46:28 -0500
From: Michael Peters <mpeters@plusthree.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: tap@ietf.org
References: <4984B200.6060907@pobox.com> <20090131213720.GB30031@klangraum.plasmasturm.org>
In-Reply-To: <20090131213720.GB30031@klangraum.plasmasturm.org>
Subject: Re: [tap] Parse error vs failure
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

Aristotle Pagaltzis wrote:
> * Michael G Schwern <schwern@pobox.com> [2009-01-31 21:20]:
>> Generally prefer failure-with-warning over parse error for
>> valid but sort of nonsense output?
> 
> Basically. I think we should differentiate between syntactical
> and semantic errors.

I agree. Syntax errors should be parse errors, but semantic errors should be failure-with-warning.

-- 
Michael Peters
Plus Three, LP

_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 31 16:52:37 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 009703A68CB; Sat, 31 Jan 2009 16:52:37 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BA573A68E4 for <tap@core3.amsl.com>; Sat, 31 Jan 2009 16:52:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h4QyzOQknXRp for <tap@core3.amsl.com>; Sat, 31 Jan 2009 16:52:35 -0800 (PST)
Received: from h132974.serverkompetenz.net (renormalist.net [81.169.141.46]) by core3.amsl.com (Postfix) with ESMTP id D89ED3A68CB for <tap@ietf.org>; Sat, 31 Jan 2009 16:52:34 -0800 (PST)
Received: from ss5 by h132974.serverkompetenz.net with local (Exim 4.63) (envelope-from <ss5@renormalist.net>) id 1LTQZK-0005eU-EN for tap@ietf.org; Sun, 01 Feb 2009 01:52:14 +0100
To: tap@ietf.org
References: <497A77D0.8070500@pobox.com> <335014.20536.qm@web65715.mail.ac4.yahoo.com> <20090124115427.GC9114@pjcj.net> <87vds4podb.fsf@renormalist.net> <497B8530.4080903@pobox.com> <873aezxgen.fsf@renormalist.net> <4984E18D.7000606@pobox.com>
From: Steffen Schwigon <ss5@renormalist.net>
Date: Sun, 01 Feb 2009 01:52:14 +0100
In-Reply-To: <4984E18D.7000606@pobox.com> (Michael G. Schwern's message of "Sat, 31 Jan 2009 15:41:01 -0800")
Message-ID: <87tz7fvv0h.fsf@renormalist.net>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.19 (linux)
MIME-Version: 1.0
Subject: Re: [tap] "ok 1 description" vs "ok 1 - description"
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

Michael G Schwern <schwern@pobox.com> writes:
> Steffen Schwigon wrote:
>> I see that the dash was meant optional for TAP. Maybe the
>> optionality of the dash changed in TAP::Parser 3? Admittedly, I
>> didn't try.
>
> The last version of Test::Harness 2 before TAP::Parser strips the
> dash if its there
>
> But earlier versions of TH2 do not.
>
> TAP::Parser (aka Test::Harness 3) does not strip the dash.

So it already flip-flop'ed in the short history

 TH2early (not stripped),
 TH2late  (stripped),
 TH3/TP   (not stripped),

?

I agree then that stripping the dash from description might not be so
end-of-world as I initially thought.

I'm maybe one of the very few who currently depend on the exact
descriptions but I can probably even change my evaluation tools.

Kind regards,
Steffen 
-- 
Steffen Schwigon <ss5@renormalist.net>
Dresden Perl Mongers <http://dresden-pm.org/>
German Perl-Workshop 2009 <http://www.perl-workshop.de/en/2009>
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 31 16:58:56 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 381633A686D; Sat, 31 Jan 2009 16:58:56 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F257B3A686D for <tap@core3.amsl.com>; Sat, 31 Jan 2009 16:58:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kGUhenvkmoOJ for <tap@core3.amsl.com>; Sat, 31 Jan 2009 16:58:54 -0800 (PST)
Received: from h132974.serverkompetenz.net (renormalist.net [81.169.141.46]) by core3.amsl.com (Postfix) with ESMTP id 2E1413A6A8D for <tap@ietf.org>; Sat, 31 Jan 2009 16:58:53 -0800 (PST)
Received: from ss5 by h132974.serverkompetenz.net with local (Exim 4.63) (envelope-from <ss5@renormalist.net>) id 1LTQfQ-0005g2-Fz for tap@ietf.org; Sun, 01 Feb 2009 01:58:32 +0100
To: tap@ietf.org
References: <4984B200.6060907@pobox.com> <20090131213720.GB30031@klangraum.plasmasturm.org> <4984F0E4.8090001@plusthree.com>
From: Steffen Schwigon <ss5@renormalist.net>
Date: Sun, 01 Feb 2009 01:58:32 +0100
In-Reply-To: <4984F0E4.8090001@plusthree.com> (Michael Peters's message of "Sat, 31 Jan 2009 19:46:28 -0500")
Message-ID: <87pri3vupz.fsf@renormalist.net>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.19 (linux)
MIME-Version: 1.0
Subject: Re: [tap] Parse error vs failure
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

Michael Peters <mpeters@plusthree.com> writes:
> Aristotle Pagaltzis wrote:
>> * Michael G Schwern <schwern@pobox.com> [2009-01-31 21:20]:
>>> Generally prefer failure-with-warning over parse error for
>>> valid but sort of nonsense output?
>> Basically. I think we should differentiate between syntactical
>> and semantic errors.
>
> I agree. Syntax errors should be parse errors, but semantic errors should be failure-with-warning.

+1 Me too.

Steffen
-- 
Steffen Schwigon <ss5@renormalist.net>
Dresden Perl Mongers <http://dresden-pm.org/>
German Perl-Workshop 2009 <http://www.perl-workshop.de/en/2009>
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

From tap-bounces@ietf.org  Sat Jan 31 18:57:44 2009
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 337003A677C; Sat, 31 Jan 2009 18:57:44 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E24D83A6806 for <tap@core3.amsl.com>; Sat, 31 Jan 2009 18:57:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.471
X-Spam-Level: 
X-Spam-Status: No, score=-2.471 tagged_above=-999 required=5 tests=[AWL=0.128,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7FRR+if-pSCZ for <tap@core3.amsl.com>; Sat, 31 Jan 2009 18:57:42 -0800 (PST)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by core3.amsl.com (Postfix) with ESMTP id 19A7F3A677C for <tap@ietf.org>; Sat, 31 Jan 2009 18:57:41 -0800 (PST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 14E4C95D27; Sat, 31 Jan 2009 21:57:22 -0500 (EST)
Received: from [10.23.42.2] (unknown [69.64.236.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id EED7595D26; Sat, 31 Jan 2009 21:57:19 -0500 (EST)
Message-ID: <49850F8C.4020904@pobox.com>
Date: Sat, 31 Jan 2009 18:57:16 -0800
From: Michael G Schwern <schwern@pobox.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Steffen Schwigon <ss5@renormalist.net>
References: <497A77D0.8070500@pobox.com> <335014.20536.qm@web65715.mail.ac4.yahoo.com> <20090124115427.GC9114@pjcj.net> <87vds4podb.fsf@renormalist.net> <497B8530.4080903@pobox.com> <873aezxgen.fsf@renormalist.net> <4984E18D.7000606@pobox.com> <87tz7fvv0h.fsf@renormalist.net>
In-Reply-To: <87tz7fvv0h.fsf@renormalist.net>
X-Enigmail-Version: 0.95.7
X-Pobox-Relay-ID: 0BE39E3C-F00C-11DD-B392-CC4CC92D7133-02258300!a-sasl-fastnet.pobox.com
Cc: tap@ietf.org
Subject: Re: [tap] "ok 1 description" vs "ok 1 - description"
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

Steffen Schwigon wrote:
>>> I see that the dash was meant optional for TAP. Maybe the
>>> optionality of the dash changed in TAP::Parser 3? Admittedly, I
>>> didn't try.
>> The last version of Test::Harness 2 before TAP::Parser strips the
>> dash if its there
>>
>> But earlier versions of TH2 do not.
>>
>> TAP::Parser (aka Test::Harness 3) does not strip the dash.
> 
> So it already flip-flop'ed in the short history
> 
>  TH2early (not stripped),
>  TH2late  (stripped),
>  TH3/TP   (not stripped),
> 
> ?

Yep, that's about right.  Nothing before TH2 did anything at all with the
description.


> I agree then that stripping the dash from description might not be so
> end-of-world as I initially thought.
> 
> I'm maybe one of the very few who currently depend on the exact
> descriptions but I can probably even change my evaluation tools.

Fortunately, it will be self consistent within one tool.

What are you doing with them?


-- 
'All anyone gets in a mirror is themselves,' she said. 'But what you
gets in a good gumbo is everything.'
    -- "Witches Abroad" by Terry Prachett
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap
