[Techspec] Validation of formal languages

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 24 May 2006 18:40 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiyHp-0002gx-Ls; Wed, 24 May 2006 14:40:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiyHo-0002g3-JD for techspec@ietf.org; Wed, 24 May 2006 14:40:48 -0400
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiyHn-0007KB-5I for techspec@ietf.org; Wed, 24 May 2006 14:40:48 -0400
Received: from [10.20.30.249] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k4OIeg7K040366 for <techspec@ietf.org>; Wed, 24 May 2006 11:40:46 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p062309d4c09a5393fadc@[10.20.30.249]>
Date: Wed, 24 May 2006 11:36:50 -0700
To: techspec@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: [Techspec] Validation of formal languages
X-BeenThere: techspec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" <techspec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/techspec>, <mailto:techspec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/techspec>
List-Post: <mailto:techspec@ietf.org>
List-Help: <mailto:techspec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/techspec>, <mailto:techspec-request@ietf.org?subject=subscribe>
Errors-To: techspec-bounces@ietf.org

Section 3.5 that seems out of place in that it is the only part of 
this document that says "the IETF technical publisher will review 
this part of documents for technical correctness". It makes sense to 
say "if automated tools are available to check formal languages, the 
IETF technical publisher should run the tools late in the editing 
process", but not to make it seem like that validation is the job of 
the technical publisher.

This section might also add a requirement that the IETF technical 
publisher should not change any examples (changing words, 
reformatting with line breaks, and so on) without explicitly alerting 
the document authors. Some formal languages are quite sensitive to 
byte counts and line breaks.

--Paul Hoffman, Director
--VPN Consortium

_______________________________________________
Techspec mailing list
Techspec@ietf.org
https://www1.ietf.org/mailman/listinfo/techspec