
From jnc@mercury.lcs.mit.edu  Mon Jul  2 07:40:58 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CFE721F85CC for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 07:40:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MOa06JlAzUqJ for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 07:40:58 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id EA34221F85B5 for <xml2rfc@ietf.org>; Mon,  2 Jul 2012 07:40:57 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 72B3A18C0A4; Mon,  2 Jul 2012 10:41:02 -0400 (EDT)
To: xml2rfc@ietf.org
Message-Id: <20120702144102.72B3A18C0A4@mercury.lcs.mit.edu>
Date: Mon,  2 Jul 2012 10:41:02 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Mailman-Approved-At: Mon, 02 Jul 2012 08:44:58 -0700
Cc: jnc@mercury.lcs.mit.edu
Subject: [xml2rfc] Footnotes?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2012 14:40:58 -0000

Maybe I missed it in reading through all the doc, but is there any way to do a
footnote? (If not, I guess I can manually float it down to the end of the
section, if I'm using the output type where each section starts at the head of
a new page.)


Oh, while I'm sending this, let me add that it's mildly irritating that in the
initial author element, one is only allowed a single initial, i.e. I can't do:

  <author fullname="J. Noel Chiappa" initials="J.N." surname="Chiappa">

As usual, the world is prejudiced against those of us who use their middle
names! Vaguely expected of paper forms, but computers should be more flexible.

And I too was bitten by not being able to have Appendixes before the References
(as are several IDs co-workers are working on). Please, let authors figure out
which ordering works best for their document.

       Noel

PS: Please CC me on any replies, I'm not on the mailing list.

From julian.reschke@gmx.de  Mon Jul  2 09:04:59 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1064D21F871A for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.165
X-Spam-Level: 
X-Spam-Status: No, score=-105.165 tagged_above=-999 required=5 tests=[AWL=-2.566, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hfIzAY8fZ-Mq for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:04:58 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 100C821F8692 for <xml2rfc@ietf.org>; Mon,  2 Jul 2012 09:04:57 -0700 (PDT)
Received: (qmail invoked by alias); 02 Jul 2012 16:04:54 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp069) with SMTP; 02 Jul 2012 18:04:54 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/lScJtPYPluRP8iVTUwwxRwob+A20OTP/mkxD7/+ gMcaPf4WbHiy+j
Message-ID: <4FF1C6A6.1020803@gmx.de>
Date: Mon, 02 Jul 2012 18:04:54 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20120702144102.72B3A18C0A4@mercury.lcs.mit.edu>
In-Reply-To: <20120702144102.72B3A18C0A4@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Footnotes?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2012 16:04:59 -0000

On 2012-07-02 16:41, Noel Chiappa wrote:
> Maybe I missed it in reading through all the doc, but is there any way to do a
> footnote? (If not, I guess I can manually float it down to the end of the
> section, if I'm using the output type where each section starts at the head of
> a new page.)

No, there is no footnote support (and I believe there shouldn't be one, 
as we're trying to move away from page-oriented design).

> Oh, while I'm sending this, let me add that it's mildly irritating that in the
> initial author element, one is only allowed a single initial, i.e. I can't do:
>
>    <author fullname="J. Noel Chiappa" initials="J.N." surname="Chiappa">

I don't see anything wrong with the above (well, except for missing 
whitespace between "J." and "N.").

> As usual, the world is prejudiced against those of us who use their middle
> names! Vaguely expected of paper forms, but computers should be more flexible.
 >
> And I too was bitten by not being able to have Appendixes before the References
> (as are several IDs co-workers are working on). Please, let authors figure out
> which ordering works best for their document.

I'd like the documents to be consistent; is there a particular reason 
why the default is a problem?

> PS: Please CC me on any replies, I'm not on the mailing list.

Ack, but please consider joining.

Best regards, Julian

From nico@cryptonector.com  Mon Jul  2 09:20:43 2012
Return-Path: <nico@cryptonector.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 125A821F8741 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Level: 
X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=-1.121, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HxQgwtvZvsJI for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:20:42 -0700 (PDT)
Received: from homiemail-a95.g.dreamhost.com (caiajhbdccac.dreamhost.com [208.97.132.202]) by ietfa.amsl.com (Postfix) with ESMTP id 89B5421F86C9 for <xml2rfc@ietf.org>; Mon,  2 Jul 2012 09:20:42 -0700 (PDT)
Received: from homiemail-a95.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a95.g.dreamhost.com (Postfix) with ESMTP id ED99A1E05C for <xml2rfc@ietf.org>; Mon,  2 Jul 2012 09:20:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=TQTgMQg3ivHFnyWpqL9ha PpZJ7g8wWJjTWc7rfarD4s3ZYtUE+Eggj4MW9opKZKDvUm2ibyaBL6s8eetkH0fG 7tjPzIVCb3Nfvfk19wcRI988+VUQYDpdwnB/DY7RjbBP+1uKvHBts6FLESWqO6Qa MLTpNkN8mGYSiic8DSTw4s=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=mHdv1A6Yxe75/m+MDkuc CqAk4rc=; b=fK2dG4kOe4FC1sVAT4U0YSeEMS2Gfy4kde664X9UGcn6oa/MqgF1 p88iOAQzcf8OcTi4ZXweg84N1YJO2z2kZzEcIRp2IC6/Ch24Wbnik5AoJWpTY9nP uFa4XrlPJ+TQRrRk0oNxVWO7gALYpQava+cOBCrOpBsZ1WK/KKUstqk=
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a95.g.dreamhost.com (Postfix) with ESMTPSA id B42881E00D for <xml2rfc@ietf.org>; Mon,  2 Jul 2012 09:20:47 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so4003206vcq.31 for <xml2rfc@ietf.org>; Mon, 02 Jul 2012 09:20:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.19.133 with SMTP id f5mr5335312vde.41.1341246047068; Mon, 02 Jul 2012 09:20:47 -0700 (PDT)
Received: by 10.220.76.203 with HTTP; Mon, 2 Jul 2012 09:20:46 -0700 (PDT)
In-Reply-To: <4FF1C6A6.1020803@gmx.de>
References: <20120702144102.72B3A18C0A4@mercury.lcs.mit.edu> <4FF1C6A6.1020803@gmx.de>
Date: Mon, 2 Jul 2012 11:20:46 -0500
Message-ID: <CAK3OfOgaaAvq8vQVcL_+5CHAcRc1SsBLBGWkDMiuw3p868==FA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=UTF-8
Cc: xml2rfc@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [xml2rfc] Footnotes?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2012 16:20:43 -0000

On Mon, Jul 2, 2012 at 11:04 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> No, there is no footnote support (and I believe there shouldn't be one, as
> we're trying to move away from page-oriented design).

Er, why?  I mean, with e-readers there's still something close to a
page, and footnotes in books still get rendered properly.  It's only
with web pages that this is not true -- a major use case, for sure,
but even if we do get rid of pagination for the HTML rendering, the
footnotes could get collected into one section at the end.  Indeed,
<cref>s, if not made to render inline, get grouped together and
approximate footnotes.

Nico
--

From jnc@mercury.lcs.mit.edu  Mon Jul  2 09:20:53 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0817821F8705 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.339
X-Spam-Level: 
X-Spam-Status: No, score=-6.339 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tI0u328zrO0D for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:20:52 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 6F47921F8702 for <xml2rfc@ietf.org>; Mon,  2 Jul 2012 09:20:52 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 5849918C0B2; Mon,  2 Jul 2012 12:20:57 -0400 (EDT)
To: julian.reschke@gmx.de
Message-Id: <20120702162057.5849918C0B2@mercury.lcs.mit.edu>
Date: Mon,  2 Jul 2012 12:20:57 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: xml2rfc@ietf.org, jnc@mercury.lcs.mit.edu
Subject: Re: [xml2rfc] Footnotes?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2012 16:20:53 -0000

    > From: Julian Reschke <julian.reschke@gmx.de>

    > No, there is no footnote support (and I believe there shouldn't be one,
    > as we're trying to move away from page-oriented design).

I understand, but I wish there was some place to exile less-pressing text to.
Some texts (e.g. many books, Wikipedia articles) have separate 'footnote'
sections at the end which are separate from 'source notes' sections (a.k.a.
References), so it's not just always 'to the bottom of the page'.

I personally don't like the 'at the end of the book' for footnotes, as I have
to keep flipping back and forth - ditto for the Wikipedia style: scroll up,
scroll down, repeat 172 times.

It wouldn't be so bad if they were implemented (on web pages) as 'tooltips'
(i.e. wave your mouse over it, and you get a tiny little pop-up window), but
in a non-paginated ASCII file, what can one do?


    > I don't see anything wrong with the above (well, except for missing
    > whitespace between "J." and "N.").

When I tried that (I started with "J. N.", and also tried "J.&nbsp;N.", it
truncated it to 'J. Chiappa' in the header page in the output. (Tries it
again to make sure he wasn't dreaming.) Yup, truncates to "J.".


    > I'd like the documents to be consistent; is there a particular reason
    > why the default is a problem?

Sometimes it's ugly, and then the appendices before the references makes more
sense. 

Also, as someone said, having the references before the (variable
length/number) appendixes, which maybe lengthy means the references are in
fact not in a fixed, easily-findable, location.

	Noel

From tom.taylor.stds@gmail.com  Mon Jul  2 09:26:52 2012
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC02F21F8758 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZK4gRsgB9tCA for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:26:52 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 16ADC21F873B for <xml2rfc@ietf.org>; Mon,  2 Jul 2012 09:26:51 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so8522076lbb.31 for <xml2rfc@ietf.org>; Mon, 02 Jul 2012 09:26:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-antivirus:x-antivirus-status; bh=ke9UydxwKI9V+5inYzf8aJOyziGl4mb/S+dNi3pOefU=; b=sWKp+Lin5txo80UkbLbi9TOOu7Tp3De7N/cQSKMfkRVsVmjk74hUy+fsLVG95lN88T OzR3LqK4ZD8CHsI1OW5ivb0+CAc1ctA451I+eav4GTw78jktaPGP3Uxy5n9+iul6S5ft QgNef4AlMzv2mDjVGGPaQ4lQHy1ZIwICIM9+WcJuDDdi3N11nWg3FhArqkZQcFpDeLnk MhmyszXk3eYts9p5BMaX7AARkx4dglS0nZvAs9TuhJnI/Jg8vSasOCMhU7vMexWIkCnM SsuIjKsV+dhQpgs0L41EHXDFXK7ibcURtijWUSwNWpFF298rc3KrdeKbE5hUKcHkYLNc CVAQ==
Received: by 10.112.100.234 with SMTP id fb10mr6527702lbb.12.1341246416388; Mon, 02 Jul 2012 09:26:56 -0700 (PDT)
Received: from [127.0.0.1] ([207.112.119.108]) by mx.google.com with ESMTPS id j3sm11048369lbh.0.2012.07.02.09.26.55 (version=SSLv3 cipher=OTHER); Mon, 02 Jul 2012 09:26:55 -0700 (PDT)
Message-ID: <4FF1CBCE.8010400@gmail.com>
Date: Mon, 02 Jul 2012 12:26:54 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20120702162057.5849918C0B2@mercury.lcs.mit.edu>
In-Reply-To: <20120702162057.5849918C0B2@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120702-1, 02/07/2012), Outbound message
X-Antivirus-Status: Clean
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Footnotes?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2012 16:26:53 -0000

My solution for less-pressing text is to indent it in a separate 
paragraph via <list style="empty">.

On 02/07/2012 12:20 PM, Noel Chiappa wrote:
>      > From: Julian Reschke <julian.reschke@gmx.de>
>
>      > No, there is no footnote support (and I believe there shouldn't be one,
>      > as we're trying to move away from page-oriented design).
>
> I understand, but I wish there was some place to exile less-pressing text to.
> Some texts (e.g. many books, Wikipedia articles) have separate 'footnote'
> sections at the end which are separate from 'source notes' sections (a.k.a.
> References), so it's not just always 'to the bottom of the page'.
>
> I personally don't like the 'at the end of the book' for footnotes, as I have
> to keep flipping back and forth - ditto for the Wikipedia style: scroll up,
> scroll down, repeat 172 times.
>
> It wouldn't be so bad if they were implemented (on web pages) as 'tooltips'
> (i.e. wave your mouse over it, and you get a tiny little pop-up window), but
> in a non-paginated ASCII file, what can one do?
>
...

From julian.reschke@gmx.de  Mon Jul  2 09:37:54 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B97621F86C5 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:37:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.076
X-Spam-Level: 
X-Spam-Status: No, score=-105.076 tagged_above=-999 required=5 tests=[AWL=-2.477, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v41Sb+EIT9BT for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:37:53 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 26B4B21F86B6 for <xml2rfc@ietf.org>; Mon,  2 Jul 2012 09:37:52 -0700 (PDT)
Received: (qmail invoked by alias); 02 Jul 2012 16:37:57 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp032) with SMTP; 02 Jul 2012 18:37:57 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/ec1hfSEHeBwYDoYuaRmf/yWvfryj/k9HwSaCM+M ZuUhUcNyKmBNgu
Message-ID: <4FF1CE62.9070401@gmx.de>
Date: Mon, 02 Jul 2012 18:37:54 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20120702162057.5849918C0B2@mercury.lcs.mit.edu>
In-Reply-To: <20120702162057.5849918C0B2@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Footnotes?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2012 16:37:54 -0000

On 2012-07-02 18:20, Noel Chiappa wrote:
>      > From: Julian Reschke <julian.reschke@gmx.de>
>
>      > No, there is no footnote support (and I believe there shouldn't be one,
>      > as we're trying to move away from page-oriented design).
>
> I understand, but I wish there was some place to exile less-pressing text to.
> Some texts (e.g. many books, Wikipedia articles) have separate 'footnote'
> sections at the end which are separate from 'source notes' sections (a.k.a.
> References), so it's not just always 'to the bottom of the page'.
>
> I personally don't like the 'at the end of the book' for footnotes, as I have
> to keep flipping back and forth - ditto for the Wikipedia style: scroll up,
> scroll down, repeat 172 times.
>
> It wouldn't be so bad if they were implemented (on web pages) as 'tooltips'
> (i.e. wave your mouse over it, and you get a tiny little pop-up window), but
> in a non-paginated ASCII file, what can one do?

Rendering in paged plain text indeed is the biggest problem, because it 
makes the layout engine much more complex.

>      > I don't see anything wrong with the above (well, except for missing
>      > whitespace between "J." and "N.").
>
> When I tried that (I started with "J. N.", and also tried "J.&nbsp;N.", it
> truncated it to 'J. Chiappa' in the header page in the output. (Tries it
> again to make sure he wasn't dreaming.) Yup, truncates to "J.".

Which version of xml2rfc are you trying?

>      > I'd like the documents to be consistent; is there a particular reason
>      > why the default is a problem?
>
> Sometimes it's ugly, and then the appendices before the references makes more
> sense.
>
> Also, as someone said, having the references before the (variable
> length/number) appendixes, which maybe lengthy means the references are in
> fact not in a fixed, easily-findable, location.

Maybe. In any case, it would be awesome if we could avoid to make this 
variable; maybe the other default would be better. I recommend you bring 
that up on the rfc-interest mailing list.

Best regards, Julian

From julian.reschke@gmx.de  Mon Jul  2 09:53:34 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21FD621F871D for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.994
X-Spam-Level: 
X-Spam-Status: No, score=-104.994 tagged_above=-999 required=5 tests=[AWL=-2.395, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ta7zopzqc4gj for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:53:33 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 0FD1C21F869E for <xml2rfc@ietf.org>; Mon,  2 Jul 2012 09:53:32 -0700 (PDT)
Received: (qmail invoked by alias); 02 Jul 2012 16:53:37 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp016) with SMTP; 02 Jul 2012 18:53:37 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+Prdwh5CmP1aLHvzP40gqLSlxbU2kH41qnYlXNnm EQGdp5Zfa1230E
Message-ID: <4FF1D210.7020603@gmx.de>
Date: Mon, 02 Jul 2012 18:53:36 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20120702162057.5849918C0B2@mercury.lcs.mit.edu> <4FF1CE62.9070401@gmx.de>
In-Reply-To: <4FF1CE62.9070401@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: [xml2rfc] initials handling
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2012 16:53:34 -0000

On 2012-07-02 18:37, Julian Reschke wrote:
> ...
>>      > I don't see anything wrong with the above (well, except for
>> missing
>>      > whitespace between "J." and "N.").
>>
>> When I tried that (I started with "J. N.", and also tried
>> "J.&nbsp;N.", it
>> truncated it to 'J. Chiappa' in the header page in the output. (Tries it
>> again to make sure he wasn't dreaming.) Yup, truncates to "J.".
>
> Which version of xml2rfc are you trying?
> ...

In the meantime I recalled that this is 
<http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10>; so this is a 
RFC style requirement; If you don't like it you should bring it up on 
rfc-interest mailing list as well...

Best regards, Julian

From jnc@mercury.lcs.mit.edu  Mon Jul  2 09:58:00 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ACA221F85A0 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:58:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level: 
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[AWL=0.217,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pxhAKzZqyDLs for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 09:58:00 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 2EB0B21F8595 for <xml2rfc@ietf.org>; Mon,  2 Jul 2012 09:57:59 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 3F58218C0B2; Mon,  2 Jul 2012 12:58:05 -0400 (EDT)
To: julian.reschke@gmx.de
Message-Id: <20120702165805.3F58218C0B2@mercury.lcs.mit.edu>
Date: Mon,  2 Jul 2012 12:58:05 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: xml2rfc@ietf.org, jnc@mercury.lcs.mit.edu
Subject: Re: [xml2rfc] Footnotes?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2012 16:58:00 -0000

    > From: Julian Reschke <julian.reschke@gmx.de>

    > In any case, it would be awesome if we could avoid to make this
    > variable

I guess I don't see why - do you really think the world will notice much if
some RFCs have 'appendixes - references' and others have 'references -
appendixes'? I mean, a quick look at the TOC will tell them where things are.

(I see, looking at a sample TOC, that the References have a section number,
and the Appendixes don't - is that the issue, that if you reverse the order,
doing the number is problematic? I would just not have a section number on the
References: other sections - Abstact, Author's Address, etc - don't.)

    > maybe the other default would be better.

Definitely. If we have to have only one, put the Appendices first.

    > I recommend you bring that up on the rfc-interest mailing list.

In my copious free time... :-)

	Noel

From julian.reschke@gmx.de  Mon Jul  2 10:06:04 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 289C721F85C5 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 10:06:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.916
X-Spam-Level: 
X-Spam-Status: No, score=-104.916 tagged_above=-999 required=5 tests=[AWL=-2.317, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bn+q10N3Lvhw for <xml2rfc@ietfa.amsl.com>; Mon,  2 Jul 2012 10:06:03 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id E393221F8587 for <xml2rfc@ietf.org>; Mon,  2 Jul 2012 10:06:02 -0700 (PDT)
Received: (qmail invoked by alias); 02 Jul 2012 17:06:07 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp029) with SMTP; 02 Jul 2012 19:06:07 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/uLX5RKgTuRYIZWDAu6A4C9Q4tJyEjcfxrkVMYLE SYMOoZQnxeZCXf
Message-ID: <4FF1D4FE.2030500@gmx.de>
Date: Mon, 02 Jul 2012 19:06:06 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20120702165805.3F58218C0B2@mercury.lcs.mit.edu>
In-Reply-To: <20120702165805.3F58218C0B2@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Footnotes?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2012 17:06:04 -0000

On 2012-07-02 18:58, Noel Chiappa wrote:
>      > From: Julian Reschke <julian.reschke@gmx.de>
>
>      > In any case, it would be awesome if we could avoid to make this
>      > variable
>
> I guess I don't see why - do you really think the world will notice much if
> some RFCs have 'appendixes - references' and others have 'references -
> appendixes'? I mean, a quick look at the TOC will tell them where things are.
>
> (I see, looking at a sample TOC, that the References have a section number,
> and the Appendixes don't - is that the issue, that if you reverse the order,

The Appendixes are "Numbered" as well (A, B, C, ...)

> doing the number is problematic? I would just not have a section number on the
> References: other sections - Abstact, Author's Address, etc - don't.)

Well, it's a format change; we would need to update quite a few tools.

We may want to address these questions once we make progress with the 
new formats.

>      > maybe the other default would be better.
>
> Definitely. If we have to have only one, put the Appendices first.
>
>      > I recommend you bring that up on the rfc-interest mailing list.
>
> In my copious free time... :-)
>
> 	Noel
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
>



From jnc@mercury.lcs.mit.edu  Tue Jul  3 07:58:45 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E304C21F8826 for <xml2rfc@ietfa.amsl.com>; Tue,  3 Jul 2012 07:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.206
X-Spam-Level: 
X-Spam-Status: No, score=-5.206 tagged_above=-999 required=5 tests=[AWL=-1.021, BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iTVGErrp5KWM for <xml2rfc@ietfa.amsl.com>; Tue,  3 Jul 2012 07:58:45 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 0796C21F854F for <xml2rfc@ietf.org>; Tue,  3 Jul 2012 07:58:44 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id F17A218C0C3; Tue,  3 Jul 2012 10:58:51 -0400 (EDT)
To: xml2rfc@ietf.org
Message-Id: <20120703145851.F17A218C0C3@mercury.lcs.mit.edu>
Date: Tue,  3 Jul 2012 10:58:51 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
Subject: [xml2rfc] Symbol list spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jul 2012 14:58:46 -0000

I'm going to guess that there's no (easy) way to suppress the double-space
between the symbol and the list element text, e.g.:

   -  Robust
   -  Efficient
   -  Fast

right? (Back to <artwork> for them, I guess...)

	Noel

From jabley@hopcount.ca  Tue Jul  3 08:05:53 2012
Return-Path: <jabley@hopcount.ca>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 235AB21F8874 for <xml2rfc@ietfa.amsl.com>; Tue,  3 Jul 2012 08:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.392
X-Spam-Level: 
X-Spam-Status: No, score=-101.392 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E0MDxN2Jb+X7 for <xml2rfc@ietfa.amsl.com>; Tue,  3 Jul 2012 08:05:52 -0700 (PDT)
Received: from mail.hopcount.ca (mail.hopcount.ca [216.235.14.37]) by ietfa.amsl.com (Postfix) with ESMTP id 80CD321F8865 for <xml2rfc@ietf.org>; Tue,  3 Jul 2012 08:05:52 -0700 (PDT)
Received: from [2001:4900:1042:100:4ce7:599d:3afd:a3a0] by mail.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1Sm4fo-000AYw-TC; Tue, 03 Jul 2012 15:05:58 +0000
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <20120703145851.F17A218C0C3@mercury.lcs.mit.edu>
Date: Tue, 3 Jul 2012 11:05:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F4B565E2-8C72-4670-AF92-73D6D0229FA7@hopcount.ca>
References: <20120703145851.F17A218C0C3@mercury.lcs.mit.edu>
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Mailer: Apple Mail (2.1278)
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Symbol list spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jul 2012 15:05:53 -0000

On 2012-07-03, at 10:58, Noel Chiappa wrote:

> I'm going to guess that there's no (easy) way to suppress the =
double-space
> between the symbol and the list element text, e.g.:
>=20
>   -  Robust
>   -  Efficient
>   -  Fast
>=20
> right? (Back to <artwork> for them, I guess...)

Seems to me that one of the advantages of having IETF documentation =
produced as structured (XML) documents is that we have a way to mine =
them which is independent of presentation. Another is that we retain the =
ability to change the presentation format (to a different publication =
format, or due to changed style guidelines) without having to =
substantially edit the source, which might cause editorial issues to be =
raised.

When I write I-Ds I try hard to avoid <artwork> elements for things that =
are not actually artwork for these reasons. The presentation style (to =
me) is less important than the content.


Joe=

From julian.reschke@gmx.de  Tue Jul  3 08:08:18 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93C1E21F8885 for <xml2rfc@ietfa.amsl.com>; Tue,  3 Jul 2012 08:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.897
X-Spam-Level: 
X-Spam-Status: No, score=-104.897 tagged_above=-999 required=5 tests=[AWL=-2.298, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BJvMJ3gcDCU9 for <xml2rfc@ietfa.amsl.com>; Tue,  3 Jul 2012 08:08:17 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 5464B21F8883 for <xml2rfc@ietf.org>; Tue,  3 Jul 2012 08:08:16 -0700 (PDT)
Received: (qmail invoked by alias); 03 Jul 2012 15:08:24 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp012) with SMTP; 03 Jul 2012 17:08:24 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18lredz5z0l/e/myHwUOHffMzb2v5LOKHuMsk8Jfp /y6rdiLnlXNVOR
Message-ID: <4FF30AE6.1050606@gmx.de>
Date: Tue, 03 Jul 2012 17:08:22 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20120703145851.F17A218C0C3@mercury.lcs.mit.edu>
In-Reply-To: <20120703145851.F17A218C0C3@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Symbol list spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jul 2012 15:08:19 -0000

On 2012-07-03 16:58, Noel Chiappa wrote:
> I'm going to guess that there's no (easy) way to suppress the double-space
> between the symbol and the list element text, e.g.:
>
>     -  Robust
>     -  Efficient
>     -  Fast

Yes.

> right? (Back to <artwork> for them, I guess...)

No. That makes it just harder for the RFC production center to convert 
to nroff; it probably is less work to just ask for less whitespace 
during AUTH48.

Optimally, we wouldn't waste our time with this; seriously. It should be 
up to the production center to figure out the right format, and they 
should do it consistently.

Best regards, Julian



From russw@riw.us  Thu Jul  5 06:07:48 2012
Return-Path: <russw@riw.us>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8084A21F853B for <xml2rfc@ietfa.amsl.com>; Thu,  5 Jul 2012 06:07:48 -0700 (PDT)
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_20=-0.74]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06+sH19jf7xR for <xml2rfc@ietfa.amsl.com>; Thu,  5 Jul 2012 06:07:47 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id 7F56421F84D3 for <xml2rfc@ietf.org>; Thu,  5 Jul 2012 06:07:47 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1Smlmq-0001ij-G7 for xml2rfc@ietf.org; Thu, 05 Jul 2012 06:08:00 -0700
Message-ID: <4FF591B2.1050100@riw.us>
Date: Thu, 05 Jul 2012 09:08:02 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: xml2rfc@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Subject: [xml2rfc] Question on Reference Error
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2012 13:07:48 -0000

What does this mean, and how do I fix it?

==
[Error] INPUT:82:923: Attribute value "3GPP" of type IDREF must be an
NCName when namespaces are enabled.
[Error] INPUT:309:90: Attribute value "3GPP" of type ID must be an
NCName when namespaces are enabled.
==

This is the reference...

==
<reference anchor="3GPP"
target='http://3gpp.org/ftp/Specs/html-info/25927.htm'>
<front>
<title>3GPP TR 25-927 Solutions for energy saving within UTRA Node B</title>
<author initials="NA" surname="NA">
<organization>3GPP</organization>
</author>
<date year="2011" />
</front>
</reference>	
==

Any ideas?

Russ

-- 
<><
riwhite@verisign.com
russw@riw.us

From julian.reschke@gmx.de  Thu Jul  5 06:38:58 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C50BC21F85CE for <xml2rfc@ietfa.amsl.com>; Thu,  5 Jul 2012 06:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.766
X-Spam-Level: 
X-Spam-Status: No, score=-104.766 tagged_above=-999 required=5 tests=[AWL=-2.167, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2wXQdn--ZO+s for <xml2rfc@ietfa.amsl.com>; Thu,  5 Jul 2012 06:38:58 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 9AC1121F85C9 for <xml2rfc@ietf.org>; Thu,  5 Jul 2012 06:38:57 -0700 (PDT)
Received: (qmail invoked by alias); 05 Jul 2012 13:39:09 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp035) with SMTP; 05 Jul 2012 15:39:09 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+M694NwB6Mv+2r13tTHkZQqrbNDis48S67u8raDe 64pbUuiKoEHW0O
Message-ID: <4FF598F6.4080708@gmx.de>
Date: Thu, 05 Jul 2012 15:39:02 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Russ White <russw@riw.us>
References: <4FF591B2.1050100@riw.us>
In-Reply-To: <4FF591B2.1050100@riw.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Question on Reference Error
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2012 13:38:58 -0000

On 2012-07-05 15:08, Russ White wrote:
>
> What does this mean, and how do I fix it?
>
> ==
> [Error] INPUT:82:923: Attribute value "3GPP" of type IDREF must be an
> NCName when namespaces are enabled.
> [Error] INPUT:309:90: Attribute value "3GPP" of type ID must be an
> NCName when namespaces are enabled.
> ==
>
> This is the reference...
>
> ==
> <reference anchor="3GPP"
> target='http://3gpp.org/ftp/Specs/html-info/25927.htm'>
> <front>
> <title>3GPP TR 25-927 Solutions for energy saving within UTRA Node B</title>
> <author initials="NA" surname="NA">
> <organization>3GPP</organization>
> </author>
> <date year="2011" />
> </front>
> </reference>	
> ==
>
> Any ideas?

The anchor element is an XML identifier, and those can not start with 
digits.

Best regards, Julian

From jnc@mercury.lcs.mit.edu  Fri Jul  6 11:56:41 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 486E111E80A5 for <xml2rfc@ietfa.amsl.com>; Fri,  6 Jul 2012 11:56:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.079
X-Spam-Level: 
X-Spam-Status: No, score=-5.079 tagged_above=-999 required=5 tests=[AWL=-0.894, BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w+ahqMZhpXxR for <xml2rfc@ietfa.amsl.com>; Fri,  6 Jul 2012 11:56:40 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id BCB9111E8079 for <xml2rfc@ietf.org>; Fri,  6 Jul 2012 11:56:40 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 7CEFF18C110; Fri,  6 Jul 2012 14:56:56 -0400 (EDT)
To: xml2rfc@ietf.org
Message-Id: <20120706185656.7CEFF18C110@mercury.lcs.mit.edu>
Date: Fri,  6 Jul 2012 14:56:56 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
Subject: [xml2rfc] xref inside cref
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jul 2012 18:56:41 -0000

It's very mildly unfortunate that cross section references (xref) inside a
cref don't work - not a big deal, one can always write it out the target
section name.

     Noel

From julian.reschke@gmx.de  Fri Jul  6 12:09:50 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E609E11E80AD for <xml2rfc@ietfa.amsl.com>; Fri,  6 Jul 2012 12:09:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.066
X-Spam-Level: 
X-Spam-Status: No, score=-105.066 tagged_above=-999 required=5 tests=[AWL=-2.467, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MiWL9qDzX5PX for <xml2rfc@ietfa.amsl.com>; Fri,  6 Jul 2012 12:09:50 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id E7E9E11E809F for <xml2rfc@ietf.org>; Fri,  6 Jul 2012 12:09:49 -0700 (PDT)
Received: (qmail invoked by alias); 06 Jul 2012 19:10:05 -0000
Received: from p5DD96F2D.dip.t-dialin.net (EHLO [192.168.178.36]) [93.217.111.45] by mail.gmx.net (mp010) with SMTP; 06 Jul 2012 21:10:05 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19RzFhmEFVRnOZAY1J6pAV841dq6oe/RGl8Q3Bu0B v2KVXqIWldZe46
Message-ID: <4FF73805.4000302@gmx.de>
Date: Fri, 06 Jul 2012 21:09:57 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20120706185656.7CEFF18C110@mercury.lcs.mit.edu>
In-Reply-To: <20120706185656.7CEFF18C110@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] xref inside cref
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jul 2012 19:09:51 -0000

On 2012-07-06 20:56, Noel Chiappa wrote:
> It's very mildly unfortunate that cross section references (xref) inside a
> cref don't work - not a big deal, one can always write it out the target
> section name.
> ...

Indeed. You can run cleanup-for-DTD.xslt (contained in rfc2629.xslt) as 
a pre-processor, then you can.

Best regards, Julian

From rgm@htt-consult.com  Mon Jul  9 09:43:40 2012
Return-Path: <rgm@htt-consult.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4D3211E8146 for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 09:43:40 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Uh8hmfio1hA for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 09:43:40 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by ietfa.amsl.com (Postfix) with ESMTP id F0F3811E8137 for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 09:43:39 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 9A10C62A82 for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 16:43:41 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KkmW18f775Au for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 12:43:26 -0400 (EDT)
Received: from lx120e.htt-consult.com (157.67.83.208.client.htt-consult.com [208.83.67.157]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id A2C4062A68 for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 12:43:26 -0400 (EDT)
Message-ID: <4FFB0A2E.8030108@htt-consult.com>
Date: Mon, 09 Jul 2012 12:43:26 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: xml2rfc@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [xml2rfc] Trying to switch to strick checking, and problems with referenced file
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 16:43:41 -0000

I am to switch to strick checking via http://xml.resource.org/index.html 
and got the following error:

[Fatal Error] INPUT:45:4: The markup declarations contained or pointed 
to by the document type declaration must be well-formed.

That means, line 45, correct?  Well it is:

<!ENTITY RFC5702 SYSTEM 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5702.xml" >

BTW, line 44 is:

<!-<!ENTITY RFC5639 SYSTEM 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" > 
brainpool ECC -->

I deleted line 44 and got past that error, so how SHOULD I comment out 
line 44?





From tom.taylor.stds@gmail.com  Mon Jul  9 09:51:16 2012
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78CCB21F86DD for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 09:51:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O1mnJbqZ0wSi for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 09:51:15 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id CF0BE21F86DC for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 09:51:14 -0700 (PDT)
Received: by bkty7 with SMTP id y7so2937050bkt.31 for <xml2rfc@ietf.org>; Mon, 09 Jul 2012 09:51:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-antivirus:x-antivirus-status; bh=6yWqnrre7/fZkWkKKP/xA+y1FOVZMFok8/4TLK4/4hs=; b=svpSEjLx3xmjzh3YAcLQOdWbMBHt1gBL8YqykpF6Aq+pFpFktoYBczRJzmeKsUL+tr RFolQ5GoRDogFh6IHWbzcdAzW5EG8AwxnJBvrhmA+2y+6LaYP0qg8/SEKPw7KPvL2AfD paZkDJy9LhkiPZ2pvY9rzPPy5sZnGQpago29yb4wY7EZRWNu1z2wYgapilGgapf6bM1j 8A2OAWIZ6MG8xr+/oJ8m/SjTc5i/SZCkRY9ATPX9KTKqXgsTOsWdd2MZdiStuxHBBlYC tPexd24oPy9KXuRAy8IJtPyswyyiY1UXZjulHz13RhDw4nx6yqfOuBBYr9S6JTwjkgga MKew==
Received: by 10.204.136.215 with SMTP id s23mr19868999bkt.32.1341852699403; Mon, 09 Jul 2012 09:51:39 -0700 (PDT)
Received: from [127.0.0.1] ([207.112.101.80]) by mx.google.com with ESMTPS id e20sm26730122bkv.10.2012.07.09.09.51.38 (version=SSLv3 cipher=OTHER); Mon, 09 Jul 2012 09:51:38 -0700 (PDT)
Message-ID: <4FFB0C06.4050000@gmail.com>
Date: Mon, 09 Jul 2012 12:51:18 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Robert Moskowitz <rgm@htt-consult.com>
References: <4FFB0A2E.8030108@htt-consult.com>
In-Reply-To: <4FFB0A2E.8030108@htt-consult.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120709-0, 09/07/2012), Outbound message
X-Antivirus-Status: Clean
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Trying to switch to strick checking, and problems with referenced file
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 16:51:16 -0000

How about just <-- RFC5639 --> ?

On 09/07/2012 12:43 PM, Robert Moskowitz wrote:
> I am to switch to strick checking via http://xml.resource.org/index.html
> and got the following error:
>
> [Fatal Error] INPUT:45:4: The markup declarations contained or pointed
> to by the document type declaration must be well-formed.
>
> That means, line 45, correct?  Well it is:
>
> <!ENTITY RFC5702 SYSTEM
> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5702.xml" >
>
> BTW, line 44 is:
>
> <!-<!ENTITY RFC5639 SYSTEM
> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" >
> brainpool ECC -->
>
> I deleted line 44 and got past that error, so how SHOULD I comment out
> line 44?
>
>
>
>
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
>


From rgm@htt-consult.com  Mon Jul  9 09:51:17 2012
Return-Path: <rgm@htt-consult.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A187A21F86DD for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 09:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_24=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DAWlCCOU7SIW for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 09:51:17 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by ietfa.amsl.com (Postfix) with ESMTP id 0BCD321F86DC for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 09:51:17 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 2D38362A82 for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 16:51:21 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EcrX8UVgS7ck for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 12:51:11 -0400 (EDT)
Received: from lx120e.htt-consult.com (157.67.83.208.client.htt-consult.com [208.83.67.157]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id 1FD6C62A68 for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 12:51:11 -0400 (EDT)
Message-ID: <4FFB0BFE.5060400@htt-consult.com>
Date: Mon, 09 Jul 2012 12:51:10 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: xml2rfc@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [xml2rfc] NCName?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 16:51:18 -0000

More progress in implementing Strict checking.  I have the following errors:

[Error] INPUT:749:36: Attribute value "fig:bex-simple" of type IDREF must be an NCName when namespaces are enabled.
[Error] INPUT:755:40: Attribute value "fig:bex-simple" of type ID must be an NCName when namespaces are enabled.
[Error] INPUT:1971:63: Attribute value "fig:states" of type IDREF must be an NCName when namespaces are enabled.
[Error] INPUT:1976:38: Attribute value "fig:states" of type ID must be an NCName when namespaces are enabled.


What is an NCName?  for the first error the line in question is:

          The base exchange is illustrated below in<xref
          target="fig:bex-simple" />.  The term "key"

Further down is:

        <figure anchor="fig:bex-simple">


And finally, what does:

[Error] INPUT:2475:10: The content of element type "t" must match "(list|figure|xref|eref|iref|cref|spanx|vspace)".


mean?  Lines are:

      <t>
        The process for defining new parameters is described in<xref
        target="newparameter"/>  of this document.
      </t>




From tom.taylor.stds@gmail.com  Mon Jul  9 09:52:17 2012
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D13FE21F87D3 for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 09:52:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yGhbGhsI1XLH for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 09:52:16 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7448E21F87C4 for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 09:52:16 -0700 (PDT)
Received: by bkty7 with SMTP id y7so2937958bkt.31 for <xml2rfc@ietf.org>; Mon, 09 Jul 2012 09:52:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-antivirus:x-antivirus-status; bh=HbRTDpdrbIw0H/WVUUzOPCTP85NTK28PlXim1LnFOIY=; b=UEPUWDkUWADAGjoe+WyBkRrKvRvP0SPKKWB2fLt/mBxpgwQWtgiHUuNbdxxeyOMBNa 2Qu05Cqz7X9Fl/80FSvp1i5ZsHpkOWwLsigba/684ZY/xrHGvkIFgrN23KJytJ/lcp6P akrmaaG7CKZimhbuv/QTN/yvsvrDOJtDih9GcV6h8mK7iXEPik5RHeSAc+Haeie4gSJS VdhXCvgPvHCIdLb4SK8LoMWDX/+90xchwOlKOeFkOvHtzEgrFyM1iYNrRL1U/KG52CyM 8NZQFQcPwaYJlUAR+SLtYgFKCEh7pi/x6TCqVqLVGd7GlaRKA1AE0+i63kx1Ibt/KdLl Q10g==
Received: by 10.204.128.196 with SMTP id l4mr5566921bks.21.1341852761097; Mon, 09 Jul 2012 09:52:41 -0700 (PDT)
Received: from [127.0.0.1] ([207.112.101.80]) by mx.google.com with ESMTPS id n5sm26723322bkv.14.2012.07.09.09.52.38 (version=SSLv3 cipher=OTHER); Mon, 09 Jul 2012 09:52:40 -0700 (PDT)
Message-ID: <4FFB0C56.4040808@gmail.com>
Date: Mon, 09 Jul 2012 12:52:38 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Robert Moskowitz <rgm@htt-consult.com>
References: <4FFB0A2E.8030108@htt-consult.com> <4FFB0C06.4050000@gmail.com>
In-Reply-To: <4FFB0C06.4050000@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120709-0, 09/07/2012), Outbound message
X-Antivirus-Status: Clean
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Trying to switch to strick checking, and problems with referenced file
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 16:52:18 -0000

Oops, I mean <!-- RFC5639 -->

On 09/07/2012 12:51 PM, Tom Taylor wrote:
> How about just <-- RFC5639 --> ?
>
> On 09/07/2012 12:43 PM, Robert Moskowitz wrote:
>> I am to switch to strick checking via http://xml.resource.org/index.html
>> and got the following error:
>>
>> [Fatal Error] INPUT:45:4: The markup declarations contained or pointed
>> to by the document type declaration must be well-formed.
>>
>> That means, line 45, correct?  Well it is:
>>
>> <!ENTITY RFC5702 SYSTEM
>> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5702.xml" >
>>
>> BTW, line 44 is:
>>
>> <!-<!ENTITY RFC5639 SYSTEM
>> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" >
>> brainpool ECC -->
>>
>> I deleted line 44 and got past that error, so how SHOULD I comment out
>> line 44?
>>
>>
>>
>>
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>
>


From julian.reschke@gmx.de  Mon Jul  9 09:56:26 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3957B21F882C for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 09:56:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.595
X-Spam-Level: 
X-Spam-Status: No, score=-104.595 tagged_above=-999 required=5 tests=[AWL=-1.996, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xxEMeUuxrKGO for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 09:56:25 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 033CD21F882B for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 09:56:24 -0700 (PDT)
Received: (qmail invoked by alias); 09 Jul 2012 16:56:49 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp037) with SMTP; 09 Jul 2012 18:56:49 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/ZZZwZJA7ZkW5VRuKAuFOADOK33I38j+vqMbfmDd qmO77AZfXeywD5
Message-ID: <4FFB0D4D.4080900@gmx.de>
Date: Mon, 09 Jul 2012 18:56:45 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Robert Moskowitz <rgm@htt-consult.com>
References: <4FFB0A2E.8030108@htt-consult.com>
In-Reply-To: <4FFB0A2E.8030108@htt-consult.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Trying to switch to strick checking, and problems with referenced file
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 16:56:26 -0000

On 2012-07-09 18:43, Robert Moskowitz wrote:
> I am to switch to strick checking via http://xml.resource.org/index.html
> and got the following error:
>
> [Fatal Error] INPUT:45:4: The markup declarations contained or pointed
> to by the document type declaration must be well-formed.
>
> That means, line 45, correct?  Well it is:
>
> <!ENTITY RFC5702 SYSTEM
> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5702.xml" >
>
> BTW, line 44 is:
>
> <!-<!ENTITY RFC5639 SYSTEM
> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" >
> brainpool ECC -->
>
> I deleted line 44 and got past that error, so how SHOULD I comment out
> line 44?

By commenting out properly:

<!-- <!ENTITY RFC5639 SYSTEM 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" > 
brainpool ECC -->


Best regards, Julian

From julian.reschke@gmx.de  Mon Jul  9 09:59:09 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1967411E80EA for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 09:59:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.249
X-Spam-Level: 
X-Spam-Status: No, score=-104.249 tagged_above=-999 required=5 tests=[AWL=-2.250, BAYES_00=-2.599, J_CHICKENPOX_24=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2yKt8w+x+LLD for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 09:59:08 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 2FF0211E80E8 for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 09:59:08 -0700 (PDT)
Received: (qmail invoked by alias); 09 Jul 2012 16:59:32 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp040) with SMTP; 09 Jul 2012 18:59:32 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/ohdItYzXoYQwAiEgria6zwKwic1TasmL/Vq1mI+ UuKOH2au0iHBIF
Message-ID: <4FFB0DF1.5000508@gmx.de>
Date: Mon, 09 Jul 2012 18:59:29 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Robert Moskowitz <rgm@htt-consult.com>
References: <4FFB0BFE.5060400@htt-consult.com>
In-Reply-To: <4FFB0BFE.5060400@htt-consult.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] NCName?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 16:59:09 -0000

On 2012-07-09 18:51, Robert Moskowitz wrote:
> More progress in implementing Strict checking.  I have the following
> errors:
>
> [Error] INPUT:749:36: Attribute value "fig:bex-simple" of type IDREF
> must be an NCName when namespaces are enabled.
> [Error] INPUT:755:40: Attribute value "fig:bex-simple" of type ID must
> be an NCName when namespaces are enabled.
> [Error] INPUT:1971:63: Attribute value "fig:states" of type IDREF must
> be an NCName when namespaces are enabled.
> [Error] INPUT:1976:38: Attribute value "fig:states" of type ID must be
> an NCName when namespaces are enabled.
>
>
> What is an NCName?  for the first error the line in question is:

<http://www.w3.org/TR/REC-xml-names/#NT-NCName>:

'An XML Name, minus the ":"'

>           The base exchange is illustrated below in<xref
>           target="fig:bex-simple" />.  The term "key"
>
> Further down is:
>
>         <figure anchor="fig:bex-simple">
>
>
> And finally, what does:
>
> [Error] INPUT:2475:10: The content of element type "t" must match
> "(list|figure|xref|eref|iref|cref|spanx|vspace)".
>
>
> mean?  Lines are:
>
>       <t>
>         The process for defining new parameters is described in<xref
>         target="newparameter"/>  of this document.
>       </t>

That looks ok to me; the problem is likely somewhere else.

(feel free to send me the complete document in private mail for checking)

Best regards, Julian


From rgm@htt-consult.com  Mon Jul  9 10:08:16 2012
Return-Path: <rgm@htt-consult.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 248B811E80FE for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 10:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xCENgpGXMJ95 for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 10:08:15 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by ietfa.amsl.com (Postfix) with ESMTP id 45D4C11E80E8 for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 10:08:15 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 63C7462ABA; Mon,  9 Jul 2012 17:08:19 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wt3jk3Zle97c; Mon,  9 Jul 2012 13:08:03 -0400 (EDT)
Received: from lx120e.htt-consult.com (157.67.83.208.client.htt-consult.com [208.83.67.157]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id C68D862A82; Mon,  9 Jul 2012 13:08:03 -0400 (EDT)
Message-ID: <4FFB0FF3.1020802@htt-consult.com>
Date: Mon, 09 Jul 2012 13:08:03 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Tom Taylor <tom.taylor.stds@gmail.com>
References: <4FFB0A2E.8030108@htt-consult.com> <4FFB0C06.4050000@gmail.com> <4FFB0C56.4040808@gmail.com>
In-Reply-To: <4FFB0C56.4040808@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Trying to switch to strick checking, and problems with referenced file
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 17:08:16 -0000

On 07/09/2012 12:52 PM, Tom Taylor wrote:
> Oops, I mean <!-- RFC5639 -->

Just in case for some reason we add the reference back in, I guess.  
When it was decided to take the RFC out as a referenced it just seemed 
easier to turn it into a comment but leave the full line in.

BTW, I had an error with:

<!--<!ENTITY RFC5639 SYSTEM 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" > 
brainpool ECC -->

but not with:

<!-<!ENTITY RFC5639 SYSTEM 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" > 
brainpool ECC -->

Something about not liking -- in the comment (but I only had to change 
the first one, not the second).


>
> On 09/07/2012 12:51 PM, Tom Taylor wrote:
>> How about just <-- RFC5639 --> ?
>>
>> On 09/07/2012 12:43 PM, Robert Moskowitz wrote:
>>> I am to switch to strick checking via 
>>> http://xml.resource.org/index.html
>>> and got the following error:
>>>
>>> [Fatal Error] INPUT:45:4: The markup declarations contained or pointed
>>> to by the document type declaration must be well-formed.
>>>
>>> That means, line 45, correct?  Well it is:
>>>
>>> <!ENTITY RFC5702 SYSTEM
>>> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5702.xml" >
>>>
>>> BTW, line 44 is:
>>>
>>> <!-<!ENTITY RFC5639 SYSTEM
>>> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" >
>>> brainpool ECC -->
>>>
>>> I deleted line 44 and got past that error, so how SHOULD I comment out
>>> line 44?
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> xml2rfc mailing list
>>> xml2rfc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>>
>>
>
>

From rgm@htt-consult.com  Mon Jul  9 10:12:07 2012
Return-Path: <rgm@htt-consult.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4536811E8137 for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 10:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YXeqODVLSEuB for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 10:12:06 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9A411E8122 for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 10:12:06 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 8648062ABA; Mon,  9 Jul 2012 17:12:10 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hTk3-ncHOsvY; Mon,  9 Jul 2012 13:12:00 -0400 (EDT)
Received: from lx120e.htt-consult.com (157.67.83.208.client.htt-consult.com [208.83.67.157]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id 3CEC862A82; Mon,  9 Jul 2012 13:12:00 -0400 (EDT)
Message-ID: <4FFB10DF.9030809@htt-consult.com>
Date: Mon, 09 Jul 2012 13:11:59 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <4FFB0A2E.8030108@htt-consult.com> <4FFB0D4D.4080900@gmx.de>
In-Reply-To: <4FFB0D4D.4080900@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Trying to switch to strick checking, and problems with referenced file
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 17:12:07 -0000

On 07/09/2012 12:56 PM, Julian Reschke wrote:
> On 2012-07-09 18:43, Robert Moskowitz wrote:
>> I am to switch to strick checking via http://xml.resource.org/index.html
>> and got the following error:
>>
>> [Fatal Error] INPUT:45:4: The markup declarations contained or pointed
>> to by the document type declaration must be well-formed.
>>
>> That means, line 45, correct?  Well it is:
>>
>> <!ENTITY RFC5702 SYSTEM
>> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5702.xml" >
>>
>> BTW, line 44 is:
>>
>> <!-<!ENTITY RFC5639 SYSTEM
>> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" >
>> brainpool ECC -->
>>
>> I deleted line 44 and got past that error, so how SHOULD I comment out
>> line 44?
>
> By commenting out properly:
>
> <!-- <!ENTITY RFC5639 SYSTEM 
> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" > 
> brainpool ECC -->

That gets the error:

[Fatal Error] INPUT:45:10: The string "--" is not permitted within comments.






From julian.reschke@gmx.de  Mon Jul  9 10:22:49 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19D2511E8170 for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 10:22:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.498
X-Spam-Level: 
X-Spam-Status: No, score=-104.498 tagged_above=-999 required=5 tests=[AWL=-1.899, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b6mZj5gj8RPe for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 10:22:48 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 4E39A11E816C for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 10:22:43 -0700 (PDT)
Received: (qmail invoked by alias); 09 Jul 2012 17:23:07 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp037) with SMTP; 09 Jul 2012 19:23:07 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/mlIUf1kHmmCmCYs3rXQNjj8qlQI16167HFa++Wc PhgVgutyWFWrYu
Message-ID: <4FFB1378.9000800@gmx.de>
Date: Mon, 09 Jul 2012 19:23:04 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Robert Moskowitz <rgm@htt-consult.com>
References: <4FFB0A2E.8030108@htt-consult.com> <4FFB0D4D.4080900@gmx.de> <4FFB10DF.9030809@htt-consult.com>
In-Reply-To: <4FFB10DF.9030809@htt-consult.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Trying to switch to strick checking, and problems with referenced file
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 17:22:49 -0000

On 2012-07-09 19:11, Robert Moskowitz wrote:
>> By commenting out properly:
>>
>> <!-- <!ENTITY RFC5639 SYSTEM
>> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" >
>> brainpool ECC -->
>
> That gets the error:
>
> [Fatal Error] INPUT:45:10: The string "--" is not permitted within
> comments.

That appears to be a bug in xml2rfc.tcl, then.

(It's correct that you can't have "--" inside the comment, but in this 
case it's not "inside")

-> http://trac.tools.ietf.org/tools/xml2rfc/trac/

From rgm@htt-consult.com  Mon Jul  9 10:53:21 2012
Return-Path: <rgm@htt-consult.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A25F11E8106 for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 10:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZwRaOkR4GuG for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 10:53:20 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by ietfa.amsl.com (Postfix) with ESMTP id 1613411E80C8 for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 10:53:20 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 0C53362A6F; Mon,  9 Jul 2012 17:53:24 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bUQFtoijDGni; Mon,  9 Jul 2012 13:53:07 -0400 (EDT)
Received: from lx120e.htt-consult.com (157.67.83.208.client.htt-consult.com [208.83.67.157]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id 9F98162820; Mon,  9 Jul 2012 13:53:07 -0400 (EDT)
Message-ID: <4FFB1A83.4030701@htt-consult.com>
Date: Mon, 09 Jul 2012 13:53:07 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <4FFB0A2E.8030108@htt-consult.com> <4FFB0D4D.4080900@gmx.de> <4FFB10DF.9030809@htt-consult.com> <4FFB1378.9000800@gmx.de>
In-Reply-To: <4FFB1378.9000800@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Trying to switch to strick checking, and problems with referenced file
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 17:53:21 -0000

On 07/09/2012 01:23 PM, Julian Reschke wrote:
> On 2012-07-09 19:11, Robert Moskowitz wrote:
>>> By commenting out properly:
>>>
>>> <!-- <!ENTITY RFC5639 SYSTEM
>>> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" >
>>> brainpool ECC -->
>>
>> That gets the error:
>>
>> [Fatal Error] INPUT:45:10: The string "--" is not permitted within
>> comments.
>
> That appears to be a bug in xml2rfc.tcl, then.

So you will fix this?

>
> (It's correct that you can't have "--" inside the comment, but in this 
> case it's not "inside")
>
> -> http://trac.tools.ietf.org/tools/xml2rfc/trac/

Um, why did you include this URL?  It just leads to:

Welcome to the xml2rfc working space



From julian.reschke@gmx.de  Mon Jul  9 11:00:47 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBBAA21F885D for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 11:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.456
X-Spam-Level: 
X-Spam-Status: No, score=-104.456 tagged_above=-999 required=5 tests=[AWL=-1.857, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3EPOMrTDbxeH for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 11:00:47 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 8F04921F8859 for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 11:00:46 -0700 (PDT)
Received: (qmail invoked by alias); 09 Jul 2012 18:01:10 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp072) with SMTP; 09 Jul 2012 20:01:10 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1848mVX/SM4ep//C2XWFjNst3aukCTf97osoJGjnj /uwBoka1GNZkTE
Message-ID: <4FFB1C61.5050501@gmx.de>
Date: Mon, 09 Jul 2012 20:01:05 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Robert Moskowitz <rgm@htt-consult.com>
References: <4FFB0A2E.8030108@htt-consult.com> <4FFB0D4D.4080900@gmx.de> <4FFB10DF.9030809@htt-consult.com> <4FFB1378.9000800@gmx.de> <4FFB1A83.4030701@htt-consult.com>
In-Reply-To: <4FFB1A83.4030701@htt-consult.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Trying to switch to strick checking, and problems with referenced file
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 18:00:47 -0000

On 2012-07-09 19:53, Robert Moskowitz wrote:
> On 07/09/2012 01:23 PM, Julian Reschke wrote:
>> On 2012-07-09 19:11, Robert Moskowitz wrote:
>>>> By commenting out properly:
>>>>
>>>> <!-- <!ENTITY RFC5639 SYSTEM
>>>> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" >
>>>> brainpool ECC -->
>>>
>>> That gets the error:
>>>
>>> [Fatal Error] INPUT:45:10: The string "--" is not permitted within
>>> comments.
>>
>> That appears to be a bug in xml2rfc.tcl, then.
>
> So you will fix this?

I'm not planning to. Reminder: xml2rfc.tcl is written in TCL and uses a 
custom SGML parser. It's a maintenance nightmare.

>> (It's correct that you can't have "--" inside the comment, but in this
>> case it's not "inside")
>>
>> -> http://trac.tools.ietf.org/tools/xml2rfc/trac/
>
> Um, why did you include this URL?  It just leads to:
>
> Welcome to the xml2rfc working space

It's the issue tracker where you can report problems against the 
implementation.

Best regards, Julian


From rgm@htt-consult.com  Mon Jul  9 11:25:09 2012
Return-Path: <rgm@htt-consult.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D02621F87BE for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 11:25:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GU2lnnAnsf4i for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 11:25:08 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by ietfa.amsl.com (Postfix) with ESMTP id C684021F85AA for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 11:25:08 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id F25DD62A6F; Mon,  9 Jul 2012 18:25:12 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B3m82pyf+YYT; Mon,  9 Jul 2012 14:24:53 -0400 (EDT)
Received: from lx120e.htt-consult.com (157.67.83.208.client.htt-consult.com [208.83.67.157]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id B7CD662AB0; Mon,  9 Jul 2012 14:24:53 -0400 (EDT)
Message-ID: <4FFB21F5.2040601@htt-consult.com>
Date: Mon, 09 Jul 2012 14:24:53 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <4FFB0A2E.8030108@htt-consult.com> <4FFB0D4D.4080900@gmx.de> <4FFB10DF.9030809@htt-consult.com> <4FFB1378.9000800@gmx.de> <4FFB1A83.4030701@htt-consult.com> <4FFB1C61.5050501@gmx.de>
In-Reply-To: <4FFB1C61.5050501@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Trying to switch to strick checking, and problems with referenced file
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 18:25:09 -0000

On 07/09/2012 02:01 PM, Julian Reschke wrote:
> On 2012-07-09 19:53, Robert Moskowitz wrote:
>> On 07/09/2012 01:23 PM, Julian Reschke wrote:
>>> On 2012-07-09 19:11, Robert Moskowitz wrote:
>>>>> By commenting out properly:
>>>>>
>>>>> <!-- <!ENTITY RFC5639 SYSTEM
>>>>> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5639.xml" >
>>>>> brainpool ECC -->
>>>>
>>>> That gets the error:
>>>>
>>>> [Fatal Error] INPUT:45:10: The string "--" is not permitted within
>>>> comments.
>>>
>>> That appears to be a bug in xml2rfc.tcl, then.
>>
>> So you will fix this?
>
> I'm not planning to. Reminder: xml2rfc.tcl is written in TCL and uses 
> a custom SGML parser. It's a maintenance nightmare.

I did TCL once upon a time, like '94 on a Telebit NetBlazer.  Fun 
stuff.  Not.

>
>>> (It's correct that you can't have "--" inside the comment, but in this
>>> case it's not "inside")
>>>
>>> -> http://trac.tools.ietf.org/tools/xml2rfc/trac/
>>
>> Um, why did you include this URL?  It just leads to:
>>
>> Welcome to the xml2rfc working space
>
> It's the issue tracker where you can report problems against the 
> implementation.

OK.  Will get around to figuring it out.



From dworley@avaya.com  Mon Jul  9 14:36:26 2012
Return-Path: <dworley@avaya.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1303511E8083 for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 14:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.85
X-Spam-Level: 
X-Spam-Status: No, score=-102.85 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, J_CHICKENPOX_24=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13FUAF8KuyJW for <xml2rfc@ietfa.amsl.com>; Mon,  9 Jul 2012 14:36:25 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 8A65911E8072 for <xml2rfc@ietf.org>; Mon,  9 Jul 2012 14:36:25 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAARN+0/GmAcF/2dsb2JhbABFhWaweYEdgQeCIAEBAQEDEhERRRACAQgNCwICJgICAjAVEAEBBA4NGodrnnqKHpMfgSCPGjJgA5suig2Cew
X-IronPort-AV: E=Sophos;i="4.77,555,1336363200"; d="scan'208";a="356636341"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 09 Jul 2012 17:33:31 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 09 Jul 2012 17:33:39 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Mon, 9 Jul 2012 17:36:49 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "rgm@htt-consult.com" <rgm@htt-consult.com>
Date: Mon, 9 Jul 2012 17:36:47 -0400
Thread-Topic: [xml2rfc] NCName?
Thread-Index: Ac1eGvEpP7fZUqh+RfavlfDH4xOOOQ==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A1D45@DC-US1MBEX4.global.avaya.com>
References: <4FFB0BFE.5060400@htt-consult.com>
In-Reply-To: <4FFB0BFE.5060400@htt-consult.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] NCName?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 21:36:26 -0000

T24gTW9uLCAyMDEyLTA3LTA5IGF0IDEyOjUxIC0wNDAwLCBSb2JlcnQgTW9za293aXR6IHdyb3Rl
Ogo+IEFuZCBmaW5hbGx5LCB3aGF0IGRvZXM6Cj4gCj4gW0Vycm9yXSBJTlBVVDoyNDc1OjEwOiBU
aGUgY29udGVudCBvZiBlbGVtZW50IHR5cGUgInQiIG11c3QgbWF0Y2ggIihsaXN0fGZpZ3VyZXx4
cmVmfGVyZWZ8aXJlZnxjcmVmfHNwYW54fHZzcGFjZSkiLgo+IAo+IAo+IG1lYW4/ICBMaW5lcyBh
cmU6Cj4gCj4gICAgICAgPHQ+Cj4gICAgICAgICBUaGUgcHJvY2VzcyBmb3IgZGVmaW5pbmcgbmV3
IHBhcmFtZXRlcnMgaXMgZGVzY3JpYmVkIGluPHhyZWYKPiAgICAgICAgIHRhcmdldD0ibmV3cGFy
YW1ldGVyIi8+ICBvZiB0aGlzIGRvY3VtZW50Lgo+ICAgICAgIDwvdD4KClRoZSAiKGxpc3R8Zmln
dXJlfHhyZWZ8ZXJlZnxpcmVmfGNyZWZ8c3Bhbnh8dnNwYWNlKSIgcGFydCBpcyBhIHJlZ2V4cApk
ZXNjcmliaW5nIHdoYXQgY2FuIGFwcGVhciBpbnNpZGUgdGhlIDx0PiBlbGVtZW50LiAgSSdtIG5v
dCBjZXJ0YWluIG9mCnRoZSBzeW50YXggYW5kIHNlbWFudGljcyBvZiB0aGVzZSByZWdleHBzLCBi
dXQgdGhlIG5vdGF0aW9uIGlzIGZhaXJseQpjb252ZW50aW9uYWwuICBJIHN1c3BlY3QgdGhhdCB0
aGlzIHJlZ2V4cCBub3RhdGlvbiBpcyBkZXJpdmVkIGZyb20gYQpzaW1pbGFyIG5vdGF0aW9uIHVz
ZWQgaW4gRFREIGRlY2xhcmF0aW9ucyBvZiBwZXJtaXNzaWJsZSBlbGVtZW50CmNvbnRlbnQuICBJ
biB0aGlzIGNhc2UsIGl0IG1lYW5zIHRoYXQgPHQ+IGNhbiBjb250YWluIDxsaXN0PiwgPGZpZ3Vy
ZT4sCjx4cmVmPiwgZXRjLiAgSSdtIG5vdCBzdXJlIGhvdyB0aGUgc3ludGF4IHNwZWNpZmllcyB0
aGF0IGNoYXJhY3Rlcgpjb250ZW50IGlzIGFsbG93ZWQgKG9yIHdoZXRoZXIgdGhlIHN5bnRheCBz
cGVjaWZpZXMgd2hldGhlciBvciBub3QKY2hhcmFjdGVyIGNvbnRlbnQgaXMgYWxsb3dlZCkuCgpJ
biB5b3VyIGV4dHJhY3QsIG5vdGhpbmcgdXNlZnVsIGlzIHJldmVhbGVkOiAgdGhlIDx0PiBvbmx5
IGNvbnRhaW5zIGFuCjx4cmVmPiwgYW5kIHRoZSBtZXNzYWdlIHNheXMgdGhhdCBpcyB2YWxpZC4g
IFNvIEkgYW0gbGVmdCB0byBndWVzcyB0aGF0CnRoZSA8dD4gZWxlbWVudCB5b3Ugc2hvdyBpcyBp
bW1lZGlhdGVseSBjb250YWluZWQgaW4gKmFub3RoZXIqIDx0PgplbGVtZW50LCBhbmQgdGhlIG1l
c3NhZ2UgaXMgc2F5aW5nIHRoYXQgdGhlIDx0PiBhdCBsaW5lIDI0NzUgaXMgbm90CnZhbGlkIGNv
bnRlbnQgZm9yIHRoZSBvdXRlciA8dD4uCgpEYWxlCgo=

From subirdas21@gmail.com  Thu Jul 12 20:50:38 2012
Return-Path: <subirdas21@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D0AD11E80E5 for <xml2rfc@ietfa.amsl.com>; Thu, 12 Jul 2012 20:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KEH-LFuCW6+2 for <xml2rfc@ietfa.amsl.com>; Thu, 12 Jul 2012 20:50:37 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2C2F711E80DC for <xml2rfc@ietf.org>; Thu, 12 Jul 2012 20:50:36 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so4393910lbb.31 for <xml2rfc@ietf.org>; Thu, 12 Jul 2012 20:51:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=/bkiN/AXOqYzOmPPW27twIEoLhCp27wq7wkjig7uZBU=; b=loYHYpKF2AZR3YzdS04nE+w+AtGkMXjW+VmNScRpby79LbyZLNqb7bn2AZdblXW8Jp uneCnJNpkjcRuDowi7KC5xTdUXq1Z3DdJllT62qsjtgI4EnFtYJaVhnAvmXYPTQNJnph 6l8vc6WZFsxKBHWUcgYcUC1kgCtOunU7Kk6m7qRpVuBcW1yt2QSJNb6/F4IgDGuL1KT2 XAb/PQOoY5O7kDUj7vRmf5Fo3DiRkNhwogrv7LwyTjaUmU8yXL6mo/7bR1pkAKZ8Ux/D Vp6k+LEp7vE1YvXMgierRB2vJu8JWa2qGs9CMyuZDb/LPtJZJHE3WhhePlovrqxRbrQC 0NHA==
MIME-Version: 1.0
Received: by 10.112.83.228 with SMTP id t4mr2328939lby.74.1342151471338; Thu, 12 Jul 2012 20:51:11 -0700 (PDT)
Received: by 10.112.30.97 with HTTP; Thu, 12 Jul 2012 20:51:11 -0700 (PDT)
Date: Thu, 12 Jul 2012 23:51:11 -0400
Message-ID: <CAFb8J8o676=AkFTTGxGU0b1E-c9Akgt7ipZovsUAFaD6KeOaPA@mail.gmail.com>
From: Subir Das <subirdas21@gmail.com>
To: xml2rfc@ietf.org
Content-Type: multipart/alternative; boundary=f46d040167f5af14d204c4adfdb7
Subject: [xml2rfc] TOC problem
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 03:50:38 -0000

--f46d040167f5af14d204c4adfdb7
Content-Type: text/plain; charset=ISO-8859-1

I am using the follwoing options in my source and using the online tool for
conversion.

<?rfc iprnotified="yes"?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no"?>
<?rfc inline="no"?>

Getting the following toc representation instead of section title should
be referenced  to page numbers:


Table of Contents



   1.  Convention used in this document  . . . . . . . . . . . . . ancho

   2.  Terminology and abbreviations used in this document . . . . Termi

   3.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . ancho

Any help will be appreciated.


thanks,
-Subir

--f46d040167f5af14d204c4adfdb7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>I am using the follwoing options in my source and using the online too=
l for conversion.</div><div>=A0</div><div>&lt;?rfc iprnotified=3D&quot;yes&=
quot;?&gt; <br>&lt;?rfc toc=3D&quot;yes&quot; ?&gt;<br>&lt;?rfc symrefs=3D&=
quot;yes&quot; ?&gt;<br>
&lt;?rfc compact=3D&quot;yes&quot; ?&gt;<br>&lt;?rfc subcompact=3D&quot;no&=
quot;?&gt;<br>&lt;?rfc inline=3D&quot;no&quot;?&gt;</div><div>=A0</div><div=
>Getting the following toc representation instead of section title should b=
e=A0referenced =A0to page numbers:</div>
<div>=A0</div><div><font size=3D"3" face=3D"Times New Roman">

</font><p style=3D"margin:0in 0in 0pt" class=3D"MsoNormal"><span style=3D"f=
ont-family:&quot;Courier New&quot;;font-size:10pt">Table
of Contents</span></p><font size=3D"3" face=3D"Times New Roman">

</font><p style=3D"margin:0in 0in 0pt" class=3D"MsoNormal"><span style=3D"f=
ont-family:&quot;Courier New&quot;;font-size:10pt">=A0</span></p><font size=
=3D"3" face=3D"Times New Roman">

</font><p style=3D"margin:0in 0in 0pt" class=3D"MsoNormal"><span style=3D"f=
ont-family:&quot;Courier New&quot;;font-size:10pt">=A0=A0
1.=A0 Convention used in this document=A0 . . . . . . . . . . . . . ancho</=
span></p><font size=3D"3" face=3D"Times New Roman">

</font><p style=3D"margin:0in 0in 0pt" class=3D"MsoNormal"><span style=3D"f=
ont-family:&quot;Courier New&quot;;font-size:10pt">=A0=A0
2.=A0 Terminology and abbreviations used in this document . . . . Termi</sp=
an></p><font size=3D"3" face=3D"Times New Roman">

</font><p style=3D"margin:0in 0in 0pt" class=3D"MsoNormal"><span style=3D"f=
ont-family:&quot;Courier New&quot;;font-size:10pt">=A0=A0
3.=A0 Introduction=A0 . . . . . . . . . . . . . . . . . . . . . . . ancho</=
span></p><font size=3D"3" face=3D"Times New Roman">

</font></div><div>=A0</div><div>Any=A0help will be appreciated.</div><div>=
=A0</div><div>=A0</div><div>thanks,</div><div>-Subir </div><div>=A0</div><d=
iv>=A0</div>

--f46d040167f5af14d204c4adfdb7--

From julian.reschke@gmx.de  Fri Jul 13 00:36:03 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2AA221F875A for <xml2rfc@ietfa.amsl.com>; Fri, 13 Jul 2012 00:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.148
X-Spam-Level: 
X-Spam-Status: No, score=-105.148 tagged_above=-999 required=5 tests=[AWL=-2.549, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qv1Yc3IvH8Io for <xml2rfc@ietfa.amsl.com>; Fri, 13 Jul 2012 00:36:03 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id D44B921F86F7 for <xml2rfc@ietf.org>; Fri, 13 Jul 2012 00:36:02 -0700 (PDT)
Received: (qmail invoked by alias); 13 Jul 2012 07:36:37 -0000
Received: from p5DD96F43.dip.t-dialin.net (EHLO [192.168.178.36]) [93.217.111.67] by mail.gmx.net (mp071) with SMTP; 13 Jul 2012 09:36:37 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18WVrAiaOcWJl37IqxgnoHGtptJ2WNGfdtOz6D1oW 2NeZjh8W6Rg1d0
Message-ID: <4FFFD004.1010300@gmx.de>
Date: Fri, 13 Jul 2012 09:36:36 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Subir Das <subirdas21@gmail.com>
References: <CAFb8J8o676=AkFTTGxGU0b1E-c9Akgt7ipZovsUAFaD6KeOaPA@mail.gmail.com>
In-Reply-To: <CAFb8J8o676=AkFTTGxGU0b1E-c9Akgt7ipZovsUAFaD6KeOaPA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] TOC problem
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 07:36:04 -0000

On 2012-07-13 05:51, Subir Das wrote:
> I am using the follwoing options in my source and using the online tool
> for conversion.
> <?rfc iprnotified="yes"?>
> <?rfc toc="yes" ?>
> <?rfc symrefs="yes" ?>
> <?rfc compact="yes" ?>
> <?rfc subcompact="no"?>
> <?rfc inline="no"?>
> Getting the following toc representation instead of section title should
> be referenced  to page numbers:
>
> Table of Contents
>
> 1.  Convention used in this document  . . . . . . . . . . . . . ancho
>
> 2.  Terminology and abbreviations used in this document . . . . Termi
>
> 3.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . ancho
>
> Any help will be appreciated.
> thanks,
> -Subir
> ...

xml2rfc.tcl makes two passes, and what you see I think is the output of 
the first pass.

How do you run it? Do you see any error messages?

Best regards, Julian

From julian.reschke@gmx.de  Fri Jul 13 06:22:03 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3722F21F8853 for <xml2rfc@ietfa.amsl.com>; Fri, 13 Jul 2012 06:22:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.59
X-Spam-Level: 
X-Spam-Status: No, score=-104.59 tagged_above=-999 required=5 tests=[AWL=-1.991, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dumah6DYw1I5 for <xml2rfc@ietfa.amsl.com>; Fri, 13 Jul 2012 06:22:02 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 9D6CA21F8852 for <xml2rfc@ietf.org>; Fri, 13 Jul 2012 06:21:56 -0700 (PDT)
Received: (qmail invoked by alias); 13 Jul 2012 13:22:31 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp001) with SMTP; 13 Jul 2012 15:22:31 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+jf9kOInGj96ktrTxBtRgogvoSXJvamPbK4eREDA FNb6a3Sb3Drkf3
Message-ID: <50002115.3010506@gmx.de>
Date: Fri, 13 Jul 2012 15:22:29 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Subir Das <subirdas21@gmail.com>
References: <CAFb8J8o676=AkFTTGxGU0b1E-c9Akgt7ipZovsUAFaD6KeOaPA@mail.gmail.com> <4FFFD004.1010300@gmx.de>
In-Reply-To: <4FFFD004.1010300@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] TOC problem
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 13:22:03 -0000

On 2012-07-13 09:36, Julian Reschke wrote:
> On 2012-07-13 05:51, Subir Das wrote:
>> I am using the follwoing options in my source and using the online tool
>> for conversion.
>> <?rfc iprnotified="yes"?>
>> <?rfc toc="yes" ?>
>> <?rfc symrefs="yes" ?>
>> <?rfc compact="yes" ?>
>> <?rfc subcompact="no"?>
>> <?rfc inline="no"?>
>> Getting the following toc representation instead of section title should
>> be referenced  to page numbers:
>>
>> Table of Contents
>>
>> 1.  Convention used in this document  . . . . . . . . . . . . . ancho
>>
>> 2.  Terminology and abbreviations used in this document . . . . Termi
>>
>> 3.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . ancho
>>
>> Any help will be appreciated.
>> thanks,
>> -Subir
>> ...
>
> xml2rfc.tcl makes two passes, and what you see I think is the output of
> the first pass.
>
> How do you run it? Do you see any error messages?
> ...

Debugged off-list.

Lesson, once again: run your files through a proper XML parser first 
(for instance, by opening it in a browser).

Best regards, Julian


From rs@netapp.com  Mon Jul 16 01:39:38 2012
Return-Path: <rs@netapp.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4028221F85FC for <xml2rfc@ietfa.amsl.com>; Mon, 16 Jul 2012 01:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.252
X-Spam-Level: 
X-Spam-Status: No, score=-5.252 tagged_above=-999 required=5 tests=[AWL=-5.067, BAYES_40=-0.185, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k0YFV5OkVVz6 for <xml2rfc@ietfa.amsl.com>; Mon, 16 Jul 2012 01:39:37 -0700 (PDT)
Received: from cyclone.public.resource.org (cyclone.public.resource.org [192.101.98.135]) by ietfa.amsl.com (Postfix) with ESMTP id 1850621F85E5 for <xml2rfc@ietf.org>; Mon, 16 Jul 2012 01:39:37 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by cyclone.public.resource.org (8.14.4/8.14.4) with ESMTP id q6G8eFei010578 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for <xml2rfc@lists.xml.resource.org>; Mon, 16 Jul 2012 01:40:15 -0700 (PDT) (envelope-from rs@netapp.com)
X-IronPort-AV: E=Sophos;i="4.77,592,1336374000";  d="scan'208,217";a="666049462"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 16 Jul 2012 01:39:55 -0700
Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q6G8dsmx003829 for <xml2rfc@lists.xml.resource.org>; Mon, 16 Jul 2012 01:39:55 -0700 (PDT)
Received: from SACEXCMBX02-PRD.hq.netapp.com ([169.254.1.34]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.02.0298.004; Mon, 16 Jul 2012 01:39:54 -0700
From: "Scheffenegger, Richard" <rs@netapp.com>
To: "xml2rfc@lists.xml.resource.org" <xml2rfc@lists.xml.resource.org>
Thread-Topic: Pagination between References and Appendix
Thread-Index: Ac1jLe1H8bWohuONTMidHf4AyvbYdQ==
Date: Mon, 16 Jul 2012 08:39:53 +0000
Message-ID: <012C3117EDDB3C4781FD802A8C27DD4F0D4A87FF@SACEXCMBX02-PRD.hq.netapp.com>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: multipart/alternative; boundary="_000_012C3117EDDB3C4781FD802A8C27DD4F0D4A87FFSACEXCMBX02PRDh_"
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 16 Jul 2012 06:11:16 -0700
Subject: [xml2rfc] Pagination between References and Appendix
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 08:39:38 -0000

--_000_012C3117EDDB3C4781FD802A8C27DD4F0D4A87FFSACEXCMBX02PRDh_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

is there a way to start the Appendix section on a new page after the Refere=
nces?

Apparently, neither <?rfc needLines=3D"100" ?> nor <vspace /> will work in =
the references section, or when the appendix section...

Alternatively, is there any directive to have new 1st level sections always=
 start on a fresh page? (Not as nice if that would apply globally, but bett=
er than having <20 lines of the Appendix start below the references).

Richard Scheffenegger




--_000_012C3117EDDB3C4781FD802A8C27DD4F0D4A87FFSACEXCMBX02PRDh_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt;">
<div>Hi,</div>
<div>&nbsp;</div>
<div>is there a way to start the Appendix section on a new page after the R=
eferences?</div>
<div>&nbsp;</div>
<div>Apparently, neither &lt;?rfc needLines=3D&quot;100&quot; ?&gt; nor &lt=
;vspace /&gt; will work in the references section, or when the appendix sec=
tion&#8230;</div>
<div>&nbsp;</div>
<div>Alternatively, is there any directive to have new 1<font size=3D"1"><s=
pan style=3D"font-size:7.3pt;"><sup>st</sup></span></font> level sections a=
lways start on a fresh page? (Not as nice if that would apply globally, but=
 better than having &lt;20 lines of the
Appendix start below the references). </div>
<div>&nbsp;</div>
<div>Richard Scheffenegger<br>

<br>

</div>
<div>&nbsp;</div>
</span></font>
</body>
</html>

--_000_012C3117EDDB3C4781FD802A8C27DD4F0D4A87FFSACEXCMBX02PRDh_--

From arusso@amsl.com  Thu Jul 19 14:37:17 2012
Return-Path: <arusso@amsl.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD7C511E80F4 for <xml2rfc@ietfa.amsl.com>; Thu, 19 Jul 2012 14:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4-u61bJE3uwN for <xml2rfc@ietfa.amsl.com>; Thu, 19 Jul 2012 14:37:17 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id C48D911E80EC for <xml2rfc@ietf.org>; Thu, 19 Jul 2012 14:37:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 2506312C6EE; Thu, 19 Jul 2012 14:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WFu9jeEVQfH7; Thu, 19 Jul 2012 14:38:11 -0700 (PDT)
Received: from rfc2.home (pool-173-73-60-7.washdc.fios.verizon.net [173.73.60.7]) by c8a.amsl.com (Postfix) with ESMTPSA id 6076E12C6E8; Thu, 19 Jul 2012 14:38:10 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Alice Russo <arusso@amsl.com>
In-Reply-To: <4FF1D210.7020603@gmx.de>
Date: Thu, 19 Jul 2012 17:38:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F7C4B87-5D18-4B3D-A17F-848C996F1463@amsl.com>
References: <20120702162057.5849918C0B2@mercury.lcs.mit.edu> <4FF1CE62.9070401@gmx.de> <4FF1D210.7020603@gmx.de>
To: xml2rfc list <xml2rfc@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: Julian Reschke <julian.reschke@gmx.de>, RSE <rse@rfc-editor.org>
Subject: Re: [xml2rfc] initials handling
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 21:37:17 -0000

Below is a note from the RFC Series Editor regarding how an RFC author's =
name appears. I have amended ticket #10 (which Julian pointed to) on =
this topic.

Thanks,
Alice
RFC Production Center

-----

Traditionally, the RFC Series requests that authors names be presented
with "first name initial, last name".  There have been enough exceptions
over the years, however, to make this a rather fuzzy tradition.

What is most important to the Series is that authors names be consistent
over time and using standard capitalization.  If author feels 2 initials
distinguishes them, then we should allow it.  For the sake of the
readership, however, an author can't switch between H. Flanagan, H. L.
Flanagan, H.L. Flanagan, and so on.

So, what the RFC Editor would like to see out of xml2rfc is more
flexibility to allow for author preferences.  =46rom our side, we will =
be
documenting this more fully in the new version of the Style Guide, which
will be made available for comment shortly after IETF 84.  This will go
on the web page component of the Style Guide.

Please let me know if there are any questions!

-Heather Flanagan, RSE

On Jul 2, 2012, at 12:53 PM, Julian Reschke wrote:

> On 2012-07-02 18:37, Julian Reschke wrote:
>> ...
>>>     > I don't see anything wrong with the above (well, except for
>>> missing
>>>     > whitespace between "J." and "N.").
>>>=20
>>> When I tried that (I started with "J. N.", and also tried
>>> "J.&nbsp;N.", it
>>> truncated it to 'J. Chiappa' in the header page in the output. =
(Tries it
>>> again to make sure he wasn't dreaming.) Yup, truncates to "J.".
>>=20
>> Which version of xml2rfc are you trying?
>> ...
>=20
> In the meantime I recalled that this is =
<http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10>; so this is a =
RFC style requirement; If you don't like it you should bring it up on =
rfc-interest mailing list as well...
>=20
> Best regards, Julian
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
>=20


From julian.reschke@gmx.de  Fri Jul 20 00:15:19 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE1621F852B for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 00:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.047
X-Spam-Level: 
X-Spam-Status: No, score=-105.047 tagged_above=-999 required=5 tests=[AWL=-2.448, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X6ugXGo8D0FH for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 00:15:18 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 3FCF321F8522 for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 00:15:17 -0700 (PDT)
Received: (qmail invoked by alias); 20 Jul 2012 07:16:11 -0000
Received: from p54BB27D6.dip.t-dialin.net (EHLO [192.168.178.36]) [84.187.39.214] by mail.gmx.net (mp002) with SMTP; 20 Jul 2012 09:16:11 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/pXY1TFonpKahdyVgEd8hBOGf4jrzOeFBF0KPy/2 0Qrg+lraRIyKTI
Message-ID: <500905BA.1070003@gmx.de>
Date: Fri, 20 Jul 2012 09:16:10 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Alice Russo <arusso@amsl.com>
References: <20120702162057.5849918C0B2@mercury.lcs.mit.edu> <4FF1CE62.9070401@gmx.de> <4FF1D210.7020603@gmx.de> <7F7C4B87-5D18-4B3D-A17F-848C996F1463@amsl.com>
In-Reply-To: <7F7C4B87-5D18-4B3D-A17F-848C996F1463@amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc list <xml2rfc@ietf.org>, RSE <rse@rfc-editor.org>
Subject: Re: [xml2rfc] initials handling
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 07:15:19 -0000

On 2012-07-19 23:38, Alice Russo wrote:
> Below is a note from the RFC Series Editor regarding how an RFC author's name appears. I have amended ticket #10 (which Julian pointed to) on this topic.
>
> Thanks,
> Alice
> RFC Production Center
>
> -----
>
> Traditionally, the RFC Series requests that authors names be presented
> with "first name initial, last name".  There have been enough exceptions
> over the years, however, to make this a rather fuzzy tradition.
>
> What is most important to the Series is that authors names be consistent
> over time and using standard capitalization.  If author feels 2 initials
> distinguishes them, then we should allow it.  For the sake of the
> readership, however, an author can't switch between H. Flanagan, H. L.
> Flanagan, H.L. Flanagan, and so on.

Consistency is good. Right now it's not consistent because the 
additional initials are dropped on the first page, causing people to do 
things like

   HL. Flanagan

It would be trivial to remove this from xml2rfc.tcl; see 
<http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10>.

> ...

Best regards, Julian


From glenzorn@gmail.com  Fri Jul 20 02:33:42 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D3D021F8557 for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 02:33:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.338
X-Spam-Level: 
X-Spam-Status: No, score=-3.338 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XXQ-ji2cPLAj for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 02:33:41 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5230D21F84D0 for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 02:33:41 -0700 (PDT)
Received: by yenq13 with SMTP id q13so4117769yen.31 for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 02:34:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=zwNdNM+9+xbWNMHJXBN9DinHf97vWrBLocVZeeCx6yY=; b=pQSy5Nrot/Qvo/gRuS2O86wSQzOMqihAamV2rnZpOzqjq5joOph6aNyTQiyBq64lxC UrYJH/Z7TzqtZochrwz1zOjEFv8Kmu3agbDRQBXHYhmXKjAvut6O76dwCnkDnEHukMZo MGXX5C4Eh/BLDwvJLthl8qjqC5WkFx14yJMWnyVLy8FhF+EmiFlaUjVQksmG5Ix3TZ1X I8b0UMklRn4ur602egOoVeA4siTRGRnL3CAcYWakozEhlCnfkeG++0OkbLmXkToiwIkf a+9+JblXr1Ztc9cRDGjdraKS7BXF2JAH1nd1PC6o7Qhv2GNXy9uotLtN30EcLEf3yhQz w0IA==
Received: by 10.66.72.163 with SMTP id e3mr10075724pav.42.1342776876488; Fri, 20 Jul 2012 02:34:36 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-122-187-245.revip2.asianet.co.th. [124.122.187.245]) by mx.google.com with ESMTPS id rg9sm3630840pbc.67.2012.07.20.02.34.34 (version=SSLv3 cipher=OTHER); Fri, 20 Jul 2012 02:34:35 -0700 (PDT)
From: Glen Zorn <glenzorn@gmail.com>
To: xml2rfc@ietf.org
In-Reply-To: <500905BA.1070003@gmx.de>
References: <20120702162057.5849918C0B2@mercury.lcs.mit.edu> <4FF1CE62.9070401@gmx.de> <4FF1D210.7020603@gmx.de> <7F7C4B87-5D18-4B3D-A17F-848C996F1463@amsl.com> <500905BA.1070003@gmx.de>
Content-Type: multipart/alternative; boundary="=-8bd1ky5BGtUbVdhleZha"
Organization: Network Zen
Date: Fri, 20 Jul 2012 16:34:31 +0700
Message-ID: <1342776871.7688.2.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
Subject: Re: [xml2rfc] initials handling
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 09:33:42 -0000

--=-8bd1ky5BGtUbVdhleZha
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Fri, 2012-07-20 at 09:16 +0200, Julian Reschke wrote:

> On 2012-07-19 23:38, Alice Russo wrote:
> > Below is a note from the RFC Series Editor regarding how an RFC author's name appears. I have amended ticket #10 (which Julian pointed to) on this topic.
> >
> > Thanks,
> > Alice
> > RFC Production Center
> >
> > -----
> >
> > Traditionally, the RFC Series requests that authors names be presented
> > with "first name initial, last name".  There have been enough exceptions
> > over the years, however, to make this a rather fuzzy tradition.
> >
> > What is most important to the Series is that authors names be consistent
> > over time and using standard capitalization.  If author feels 2 initials
> > distinguishes them, then we should allow it.  For the sake of the
> > readership, however, an author can't switch between H. Flanagan, H. L.
> > Flanagan, H.L. Flanagan, and so on.
> 
> Consistency is good. Right now it's not consistent because the 
> additional initials are dropped on the first page, causing people to do 
> things like
> 
>    HL. Flanagan


Consistency is good, but I'm wondering 1) how to enforce this across
documents and 2) why I can't change my mind (e.g. decide that I prefer
G.W. instead of G.)


> 
> It would be trivial to remove this from xml2rfc.tcl; see 
> <http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10>.
> 
> > ...
> 
> Best regards, Julian
> 
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc



--=-8bd1ky5BGtUbVdhleZha
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Fri, 2012-07-20 at 09:16 +0200, Julian Reschke wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On 2012-07-19 23:38, Alice Russo wrote:
&gt; Below is a note from the RFC Series Editor regarding how an RFC author's name appears. I have amended ticket #10 (which Julian pointed to) on this topic.
&gt;
&gt; Thanks,
&gt; Alice
&gt; RFC Production Center
&gt;
&gt; -----
&gt;
&gt; Traditionally, the RFC Series requests that authors names be presented
&gt; with &quot;first name initial, last name&quot;.  There have been enough exceptions
&gt; over the years, however, to make this a rather fuzzy tradition.
&gt;
&gt; What is most important to the Series is that authors names be consistent
&gt; over time and using standard capitalization.  If author feels 2 initials
&gt; distinguishes them, then we should allow it.  For the sake of the
&gt; readership, however, an author can't switch between H. Flanagan, H. L.
&gt; Flanagan, H.L. Flanagan, and so on.

Consistency is good. Right now it's not consistent because the 
additional initials are dropped on the first page, causing people to do 
things like

&nbsp;&nbsp; HL. Flanagan
</PRE>
</BLOCKQUOTE>
<BR>
Consistency is good, but I'm wondering 1) how to enforce this across documents and 2) why I can't change my mind (e.g. decide that I prefer G.W. instead of G.)<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>

It would be trivial to remove this from xml2rfc.tcl; see 
&lt;<A HREF="http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10">http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10</A>&gt;.

&gt; ...

Best regards, Julian

_______________________________________________
xml2rfc mailing list
<A HREF="mailto:xml2rfc@ietf.org">xml2rfc@ietf.org</A>
<A HREF="https://www.ietf.org/mailman/listinfo/xml2rfc">https://www.ietf.org/mailman/listinfo/xml2rfc</A>
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-8bd1ky5BGtUbVdhleZha--


From julian.reschke@gmx.de  Fri Jul 20 02:36:07 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69D3621F857A for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 02:36:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.37
X-Spam-Level: 
X-Spam-Status: No, score=-104.37 tagged_above=-999 required=5 tests=[AWL=-1.771, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V--7K6m+Zed9 for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 02:36:07 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 7385C21F8557 for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 02:36:06 -0700 (PDT)
Received: (qmail invoked by alias); 20 Jul 2012 09:37:00 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp033) with SMTP; 20 Jul 2012 11:37:00 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+6i69xy5q63zAywg2v8rs9IoVAsB0SnXEt+u+Q/+ h++IL6cscxQAps
Message-ID: <500926BA.1070506@gmx.de>
Date: Fri, 20 Jul 2012 11:36:58 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Glen Zorn <glenzorn@gmail.com>
References: <20120702162057.5849918C0B2@mercury.lcs.mit.edu> <4FF1CE62.9070401@gmx.de> <4FF1D210.7020603@gmx.de> <7F7C4B87-5D18-4B3D-A17F-848C996F1463@amsl.com> <500905BA.1070003@gmx.de> <1342776871.7688.2.camel@gwz-laptop>
In-Reply-To: <1342776871.7688.2.camel@gwz-laptop>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] initials handling
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 09:36:07 -0000

On 2012-07-20 11:34, Glen Zorn wrote:
> On Fri, 2012-07-20 at 09:16 +0200, Julian Reschke wrote:
>> On 2012-07-19 23:38, Alice Russo wrote:
>> > Below is a note from the RFC Series Editor regarding how an RFC author's name appears. I have amended ticket #10 (which Julian pointed to) on this topic.
>> >
>> > Thanks,
>> > Alice
>> > RFC Production Center
>> >
>> > -----
>> >
>> > Traditionally, the RFC Series requests that authors names be presented
>> > with "first name initial, last name".  There have been enough exceptions
>> > over the years, however, to make this a rather fuzzy tradition.
>> >
>> > What is most important to the Series is that authors names be consistent
>> > over time and using standard capitalization.  If author feels 2 initials
>> > distinguishes them, then we should allow it.  For the sake of the
>> > readership, however, an author can't switch between H. Flanagan, H. L.
>> > Flanagan, H.L. Flanagan, and so on.
>>
>> Consistency is good. Right now it's not consistent because the
>> additional initials are dropped on the first page, causing people to do
>> things like
>>
>>     HL. Flanagan
>
> Consistency is good, but I'm wondering 1) how to enforce this across
> documents and 2) why I can't change my mind (e.g. decide that I prefer
> G.W. instead of G.)
> ...

Oh, I don't think we can enforce consistency *across* documents.

But optimally, the initials are the same (1) on page 1, (2) in footers, 
and (3) in citations of the document.

Best regards, Julian

From glenzorn@gmail.com  Fri Jul 20 05:09:23 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 570D521F8566 for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 05:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.381
X-Spam-Level: 
X-Spam-Status: No, score=-3.381 tagged_above=-999 required=5 tests=[AWL=0.217,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ud5kKbEczCzE for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 05:09:22 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 745C621F8565 for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 05:09:22 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so4247420ghb.31 for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 05:10:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=lcGKaRZ0fsC2cefgmdxFxqeDlnKWK+iLdbctwPosNjo=; b=J/6mj3+FgCBS0Y0IO+x+/kKWq4dYq6bTDRq0TfvwtvHVW9cR11kuzC1APYAf4vEqB6 UK67pNOjVo2k63sH0OjF+qtIN3UUmNKv6kHPZM+2QZQnOAoIBSagRVCcV7zEMzWrDyK1 acT4effP25POV7ya9+Sz4Vm1mB6y/SLh9b7srSmrWVVdgmU0ZskMtWUbnVfBPoICcp/u /7nGt579CJ8s3qKF5Sa5qdikYOyGizmfXA8eu12FSgNrzK4BEm8PvZUOrAaFrRgH4N0H rLZHB2p+TcQHdiRrsHt+Y7irZ7JJU0Z36zsnFMiFMrFgb0peYNJmJwJ81v5RTXhN6o7A PgQg==
Received: by 10.66.72.225 with SMTP id g1mr11250385pav.3.1342786217622; Fri, 20 Jul 2012 05:10:17 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-122-187-245.revip2.asianet.co.th. [124.122.187.245]) by mx.google.com with ESMTPS id pp2sm3883580pbb.1.2012.07.20.05.10.15 (version=SSLv3 cipher=OTHER); Fri, 20 Jul 2012 05:10:16 -0700 (PDT)
From: Glen Zorn <glenzorn@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
In-Reply-To: <500926BA.1070506@gmx.de>
References: <20120702162057.5849918C0B2@mercury.lcs.mit.edu> <4FF1CE62.9070401@gmx.de> <4FF1D210.7020603@gmx.de> <7F7C4B87-5D18-4B3D-A17F-848C996F1463@amsl.com> <500905BA.1070003@gmx.de> <1342776871.7688.2.camel@gwz-laptop>  <500926BA.1070506@gmx.de>
Content-Type: multipart/alternative; boundary="=-8n4MtovPgkbhQ7Ya7pIA"
Organization: Network Zen
Date: Fri, 20 Jul 2012 19:10:13 +0700
Message-ID: <1342786213.7688.5.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] initials handling
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 12:09:23 -0000

--=-8n4MtovPgkbhQ7Ya7pIA
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Fri, 2012-07-20 at 11:36 +0200, Julian Reschke wrote:

> On 2012-07-20 11:34, Glen Zorn wrote:
> > On Fri, 2012-07-20 at 09:16 +0200, Julian Reschke wrote:
> >> On 2012-07-19 23:38, Alice Russo wrote:
> >> > Below is a note from the RFC Series Editor regarding how an RFC author's name appears. I have amended ticket #10 (which Julian pointed to) on this topic.
> >> >
> >> > Thanks,
> >> > Alice
> >> > RFC Production Center
> >> >
> >> > -----
> >> >
> >> > Traditionally, the RFC Series requests that authors names be presented
> >> > with "first name initial, last name".  There have been enough exceptions
> >> > over the years, however, to make this a rather fuzzy tradition.
> >> >
> >> > What is most important to the Series is that authors names be consistent
> >> > over time and using standard capitalization.  If author feels 2 initials
> >> > distinguishes them, then we should allow it.  For the sake of the
> >> > readership, however, an author can't switch between H. Flanagan, H. L.
> >> > Flanagan, H.L. Flanagan, and so on.
> >>
> >> Consistency is good. Right now it's not consistent because the
> >> additional initials are dropped on the first page, causing people to do
> >> things like
> >>
> >>     HL. Flanagan
> >
> > Consistency is good, but I'm wondering 1) how to enforce this across
> > documents and 2) why I can't change my mind (e.g. decide that I prefer
> > G.W. instead of G.)
> > ...
> 
> Oh, I don't think we can enforce consistency *across* documents.


Oh.  That's what I understood Alice to be requesting, that an author be
consistently recognizable by name.


> 
> But optimally, the initials are the same (1) on page 1, (2) in footers, 
> and (3) in citations of the document.
> 
> Best regards, Julian



--=-8n4MtovPgkbhQ7Ya7pIA
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Fri, 2012-07-20 at 11:36 +0200, Julian Reschke wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On 2012-07-20 11:34, Glen Zorn wrote:
&gt; On Fri, 2012-07-20 at 09:16 +0200, Julian Reschke wrote:
&gt;&gt; On 2012-07-19 23:38, Alice Russo wrote:
&gt;&gt; &gt; Below is a note from the RFC Series Editor regarding how an RFC author's name appears. I have amended ticket #10 (which Julian pointed to) on this topic.
&gt;&gt; &gt;
&gt;&gt; &gt; Thanks,
&gt;&gt; &gt; Alice
&gt;&gt; &gt; RFC Production Center
&gt;&gt; &gt;
&gt;&gt; &gt; -----
&gt;&gt; &gt;
&gt;&gt; &gt; Traditionally, the RFC Series requests that authors names be presented
&gt;&gt; &gt; with &quot;first name initial, last name&quot;.  There have been enough exceptions
&gt;&gt; &gt; over the years, however, to make this a rather fuzzy tradition.
&gt;&gt; &gt;
&gt;&gt; &gt; What is most important to the Series is that authors names be consistent
&gt;&gt; &gt; over time and using standard capitalization.  If author feels 2 initials
&gt;&gt; &gt; distinguishes them, then we should allow it.  For the sake of the
&gt;&gt; &gt; readership, however, an author can't switch between H. Flanagan, H. L.
&gt;&gt; &gt; Flanagan, H.L. Flanagan, and so on.
&gt;&gt;
&gt;&gt; Consistency is good. Right now it's not consistent because the
&gt;&gt; additional initials are dropped on the first page, causing people to do
&gt;&gt; things like
&gt;&gt;
&gt;&gt;     HL. Flanagan
&gt;
&gt; Consistency is good, but I'm wondering 1) how to enforce this across
&gt; documents and 2) why I can't change my mind (e.g. decide that I prefer
&gt; G.W. instead of G.)
&gt; ...

Oh, I don't think we can enforce consistency *across* documents.
</PRE>
</BLOCKQUOTE>
<BR>
Oh.&nbsp; That's what I understood Alice to be requesting, that an author be consistently recognizable by name.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>

But optimally, the initials are the same (1) on page 1, (2) in footers, 
and (3) in citations of the document.

Best regards, Julian
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-8n4MtovPgkbhQ7Ya7pIA--


From randy@psg.com  Fri Jul 20 05:11:55 2012
Return-Path: <randy@psg.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC40021F8570 for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 05:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.575
X-Spam-Level: 
X-Spam-Status: No, score=-2.575 tagged_above=-999 required=5 tests=[AWL=0.024,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G2o-O8M5+GVf for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 05:11:55 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 8A93221F856D for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 05:11:55 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SsC4e-0007vd-QJ; Fri, 20 Jul 2012 12:12:49 +0000
Date: Fri, 20 Jul 2012 13:12:47 +0100
Message-ID: <m2fw8mvdfk.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Glen Zorn <glenzorn@gmail.com>
In-Reply-To: <1342786213.7688.5.camel@gwz-laptop>
References: <20120702162057.5849918C0B2@mercury.lcs.mit.edu> <4FF1CE62.9070401@gmx.de> <4FF1D210.7020603@gmx.de> <7F7C4B87-5D18-4B3D-A17F-848C996F1463@amsl.com> <500905BA.1070003@gmx.de> <1342776871.7688.2.camel@gwz-laptop> <500926BA.1070506@gmx.de> <1342786213.7688.5.camel@gwz-laptop>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: Julian Reschke <julian.reschke@gmx.de>, xml2rfc@ietf.org
Subject: Re: [xml2rfc] initials handling
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 12:11:56 -0000

>> Oh, I don't think we can enforce consistency *across* documents.
> Oh.  That's what I understood Alice to be requesting, that an author be
> consistently recognizable by name.

consistent author across all, reauired.  inconsistent syntax between
authors, fine.

randy

From dworley@avaya.com  Fri Jul 20 06:58:48 2012
Return-Path: <dworley@avaya.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C74021F858E for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 06:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.186
X-Spam-Level: 
X-Spam-Status: No, score=-103.186 tagged_above=-999 required=5 tests=[AWL=0.413, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Ywzo0HH8yc2 for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 06:58:47 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 9115521F858D for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 06:58:47 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAGtjCVDGmAcF/2dsb2JhbABFhXSyNYEXgQeCIAEBAQECARIREUUFCwIBCA0LAgImAgICMBUQAQEEDg0ah2UGoV2KHpMZgSCPfDJgA5tAig+Cew
X-IronPort-AV: E=Sophos;i="4.77,623,1336363200"; d="scan'208";a="315731193"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 20 Jul 2012 09:55:48 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 20 Jul 2012 09:55:50 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Fri, 20 Jul 2012 09:59:36 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "glenzorn@gmail.com" <glenzorn@gmail.com>
Date: Fri, 20 Jul 2012 09:59:36 -0400
Thread-Topic: [xml2rfc] initials handling
Thread-Index: Ac1mf+Xoj8xJN0ZrTmuKur6YUOCEiA==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A1D8D@DC-US1MBEX4.global.avaya.com>
References: <20120702162057.5849918C0B2@mercury.lcs.mit.edu> <4FF1CE62.9070401@gmx.de> <4FF1D210.7020603@gmx.de> <7F7C4B87-5D18-4B3D-A17F-848C996F1463@amsl.com> <500905BA.1070003@gmx.de> <1342776871.7688.2.camel@gwz-laptop>
In-Reply-To: <1342776871.7688.2.camel@gwz-laptop>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] initials handling
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 13:58:48 -0000

T24gRnJpLCAyMDEyLTA3LTIwIGF0IDE2OjM0ICswNzAwLCBHbGVuIFpvcm4gd3JvdGU6Cj4gQ29u
c2lzdGVuY3kgaXMgZ29vZCwgYnV0IEknbSB3b25kZXJpbmcgMSkgaG93IHRvIGVuZm9yY2UgdGhp
cyBhY3Jvc3MKPiBkb2N1bWVudHMKCklmIHdlIGFsbG93IGRpZmZlcmVudCBhdXRob3JzIHRvIHVz
ZSBkaWZmZXJlbnQgZm9ybWF0cywgdGhlcmUncyByZWFsbHkKbm8gd2F5IHRvIGVuZm9yY2UgY29u
c2lzdGVuY3kgZm9yIG9uZSBhdXRob3IgYWNyb3NzIG1hbnkgZG9jdW1lbnRzLgoKPiBhbmQgMikg
d2h5IEkgY2FuJ3QgY2hhbmdlIG15IG1pbmQgKGUuZy4gZGVjaWRlIHRoYXQgSSBwcmVmZXIgRy5X
Lgo+IGluc3RlYWQgb2YgRy4pCgpCZWNhdXNlIGlmIHNvbWUgZW50cmllcyBpbiByZmMtaW5kZXgu
dHh0IGxpc3QgIkcuIFpvcm4iIGFuZCBzb21lIGxpc3QKIkcuVy4gWm9ybiIsIGhvdyBpcyBvbmUg
dG8ganVkZ2UgdGhhdCB0aGV5IGFyZSB0aGUgc2FtZSBwZXJzb24/ClVsdGltYXRlbHksIHRoZSAi
YXV0aG9yIG5hbWUiIG9uIGEgZG9jdW1lbnQgaXMgbm90IGZvciB0aGUgZ3JhdGlmaWNhdGlvbgpv
ZiB0aGUgYXV0aG9yIGJ1dCBmb3IgdGhlIGluZm9ybWF0aW9uIG9mIHRoZSByZWFkZXIuCgpEYWxl
Cgo=

From paul.hoffman@vpnc.org  Fri Jul 20 07:22:24 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8316821F85A3 for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 07:22:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UlInDdxMkc2X for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 07:22:24 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id CCD6121F8672 for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 07:22:23 -0700 (PDT)
Received: from [10.20.30.102] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q6KDW21H049194 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 20 Jul 2012 06:32:03 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <1342786213.7688.5.camel@gwz-laptop>
Date: Fri, 20 Jul 2012 07:23:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <90CEDCA1-6218-4FA5-B508-1E5C593B4538@vpnc.org>
References: <20120702162057.5849918C0B2@mercury.lcs.mit.edu> <4FF1CE62.9070401@gmx.de> <4FF1D210.7020603@gmx.de> <7F7C4B87-5D18-4B3D-A17F-848C996F1463@amsl.com> <500905BA.1070003@gmx.de> <1342776871.7688.2.camel@gwz-laptop> <500926BA.1070506@gmx.de> <1342786213.7688.5.camel@gwz-laptop>
To: Alice Russo <arusso@amsl.com>
X-Mailer: Apple Mail (2.1278)
Cc: xml2rfc list <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] initials handling
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 14:22:24 -0000

On Jul 20, 2012, at 5:10 AM, Glen Zorn wrote:

>> Oh, I don't think we can enforce consistency *across* documents.
>=20
> Oh.  That's what I understood Alice to be requesting, that an author =
be consistently recognizable by name.


Alice: what did you mean by:

What is most important to the Series is that authors names be consistent
over time and using standard capitalization.  If author feels 2 initials
distinguishes them, then we should allow it.  For the sake of the
readership, however, an author can't switch between H. Flanagan, H. L.
Flanagan, H.L. Flanagan, and so on.

Is that "within the RFC series", or something else?

--Paul Hoffman


From arusso@amsl.com  Fri Jul 20 07:40:02 2012
Return-Path: <arusso@amsl.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D02721F8530 for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 07:40:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.466
X-Spam-Level: 
X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tV4sNZPUqNES for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 07:40:02 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id EE7DF21F858A for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 07:40:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 57A7D12CB9A; Fri, 20 Jul 2012 07:40:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D5MEOAe9GEXC; Fri, 20 Jul 2012 07:40:58 -0700 (PDT)
Received: from rfc2.home (pool-173-73-60-7.washdc.fios.verizon.net [173.73.60.7]) by c8a.amsl.com (Postfix) with ESMTPSA id D2F9212CB8D; Fri, 20 Jul 2012 07:40:57 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Alice Russo <arusso@amsl.com>
In-Reply-To: <1342786213.7688.5.camel@gwz-laptop>
Date: Fri, 20 Jul 2012 10:40:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <52F7D038-D475-42DA-8867-8A25E6245A38@amsl.com>
References: <20120702162057.5849918C0B2@mercury.lcs.mit.edu> <4FF1CE62.9070401@gmx.de> <4FF1D210.7020603@gmx.de> <7F7C4B87-5D18-4B3D-A17F-848C996F1463@amsl.com> <500905BA.1070003@gmx.de> <1342776871.7688.2.camel@gwz-laptop> <500926BA.1070506@gmx.de> <1342786213.7688.5.camel@gwz-laptop>
To: xml2rfc list <xml2rfc@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: RSE <rse@rfc-editor.org>
Subject: Re: [xml2rfc] initials handling
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 14:40:02 -0000

Glen wrote:
> Oh.  That's what I understood Alice to be requesting,

Paul wrote:
> Alice: what did you mean by:


To be clear: The note on this topic was written by the RFC Series Editor =
(Heather Flanagan). She will review your concerns/questions.

Thanks,
Alice

On Jul 19, 2012, Alice Russo wrote:
> Below is a note from the RFC Series Editor regarding how an RFC =
author's name appears. I have amended ticket #10 (which Julian pointed =
to) on this topic.
>=20
> Thanks,
> Alice
> RFC Production Center
>=20
> -----
>=20
> Traditionally, the RFC Series requests that authors names be presented
> with "first name initial, last name".  There have been enough =
exceptions
> over the years, however, to make this a rather fuzzy tradition.
>=20
> What is most important to the Series is that authors names be =
consistent
> over time and using standard capitalization.  If author feels 2 =
initials
> distinguishes them, then we should allow it.  For the sake of the
> readership, however, an author can't switch between H. Flanagan, H. L.
> Flanagan, H.L. Flanagan, and so on.
>=20
> So, what the RFC Editor would like to see out of xml2rfc is more
> flexibility to allow for author preferences.  =46rom our side, we will =
be
> documenting this more fully in the new version of the Style Guide, =
which
> will be made available for comment shortly after IETF 84.  This will =
go
> on the web page component of the Style Guide.
>=20
> Please let me know if there are any questions!
>=20
> -Heather Flanagan, RSE
>=20
> On Jul 2, 2012, at 12:53 PM, Julian Reschke wrote:
>=20
>> On 2012-07-02 18:37, Julian Reschke wrote:
>>> ...
>>>>> I don't see anything wrong with the above (well, except for
>>>> missing
>>>>> whitespace between "J." and "N.").
>>>>=20
>>>> When I tried that (I started with "J. N.", and also tried
>>>> "J.&nbsp;N.", it
>>>> truncated it to 'J. Chiappa' in the header page in the output. =
(Tries it
>>>> again to make sure he wasn't dreaming.) Yup, truncates to "J.".
>>>=20
>>> Which version of xml2rfc are you trying?
>>> ...
>>=20
>> In the meantime I recalled that this is =
<http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10>; so this is a =
RFC style requirement; If you don't like it you should bring it up on =
rfc-interest mailing list as well...
>>=20
>> Best regards, Julian
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>=20
>=20
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
>=20

From nico@cryptonector.com  Fri Jul 20 08:42:16 2012
Return-Path: <nico@cryptonector.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3131921F8554 for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 08:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.343
X-Spam-Level: 
X-Spam-Status: No, score=-3.343 tagged_above=-999 required=5 tests=[AWL=-1.366, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQK3EnGR3XV9 for <xml2rfc@ietfa.amsl.com>; Fri, 20 Jul 2012 08:42:15 -0700 (PDT)
Received: from homiemail-a77.g.dreamhost.com (caiajhbdcbbj.dreamhost.com [208.97.132.119]) by ietfa.amsl.com (Postfix) with ESMTP id 90FFC21F854A for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 08:42:15 -0700 (PDT)
Received: from homiemail-a77.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a77.g.dreamhost.com (Postfix) with ESMTP id D17819405E for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 08:43:11 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=JORxFnv5qhGhxs/MSwYsz 4WXkik5aaU9t6cwdHz2C27syQPHM7+qPafAOx7J3CF1Jz3w3mgOUxJpkG76VxQ8h ZxFKoUzmq8S6H74QQyapYUSxfyGK6s1BdkMbCI4mOpyeIyk3D6KM/D4hpKat8DtO kAUp2dkswZYT/csvcGNr3A=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=iU5i6CFI0XxUwLnEedVn nugzCSY=; b=UzRq4NClTK8ac4Av0S/6puCM3Ah+apWXfjtF7B+c5WcQ/J9i1pbR QpbZTcE3C5JCbw5Pq3LMDBrFzkZ3kK7a4WfkX08ki4GeD+u7oRsRnrHnOl4g0P8k aa/104Gzh0cWk1Nf7W1WwgPUOhYkWoLIj/O45CqiNaMMk36tgJWf9Tk=
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a77.g.dreamhost.com (Postfix) with ESMTPSA id A701B9405C for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 08:43:11 -0700 (PDT)
Received: by yenq13 with SMTP id q13so4509504yen.31 for <xml2rfc@ietf.org>; Fri, 20 Jul 2012 08:43:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.223.138 with SMTP id qu10mr14925055pbc.50.1342798990487; Fri, 20 Jul 2012 08:43:10 -0700 (PDT)
Received: by 10.143.29.16 with HTTP; Fri, 20 Jul 2012 08:43:10 -0700 (PDT)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A1D8D@DC-US1MBEX4.global.avaya.com>
References: <20120702162057.5849918C0B2@mercury.lcs.mit.edu> <4FF1CE62.9070401@gmx.de> <4FF1D210.7020603@gmx.de> <7F7C4B87-5D18-4B3D-A17F-848C996F1463@amsl.com> <500905BA.1070003@gmx.de> <1342776871.7688.2.camel@gwz-laptop> <CD5674C3CD99574EBA7432465FC13C1B22726A1D8D@DC-US1MBEX4.global.avaya.com>
Date: Fri, 20 Jul 2012 10:43:10 -0500
Message-ID: <CAK3OfOhYU2daak4yMrC=grP=g7Gh_2vwnZY5FF9KOunEtDaLAA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Content-Type: text/plain; charset=UTF-8
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] initials handling
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 15:42:16 -0000

On Fri, Jul 20, 2012 at 8:59 AM, Worley, Dale R (Dale)
<dworley@avaya.com> wrote:
> Because if some entries in rfc-index.txt list "G. Zorn" and some list
> "G.W. Zorn", how is one to judge that they are the same person?
> Ultimately, the "author name" on a document is not for the gratification
> of the author but for the information of the reader.

Exact name conflicts do arise, and THEN how do you know that one
author, J. Sixpack, is or is not the same as another J. Sixpack?  By
having an option to include middle initials you reduce the chances of
such conflicts, though you can't entirely prevent conflicts.

Maybe we should have an IANA registry of authors, that way any second
and third authors with the same name as a first can just assign
themselves (or have assigned to them) a
similar-but-different-and-unique alternative name.  (That's... not a
serious proposal.  The point is that I find this forcing authors to
have/use a single initial to be only somewhat less heavyhanded than
such an IANA registry.)

Forcing the use of a single initial does get us consistency, but it's
a hack.  If I were to suddenly want to use my middle initial and I
understand that doing so will cause a small amount of brief confusion
for a few RFC readers, I might still want to do it.  Why shouldn't I
get to, when I would be the one most affected by the change?

Nico
--

From john+xml@jck.com  Mon Jul 23 10:15:50 2012
Return-Path: <john+xml@jck.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 536F511E80C8 for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 10:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QkMOueayyxYh for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 10:15:49 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id ACAE111E808E for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 10:15:49 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john+xml@jck.com>) id 1StM91-0003Oh-HZ; Mon, 23 Jul 2012 13:10:07 -0400
Date: Mon, 23 Jul 2012 13:15:35 -0400
From: John C Klensin <john+xml@jck.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, xml2rfc@ietf.org
Message-ID: <F09D983D78ED05C0A742ABDC@JcK-HP8200.jck.com>
In-Reply-To: <20120706185656.7CEFF18C110@mercury.lcs.mit.edu>
References: <20120706185656.7CEFF18C110@mercury.lcs.mit.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [xml2rfc] xref inside cref
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 17:15:50 -0000

(catching up on past messages before asking a question)

--On Friday, July 06, 2012 14:56 -0400 Noel Chiappa
<jnc@mercury.lcs.mit.edu> wrote:

> It's very mildly unfortunate that cross section references
> (xref) inside a cref don't work - not a big deal, one can
> always write it out the target section name.

For a variety of reasons, it is a lot more than mildly
unfortunate that <cref>s cannot contain just about anything that
<t> can contain, including <list> and <vspace> elements as well
as <xref> ones.  It is also unfortunately that they cannot be
explicitly anchored so that one can refer to one note from
within another.  If one had those things, it might actually be
possible to use xml2rfc for an incrementally-developed
collaborative document.

However,...

     john





From john+xml@jck.com  Mon Jul 23 10:32:22 2012
Return-Path: <john+xml@jck.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 829CC11E80CE for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 10:32:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wYQfzBX-FtCR for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 10:32:21 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A929711E8091 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 10:32:21 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john+xml@jck.com>) id 1StMP1-0003T5-Ed for xml2rfc@ietf.org; Mon, 23 Jul 2012 13:26:39 -0400
Date: Mon, 23 Jul 2012 13:32:07 -0400
From: John C Klensin <john+xml@jck.com>
To: xml2rfc list <xml2rfc@ietf.org>
Message-ID: <E771C8390C019AD8BE07CA8B@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: [xml2rfc] RFC-like documents
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 17:32:22 -0000

Hi.

When XML2RFC was first designed, the target audience was RFCs,
I-Ds, and other documents "like" them.  It was used to produce
several such documents of some utility to the IETF community.
It appears that the new version now has enough checks for I-D
and RFC formats that there is no more "like" -- one gets either
I-D format or RFC format with all of the associated front and
back boilerplate or one gets nothing at all?

Perhaps there is a processing directive to overcome that, but,
if so, I can't find it.

So...

(1) Is the elimination of RFC-like documents that are neither
RFCs nor I-Ds intentional or was it an accidental side-effect of
putting in additional checking?

(2) Is there a processing directive that would permit more
general documents that follow the general RFC/I-D style but are
neither.

(3) As a generalization of (2), is there a comprehensive list of
available processing directives and what they do (other than
scattered through various templates) and, if so, where is it and
can we get a prominent link to it from the
http://xml.resource.org/ home page?

   best,
    john

p.s. For anyone who can't answer or understand the above
questions without a use case, I decided to try to render the
latest IESG "shepherd write up" form into something that could
be processed and read properly.  Since much of the relevant part
of the community is familiar with xml2rfc, it seemed like an
obvious candidate.  But that apparently cannot be done without
faking an RFC and then post-processing the document to eliminate
a lot of irrelevant material in the front and back.


From nico@cryptonector.com  Mon Jul 23 10:41:01 2012
Return-Path: <nico@cryptonector.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D7D111E80E1 for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 10:41:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[AWL=-1.349, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cU0y3yyqqys1 for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 10:41:00 -0700 (PDT)
Received: from homiemail-a88.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by ietfa.amsl.com (Postfix) with ESMTP id 669D211E807F for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 10:41:00 -0700 (PDT)
Received: from homiemail-a88.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a88.g.dreamhost.com (Postfix) with ESMTP id 95FD326407C for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 10:40:52 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=MuTJAi/Cx9GiGHc8dug3K IkR+zWztzVYWrawm4iCyGhLzvqSsgtUiBkysAZCwGIt6bYt8JGTswb3JW6fEDAiD u1SaOsbcNV1VaKFkrcCA8WGs9//YeErGkNNvglb1fr5kGDS3jwvakrzgJMy+Vpgj mGgfIyKUaV3cuSfvgL3yQA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=WInXgMFefuviH9MF2ZPj EAzIfDM=; b=jD23hOtFckBFTr2+0idWaN6j/+9pSYP/MumCT8tuEHQrJWsYKrKs Qw0sz2+M7jz0lzMg89XbbXZ6IPWoYqPdr9uMzdrsJBCDA02xb+Um5gxPinDj6Opk NuFb/Kco5ZOUsFLAT05aKRAxUN2G1MhbGF1Hh3q+zcRiG8jQR/dXp8M=
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a88.g.dreamhost.com (Postfix) with ESMTPSA id 804DC264079 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 10:40:52 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so11559904pbc.31 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 10:40:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.135.201 with SMTP id pu9mr36551120pbb.146.1343065251771; Mon, 23 Jul 2012 10:40:51 -0700 (PDT)
Received: by 10.143.29.16 with HTTP; Mon, 23 Jul 2012 10:40:51 -0700 (PDT)
In-Reply-To: <E771C8390C019AD8BE07CA8B@JcK-HP8200.jck.com>
References: <E771C8390C019AD8BE07CA8B@JcK-HP8200.jck.com>
Date: Mon, 23 Jul 2012 12:40:51 -0500
Message-ID: <CAK3OfOgX56OPrnynZ57G_t62kAjasgUbyTTOHaPY_BXa3D9zww@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: John C Klensin <john+xml@jck.com>
Content-Type: text/plain; charset=UTF-8
Cc: xml2rfc list <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] RFC-like documents
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 17:41:01 -0000

On Mon, Jul 23, 2012 at 12:32 PM, John C Klensin <john+xml@jck.com> wrote:
> When XML2RFC was first designed, the target audience was RFCs,
> I-Ds, and other documents "like" them.  It was used to produce
> several such documents of some utility to the IETF community.
> It appears that the new version now has enough checks for I-D
> and RFC formats that there is no more "like" -- one gets either
> I-D format or RFC format with all of the associated front and
> back boilerplate or one gets nothing at all?
>
> Perhaps there is a processing directive to overcome that, but,
> if so, I can't find it.

The old version had a "private" PI for this.  Is that gone in the new version?

I've used it before for docs that have nothing to do with the IETF,
due to my [then] liking the xml2rfc schema well enough.  Nowadays I
seem to have a mild love affair with LyX, so I've been using
lyx2xml2rfc to format I-Ds, and formatting private docs directly is
trivial.

> (2) Is there a processing directive that would permit more
> general documents that follow the general RFC/I-D style but are
> neither.

Did you try the private PI?

> (3) As a generalization of (2), is there a comprehensive list of
> available processing directives and what they do (other than
> scattered through various templates) and, if so, where is it and
> can we get a prominent link to it from the
> http://xml.resource.org/ home page?

The list of PIs is here:

http://xml.resource.org/authoring/README.html#anchor7

> p.s. For anyone who can't answer or understand the above
> questions without a use case, I decided to try to render the
> latest IESG "shepherd write up" form into something that could
> be processed and read properly.  Since much of the relevant part
> of the community is familiar with xml2rfc, it seemed like an
> obvious candidate.  But that apparently cannot be done without
> faking an RFC and then post-processing the document to eliminate
> a lot of irrelevant material in the front and back.

It's worth having a private mode (within reason, by which I mean just
not including any boilerplate) in any case because it's a useful tool,
and more users -> improved tooling.

Nico
--

From nico@cryptonector.com  Mon Jul 23 10:42:15 2012
Return-Path: <nico@cryptonector.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BFEB11E807F for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 10:42:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.309
X-Spam-Level: 
X-Spam-Status: No, score=-3.309 tagged_above=-999 required=5 tests=[AWL=-1.332, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rhvvswmYUoBa for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 10:42:14 -0700 (PDT)
Received: from homiemail-a85.g.dreamhost.com (mailbigip.dreamhost.com [208.97.132.5]) by ietfa.amsl.com (Postfix) with ESMTP id 8947411E8093 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 10:42:14 -0700 (PDT)
Received: from homiemail-a85.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a85.g.dreamhost.com (Postfix) with ESMTP id 4DC42BC034 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 10:42:14 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=ipYf3pJf+MrNNpUXV9xxD RM2K+H1l4ZAoS4sutQadKwn/hJeMNujCBbusyCsk7kqoXjYugOJiUaLqEIEzvpnt c1rZ/qLiwGzyR93Bb47vLlax49SlBcmR2Vxw7DCzZBjrpdp10gYueFt0MBeped0m LXvmTIsw3M/1IxgwBFeG0A=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=D4fiBXTc3QJv7e2BVTF0 Wy8Ezgg=; b=LhRs2EKk3XNPblP5i6MbmlVOG7ZWEB6DA7Aitfdzs0OYJMWVJ0wD MZz2SA8M0MZLFziGNjMnsoTQGoRzyYVOGD4f8w2qP/1onchMeBZRciKHvvamCylc oZri1v023uMEBt2v0jEGV6avZzUEHojuP5Jml2v6zodESf8sp0Tqhik=
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a85.g.dreamhost.com (Postfix) with ESMTPSA id 267D6BC033 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 10:42:14 -0700 (PDT)
Received: by yenq13 with SMTP id q13so6286226yen.31 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 10:42:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.223.138 with SMTP id qu10mr37378297pbc.50.1343065333048; Mon, 23 Jul 2012 10:42:13 -0700 (PDT)
Received: by 10.143.29.16 with HTTP; Mon, 23 Jul 2012 10:42:12 -0700 (PDT)
In-Reply-To: <F09D983D78ED05C0A742ABDC@JcK-HP8200.jck.com>
References: <20120706185656.7CEFF18C110@mercury.lcs.mit.edu> <F09D983D78ED05C0A742ABDC@JcK-HP8200.jck.com>
Date: Mon, 23 Jul 2012 12:42:12 -0500
Message-ID: <CAK3OfOgBbsCqf1KEBEGohe=Lq+PP86gWNHhAVuxai6kf0Wuc1Q@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: John C Klensin <john+xml@jck.com>
Content-Type: text/plain; charset=UTF-8
Cc: xml2rfc@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [xml2rfc] xref inside cref
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 17:42:15 -0000

On Mon, Jul 23, 2012 at 12:15 PM, John C Klensin <john+xml@jck.com> wrote:
> For a variety of reasons, it is a lot more than mildly
> unfortunate that <cref>s cannot contain just about anything that
> <t> can contain, including <list> and <vspace> elements as well
> as <xref> ones.  It is also unfortunately that they cannot be
> explicitly anchored so that one can refer to one note from
> within another.  If one had those things, it might actually be
> possible to use xml2rfc for an incrementally-developed
> collaborative document.

+1.  Because of this I just use <t> and add square brackets.

From julian.reschke@gmx.de  Mon Jul 23 10:49:04 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3B6511E80E8 for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 10:49:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.33
X-Spam-Level: 
X-Spam-Status: No, score=-104.33 tagged_above=-999 required=5 tests=[AWL=-1.731, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4NJ0l8wFL8Y3 for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 10:49:03 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id CCCA011E80AE for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 10:49:02 -0700 (PDT)
Received: (qmail invoked by alias); 23 Jul 2012 17:48:51 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp070) with SMTP; 23 Jul 2012 19:48:51 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX185Mzg4fh45S2VD26Yns0hCMf7t/O1eNtkQ/CLhpe 5asCWnY8sbkSm3
Message-ID: <500D8E7B.20403@gmx.de>
Date: Mon, 23 Jul 2012 19:48:43 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: John C Klensin <john+xml@jck.com>
References: <20120706185656.7CEFF18C110@mercury.lcs.mit.edu> <F09D983D78ED05C0A742ABDC@JcK-HP8200.jck.com>
In-Reply-To: <F09D983D78ED05C0A742ABDC@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [xml2rfc] xref inside cref
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 17:49:04 -0000

On 2012-07-23 19:15, John C Klensin wrote:
> (catching up on past messages before asking a question)
>
> --On Friday, July 06, 2012 14:56 -0400 Noel Chiappa
> <jnc@mercury.lcs.mit.edu> wrote:
>
>> It's very mildly unfortunate that cross section references
>> (xref) inside a cref don't work - not a big deal, one can
>> always write it out the target section name.
>
> For a variety of reasons, it is a lot more than mildly
> unfortunate that <cref>s cannot contain just about anything that
> <t> can contain, including <list> and <vspace> elements as well
> as <xref> ones.  It is also unfortunately that they cannot be
> explicitly anchored so that one can refer to one note from
> within another.  If one had those things, it might actually be
> possible to use xml2rfc for an incrementally-developed
> collaborative document.

I recommend opening a ticket in 
<http://trac.tools.ietf.org/tools/xml2rfc/trac/report>, component 
"vocabulary".

Best regards, Julian


From john+xml@jck.com  Mon Jul 23 10:52:59 2012
Return-Path: <john+xml@jck.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9959A11E80D7 for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 10:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D0gimYmp3+DC for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 10:52:58 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A415F11E80CF for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 10:52:58 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john+xml@jck.com>) id 1StMiy-0003YC-66; Mon, 23 Jul 2012 13:47:16 -0400
Date: Mon, 23 Jul 2012 13:52:44 -0400
From: John C Klensin <john+xml@jck.com>
To: Alice Russo <arusso@amsl.com>, xml2rfc list <xml2rfc@ietf.org>
Message-ID: <DECC1D3B4137912FD8432EE3@JcK-HP8200.jck.com>
In-Reply-To: <DAE4C8EF-844B-4FBB-AC21-8B14EA0E857F@amsl.com>
References: <4FD6EFB7.7020906@gmx.de> <4FD6F171.3000506@it.aoyama.ac.jp>	<4FD6F4D6.8090904@gmx.de> <4FD6FEA2.9020307@gmail.com> <DAE4C8EF-844B-4FBB-AC21-8B14EA0E857F@amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: RFC Editor <rfc-editor@rfc-editor.org>
Subject: Re: [xml2rfc] BCP references
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 17:52:59 -0000

--On Thursday, June 28, 2012 12:00 -0400 Alice Russo
<arusso@amsl.com> wrote:

> For creating a reference element for a subseries identifier
> that contains more than one RFC (for example: BCP 9 or STD 62)
> -- from the perspective of the RFC Production Center, this
> text is recommended:
> 
>   [BCP9]     Bradner, S., "The Internet Standards Process --
> Revision              3", BCP 9, RFC 2026, October 1996.
> 
>              Dusseault, L. and R. Sparks, "Guidance on
> Interoperation              and Implementation Reports for
> Advancement to Draft              Standard", BCP 9, RFC 5657,
> September 2009.
> 
>              Housley, R., Crocker, D., and E. Burger,
> "Reducing the              Standards Track to Two Maturity
> Levels", BCP 9, RFC 6410,              October 2011.
> 
> In XML, as a work-around, the annotation element can be used
> to create that entry (the text can be copied & pasted from the
> RFC bibliographic entries on
> ftp://ftp.rfc-editor.org/in-notes/rfc-ref.txt):
>...

Alice,

Yes, but this is a horrible kludge that defeats most of the
value of generic markup within references as well as forcing
copying from the library rather than incorporating references by
inclusion.  The latter is both error-prone and, unless
everything copies in the same way, prone to inconsistency.

FWIW, one of the originators of xml2rfc once suggested using
<seriesInfo> elements for these sorts of compound references,
not >annotation>.  Also a horrible kludge, not necessarily a
worse one.

While horrible kludges are appropriate until a solution can be
deployed, the solution has been known, and suggested multiple
times, for years.  It is to allow nested references, e.g., to
permit 

  <reference anchor="BCP9">
    &rfc2026;
    &rfc5657;
    &rfc6410;
  </reference>

(or, of course, the expanded versions of the named entities).

With some careful attention to formatting or an additional
attribute like 
   <reference anchor="XX" referenceType="bookChapter">
, the above construction would also deal with the problem of 

   Bloggs, J., "Spring flowers", ... in Smith, A., Flowers of
Southern Antarctica, ...

As I said when the Reference committee report appeared, I think
it is important that the RFC Editor do, or sponsor, an analysis
of the use cases of compound references and then help those who
are in charge of tools like xml2rfc to get the right
constructions into their definitions and code.  Fortunately,
there are not a huge number of such cases.  As far as I know,
chapters in books, articles in journals, various sorts of
compendia (or which BCP and STD references are examples), and a
referenced item that is available via multiple sources (reprints
as well as online and offline) just about covers the space.

   best,
     john


From john+xml@jck.com  Mon Jul 23 11:19:33 2012
Return-Path: <john+xml@jck.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD36311E80BF for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 11:19:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3kGzgp7fSPLw for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 11:19:33 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 267A411E8093 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 11:19:33 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john+xml@jck.com>) id 1StN8Z-0003ft-W2; Mon, 23 Jul 2012 14:13:43 -0400
Date: Mon, 23 Jul 2012 14:19:12 -0400
From: John C Klensin <john+xml@jck.com>
To: Nico Williams <nico@cryptonector.com>
Message-ID: <BC4A11CE34FEE9CC5F4D1D06@JcK-HP8200.jck.com>
In-Reply-To: <CAK3OfOgBbsCqf1KEBEGohe=Lq+PP86gWNHhAVuxai6kf0Wuc1Q@mail.gmail.com>
References: <20120706185656.7CEFF18C110@mercury.lcs.mit.edu> <F09D983D78ED05C0A742ABDC@JcK-HP8200.jck.com> <CAK3OfOgBbsCqf1KEBEGohe=Lq+PP86gWNHhAVuxai6kf0Wuc1Q@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: xml2rfc@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [xml2rfc] xref inside cref
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 18:19:33 -0000

--On Monday, July 23, 2012 12:42 -0500 Nico Williams
<nico@cryptonector.com> wrote:

> On Mon, Jul 23, 2012 at 12:15 PM, John C Klensin
> <john+xml@jck.com> wrote:
>> For a variety of reasons, it is a lot more than mildly
>> unfortunate that <cref>s cannot contain just about anything
>> that <t> can contain, including <list> and <vspace> elements
>> as well as <xref> ones.  It is also unfortunately that they
>> cannot be explicitly anchored so that one can refer to one
>> note from within another.  If one had those things, it might
>> actually be possible to use xml2rfc for an
>> incrementally-developed collaborative document.
> 
> +1.  Because of this I just use <t> and add square brackets.

Sure.  But, absent <t anchor="XXX"> (probably at least as hard
to even think about than it would be to implement, except
possibly as an element of a list), that leaves one without any
way to create a central way to keep track of these placeholders
and similar comments.  So IMnvHO, use of <t> [[ ... ]]</t> as a
substitute for <t><cref> ... </cref></t> is just substitution
one kludge for another one with a different set of drawbacks.

<rant>
If we really want to think about xml2rfc as the foundation for a
canonical submission format, one prerequisite, IMO, is to start
treating these kludges as serious deficiencies that need to be
fixed, rather than as little tricks that we tell each other
about and add to the oral tradition.
</rant>

    john



From nico@cryptonector.com  Mon Jul 23 11:27:44 2012
Return-Path: <nico@cryptonector.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 965A611E80D9 for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 11:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.292
X-Spam-Level: 
X-Spam-Status: No, score=-3.292 tagged_above=-999 required=5 tests=[AWL=-1.315, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mMH2QILh0lhp for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 11:27:43 -0700 (PDT)
Received: from homiemail-a72.g.dreamhost.com (caiajhbdcbef.dreamhost.com [208.97.132.145]) by ietfa.amsl.com (Postfix) with ESMTP id C86F111E80DB for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 11:27:43 -0700 (PDT)
Received: from homiemail-a72.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTP id 4F6956B007B for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 11:27:43 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=NEysucgcudVh4XAcWms/Y HShFUXfd5laPpnE8mdxD0naWjKlYVu6rCPEpcm6tp7cEHnkj2Efq0uyi7ARER8aD +6Vj2/4nn31IUyefYae2xervobsl7LdlMAlpaQnkOLdiU8zi69i5eW3yRe6YxzRk vS117KWLyYLJytIs0MCH0A=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=/sUIQJvgl/rD53U/UK+o J+IWnM8=; b=rmDJS8Sx2rtLLR7bF+ECLWEbO2oDY81JgRG1CiKe2sesYQgEHHi4 6wn3Ar37jJ3meMCUdrxog8mxm8WlOfip1ktR4fqS0o/bs4EHKycDFllNgdD2+LFk 0QdCOre2oyJiRZlbnP/SdJgQYYlMH7Gb56dMvQoIBB6oIG2zbwxKa90=
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTPSA id 353F06B0070 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 11:27:43 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so11614667pbc.31 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 11:27:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.130.67 with SMTP id oc3mr37387859pbb.18.1343068062749; Mon, 23 Jul 2012 11:27:42 -0700 (PDT)
Received: by 10.143.29.16 with HTTP; Mon, 23 Jul 2012 11:27:42 -0700 (PDT)
In-Reply-To: <BC4A11CE34FEE9CC5F4D1D06@JcK-HP8200.jck.com>
References: <20120706185656.7CEFF18C110@mercury.lcs.mit.edu> <F09D983D78ED05C0A742ABDC@JcK-HP8200.jck.com> <CAK3OfOgBbsCqf1KEBEGohe=Lq+PP86gWNHhAVuxai6kf0Wuc1Q@mail.gmail.com> <BC4A11CE34FEE9CC5F4D1D06@JcK-HP8200.jck.com>
Date: Mon, 23 Jul 2012 13:27:42 -0500
Message-ID: <CAK3OfOhpyqv+p9g6ZO9+FfqkNqkDi2aPDjn=kkHGzFbGbRbFZA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: John C Klensin <john+xml@jck.com>
Content-Type: text/plain; charset=UTF-8
Cc: xml2rfc@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [xml2rfc] xref inside cref
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 18:27:44 -0000

On Mon, Jul 23, 2012 at 1:19 PM, John C Klensin <john+xml@jck.com> wrote:
>> +1.  Because of this I just use <t> and add square brackets.
>
> Sure.  But, absent <t anchor="XXX"> (probably at least as hard
> to even think about than it would be to implement, except
> possibly as an element of a list), that leaves one without any
> way to create a central way to keep track of these placeholders
> and similar comments.  So IMnvHO, use of <t> [[ ... ]]</t> as a
> substitute for <t><cref> ... </cref></t> is just substitution
> one kludge for another one with a different set of drawbacks.

Agreed.

> <rant>
> If we really want to think about xml2rfc as the foundation for a
> canonical submission format, one prerequisite, IMO, is to start
> treating these kludges as serious deficiencies that need to be
> fixed, rather than as little tricks that we tell each other
> about and add to the oral tradition.
> </rant>

LyX has fewer such deficiencies...  Why not use that?  (I know, just
kidding, sortof, maybe.)

From julian.reschke@gmx.de  Mon Jul 23 11:33:49 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78A9911E80DF for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 11:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.26
X-Spam-Level: 
X-Spam-Status: No, score=-104.26 tagged_above=-999 required=5 tests=[AWL=-1.661, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7fvPUj5ya-no for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 11:33:48 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 2E29E11E80BF for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 11:33:47 -0700 (PDT)
Received: (qmail invoked by alias); 23 Jul 2012 18:33:46 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp039) with SMTP; 23 Jul 2012 20:33:46 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/mTn8i8bPm9nRFaWvzn0yQe2J9pUPfArrPtM9Vf1 RlK5WcbfnsVg7X
Message-ID: <500D98FC.40701@gmx.de>
Date: Mon, 23 Jul 2012 20:33:32 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: John C Klensin <john+xml@jck.com>
References: <20120706185656.7CEFF18C110@mercury.lcs.mit.edu> <F09D983D78ED05C0A742ABDC@JcK-HP8200.jck.com> <CAK3OfOgBbsCqf1KEBEGohe=Lq+PP86gWNHhAVuxai6kf0Wuc1Q@mail.gmail.com> <BC4A11CE34FEE9CC5F4D1D06@JcK-HP8200.jck.com>
In-Reply-To: <BC4A11CE34FEE9CC5F4D1D06@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [xml2rfc] xref inside cref
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 18:33:49 -0000

On 2012-07-23 20:19, John C Klensin wrote:
>
>
> --On Monday, July 23, 2012 12:42 -0500 Nico Williams
> <nico@cryptonector.com> wrote:
>
>> On Mon, Jul 23, 2012 at 12:15 PM, John C Klensin
>> <john+xml@jck.com> wrote:
>>> For a variety of reasons, it is a lot more than mildly
>>> unfortunate that <cref>s cannot contain just about anything
>>> that <t> can contain, including <list> and <vspace> elements
>>> as well as <xref> ones.  It is also unfortunately that they
>>> cannot be explicitly anchored so that one can refer to one
>>> note from within another.  If one had those things, it might
>>> actually be possible to use xml2rfc for an
>>> incrementally-developed collaborative document.
>>
>> +1.  Because of this I just use <t> and add square brackets.
>
> Sure.  But, absent <t anchor="XXX"> (probably at least as hard
> to even think about than it would be to implement, except
> possibly as an element of a list), that leaves one without any
> way to create a central way to keep track of these placeholders
> and similar comments.  So IMnvHO, use of <t> [[ ... ]]</t> as a
> substitute for <t><cref> ... </cref></t> is just substitution
> one kludge for another one with a different set of drawbacks.

<cref> *does* take an anchor attribute; what's missing is a way to 
<xref>erence them.

> <rant>
> If we really want to think about xml2rfc as the foundation for a
> canonical submission format, one prerequisite, IMO, is to start
> treating these kludges as serious deficiencies that need to be
> fixed, rather than as little tricks that we tell each other
> about and add to the oral tradition.
> </rant>

Indeed.

I've been working on experimental extensions for years, see 
<http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#extensions>; 
but I'm not going to implement in the old TCL code.

The plan was that the new, python-based xml2rfc processor *can* be 
extended more easily; hopefully we'll get there soon (it appears that 
the RFC Production Center hasn't made the switch yet).

Best regards, Julian


From duerst@it.aoyama.ac.jp  Mon Jul 23 18:29:32 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03BBB11E80F3 for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 18:29:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.304
X-Spam-Level: 
X-Spam-Status: No, score=-100.304 tagged_above=-999 required=5 tests=[AWL=-0.514, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jqrzp6aZo8Jn for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 18:29:31 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 7C0B411E8085 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 18:29:30 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q6O1TT8w026011 for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 10:29:29 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 1b6e_7210_03584694_d52f_11e1_a061_001d096c5782; Tue, 24 Jul 2012 10:29:29 +0900
Received: from [IPv6:::1] ([133.2.210.1]:48006) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15E6A90> for <xml2rfc@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 24 Jul 2012 10:29:32 +0900
Message-ID: <500DFA74.5030002@it.aoyama.ac.jp>
Date: Tue, 24 Jul 2012 10:29:24 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Nico Williams <nico@cryptonector.com>
References: <E771C8390C019AD8BE07CA8B@JcK-HP8200.jck.com> <CAK3OfOgX56OPrnynZ57G_t62kAjasgUbyTTOHaPY_BXa3D9zww@mail.gmail.com>
In-Reply-To: <CAK3OfOgX56OPrnynZ57G_t62kAjasgUbyTTOHaPY_BXa3D9zww@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: xml2rfc list <xml2rfc@ietf.org>, John C Klensin <john+xml@jck.com>
Subject: [xml2rfc] lyx2xml2rfc (was: Re:  RFC-like documents)
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 01:29:32 -0000

On 2012/07/24 2:40, Nico Williams wrote:

> I've used it before for docs that have nothing to do with the IETF,
> due to my [then] liking the xml2rfc schema well enough.  Nowadays I
> seem to have a mild love affair with LyX, so I've been using
> lyx2xml2rfc to format I-Ds, and formatting private docs directly is
> trivial.

I have tried to find  lyx2xml2rfc, but google says "Your search - 
lyx2xml2rfc - did not match any documents.".

Any hints?

Regards,   Martin.

From nico@cryptonector.com  Mon Jul 23 18:37:32 2012
Return-Path: <nico@cryptonector.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C1ED11E80F3 for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 18:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.126
X-Spam-Level: 
X-Spam-Status: No, score=-3.126 tagged_above=-999 required=5 tests=[AWL=-1.449, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mQH3tjeZjyyV for <xml2rfc@ietfa.amsl.com>; Mon, 23 Jul 2012 18:37:31 -0700 (PDT)
Received: from homiemail-a95.g.dreamhost.com (caiajhbdcagg.dreamhost.com [208.97.132.66]) by ietfa.amsl.com (Postfix) with ESMTP id EE01411E80E2 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 18:37:31 -0700 (PDT)
Received: from homiemail-a95.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a95.g.dreamhost.com (Postfix) with ESMTP id 7ECD51E059 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 18:37:31 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; q=dns; s= cryptonector.com; b=uqr5lZd5mYWVK+hJ7adRqdCo7nh+9Bn1BP1EvRxuyg4O ewpKVtq7/zPX6gzejThekXFu62XgLbqRNljgq+eZYnBRR6KwykVJfdGnpe2Eoivs +i+k+X7g07+zoXnOHJ/CVDVNfq+I/hcXv4BgYOw4k7KAdNsUjxquhlIyH/n47q0=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type:content-transfer-encoding; s= cryptonector.com; bh=SFnxbhgU1AcG8+9hDZBJ+/uZJoM=; b=GqK35QbMJqz ZS4W8ko4rKpswBNxU8j4zFSH57wc4ij5vygSej6SgQ21Y9uICkcV3Agdflmq5oAu 19WUy8ke4RaxykiW0QXj0JbLOQckNMERKSzRRJ+SUQnXVVv3ZKf0CDer8BRvr2AO AM3rVkjy/6HOlMQrayXQJaGxo4THkaUM=
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a95.g.dreamhost.com (Postfix) with ESMTPSA id 631FC1E00B for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 18:37:31 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so12129030pbc.31 for <xml2rfc@ietf.org>; Mon, 23 Jul 2012 18:37:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.221.227 with SMTP id qh3mr40067358pbc.115.1343093851012; Mon, 23 Jul 2012 18:37:31 -0700 (PDT)
Received: by 10.143.29.16 with HTTP; Mon, 23 Jul 2012 18:37:30 -0700 (PDT)
In-Reply-To: <500DFA74.5030002@it.aoyama.ac.jp>
References: <E771C8390C019AD8BE07CA8B@JcK-HP8200.jck.com> <CAK3OfOgX56OPrnynZ57G_t62kAjasgUbyTTOHaPY_BXa3D9zww@mail.gmail.com> <500DFA74.5030002@it.aoyama.ac.jp>
Date: Mon, 23 Jul 2012 20:37:30 -0500
Message-ID: <CAK3OfOiUCTaHR5fhu=fFPmp_b_vG4bi9zn-oOtJV4Be-uPVW2Q@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: =?UTF-8?Q?Martin_J=2E_D=C3=BCrst?= <duerst@it.aoyama.ac.jp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: xml2rfc list <xml2rfc@ietf.org>, John C Klensin <john+xml@jck.com>
Subject: Re: [xml2rfc] lyx2xml2rfc (was: Re:  RFC-like documents)
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 01:37:32 -0000

On Mon, Jul 23, 2012 at 8:29 PM, "Martin J. D=C3=BCrst"
<duerst@it.aoyama.ac.jp> wrote:
> I have tried to find  lyx2xml2rfc, but google says "Your search -
> lyx2xml2rfc - did not match any documents.".

I misremembered the name of the script, which is lyx2rfc.  Heh.

https://github.com/nicowilliams/lyx2rfc

You need LyX 2.0.0 or higher (2.0.4 has a fix for a bug that I work
around in the XSLT; I've not tested 2.0.4 but I expect it to work).
You also need Saxon or some other XSLT 2.0 processor.  You may need to
play with the lyx2rfc script to get it to work for you.

Anyways, there's a test I-D and output in that git repo.  Larger,
actual I-Ds written with LyX can be found here:

https://github.com/nicowilliams/httpbisIDs

Nico
--

From brian.e.carpenter@gmail.com  Tue Jul 24 00:19:59 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6F6C21F858F for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 00:19:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.371
X-Spam-Level: 
X-Spam-Status: No, score=-101.371 tagged_above=-999 required=5 tests=[AWL=0.320, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TpP3XRMUBlDS for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 00:19:59 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id A27F221F858D for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 00:19:58 -0700 (PDT)
Received: by bkty7 with SMTP id y7so5676847bkt.31 for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 00:19:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1+SN23vr3ocHyp1Hh4edPKGoQlcwpeEzNrr4BEG1/m4=; b=cLvAcMOg0dnYBoR19LmGbzlck84WcGG9ettTzzppx45ybZsAsa+0XNMBjlenMsrxlM QJ0WNwvzq5INMG6D+YOhi69p/PFSvM/CTH9d1ZTr8Sr2mD4rnJnL0NBz64bSjBcQWbFp M9cianqWJyIUNTthqKJJ4K5+q9G+O7TKpfsr5MPOD7kp0p2tZldxYiBxQBlohpdeCvn5 IT5qbI5PzlT6R7VdIpHHxsZeNVgavNtJNzCWswRLwQIzjUwC2/Y6kNx6aMGwFXmXVZbO R57Et4w6OKVXtX5tfBvBB1G/DPz+ybJrvQYtimdlaPx8QrKURA90GiZkNj7nkh3wBA4O 7szg==
Received: by 10.204.130.156 with SMTP id t28mr9776757bks.33.1343114397598; Tue, 24 Jul 2012 00:19:57 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-218-212.as13285.net. [2.102.218.212]) by mx.google.com with ESMTPS id g6sm9505827bkg.2.2012.07.24.00.19.54 (version=SSLv3 cipher=OTHER); Tue, 24 Jul 2012 00:19:55 -0700 (PDT)
Message-ID: <500E4C97.8070907@gmail.com>
Date: Tue, 24 Jul 2012 08:19:51 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john+xml@jck.com>
References: <E771C8390C019AD8BE07CA8B@JcK-HP8200.jck.com>
In-Reply-To: <E771C8390C019AD8BE07CA8B@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: xml2rfc list <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] RFC-like documents
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 07:19:59 -0000

John,

I don't know exactly which features you want to eliminate, but the page at
http://www.ietf.org/about/process-docs.html
is produced using xml2rfc, and I just checked that the source file
works with the pre-release at http://xml.resource.org/experimental.html

The special bits I see in the source are:

<?rfc topblock="no"?>        <!-- Don't want the RFC boilerplate -->
<?rfc private="procdocs"?>

<!-- This line seems to be required but is irrelevant since it isn't an RFC -->
<rfc ipr="trust200902" docName=" ">

<!-- We don't want an Author's Address section but this element is compulsory in the DTD. -->
<!-- You will need to delete the string "Author's Address" from the output file (twice).  -->
<author initials=" " surname=" " fullname=" "/>


And between </abstract> and  </front> :

 <note title="Administrivia">
 <t><list>
  <t>Date: 2012-06-12</t>
  <t>Document editor: Brian Carpenter</t>
  <t>Discussion forum: ietf@ietf.org</t>
 </list></t>
 </note>

which is a remnant of the ad hoc format invented for IONs a few years ago.

Regards
   Brian

On 23/07/2012 18:32, John C Klensin wrote:
> Hi.
> 
> When XML2RFC was first designed, the target audience was RFCs,
> I-Ds, and other documents "like" them.  It was used to produce
> several such documents of some utility to the IETF community.
> It appears that the new version now has enough checks for I-D
> and RFC formats that there is no more "like" -- one gets either
> I-D format or RFC format with all of the associated front and
> back boilerplate or one gets nothing at all?
> 
> Perhaps there is a processing directive to overcome that, but,
> if so, I can't find it.
> 
> So...
> 
> (1) Is the elimination of RFC-like documents that are neither
> RFCs nor I-Ds intentional or was it an accidental side-effect of
> putting in additional checking?
> 
> (2) Is there a processing directive that would permit more
> general documents that follow the general RFC/I-D style but are
> neither.
> 
> (3) As a generalization of (2), is there a comprehensive list of
> available processing directives and what they do (other than
> scattered through various templates) and, if so, where is it and
> can we get a prominent link to it from the
> http://xml.resource.org/ home page?
> 
>    best,
>     john
> 
> p.s. For anyone who can't answer or understand the above
> questions without a use case, I decided to try to render the
> latest IESG "shepherd write up" form into something that could
> be processed and read properly.  Since much of the relevant part
> of the community is familiar with xml2rfc, it seemed like an
> obvious candidate.  But that apparently cannot be done without
> faking an RFC and then post-processing the document to eliminate
> a lot of irrelevant material in the front and back.
> 
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
> .
> 

From john+xml@jck.com  Tue Jul 24 08:25:13 2012
Return-Path: <john+xml@jck.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E85C621F8503 for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 08:25:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level: 
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e7RvEDiLCBqW for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 08:25:12 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A75E621F84FE for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 08:25:12 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john+xml@jck.com>) id 1StgtU-0007nP-OM; Tue, 24 Jul 2012 11:19:28 -0400
Date: Tue, 24 Jul 2012 11:24:58 -0400
From: John C Klensin <john+xml@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <A63C9BAACD62389312D26131@JcK-HP8200.jck.com>
In-Reply-To: <500E4C97.8070907@gmail.com>
References: <E771C8390C019AD8BE07CA8B@JcK-HP8200.jck.com> <500E4C97.8070907@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: xml2rfc list <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] RFC-like documents
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 15:25:14 -0000

Brian,

Huge help -- thank you.  I've verified this with a few
additional tweaks against both the installed version of xml2rfc
(in "Strict" mode) and with the experimental one.  A few
comments inline below.


--On Tuesday, July 24, 2012 08:19 +0100 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> John,
> 
> I don't know exactly which features you want to eliminate, but
> the page at http://www.ietf.org/about/process-docs.html
> is produced using xml2rfc, and I just checked that the source
> file works with the pre-release at
> http://xml.resource.org/experimental.html
> 
> The special bits I see in the source are:
> 
> <?rfc topblock="no"?>
>  <!-- Don't want the RFC boilerplate --> 
>  <?rfc private="procdocs"?>

Of course, this points out (again) the importance of having a
list of processing directives and explanations of their actions
as part of the xml2rfc document set.

> <!-- This line seems to be required but is irrelevant since it
> isn't an RFC --> <rfc ipr="trust200902" docName=" ">
> 
> <!-- We don't want an Author's Address section but this
> element is compulsory in the DTD. --> <!-- You will need to
> delete the string "Author's Address" from the output file
> (twice).  --> <author initials=" " surname=" " fullname=" "/>

A <title> element is also needed, but an <abstract> is not.  I
found it worked more smoothly to put content in the title
element and then to make the title attribute in <note> empty.

> And between </abstract> and  </front> :
> 
>  <note title="Administrivia">
>  <t><list>
>   <t>Date: 2012-06-12</t>
>   <t>Document editor: Brian Carpenter</t>
>   <t>Discussion forum: ietf@ietf.org</t>
>  </list></t>
>  </note>
> 
> which is a remnant of the ad hoc format invented for IONs a
> few years ago.

I've now got a working Shepherd Report template based on the
IESG's latest form.  If others would find it useful and someone
from the xml2rfc or Tools teams wants to post it somewhere, I'll
be happy to supply it (I'll repeat this offer on the WGChairs
list).

best,
    john



From nico@cryptonector.com  Tue Jul 24 08:32:54 2012
Return-Path: <nico@cryptonector.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCF6B21F84A0 for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 08:32:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.258
X-Spam-Level: 
X-Spam-Status: No, score=-3.258 tagged_above=-999 required=5 tests=[AWL=-1.281, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JNPIzW79O9VZ for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 08:32:54 -0700 (PDT)
Received: from homiemail-a73.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by ietfa.amsl.com (Postfix) with ESMTP id 561C221F864C for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 08:32:54 -0700 (PDT)
Received: from homiemail-a73.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a73.g.dreamhost.com (Postfix) with ESMTP id 63CAF1F0088 for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 08:32:52 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=VCz97CNyEDVFPrYGPkhKA DpqLis7+GyQpWKmmbhSMAHtK0EpUC+7D5BErMMUDJTDq7qvr6y7c6SCquG6UK31F q/tmf2tA970DwSiFywScOMuuxGK8fIxXLvu9YiExjchkFF8GNqSa+vOr83ANfrEx kSDoXW3dpuFkXosHopaW3g=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=lYYDcCWlq+ZUHf9nDHo/ SoUgNAY=; b=eOP6NIDfldSu5WXBl72Sl54sWj2faf+78d7Mvgwq730Xf0wnx1SV poUe+vV6um4/qxLbqoBtf9r9O3IE9YleWa/HhIyFMLhst7lIAxMLSo8tbfHYUZ9W 0AL9hfA95sFAHpvnE/4GdbdKCuITK70qHZ4U555DVdTuVU/W+yIWBfU=
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a73.g.dreamhost.com (Postfix) with ESMTPSA id 3EE051F0086 for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 08:32:52 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so13231514pbc.31 for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 08:32:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.221.227 with SMTP id qh3mr45273226pbc.115.1343143971918; Tue, 24 Jul 2012 08:32:51 -0700 (PDT)
Received: by 10.143.29.16 with HTTP; Tue, 24 Jul 2012 08:32:51 -0700 (PDT)
In-Reply-To: <A63C9BAACD62389312D26131@JcK-HP8200.jck.com>
References: <E771C8390C019AD8BE07CA8B@JcK-HP8200.jck.com> <500E4C97.8070907@gmail.com> <A63C9BAACD62389312D26131@JcK-HP8200.jck.com>
Date: Tue, 24 Jul 2012 10:32:51 -0500
Message-ID: <CAK3OfOgVBMPE6FUFn4QZbiB-OvejuxmVN96Tt2kxdUotEFyVkQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: John C Klensin <john+xml@jck.com>
Content-Type: text/plain; charset=UTF-8
Cc: xml2rfc list <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] RFC-like documents
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 15:32:54 -0000

On Tue, Jul 24, 2012 at 10:24 AM, John C Klensin <john+xml@jck.com> wrote:
> Of course, this points out (again) the importance of having a
> list of processing directives and explanations of their actions
> as part of the xml2rfc document set.

http://xml.resource.org/authoring/README.html#anchor7

But yeah, they ought to be listed here instead:

http://xml.resource.org/authoring/draft-mrose-writing-rfcs.html

From julian.reschke@gmx.de  Tue Jul 24 08:44:01 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C52F21F8599 for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 08:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.24
X-Spam-Level: 
X-Spam-Status: No, score=-104.24 tagged_above=-999 required=5 tests=[AWL=-1.641, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0buIlxm+1MyF for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 08:44:00 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id DD66821F858F for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 08:43:59 -0700 (PDT)
Received: (qmail invoked by alias); 24 Jul 2012 15:43:58 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp010) with SMTP; 24 Jul 2012 17:43:58 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX189My0pNWA9L6r9hGsSsKFv0Dtfklt92dhcan6tAo 1Jn0SCwMF72qTj
Message-ID: <500EC296.3000109@gmx.de>
Date: Tue, 24 Jul 2012 17:43:18 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Nico Williams <nico@cryptonector.com>
References: <E771C8390C019AD8BE07CA8B@JcK-HP8200.jck.com> <500E4C97.8070907@gmail.com> <A63C9BAACD62389312D26131@JcK-HP8200.jck.com> <CAK3OfOgVBMPE6FUFn4QZbiB-OvejuxmVN96Tt2kxdUotEFyVkQ@mail.gmail.com>
In-Reply-To: <CAK3OfOgVBMPE6FUFn4QZbiB-OvejuxmVN96Tt2kxdUotEFyVkQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc list <xml2rfc@ietf.org>, John C Klensin <john+xml@jck.com>
Subject: Re: [xml2rfc] RFC-like documents
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 15:44:01 -0000

On 2012-07-24 17:32, Nico Williams wrote:
> On Tue, Jul 24, 2012 at 10:24 AM, John C Klensin <john+xml@jck.com> wrote:
>> Of course, this points out (again) the importance of having a
>> list of processing directives and explanations of their actions
>> as part of the xml2rfc document set.
>
> http://xml.resource.org/authoring/README.html#anchor7
>
> But yeah, they ought to be listed here instead:
>
> http://xml.resource.org/authoring/draft-mrose-writing-rfcs.html

Processing directives are not part of the vocabulary; they are just a 
way to influence the behavior of specific implementations. As such, they 
need to be describes separately from the vocabulary.

If we find that some PIs are so valuable that they should be "standard" 
then we ought to extend the vocabulary accordingly.

Best regards, Julian


From john+xml@jck.com  Tue Jul 24 08:45:33 2012
Return-Path: <john+xml@jck.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E416F21F85AC for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 08:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.339
X-Spam-Level: 
X-Spam-Status: No, score=-2.339 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tiBafCJ7Suru for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 08:45:33 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5F33821F85A8 for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 08:45:33 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john+xml@jck.com>) id 1SthDA-0007sX-Q6; Tue, 24 Jul 2012 11:39:48 -0400
Date: Tue, 24 Jul 2012 11:45:18 -0400
From: John C Klensin <john+xml@jck.com>
To: Nico Williams <nico@cryptonector.com>
Message-ID: <53BD567A3EF6F5E9C254007E@JcK-HP8200.jck.com>
In-Reply-To: <CAK3OfOgVBMPE6FUFn4QZbiB-OvejuxmVN96Tt2kxdUotEFyVkQ@mail.gmail.com>
References: <E771C8390C019AD8BE07CA8B@JcK-HP8200.jck.com> <500E4C97.8070907@gmail.com> <A63C9BAACD62389312D26131@JcK-HP8200.jck.com> <CAK3OfOgVBMPE6FUFn4QZbiB-OvejuxmVN96Tt2kxdUotEFyVkQ@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: xml2rfc list <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] RFC-like documents
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 15:45:34 -0000

--On Tuesday, July 24, 2012 10:32 -0500 Nico Williams
<nico@cryptonector.com> wrote:

> On Tue, Jul 24, 2012 at 10:24 AM, John C Klensin
> <john+xml@jck.com> wrote:
>> Of course, this points out (again) the importance of having a
>> list of processing directives and explanations of their
>> actions as part of the xml2rfc document set.
> 
> http://xml.resource.org/authoring/README.html#anchor7
> 
> But yeah, they ought to be listed here instead:
> 
> http://xml.resource.org/authoring/draft-mrose-writing-rfcs.html

Or, at least, http://xml.resource.org/ and
http://xml.resource.org/experimental.html should clearly
indicate that the README file isn't just information about a
specific version (which is what the language implies) but also
contains significant documentation.  Of course, the README file
for the experimental version isn't even that -- it points back
to the production version's file and more or less starts by
saying "You need to have Tcl/Tk version 8 running on your
system".   My mind may just be getting fuzzy, but it didn't
occur to me to look there.  Using this tool should not be a
maze-navigation test.

thanks.
    john






From nico@cryptonector.com  Tue Jul 24 09:15:36 2012
Return-Path: <nico@cryptonector.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6BE821F85C2 for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 09:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.243
X-Spam-Level: 
X-Spam-Status: No, score=-3.243 tagged_above=-999 required=5 tests=[AWL=-1.266, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id doQsfr5wjCRf for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 09:15:36 -0700 (PDT)
Received: from homiemail-a85.g.dreamhost.com (caiajhbdcbbj.dreamhost.com [208.97.132.119]) by ietfa.amsl.com (Postfix) with ESMTP id 13FF821F855F for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 09:15:34 -0700 (PDT)
Received: from homiemail-a85.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a85.g.dreamhost.com (Postfix) with ESMTP id AFC2ABC049 for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 09:15:33 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=ErUgLCZb9oLhSfOquIEJN Fn3YGL7s8kw7LITUN8NWRT5E0EQ5v6wCXYf8+rpA435e5TTZLtfJwKClLdazyZM+ QfF15MyU7gRAgxBiI6JJwuUY5Y/ArcbKZVqVtaFQFgtQwnYt3/7f9MTbqTD/AGx2 VuvPB8jAszo5vs9jOen3xE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=8xLsgGsAbkdpanrmqgSn hUYt1VE=; b=j89u/sEoZob8xev+bTtu1B9QonjxppvC9MaOawERlfsbdPsl8w1M 7yMBgJ4Mh8i0ow1+6u6jMmsgC67vt+cHOnZKdzrM/6fKvxtC5b+YU3OMkqFIFAuX fKq7jC971xmBw66f5GVKG1Bd+QjOz+wCqaLXrPSLQ05Mzz6J3Q/6SKo=
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a85.g.dreamhost.com (Postfix) with ESMTPSA id 964D4BC042 for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 09:15:33 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so13285008pbc.31 for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 09:15:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.222.40 with SMTP id qj8mr45545227pbc.139.1343146533296; Tue, 24 Jul 2012 09:15:33 -0700 (PDT)
Received: by 10.143.29.16 with HTTP; Tue, 24 Jul 2012 09:15:33 -0700 (PDT)
In-Reply-To: <500EC296.3000109@gmx.de>
References: <E771C8390C019AD8BE07CA8B@JcK-HP8200.jck.com> <500E4C97.8070907@gmail.com> <A63C9BAACD62389312D26131@JcK-HP8200.jck.com> <CAK3OfOgVBMPE6FUFn4QZbiB-OvejuxmVN96Tt2kxdUotEFyVkQ@mail.gmail.com> <500EC296.3000109@gmx.de>
Date: Tue, 24 Jul 2012 11:15:33 -0500
Message-ID: <CAK3OfOgo7DO7wFKTjCn3jDUEySTrrw4yzSAWyeawjwyvoLug2A@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=UTF-8
Cc: xml2rfc list <xml2rfc@ietf.org>, John C Klensin <john+xml@jck.com>
Subject: Re: [xml2rfc] RFC-like documents
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 16:15:36 -0000

On Tue, Jul 24, 2012 at 10:43 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
>> But yeah, they ought to be listed here instead:
>>
>> http://xml.resource.org/authoring/draft-mrose-writing-rfcs.html
>
> Processing directives are not part of the vocabulary; they are just a way to
> influence the behavior of specific implementations. As such, they need to be
> describes separately from the vocabulary.

Well, users could care less whether PIs are part of the schema,
vocabulary, whatever.  Users shouldn't have to think like developers
in order to find answers to questions.  What this means is that there
should be a link from one document to the other, or an FAQ, or some
sort of breadcrumb if the developer insists on purity in the
documentation (which is quite fair).

> If we find that some PIs are so valuable that they should be "standard" then
> we ought to extend the vocabulary accordingly.

Certainly for boilerplate!  I think it'd be a lot better to have
<boilerplate> tags that we could use to include standard and
user-defined boilerplate.  The ToC control PIs could probably be moved
into a <toc> tag.  Other PIs like artworkdelimiter, say, docmapping,
needLines, and so on should remain PIs.

A complete list of PIs that should move into the schema would take a
little more work, but not much.  Implementing that should -surely-
require a lot more work.

Nico
--

From john+xml@jck.com  Tue Jul 24 09:39:46 2012
Return-Path: <john+xml@jck.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8028511E8086 for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 09:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.217,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c2mXnsTi-cXP for <xml2rfc@ietfa.amsl.com>; Tue, 24 Jul 2012 09:39:45 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C3BA311E8099 for <xml2rfc@ietf.org>; Tue, 24 Jul 2012 09:39:45 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john+xml@jck.com>) id 1Sti3d-00083o-4R; Tue, 24 Jul 2012 12:34:01 -0400
Date: Tue, 24 Jul 2012 12:39:31 -0400
From: John C Klensin <john+xml@jck.com>
To: Nico Williams <nico@cryptonector.com>, Julian Reschke <julian.reschke@gmx.de>
Message-ID: <151C6291AA78953C0FF34336@JcK-HP8200.jck.com>
In-Reply-To: <CAK3OfOgo7DO7wFKTjCn3jDUEySTrrw4yzSAWyeawjwyvoLug2A@mail.gmail.com>
References: <E771C8390C019AD8BE07CA8B@JcK-HP8200.jck.com> <500E4C97.8070907@gmail.com> <A63C9BAACD62389312D26131@JcK-HP8200.jck.com> <CAK3OfOgVBMPE6FUFn4QZbiB-OvejuxmVN96Tt2kxdUotEFyVkQ@mail.gmail.com> <500EC296.3000109@gmx.de> <CAK3OfOgo7DO7wFKTjCn3jDUEySTrrw4yzSAWyeawjwyvoLug2A@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: xml2rfc list <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] RFC-like documents
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 16:39:46 -0000

--On Tuesday, July 24, 2012 11:15 -0500 Nico Williams
<nico@cryptonector.com> wrote:

> On Tue, Jul 24, 2012 at 10:43 AM, Julian Reschke
> <julian.reschke@gmx.de> wrote:
>...
>> Processing directives are not part of the vocabulary; they
>> are just a way to influence the behavior of specific
>> implementations. As such, they need to be describes
>> separately from the vocabulary.
> 
> Well, users could care less whether PIs are part of the schema,
> vocabulary, whatever.  Users shouldn't have to think like
> developers in order to find answers to questions.  What this
> means is that there should be a link from one document to the
> other, or an FAQ, or some sort of breadcrumb if the developer
> insists on purity in the documentation (which is quite fair).

Nico, I actually agree with Julian that some purity is in order.
Using your terminology, I think the problem is with the
breadcrumbs.  As something that wouldn't require touching code
and that would presumably take five minutes for someone with the
needed access, the home page now says:

	"...(using the format defined in RFC 2629 and its
	unofficial successor) and see how the results...
	look-and-feel."
	
and

	"...Version 1.36 is available. Here's the README file."
	
If those two statements were changed to, e.g.,

	"...(using the format and XML vocabulary defined in the
	successor to the original specification in RFC 2629, and
	see how the results... look-and-feel.  Information on
	using the program, including a description of processing
	directives, appears in a README file."

That is, IMO, roughly a 90% solution to the problem.  Would I
like to see release notes, program compilation and operation
hints, and those processing directives in separate files?  Could
the above be made much more clear by rearranging the page format
somewhat?  Yes to both.  But, if there is a choice, I'd rather
see energy put into getting the "experimental" version working
than into that sort of cosmetic work.  

Put differently "that could be organized better" is, IMO, a
feature enhancement request, while "I can't find a clue as to
where to find that particular critical information" is a bug.

And yes, Julian, I suspect that belongs in the tracker, except
it still won't let me log in.

    john


best,
  john



