Re: I-D ACTION: draft-ash-alt-formats-01.txt

John Levine <johnl@iecc.com> Tue, 31 January 2006 20:10 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F41q3-000115-TO; Tue, 31 Jan 2006 15:10:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F41py-0000vC-6U for ietf@megatron.ietf.org; Tue, 31 Jan 2006 15:10:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23474 for <ietf@ietf.org>; Tue, 31 Jan 2006 15:09:10 -0500 (EST)
Received: from xuxa.iecc.com ([208.31.42.42]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F41vS-0002ht-TT for ietf@ietf.org; Tue, 31 Jan 2006 15:16:32 -0500
Received: (qmail 19635 invoked from network); 31 Jan 2006 20:05:04 -0000
Received: from simone.iecc.com (208.31.42.47) by mail2.iecc.com with QMQP; 31 Jan 2006 20:05:04 -0000
Date: Tue, 31 Jan 2006 20:05:04 -0000
Message-ID: <20060131200504.29161.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA09FA9A1E@KCCLUST06EVS1.ugd.att.com>
Mime-Version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: gash@att.com
Subject: Re: I-D ACTION: draft-ash-alt-formats-01.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

>We propose an experiment based on RFC 3933 allowing, in addition to
>ASCII text as a normative input/output format, PDF as an additional
>normative output format.

There are a lot of different formats called PDF.  There are PDF 1.1,
1.2, 1.3, and 1.4.  There's the new PDF/A archival profile along with
a variety of other industry-specific PDF/x profiles .  And there are a
whole lot of files produced by alleged PDF generators that don't
actually conform to any version of the PDF spec.  (Often they depend
on non-standard fonts that happened to be installed on the author's
computer.)

Among valid PDFs, do you include PDFs that are coded to prohibit text
extraction?  How about PDFs that are just bitmap scans of printed
documents, like the PDF versions of some early RFCs from the 1970s?

As we all know, one of the reasons that ASCII text has stood the test
of time is that its definition is stable and well-understood, so it is
at no risk of becoming unreadable due to losing the programs needed to
decode it.  I think that PDF/A may be well enough defined to be an
adequate archival format, but just "PDF" is way too vague.

R's,
John


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