Re: [tap] "ok 1 description" vs "ok 1 - description"

Paul Johnson <paul@pjcj.net> Sat, 24 January 2009 11:54 UTC

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