
From csimbi@gmail.com  Sat Dec  1 06:29:27 2012
Return-Path: <csimbi@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 6E7DE11E8099 for <xml2rfc@ietfa.amsl.com>; Sat,  1 Dec 2012 06:29:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.632
X-Spam-Level: 
X-Spam-Status: No, score=-1.632 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wvVSCzQSuXmz for <xml2rfc@ietfa.amsl.com>; Sat,  1 Dec 2012 06:29:27 -0800 (PST)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by ietfa.amsl.com (Postfix) with ESMTP id C659811E8097 for <xml2rfc@ietf.org>; Sat,  1 Dec 2012 06:29:26 -0800 (PST)
Received: by mail-wi0-f180.google.com with SMTP id hj13so228330wib.13 for <xml2rfc@ietf.org>; Sat, 01 Dec 2012 06:29:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=RRZZGaDqzb0Xgln2vDxOvvwmyiQzDiRsLT/WLt+Jj2Q=; b=l5MEfdIS7J8ctXsCq/346oD0DuWMLZ8f1eepxx306GFz6LsOrSdHiZwA6IXgfagR38 yjaYQsu6IhBLq0Mk5+04ZopYAwhW9lwjjrPkYcAAbeQjx7Aiy2LzsPoE7tsOLUzEoSyl tSnnpU3y6Tf/bJw8YS2uPKDW3jonTuGgxj1jxch6Dz9b/O6U9a1XodLQegLGjoJrcCnQ l2UJd6bYVGhhmGi4vV0aUmCBqswdU512BxN7agMcjt//P7VJ5vSpGMtgnL3R5AC2iSET zzh2snvddM3IrRPoikHYU2tRHNH2ZKDCTy183B4ln23uktiuey8Wgh9O9VLmRNHVH1Um LGeg==
Received: by 10.216.82.139 with SMTP id o11mr1518822wee.105.1354372165876; Sat, 01 Dec 2012 06:29:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.191.23 with HTTP; Sat, 1 Dec 2012 06:29:05 -0800 (PST)
In-Reply-To: <50B9699E.1090606@computer.org>
References: <50B9699E.1090606@computer.org>
From: =?UTF-8?B?Wm9sdMOhbiDDlnJkw7ZnaCAoR01haWwp?= <csimbi@gmail.com>
Date: Sat, 1 Dec 2012 09:29:05 -0500
Message-ID: <CAF2Bc5wxahYRr5VVy8sgbRTK20K5CJZ97Gr3L-YpxBNvTYTpdQ@mail.gmail.com>
To: "Charles E. Perkins" <charliep@computer.org>
Content-Type: multipart/alternative; boundary=001636d34400d73dcf04cfcb5714
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Page break in xml2rfc
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: Sat, 01 Dec 2012 14:29:27 -0000

--001636d34400d73dcf04cfcb5714
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

While at it:
How do I repeat table heading accross pages?
Thanks!

Best regards: Zolt=C3=A1n =C3=96rd=C3=B6gh


On Fri, Nov 30, 2012 at 9:21 PM, Charles E. Perkins
<charliep@computer.org>wrote:

>
> Hello folks,
>
> How do I get a page break in xml2rfc?
>
> Alternatively, how do I protect a table from getting
> a page break in the middle?
>
> --
> Regards,
> Charlie P.
>
> ______________________________**_________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/**listinfo/xml2rfc<https://www.ietf.org/mail=
man/listinfo/xml2rfc>
>

--001636d34400d73dcf04cfcb5714
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

While at it:<br>How do I repeat table heading accross pages?<br>Thanks!<br =
clear=3D"all"><br>Best regards: Zolt=C3=A1n =C3=96rd=C3=B6gh<br>
<br><br><div class=3D"gmail_quote">On Fri, Nov 30, 2012 at 9:21 PM, Charles=
 E. Perkins <span dir=3D"ltr">&lt;<a href=3D"mailto:charliep@computer.org" =
target=3D"_blank">charliep@computer.org</a>&gt;</span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">

<br>
Hello folks,<br>
<br>
How do I get a page break in xml2rfc?<br>
<br>
Alternatively, how do I protect a table from getting<br>
a page break in the middle?<span class=3D"HOEnZb"><font color=3D"#888888"><=
br>
<br>
-- <br>
Regards,<br>
Charlie P.<br>
<br>
______________________________<u></u>_________________<br>
xml2rfc mailing list<br>
<a href=3D"mailto:xml2rfc@ietf.org" target=3D"_blank">xml2rfc@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/xml2rfc" target=3D"_blank"=
>https://www.ietf.org/mailman/<u></u>listinfo/xml2rfc</a><br>
</font></span></blockquote></div><br>

--001636d34400d73dcf04cfcb5714--

From julian.reschke@gmx.de  Sun Dec  2 03:55:13 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 D600421F8B00 for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 03:55:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.449
X-Spam-Level: 
X-Spam-Status: No, score=-106.449 tagged_above=-999 required=5 tests=[AWL=-4.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 215y6QT8HSjL for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 03:55:08 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 8999821F859D for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 01:42:54 -0800 (PST)
Received: (qmail invoked by alias); 02 Dec 2012 09:41:37 -0000
Received: from p5DD94F39.dip.t-dialin.net (EHLO [192.168.2.117]) [93.217.79.57] by mail.gmx.net (mp004) with SMTP; 02 Dec 2012 10:41:37 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18TDoJ8JOcTaqlZwBRTI4oQA0vjlr3TF1BgNfn57E KnSDhSA+S0Bm+W
Message-ID: <50BB2251.3070606@gmx.de>
Date: Sun, 02 Dec 2012 10:41:37 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Zolt=E1n_=D6rd=F6gh_=28GMail=29=22?= <csimbi@gmail.com>
References: <50B9699E.1090606@computer.org> <CAF2Bc5wxahYRr5VVy8sgbRTK20K5CJZ97Gr3L-YpxBNvTYTpdQ@mail.gmail.com>
In-Reply-To: <CAF2Bc5wxahYRr5VVy8sgbRTK20K5CJZ97Gr3L-YpxBNvTYTpdQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: "Charles E. Perkins" <charliep@computer.org>, xml2rfc@ietf.org
Subject: Re: [xml2rfc] Page break in xml2rfc
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: Sun, 02 Dec 2012 11:55:13 -0000

I wouldn't worry about page breaks; when the document is published as 
RFC, the RFC editor team will take care about the final formatting.

(The same applies to table headers).

Best regards, Julian

On 2012-12-01 15:29, Zoltán Ördögh (GMail) wrote:
> While at it:
> How do I repeat table heading accross pages?
> Thanks!
>
> Best regards: Zoltán Ördögh
>
>
> On Fri, Nov 30, 2012 at 9:21 PM, Charles E. Perkins
> <charliep@computer.org <mailto:charliep@computer.org>> wrote:
>
>
>     Hello folks,
>
>     How do I get a page break in xml2rfc?
>
>     Alternatively, how do I protect a table from getting
>     a page break in the middle?
>
>     --
>     Regards,
>     Charlie P.
>
>     _________________________________________________
>     xml2rfc mailing list
>     xml2rfc@ietf.org <mailto:xml2rfc@ietf.org>
>     https://www.ietf.org/mailman/__listinfo/xml2rfc
>     <https://www.ietf.org/mailman/listinfo/xml2rfc>
>
>
>
>
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
>


From charliep@computer.org  Sun Dec  2 07:24:39 2012
Return-Path: <charliep@computer.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 19A8C21F855A for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 07:24:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Neq5LQFOorw for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 07:24:34 -0800 (PST)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id AB1CE21F84FB for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 07:24:34 -0800 (PST)
Received: from [99.51.72.196] (helo=[192.168.1.84]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charliep@computer.org>) id 1TfBPE-0000W0-S2; Sun, 02 Dec 2012 10:24:32 -0500
Message-ID: <50BB72A8.5080101@computer.org>
Date: Sun, 02 Dec 2012 07:24:24 -0800
From: "Charles E. Perkins" <charliep@computer.org>
Organization: Saratoga Blue Skies
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <50B9699E.1090606@computer.org> <CAF2Bc5wxahYRr5VVy8sgbRTK20K5CJZ97Gr3L-YpxBNvTYTpdQ@mail.gmail.com> <50BB2251.3070606@gmx.de>
In-Reply-To: <50BB2251.3070606@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956d5d4673fe7faad86d1bbd87872f53b20d6f655d38250c554350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Page break in xml2rfc
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: Sun, 02 Dec 2012 15:24:39 -0000

Hello Julian,

I get your point.  But RFC publication is the last step in the process.
In the meantime, there are many months or years of review and
revision, and each time anyone reads the document, it would be
easier if the formatting were done properly.  To put the other way,
if the document would formatted properly, a lot of people would
find their job easier.

Regards,
Charlie P.

On 12/2/2012 1:41 AM, Julian Reschke wrote:
> I wouldn't worry about page breaks; when the document is published as 
> RFC, the RFC editor team will take care about the final formatting.
>
> (The same applies to table headers).
>
> Best regards, Julian
>
> On 2012-12-01 15:29, Zoltán Ördögh (GMail) wrote:
>> While at it:
>> How do I repeat table heading accross pages?
>> Thanks!
>>
>> Best regards: Zoltán Ördögh
>>
>>
>> On Fri, Nov 30, 2012 at 9:21 PM, Charles E. Perkins
>> <charliep@computer.org <mailto:charliep@computer.org>> wrote:
>>
>>
>>     Hello folks,
>>
>>     How do I get a page break in xml2rfc?
>>
>>     Alternatively, how do I protect a table from getting
>>     a page break in the middle?
>>
>>     --
>>     Regards,
>>     Charlie P.
>>
>>     _________________________________________________
>>     xml2rfc mailing list
>>     xml2rfc@ietf.org <mailto:xml2rfc@ietf.org>
>>     https://www.ietf.org/mailman/__listinfo/xml2rfc
>>     <https://www.ietf.org/mailman/listinfo/xml2rfc>
>>
>>
>>
>>
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>
>
>


-- 
Regards,
Charlie P.


From dhc2@dcrocker.net  Sun Dec  2 10:00:17 2012
Return-Path: <dhc2@dcrocker.net>
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 7A4DA21F8634 for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 10:00:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p+AIwBRmcXJA for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 10:00:17 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C674C21F861A for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 10:00:16 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB2I09p8020753 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 2 Dec 2012 10:00:09 -0800
Message-ID: <50BB9721.4070000@dcrocker.net>
Date: Sun, 02 Dec 2012 10:00:01 -0800
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <50B9699E.1090606@computer.org> <CAF2Bc5wxahYRr5VVy8sgbRTK20K5CJZ97Gr3L-YpxBNvTYTpdQ@mail.gmail.com> <50BB2251.3070606@gmx.de>
In-Reply-To: <50BB2251.3070606@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 02 Dec 2012 10:00:09 -0800 (PST)
Cc: "Charles E. Perkins" <charliep@computer.org>, xml2rfc@ietf.org
Subject: Re: [xml2rfc] Page break in xml2rfc
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Sun, 02 Dec 2012 18:00:17 -0000

On 12/2/2012 1:41 AM, Julian Reschke wrote:
> I wouldn't worry about page breaks; when the document is published as
> RFC, the RFC editor team will take care about the final formatting.


Given the goal of permitting xml2rfc's being able to generate final-form 
RFC layout automatically, this doesn't seem like good strategic advice.

In other words, I believe xml2rfc ought to allow the author enough 
control to specify what sequence is not to be broken by a page boundary.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From johnl@iecc.com  Sun Dec  2 10:30:28 2012
Return-Path: <johnl@iecc.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 361AE21F85A8 for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 10:30:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.798
X-Spam-Level: 
X-Spam-Status: No, score=-105.798 tagged_above=-999 required=5 tests=[AWL=1.101, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YrEj2s2gzTHZ for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 10:30:27 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 64B6C21F85A9 for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 10:30:26 -0800 (PST)
Received: (qmail 923 invoked from network); 2 Dec 2012 18:30:25 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 2 Dec 2012 18:30:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50bb9e41.xn--yuvv84g.k1211; i=johnl@user.iecc.com; bh=sdlSS1UQZUbGjGCtrYmRtf0xnUck19WOj9zilqpOXAk=; b=tXDR8iogK3gJJ6DyS7THHaKBiy0Ojx9wiwgzleYGAtE5TKZl/wt/hUzwi4y2fve52tmS0JXVQDgIqyH25dqiHXjmlYh4pfGp0o+kb+rtcKGDw75B8ZdL3eMI7GYR4SLMVEEg6u6d/mUPKv0eDVs/uglsBEY/BNf783KG1J7JXe8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50bb9e41.xn--yuvv84g.k1211; olt=johnl@user.iecc.com; bh=sdlSS1UQZUbGjGCtrYmRtf0xnUck19WOj9zilqpOXAk=; b=aiQVlM5uNvG9OXKUJVdRLyypOPNZJQiso+Sk58PI+ba0P9HwW/lYxvuAB2CkNo1TFI5OdbXn/LoEgC+a20yJ6/Vz5FClw4mScJXXj0lTd1kCighGu+V5JkJqQQZaN+WSD5MxBjmJqZqCXi6S8wLfipohN88siEj+iCbx4bEQPco=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 2 Dec 2012 18:30:02 -0000
Message-ID: <20121202183002.5492.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: xml2rfc@ietf.org
In-Reply-To: <50BB9721.4070000@dcrocker.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: dcrocker@bbiw.net
Subject: Re: [xml2rfc] Page break in xml2rfc
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: Sun, 02 Dec 2012 18:30:28 -0000

>In other words, I believe xml2rfc ought to allow the author enough 
>control to specify what sequence is not to be broken by a page boundary.

Yes, but for tables more than a dozen lines long, it's often better to break
them across multiple pages, in which case it's rather nice to be able to
tell it repeat the headings on each page.

nroff has offered this facility via the tbl preprocessor since about
1978, after all.

I agree that we don't want xml2rfc to turn into yet another Turing complete
formatting language, but if it's going to replace nroff as the final tool
to produce RFCs, a few more well chosen features would make it a lot easier.

R's,
John

From julian.reschke@gmx.de  Sun Dec  2 10:45: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 0081321F86CE for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 10:45:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rGndkP4Vkt-w for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 10:45:13 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id D55B521F86C4 for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 10:45:12 -0800 (PST)
Received: (qmail invoked by alias); 02 Dec 2012 18:45:10 -0000
Received: from unknown (EHLO [192.168.2.100]) [89.204.154.29] by mail.gmx.net (mp017) with SMTP; 02 Dec 2012 19:45:10 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19NENU+jSVNfGuySLN2zZHHPH3kkH7u2DryCd8gHd B40RdB9fhpeaIZ
Message-ID: <50BBA1AE.1010307@gmx.de>
Date: Sun, 02 Dec 2012 19:45:02 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "Charles E. Perkins" <charliep@computer.org>
References: <50B9699E.1090606@computer.org> <CAF2Bc5wxahYRr5VVy8sgbRTK20K5CJZ97Gr3L-YpxBNvTYTpdQ@mail.gmail.com> <50BB2251.3070606@gmx.de> <50BB72A8.5080101@computer.org>
In-Reply-To: <50BB72A8.5080101@computer.org>
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] Page break in xml2rfc
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: Sun, 02 Dec 2012 18:45:19 -0000

On 2012-12-02 16:24, Charles E. Perkins wrote:
>
>
> Hello Julian,
>
> I get your point.  But RFC publication is the last step in the process.
> In the meantime, there are many months or years of review and
> revision, and each time anyone reads the document, it would be
> easier if the formatting were done properly.  To put the other way,
> if the document would formatted properly, a lot of people would
> find their job easier.
> ...

I would recommend to use something more readable for reviews (-> HTML).

Best regards, Julian

From dcrocker@bbiw.net  Sun Dec  2 10:50:18 2012
Return-Path: <dcrocker@bbiw.net>
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 B072821F841A for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 10:50:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jWovQSAUU1gs for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 10:50:17 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 33E8D21F88DD for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 10:50:17 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB2IoGs9021348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 2 Dec 2012 10:50:16 -0800
Message-ID: <50BBA2E0.20309@bbiw.net>
Date: Sun, 02 Dec 2012 10:50:08 -0800
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
References: <20121202183002.5492.qmail@joyce.lan>
In-Reply-To: <20121202183002.5492.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 02 Dec 2012 10:50:17 -0800 (PST)
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Page break in xml2rfc
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: Sun, 02 Dec 2012 18:50:18 -0000

On 12/2/2012 10:30 AM, John Levine wrote:
>> In other words, I believe xml2rfc ought to allow the author enough
>> control to specify what sequence is not to be broken by a page boundary.
>
> Yes, but for tables more than a dozen lines long, it's often better to break
> them across multiple pages, in which case it's rather nice to be able to
> tell it repeat the headings on each page.


Your note is orthogonal to mine.  I was responding to the view that we 
can/should leave tweaking to the manual last step of RFC publication.

You are, essentially, suggesting that automated pagination should have 
some extra sophistication in the (automated) handling of particularly 
long sequences of a particular type.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From julian.reschke@gmx.de  Sun Dec  2 10:54: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 7177F21F847B for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 10:54:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BnVdUosXBRUB for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 10:54:59 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 79F4E21F8430 for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 10:54:58 -0800 (PST)
Received: (qmail invoked by alias); 02 Dec 2012 18:54:57 -0000
Received: from unknown (EHLO [192.168.2.100]) [89.204.154.29] by mail.gmx.net (mp039) with SMTP; 02 Dec 2012 19:54:57 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+ccDBalNicHH/2c4/Cf5UZf6/v7nqQC/O+3p2zTY gXox2e8tyznYuq
Message-ID: <50BBA3F1.4000407@gmx.de>
Date: Sun, 02 Dec 2012 19:54:41 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
References: <20121202183002.5492.qmail@joyce.lan>
In-Reply-To: <20121202183002.5492.qmail@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: xml2rfc@ietf.org, dcrocker@bbiw.net
Subject: Re: [xml2rfc] Page break in xml2rfc
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: Sun, 02 Dec 2012 18:54:59 -0000

On 2012-12-02 19:30, John Levine wrote:
>> In other words, I believe xml2rfc ought to allow the author enough
>> control to specify what sequence is not to be broken by a page boundary.
>
> Yes, but for tables more than a dozen lines long, it's often better to break
> them across multiple pages, in which case it's rather nice to be able to
> tell it repeat the headings on each page.

Is there a single case where you *don*t want to repeat the page headers 
on subsequent pages?

> nroff has offered this facility via the tbl preprocessor since about
> 1978, after all.
>
> I agree that we don't want xml2rfc to turn into yet another Turing complete
> formatting language, but if it's going to replace nroff as the final tool
> to produce RFCs, a few more well chosen features would make it a lot easier.
> ...

Well, if we change to a default output format of HTML the issue goes 
away anyway...

Best regards, Julian

From rra@stanford.edu  Sun Dec  2 12:33:41 2012
Return-Path: <rra@stanford.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 89DA321F881F for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 12:33:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ecqKJz57McgG for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 12:33:40 -0800 (PST)
Received: from smtp.stanford.edu (smtp2.Stanford.EDU [171.67.219.82]) by ietfa.amsl.com (Postfix) with ESMTP id BED6B21F87B1 for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 12:33:40 -0800 (PST)
Received: from smtp.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 87B876462C3 for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 12:33:39 -0800 (PST)
Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.67.225.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.stanford.edu (Postfix) with ESMTPS id 6DCED6462B0 for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 12:33:39 -0800 (PST)
Received: by windlord.stanford.edu (Postfix, from userid 1000) id 42F642F44F; Sun,  2 Dec 2012 12:33:38 -0800 (PST)
From: Russ Allbery <rra@stanford.edu>
To: xml2rfc@ietf.org
In-Reply-To: <50BBA3F1.4000407@gmx.de> (Julian Reschke's message of "Sun, 02 Dec 2012 19:54:41 +0100")
Organization: The Eyrie
References: <20121202183002.5492.qmail@joyce.lan> <50BBA3F1.4000407@gmx.de>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Date: Sun, 02 Dec 2012 12:33:38 -0800
Message-ID: <87mwxwqjml.fsf@windlord.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [xml2rfc] Page break in xml2rfc
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: Sun, 02 Dec 2012 20:33:41 -0000

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

> Well, if we change to a default output format of HTML the issue goes
> away anyway...

I think HTML is an inferior output format for discussion of drafts on
working group mailing lists, since it's more difficult to quote and
discuss than plain text.  You end up doing a lot of copying and pasting
and manually adding quote marks, not to mention adjusting for the fact
that copy/paste of text from web pages via browsers usually ends up
producing unreadable, mangled formatting that has to be manually
corrected.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>

From johnl@taugh.com  Sun Dec  2 14:33:20 2012
Return-Path: <johnl@taugh.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 5AE3921F88EF for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 14:33:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFiPFCt97Zbe for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 14:33:19 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC6421F88EB for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 14:33:19 -0800 (PST)
Received: (qmail 65725 invoked from network); 2 Dec 2012 22:33:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=100bc.50bbd72e.k1212; bh=5lXvkzZaDV8T1QUcaVe8NDl2O/aXpJ7Q37Cjv0hw98M=; b=mACzOA3931W33jGBK5jO4cGG/XlonL3g3QXNK2j3AWrujbOnjzQGoTrnCCsUauWT6po57c3lSTqkt1caVmjt0ldKCg+R8TZ3t+iqNf3E6LLu6IgMK00WxQ8rmhP9SHzmD8x57XdHvHVI1/WwDLtrySHltvexX1bgn7a6CsbVwzc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=100bc.50bbd72e.k1212; bh=5lXvkzZaDV8T1QUcaVe8NDl2O/aXpJ7Q37Cjv0hw98M=; b=LnqLeHcDDK7DX5Kq88WNrw3D3D5SB7lNnU1+4RhTJV6Pk00tJseSwa64iYiOxJx2dewb8ro7++eQv2J52+OZ6m2yJ0lbb3GYwBG8eyKXGWYWfTthCBCOcV7n4/dZoOMO3qL7e9Hb7wrN8shsvGxljfwX94SoC8XDQ6nbB4bwi+8=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 2 Dec 2012 22:32:56 -0000
Date: 2 Dec 2012 17:33:17 -0500
Message-ID: <alpine.BSF.2.00.1212021731540.97925@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Julian Reschke" <julian.reschke@gmx.de>
In-Reply-To: <50BBA3F1.4000407@gmx.de>
References: <20121202183002.5492.qmail@joyce.lan> <50BBA3F1.4000407@gmx.de>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Page break in xml2rfc
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: Sun, 02 Dec 2012 22:33:20 -0000

> Is there a single case where you *don*t want to repeat the page headers on 
> subsequent pages?

Well, there are some table-like things that don't have headers.  But I 
suppose you could treat that as repeating an empty header.

> Well, if we change to a default output format of HTML the issue goes away 
> anyway...

It does and it doesn't.  Even HTML docs sometimes get printed on sheets of 
paper, and the header issue arises again.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From nico@cryptonector.com  Sun Dec  2 15:47:55 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 AF8A221F87EE for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 15:47:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id krZYlxqlyR+w for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 15:47:55 -0800 (PST)
Received: from homiemail-a85.g.dreamhost.com (caiajhbdcbbj.dreamhost.com [208.97.132.119]) by ietfa.amsl.com (Postfix) with ESMTP id 2E01721F8577 for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 15:47:55 -0800 (PST)
Received: from homiemail-a85.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a85.g.dreamhost.com (Postfix) with ESMTP id F141CBC033 for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 15:47:54 -0800 (PST)
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=r+SJyLm5LlUaToaEGPWT cFbpYTE=; b=Uz625q88/4t0o184AYPxIFJNrNy+aLiIW6IRZb8EUP6oolKccygx +lUzSz6UoJ+76NXQwSygEwEzNSyrIbMnZOygJgA5FJQN8nLid9ieN19eyNrOfhbG jAaTO9ft3KkM4Dbzx+xbyBnDQsRxm5erhLIVrWXXA/WCXhXq8axQEw0=
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.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 9C474BC032 for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 15:47:54 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so940295wey.31 for <xml2rfc@ietf.org>; Sun, 02 Dec 2012 15:47:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.145.81 with SMTP id o59mr2520133wej.58.1354492073269; Sun, 02 Dec 2012 15:47:53 -0800 (PST)
Received: by 10.216.192.207 with HTTP; Sun, 2 Dec 2012 15:47:53 -0800 (PST)
In-Reply-To: <87mwxwqjml.fsf@windlord.stanford.edu>
References: <20121202183002.5492.qmail@joyce.lan> <50BBA3F1.4000407@gmx.de> <87mwxwqjml.fsf@windlord.stanford.edu>
Date: Sun, 2 Dec 2012 17:47:53 -0600
Message-ID: <CAK3OfOgFq24a9G4rhtkSpbPyCbzDJcgVL-XQjk1=QuBBNGAPsg@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Russ Allbery <rra@stanford.edu>
Content-Type: text/plain; charset=UTF-8
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Page break in xml2rfc
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: Sun, 02 Dec 2012 23:47:55 -0000

On Sun, Dec 2, 2012 at 2:33 PM, Russ Allbery <rra@stanford.edu> wrote:
> Julian Reschke <julian.reschke@gmx.de> writes:
>> Well, if we change to a default output format of HTML the issue goes
>> away anyway...
>
> I think HTML is an inferior output format for discussion of drafts on
> working group mailing lists, since it's more difficult to quote and
> discuss than plain text.  You end up doing a lot of copying and pasting
> and manually adding quote marks, not to mention adjusting for the fact
> that copy/paste of text from web pages via browsers usually ends up
> producing unreadable, mangled formatting that has to be manually
> corrected.

+1.

I really want to be able to read I-Ds/RFCs on ttys, using $PAGER (less
in my case) screen(1) cut-n-paste, quote trivially on mutt, be able to
say "the second sentence in the first paragraph on page 5" and be
understood, etcetera.  It is true that tty is limiting (no images, for
example), but not too much (Unicode is fine, as are line-drawing
chars), but I can use a PDF viewer or web browser for those cases
where there are images.

That is, I think we should encourage a canonical format that is all
[Unicode] text except for those cases where non-text art images are
important.

Nico
--

From csimbi@gmail.com  Sun Dec  2 16:03:43 2012
Return-Path: <csimbi@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 159EB21F88F0 for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 16:03:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id APGfRabk-+9d for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 16:03:42 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 45DD521F88EB for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 16:03:42 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so943269wey.31 for <xml2rfc@ietf.org>; Sun, 02 Dec 2012 16:03:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=rdScC/zVlZuLf3sf+aoxCX+jCxWnkviD9WNiyqUvFL8=; b=T4BmoQ4CJyo8Dsb/6vN5zjcrmUg9omjfSRZzcZU3WPGmdUCngWJQ61GoTQ9L6mHp/w 6VBrze4bdpy2Qci05YrnDyX7CFLrLhYnloAkFGVv40jAaqtha2F/xsuNihxygsmsMmR0 IkIlFtlcirRcmHQZUOMm5HXG9f+qvqCza/w+pu2Sz5LHGAuTYPKrO96UhGvSblcMxvK0 IczNyLD096IGZPtWDPGdnXr7xS1yI9xEaaTBPeXh2UWfF9RilLIUiDLunNBwNhX9xcRS 6On2H1iU1rNfPNpJvuBNTdRKNhV4S200qtGfl7T16gfVpUp4Rp5lEQzbLe14ENYxm9Yt 27NQ==
Received: by 10.216.82.139 with SMTP id o11mr2614392wee.105.1354493021385; Sun, 02 Dec 2012 16:03:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.191.23 with HTTP; Sun, 2 Dec 2012 16:03:20 -0800 (PST)
In-Reply-To: <alpine.BSF.2.00.1212021731540.97925@joyce.lan>
References: <20121202183002.5492.qmail@joyce.lan> <50BBA3F1.4000407@gmx.de> <alpine.BSF.2.00.1212021731540.97925@joyce.lan>
From: =?UTF-8?B?Wm9sdMOhbiDDlnJkw7ZnaCAoR01haWwp?= <csimbi@gmail.com>
Date: Sun, 2 Dec 2012 19:03:20 -0500
Message-ID: <CAF2Bc5xJOCk4wpEHX7goHH4NwVKLjf7=F923J7LVy3yEuR+Vow@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=001636d3440063f48404cfe77b41
Cc: Julian Reschke <julian.reschke@gmx.de>, xml2rfc@ietf.org
Subject: Re: [xml2rfc] Page break in xml2rfc
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, 03 Dec 2012 00:03:43 -0000

--001636d3440063f48404cfe77b41
Content-Type: text/plain; charset=UTF-8

On Sun, Dec 2, 2012 at 5:33 PM, John R Levine <johnl@taugh.com> wrote:


> Well, if we change to a default output format of HTML the issue goes away
> anyway...
>
> It does and it doesn't.  Even HTML docs sometimes get printed on sheets of
> paper, and the header issue arises again.
>
>
I have not seen a printed RFC in a long, long time.
I rarely see printed documents at all nowadays - I guess nowadays documents
are only printed when they require a signature.
Bank statements are also printed generated HTML pages - and they print just
fine with/without tables.

--001636d3440063f48404cfe77b41
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br clear=3D"all"><div class=3D"gmail_quote">On Sun, Dec 2, 2012 at 5:33 PM=
, John R Levine <span dir=3D"ltr">&lt;<a href=3D"mailto:johnl@taugh.com" ta=
rget=3D"_blank">johnl@taugh.com</a>&gt;</span> wrote:<br><div>=C2=A0</div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">

Well, if we change to a default output format of HTML the issue goes away a=
nyway...<br>
<div class=3D"im">
<br></div>
It does and it doesn&#39;t. =C2=A0Even HTML docs sometimes get printed on s=
heets of paper, and the header issue arises again.<br>
<br></blockquote></div><br>I have not seen a printed RFC in a long, long ti=
me.<br>I rarely see printed documents at all nowadays - I guess nowadays do=
cuments are only printed when they require a signature.<br>Bank statements =
are also printed generated HTML pages - and they print just fine with/witho=
ut tables.<br>

<br>

--001636d3440063f48404cfe77b41--

From johnl@taugh.com  Sun Dec  2 16:10:19 2012
Return-Path: <johnl@taugh.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 2A6A121F87EB for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 16:10:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=-0.150,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 73jSDgME7gYt for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 16:10:15 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD6A21F8206 for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 16:10:14 -0800 (PST)
Received: (qmail 7643 invoked from network); 3 Dec 2012 00:10:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=1dda.50bbede4.k1212; bh=ansDQt90K9wE8g1uHXzmY0Wh8n4ht3ldO/zIhkSgk40=; b=dCagipXeNhadwcFrXYvxNh8rAWNVtQ/G6gCDo9KdDwGAVcNmC+NVKjXoi2+dPk5XJ98PMvrICcTbLZIhXCmc4Ubh9KI3l9YV/obIZ1tNBCn8iwrYqntPAGB5WatYDy9IjHlrfJKxxvYj3LLpGmaQGlNg+ORcP+9F4F8UTc17hVY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=1dda.50bbede4.k1212; bh=ansDQt90K9wE8g1uHXzmY0Wh8n4ht3ldO/zIhkSgk40=; b=VW/0/awZykXutTiSOrw8q6poXt6AxSXw+JmSeVL1AZVIalB0EHxFwoZn0sFZRb1rygmIiYHe48vysSJFX5Tvq8ih92et1CWLVulumPKeWVyJMud+kNixYsLsuuMkMZsoKMmfk+RHaTlPISJT1/ySpKmJlZ5UN0RFT8cpKVnii88=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 3 Dec 2012 00:09:50 -0000
Date: 2 Dec 2012 19:10:12 -0500
Message-ID: <alpine.BSF.2.00.1212021908370.8200@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "=?UTF-8?Q?Zolt=C3=A1n_=C3=96rd=C3=B6gh_=28GMail=29?=" <csimbi@gmail.com>
In-Reply-To: <CAF2Bc5xJOCk4wpEHX7goHH4NwVKLjf7=F923J7LVy3yEuR+Vow@mail.gmail.com>
References: <20121202183002.5492.qmail@joyce.lan> <50BBA3F1.4000407@gmx.de> <alpine.BSF.2.00.1212021731540.97925@joyce.lan> <CAF2Bc5xJOCk4wpEHX7goHH4NwVKLjf7=F923J7LVy3yEuR+Vow@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Page break in xml2rfc
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, 03 Dec 2012 00:10:19 -0000

> I have not seen a printed RFC in a long, long time.
> I rarely see printed documents at all nowadays - I guess nowadays documents
> are only printed when they require a signature.

It's rarely helpful to assume that your experience is typical of the 
entire world.

I print documents all the time and stick them in my briefcase to read on 
the plane and other places.  Particularly for us people with old tired 
eyes, paper is still a lot easier to read than screens.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From paul.hoffman@vpnc.org  Sun Dec  2 16:16:39 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 4822B21F8903 for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 16:16:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4LUu-+6JBgGq for <xml2rfc@ietfa.amsl.com>; Sun,  2 Dec 2012 16:16:39 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id C4E9021F8902 for <xml2rfc@ietf.org>; Sun,  2 Dec 2012 16:16:38 -0800 (PST)
Received: from [10.20.30.102] (50-0-66-243.dsl.dynamic.fusionbroadband.com [50.0.66.243]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id qB30GafI063243 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <xml2rfc@ietf.org>; Sun, 2 Dec 2012 17:16:37 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <alpine.BSF.2.00.1212021908370.8200@joyce.lan>
Date: Sun, 2 Dec 2012 16:16:36 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2EB2B88A-99C9-4189-89B4-4248A913CC55@vpnc.org>
References: <20121202183002.5492.qmail@joyce.lan> <50BBA3F1.4000407@gmx.de> <alpine.BSF.2.00.1212021731540.97925@joyce.lan> <CAF2Bc5xJOCk4wpEHX7goHH4NwVKLjf7=F923J7LVy3yEuR+Vow@mail.gmail.com> <alpine.BSF.2.00.1212021908370.8200@joyce.lan>
To: "xml2rfc@ietf.org list" <xml2rfc@ietf.org>
X-Mailer: Apple Mail (2.1499)
Subject: [xml2rfc] PLEASE STOP: Page break in xml2rfc
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, 03 Dec 2012 00:16:39 -0000

As most people on this list know, there is a mailing list that is =
discussing what is supposed to be the format for Internet Drafts. THIS =
IS NOT THAT LIST.

Take this over to rfc-interest@rfc-editor.org.

To finish the thread: there is no way currently in xml2rfc to insert =
page breaks.

--Paul Hoffman=

From elwynd@dial.pipex.com  Mon Dec  3 01:16:18 2012
Return-Path: <elwynd@dial.pipex.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 784E221F85AA for <xml2rfc@ietfa.amsl.com>; Mon,  3 Dec 2012 01:16:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60h-QNoSLQnN for <xml2rfc@ietfa.amsl.com>; Mon,  3 Dec 2012 01:16:17 -0800 (PST)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 9EA2221F858B for <xml2rfc@ietf.org>; Mon,  3 Dec 2012 01:16:17 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1TfS8J-0004YX-Jj; Mon, 03 Dec 2012 09:16:14 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: "Charles E. Perkins" <charliep@computer.org>
In-Reply-To: <50B9699E.1090606@computer.org>
References: <50B9699E.1090606@computer.org>
Content-Type: text/plain
Date: Mon, 03 Dec 2012 09:16:21 +0000
Message-Id: <1354526181.11916.705.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: xml2rfc@ietf.org
Subject: Re: [xml2rfc] Page break in xml2rfc
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, 03 Dec 2012 09:16:18 -0000

On Fri, 2012-11-30 at 18:21 -0800, Charles E. Perkins wrote:
> Hello folks,
> 
> How do I get a page break in xml2rfc?
> 
> Alternatively, how do I protect a table from getting
> a page break in the middle?
> 
To actually answer your question...

You can use the processing directive needLines to get the formatter to
check there is enough space for the table on the current page and throw
a page break if not, e.g.:
<?rfc needLines=12 ?> 

Unfortunately *you* need to count the number of lines needed.

Rgards,
Elwyn


From julian.reschke@gmx.de  Mon Dec  3 02:28:39 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 B923921F8661 for <xml2rfc@ietfa.amsl.com>; Mon,  3 Dec 2012 02:28:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1wsng2VmPBP0 for <xml2rfc@ietfa.amsl.com>; Mon,  3 Dec 2012 02:28:39 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id DA64521F8654 for <xml2rfc@ietf.org>; Mon,  3 Dec 2012 02:28:38 -0800 (PST)
Received: (qmail invoked by alias); 03 Dec 2012 10:28:37 -0000
Received: from unknown (EHLO [172.24.113.175]) [192.147.117.12] by mail.gmx.net (mp024) with SMTP; 03 Dec 2012 11:28:37 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19vC1lKeEBvl/xcqhKHJGevRbOWntlBkKwgQ+06l/ C441ILcdMDxGye
Message-ID: <50BC7ED5.7090005@gmx.de>
Date: Mon, 03 Dec 2012 11:28:37 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
References: <20121202183002.5492.qmail@joyce.lan> <50BBA3F1.4000407@gmx.de> <alpine.BSF.2.00.1212021731540.97925@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1212021731540.97925@joyce.lan>
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] Page break in xml2rfc
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, 03 Dec 2012 10:28:39 -0000

On 2012-12-02 23:33, John R Levine wrote:
>> Is there a single case where you *don*t want to repeat the page
>> headers on subsequent pages?
>
> Well, there are some table-like things that don't have headers.  But I
> suppose you could treat that as repeating an empty header.
>
>> Well, if we change to a default output format of HTML the issue goes
>> away anyway...
>
> It does and it doesn't.  Even HTML docs sometimes get printed on sheets
> of paper, and the header issue arises again.

Not if you have the proper CSS attached. Try the output of rfc2629.xslt.

Best regards, Julian


From Chris.Dearlove@baesystems.com  Mon Dec  3 05:19:09 2012
Return-Path: <Chris.Dearlove@baesystems.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 0A4C321F8744 for <xml2rfc@ietfa.amsl.com>; Mon,  3 Dec 2012 05:19:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4MYCBhIkQdJF for <xml2rfc@ietfa.amsl.com>; Mon,  3 Dec 2012 05:19:08 -0800 (PST)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 0393021F8714 for <xml2rfc@ietf.org>; Mon,  3 Dec 2012 05:19:06 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,206,1355097600"; d="scan'208";a="291014795"
Received: from unknown (HELO baemasmds009.greenlnk.net) ([141.245.68.246]) by baemasmds003ir.sharelnk.net with ESMTP; 03 Dec 2012 13:19:04 +0000
Received: from baemasmds017.greenlnk.net ([10.15.207.104]) by baemasmds009.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id qB3DJ31X031359 for <xml2rfc@ietf.org>; Mon, 3 Dec 2012 13:19:04 GMT
X-IronPort-AV: E=Sophos;i="4.84,206,1355097600";  d="scan'208";a="240779"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds017.greenlnk.net with ESMTP; 03 Dec 2012 13:18:48 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.7]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.02.0309.002; Mon, 3 Dec 2012 13:18:48 +0000
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, "xml2rfc@ietf.org list" <xml2rfc@ietf.org>
Thread-Topic: [xml2rfc] PLEASE STOP: Page break in xml2rfc
Thread-Index: AQHN0OuChu5Lg1naV0SyzKr1oilu5ZgHDdyA
Date: Mon, 3 Dec 2012 13:18:48 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FD08E3@GLKXM0002V.GREENLNK.net>
References: <20121202183002.5492.qmail@joyce.lan> <50BBA3F1.4000407@gmx.de> <alpine.BSF.2.00.1212021731540.97925@joyce.lan> <CAF2Bc5xJOCk4wpEHX7goHH4NwVKLjf7=F923J7LVy3yEuR+Vow@mail.gmail.com> <alpine.BSF.2.00.1212021908370.8200@joyce.lan> <2EB2B88A-99C9-4189-89B4-4248A913CC55@vpnc.org>
In-Reply-To: <2EB2B88A-99C9-4189-89B4-4248A913CC55@vpnc.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [xml2rfc] PLEASE STOP: Page break in xml2rfc
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, 03 Dec 2012 13:19:09 -0000

Actually, you can insert a manual page break by e.g.

    <t>
      <vspace blankLines=3D"999"/>
    </t>

Any large number will do, 999 just stands out.

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: xml2rfc-bounces@ietf.org [mailto:xml2rfc-bounces@ietf.org] On Behalf =
Of Paul Hoffman
Sent: 03 December 2012 00:17
To: xml2rfc@ietf.org list
Subject: [xml2rfc] PLEASE STOP: Page break in xml2rfc

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

As most people on this list know, there is a mailing list that is discussin=
g what is supposed to be the format for Internet Drafts. THIS IS NOT THAT L=
IST.

Take this over to rfc-interest@rfc-editor.org.

To finish the thread: there is no way currently in xml2rfc to insert page b=
reaks.

--Paul Hoffman
_______________________________________________
xml2rfc mailing list
xml2rfc@ietf.org
https://www.ietf.org/mailman/listinfo/xml2rfc


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From nico@cryptonector.com  Mon Dec  3 11:17:38 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 7B36A21F8817 for <xml2rfc@ietfa.amsl.com>; Mon,  3 Dec 2012 11:17:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JnxCm3KoJDt4 for <xml2rfc@ietfa.amsl.com>; Mon,  3 Dec 2012 11:17:38 -0800 (PST)
Received: from homiemail-a86.g.dreamhost.com (caiajhbdcahe.dreamhost.com [208.97.132.74]) by ietfa.amsl.com (Postfix) with ESMTP id 2093321F880B for <xml2rfc@ietf.org>; Mon,  3 Dec 2012 11:17:38 -0800 (PST)
Received: from homiemail-a86.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTP id 96B8336006B for <xml2rfc@ietf.org>; Mon,  3 Dec 2012 11:17:36 -0800 (PST)
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=gqad5VyMRFHWAvRJs70H KyASApQ=; b=xMj2mPwUxYjwx8cm+9sg8HOswNvBqNJ9XJ0rzUpDoGpkAetPjKaI bNwQ0CxLC7inTUapAZPiNebv5frD9dC93tCv+zX6d+yf/8hOSy3401Gva3cwJ630 Wis5nPve9Hc08CMXkgI7IRkYasIN6Q6pRH5u0+/33bW49bWUWmMCGNE=
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTPSA id 5CA76360075 for <xml2rfc@ietf.org>; Mon,  3 Dec 2012 11:17:35 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so1365850wey.31 for <xml2rfc@ietf.org>; Mon, 03 Dec 2012 11:17:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.227.197 with SMTP id d47mr2431006weq.83.1354562253053; Mon, 03 Dec 2012 11:17:33 -0800 (PST)
Received: by 10.216.192.207 with HTTP; Mon, 3 Dec 2012 11:17:32 -0800 (PST)
In-Reply-To: <2EB2B88A-99C9-4189-89B4-4248A913CC55@vpnc.org>
References: <20121202183002.5492.qmail@joyce.lan> <50BBA3F1.4000407@gmx.de> <alpine.BSF.2.00.1212021731540.97925@joyce.lan> <CAF2Bc5xJOCk4wpEHX7goHH4NwVKLjf7=F923J7LVy3yEuR+Vow@mail.gmail.com> <alpine.BSF.2.00.1212021908370.8200@joyce.lan> <2EB2B88A-99C9-4189-89B4-4248A913CC55@vpnc.org>
Date: Mon, 3 Dec 2012 13:17:32 -0600
Message-ID: <CAK3OfOjR443PMpOakeZc3ksMhr98OEU8hqBj4omZZg_GBCbxjA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=UTF-8
Cc: "xml2rfc@ietf.org list" <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] PLEASE STOP: Page break in xml2rfc
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, 03 Dec 2012 19:17:38 -0000

On Sun, Dec 2, 2012 at 6:16 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> As most people on this list know, there is a mailing list that is discussing what is supposed to be the format for Internet Drafts. THIS IS NOT THAT LIST.
>
> Take this over to rfc-interest@rfc-editor.org.

The tool discussions and the RFC format discussions necessarily
overlap sometimes.  It'd have been more useful to cross-post a reply
and set Reply-To: in this case.

Nico
--

From nico@cryptonector.com  Wed Dec  5 15:55:50 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 BC2F021F8CB8 for <xml2rfc@ietfa.amsl.com>; Wed,  5 Dec 2012 15:55:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.047
X-Spam-Level: 
X-Spam-Status: No, score=-1.047 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_20=-0.74, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cD7cEyOgIuGl for <xml2rfc@ietfa.amsl.com>; Wed,  5 Dec 2012 15:55:50 -0800 (PST)
Received: from homiemail-a98.g.dreamhost.com (caiajhbdccah.dreamhost.com [208.97.132.207]) by ietfa.amsl.com (Postfix) with ESMTP id 2601D21F8CB5 for <xml2rfc@ietf.org>; Wed,  5 Dec 2012 15:55:50 -0800 (PST)
Received: from homiemail-a98.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a98.g.dreamhost.com (Postfix) with ESMTP id CC67F2C2020 for <xml2rfc@ietf.org>; Wed,  5 Dec 2012 15:55:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:date:message-id:subject:from:to:content-type; s= cryptonector.com; bh=zpDcJWeJXaq7xF6TJiC/1N2A/SA=; b=TsBsgjzr7Vl zbnxbDbn7gAhzJ+Mgm4HB6gYq5BKpnwAh7eOPEcADzUEBXu97lDuUQ5jZpxJ8JMn EyDPWFc1azi1e32fn+dMBf4xkep7GdQr3chSQ8EzBiRlpWiwCDvNHuFwtbyZrv7x vViPJjaA2nRskpOJxUiNr+JFzVDiLOBM=
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a98.g.dreamhost.com (Postfix) with ESMTPSA id 7C4772C2024 for <xml2rfc@ietf.org>; Wed,  5 Dec 2012 15:55:49 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so2574144wey.31 for <xml2rfc@ietf.org>; Wed, 05 Dec 2012 15:55:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.227.197 with SMTP id d47mr5493226weq.83.1354751748273; Wed, 05 Dec 2012 15:55:48 -0800 (PST)
Received: by 10.216.192.207 with HTTP; Wed, 5 Dec 2012 15:55:48 -0800 (PST)
Date: Wed, 5 Dec 2012 17:55:48 -0600
Message-ID: <CAK3OfOiqEhnkrYe1y_NdMWGASEwtjfwaEMJcVmtU6Xyw2CaTZw@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: xml2rfc@ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [xml2rfc] xml2rfc -> DocBook XSL?
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: Wed, 05 Dec 2012 23:55:50 -0000

Has anyone written an xml2rfc->DocBook schema conversion XSL?

Nico
--

From Jeff.Hodges@KingsMountain.com  Wed Dec  5 18:32:39 2012
Return-Path: <Jeff.Hodges@KingsMountain.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 C7CAD21F8D07 for <xml2rfc@ietfa.amsl.com>; Wed,  5 Dec 2012 18:32:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.432
X-Spam-Level: 
X-Spam-Status: No, score=-102.432 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6jXI2ai+kZbI for <xml2rfc@ietfa.amsl.com>; Wed,  5 Dec 2012 18:32:39 -0800 (PST)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id 346E821F8D06 for <xml2rfc@ietf.org>; Wed,  5 Dec 2012 18:32:39 -0800 (PST)
Received: (qmail 13868 invoked by uid 0); 6 Dec 2012 02:32:14 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy3.bluehost.com with SMTP; 6 Dec 2012 02:32:14 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=LrSbf4n7ta0dRvvRZUX09vzNwMThu6Qtha0TGVTMskU=;  b=PNK7eoYv0zoJ8v4+/3DBGYVl04ArrYENNU14eVBZje7kfHL/Rsk2c6Mg36azCei80uymH3rGu1Jr2N0aZKTGz/0YSJLsF+iCmJnlVD5t0u1hmTMzAsQLUnoAkQetRv9S;
Received: from [24.4.122.173] (port=38159 helo=[192.168.11.12]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1TgRG0-0006hn-Ft for xml2rfc@ietf.org; Wed, 05 Dec 2012 19:32:12 -0700
Message-ID: <50C003AA.8090801@KingsMountain.com>
Date: Wed, 05 Dec 2012 18:32:10 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: xml2rfc list <xml2rfc@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 24.4.122.173 authed with jeff.hodges+kingsmountain.com}
Subject: [xml2rfc] is there a bibtex-to-xml2rfc <reference> element converter?
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, 06 Dec 2012 02:32:39 -0000

Hi,

Does anyone know of or have a bibtex-to-xml2rfc <reference> element converter?

i.e., I'd like to have something that converts bibtex-formatted references, e.g.:

@INPROCEEDINGS{forcehttps,
   author = {Collin Jackson and Adam Barth},
   title = {{ForceHTTPS}: Protecting High-Security Web Sites from Network Attacks},
   booktitle = {Proceedings of the 17th International World Wide Web Conference 
(WWW)},
   year = {2008},
   month = {April}
}


..to xml2rfc <reference> elements, e.g.:

       <reference anchor="ForceHTTPS" 
target="https://crypto.stanford.edu/forcehttps/">
         <front>
           <title>
               ForceHTTPS:
               Protecting High-Security Web Sites from Network
               Attacks
           </title>
           <author initials="C" surname="Jackson" fullname="Collin Jackson">
             <organization />
           </author>
           <author initials="A" surname="Barth" fullname="Adam Barth">
             <organization />
           </author>
           <date month="April" year="2008" />
         </front>
         <seriesInfo name="In Proceedings of
       the 17th International World Wide Web Conference (WWW2008)" value="" />
       </reference>


As it stands, I performed the above conversion (and a few others) by hand for a 
recent RFC, and it'd be great to have a tool that would automate this.

Thanks,

=JeffH















From Jeff.Hodges@KingsMountain.com  Wed Dec  5 18:41:25 2012
Return-Path: <Jeff.Hodges@KingsMountain.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 00BD121F8D02 for <xml2rfc@ietfa.amsl.com>; Wed,  5 Dec 2012 18:41:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.349
X-Spam-Level: 
X-Spam-Status: No, score=-102.349 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dkWjexCPwo-L for <xml2rfc@ietfa.amsl.com>; Wed,  5 Dec 2012 18:41:24 -0800 (PST)
Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id 41E4C21F8CF0 for <xml2rfc@ietf.org>; Wed,  5 Dec 2012 18:41:24 -0800 (PST)
Received: (qmail 25287 invoked by uid 0); 6 Dec 2012 02:40:58 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy7.bluehost.com with SMTP; 6 Dec 2012 02:40:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=0H6WoOZofWdsUEvAGfAVnmLxvGuOewBMm4jW4z8n8l8=;  b=GGaUVPucBcRp64l6CYfQzCjwCkCBaCeSn9o1rCYlEqrjjwid6LuD4DcPKRpxSKCuIdeDRZ6om0C5gEjR939bdYX++T6h/rFKe4R+ixXDT0wS0Nkibrg6wEcDGPA7V9Fh;
Received: from [24.4.122.173] (port=38212 helo=[192.168.11.12]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1TgROU-0000UL-0J for xml2rfc@ietf.org; Wed, 05 Dec 2012 19:40:58 -0700
Message-ID: <50C005B8.9030305@KingsMountain.com>
Date: Wed, 05 Dec 2012 18:40:56 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: xml2rfc list <xml2rfc@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 24.4.122.173 authed with jeff.hodges+kingsmountain.com}
Subject: [xml2rfc] how to submit updates to the bibxml2 misc reference collection?
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, 06 Dec 2012 02:41:25 -0000

Greetings again,

In the distant past, I submitted various references to the "Miscellaneous" 
reference collection..

   http://xml.resource.org/public/rfc/bibxml2/

..back when Marshall Rose curated that collection by hand.

How are updates to this collection being presently handled, or are they being 
handled at all?

Am curious because I have a few references I'd contribute if I knew how.

thanks,

=JeffH

From glenzorn@gmail.com  Wed Dec  5 19:49:48 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 6040E21F8C64 for <xml2rfc@ietfa.amsl.com>; Wed,  5 Dec 2012 19:49:48 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bP8DsHFn-jCW for <xml2rfc@ietfa.amsl.com>; Wed,  5 Dec 2012 19:49:47 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id A648A21F8C5C for <xml2rfc@ietf.org>; Wed,  5 Dec 2012 19:49:47 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so3985432pbc.31 for <xml2rfc@ietf.org>; Wed, 05 Dec 2012 19:49:47 -0800 (PST)
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; bh=NP2+8tWbD5rrsZUfKBIgnpQ1E9wRf8cvvaoGdeUfk/g=; b=eo4W3geFVecV0ARxg4bfsNIYTDIdfC62D+C8Vugf0VLG7qMmllnom7eYSTFC44nnqQ M3VXkwmE5Agx4lQ6Ae3T+rvyWr5DKcmeSo1AITDyoAl9VAAvai4P0ccXZwPfNmro32M/ QNCD/yFhij73i1Twb/XTecbVL5AIYVuPBmpb4MG+EogBCV6ZEFfLlfctppwjt5zlsqf7 uYq+i3ilYKqFJpNOP5x2iKSATREMONTIlej24wzoKgQdxZHatojlKE0IhR2QpcfFPVOy 7oxz15gB3uyYxRAeUMFRY1BsajgbICZusc/N4wqEMLjxy8gop3efgtU0g9ojKERC/GNE ElpQ==
Received: by 10.68.239.99 with SMTP id vr3mr2054622pbc.154.1354765766183; Wed, 05 Dec 2012 19:49:26 -0800 (PST)
Received: from [192.168.0.102] (ppp-124-122-100-165.revip2.asianet.co.th. [124.122.100.165]) by mx.google.com with ESMTPS id m7sm3854808paz.3.2012.12.05.19.49.23 (version=SSLv3 cipher=OTHER); Wed, 05 Dec 2012 19:49:25 -0800 (PST)
Message-ID: <50C015C1.8060700@gmail.com>
Date: Thu, 06 Dec 2012 10:49:21 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121030 Thunderbird/16.0.2
MIME-Version: 1.0
To: =JeffH <Jeff.Hodges@KingsMountain.com>
References: <50C005B8.9030305@KingsMountain.com>
In-Reply-To: <50C005B8.9030305@KingsMountain.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: xml2rfc list <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] how to submit updates to the bibxml2 misc reference collection?
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, 06 Dec 2012 03:49:48 -0000

On 12/06/2012 09:40 AM, =JeffH wrote:

> Greetings again,
 >
 > In the distant past, I submitted various references to the
 > "Miscellaneous" reference collection..
 >
 > http://xml.resource.org/public/rfc/bibxml2/
 >
 > ..back when Marshall Rose curated that collection by hand.
 >
 > How are updates to this collection being presently handled, or are
 > they being handled at all?

AFAICT, nobody is doing this: I've submitted a number of references but 
none have ever showed up in the collection.  I've even offered to take 
over the job of updating the collection with no response (possibly 
because there is no one to take over /from/).

>
 > Am curious because I have a few references I'd contribute if I knew
 > how.

In theory, you just send the reference to this list (but see above).

>
 > thanks,
 >
 > =JeffH _______________________________________________ xml2rfc
 > mailing list xml2rfc@ietf.org
 > https://www.ietf.org/mailman/listinfo/xml2rfc


From yaronf.ietf@gmail.com  Thu Dec  6 23:45:38 2012
Return-Path: <yaronf.ietf@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 72A6B21F87E9 for <xml2rfc@ietfa.amsl.com>; Thu,  6 Dec 2012 23:45:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JT1uMkGbdwNQ for <xml2rfc@ietfa.amsl.com>; Thu,  6 Dec 2012 23:45:37 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4D67221F86B7 for <xml2rfc@ietf.org>; Thu,  6 Dec 2012 23:45:37 -0800 (PST)
Received: by mail-bk0-f44.google.com with SMTP id w11so67806bku.31 for <xml2rfc@ietf.org>; Thu, 06 Dec 2012 23:45:36 -0800 (PST)
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:subject :content-type:content-transfer-encoding; bh=ZcC2/ApOAyqSaiP4iddjL5w2vNE3lJk7kvTqGZ+2+MY=; b=wvVlh6zgmfY15P4kwBL5j/QpvTfI3upUfNB3kKp/YkM9JNiLCxGztsDYrD+tJ5tx86 8wJKCN4rbtjNd5LwtidVbIi/46UdZHd97LbYHTuDsrOFwMq4wW867rpnjIaCWRi+f8vA 9tnaHk1DOb2wQRuitN8Ny3QreM3oTvlPmM1ZTdcwLrcg9AxAPiHSC1aU3zwOJ2YgPD/e 8smND0eQUIhv8hRVoJrFcYX4YGdFTgVZZe2vTnfN6Y2OG0VkPTJUgG74cfriBoesXeOA 3EH3evUAznIKpkx50Xn8TjYJB6BzqSHfm6vyB/g7OP0h0Pfikpy+d7r+Y90HXss0W0ce sKiA==
Received: by 10.204.129.214 with SMTP id p22mr1608123bks.47.1354866336091; Thu, 06 Dec 2012 23:45:36 -0800 (PST)
Received: from [10.0.0.3] (bzq-79-180-163-165.red.bezeqint.net. [79.180.163.165]) by mx.google.com with ESMTPS id u3sm8077889bkw.9.2012.12.06.23.45.34 (version=SSLv3 cipher=OTHER); Thu, 06 Dec 2012 23:45:35 -0800 (PST)
Message-ID: <50C19E9B.20103@gmail.com>
Date: Fri, 07 Dec 2012 09:45:31 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: xml2rfc@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [xml2rfc] Links in bibliographic items in the HTML version
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, 07 Dec 2012 07:45:38 -0000

Hi,

I am trying to include a reference that's neither an RFC nor an I-D (see 
XML below). The output looks just fine, except that no matter what I do, 
the title is not wrapped in an "a" element in the HTML output, i.e. it 
is not a link, even though I supplied a target URL. Am I missing something?

<?xml version='1.0' encoding='UTF-8'?>

<reference anchor='stats'>

     <front>
         <title>Distribution of Processing Times</title>
         <author initials='J.' surname='Arkko' fullname='J. Arkko'>
             <organization />
         </author>
         <date year='2012' month='December' />
     </front>

     <format type="HTML" octets='10000' 
target="http://www.arkko.com/tools/lifecycle/wgdistr.html" />
</reference>

Thanks,
     Yaron

From julian.reschke@gmx.de  Fri Dec  7 00:34:02 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 30DE421F85C3 for <xml2rfc@ietfa.amsl.com>; Fri,  7 Dec 2012 00:34:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pyrOh7itwKf0 for <xml2rfc@ietfa.amsl.com>; Fri,  7 Dec 2012 00:34:01 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id DD14021F853A for <xml2rfc@ietf.org>; Fri,  7 Dec 2012 00:34:00 -0800 (PST)
Received: (qmail invoked by alias); 07 Dec 2012 08:33:59 -0000
Received: from p54BB3A66.dip.t-dialin.net (EHLO [192.168.178.36]) [84.187.58.102] by mail.gmx.net (mp017) with SMTP; 07 Dec 2012 09:33:59 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19dXo8Egrdddtxboj30Bk+vlcE2C6EyPBIMtuARMB Vom4cBm3S0AafS
Message-ID: <50C1A9F6.5090607@gmx.de>
Date: Fri, 07 Dec 2012 09:33:58 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Yaron Sheffer <yaronf.ietf@gmail.com>
References: <50C19E9B.20103@gmail.com>
In-Reply-To: <50C19E9B.20103@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] Links in bibliographic items in the HTML version
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, 07 Dec 2012 08:34:02 -0000

On 2012-12-07 08:45, Yaron Sheffer wrote:
> Hi,
>
> I am trying to include a reference that's neither an RFC nor an I-D (see
> XML below). The output looks just fine, except that no matter what I do,
> the title is not wrapped in an "a" element in the HTML output, i.e. it
> is not a link, even though I supplied a target URL. Am I missing something?
>
> <?xml version='1.0' encoding='UTF-8'?>
>
> <reference anchor='stats'>
>
>      <front>
>          <title>Distribution of Processing Times</title>
>          <author initials='J.' surname='Arkko' fullname='J. Arkko'>
>              <organization />
>          </author>
>          <date year='2012' month='December' />
>      </front>
>
>      <format type="HTML" octets='10000'
> target="http://www.arkko.com/tools/lifecycle/wgdistr.html" />
> </reference>

Drop the <format> element; just add the URI as "target" attribute to 
<reference>.

Best regards, Julian


From tony@att.com  Sun Dec  9 20:36:57 2012
Return-Path: <tony@att.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 19C5721F8C9A; Sun,  9 Dec 2012 20:36:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KhpttOiVY3XN; Sun,  9 Dec 2012 20:36:56 -0800 (PST)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) by ietfa.amsl.com (Postfix) with ESMTP id B023821F8C33; Sun,  9 Dec 2012 20:36:55 -0800 (PST)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.11.0-12) over TLS secured channel with ESMTP id 7e665c05.0.138505.00-477.369063.nbfkord-smmo07.seg.att.com (envelope-from <tony@att.com>);  Mon, 10 Dec 2012 04:36:55 +0000 (UTC)
X-MXL-Hash: 50c566e754c5d563-48f5ee67f3ae6f064e250388074240cf441e77aa
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id qBA4atUI001529; Sun, 9 Dec 2012 23:36:55 -0500
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id qBA4ah5B001403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 9 Dec 2012 23:36:51 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint01.pst.cso.att.com (RSA Interceptor); Sun, 9 Dec 2012 23:27:46 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id qBA4Rb9w006845; Sun, 9 Dec 2012 23:27:37 -0500
Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id qBA4RVQl006734; Sun, 9 Dec 2012 23:27:32 -0500
Received: from [130.10.171.146] (vpn-130-10-171-146.vpn.mwst.att.com[130.10.171.146]) by maillennium.att.com (mailgw1) with ESMTP id <20121210042722gw1006320ne> (Authid: tony); Mon, 10 Dec 2012 04:27:25 +0000
X-Originating-IP: [130.10.171.146]
Message-ID: <50C564B0.9070201@att.com>
Date: Sun, 09 Dec 2012 23:27:28 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: tools-development@ietf.org
References: <50C015C1.8060700@gmail.com> <514A9964-5D1A-43C4-8821-81D658E9F95C@amsl.com>
In-Reply-To: <514A9964-5D1A-43C4-8821-81D658E9F95C@amsl.com>
Content-Type: multipart/alternative; boundary="------------060004020102040502000301"
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=2.0 cv=PJ+4D4WC c=1 sm=0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a]
X-AnalysisOut: [=l8Y221tIKz8A:10 a=PJtIR_1cTkwA:10 a=RAGmOLawKxkA:10 a=ofM]
X-AnalysisOut: [gfj31e3cA:10 a=BLceEmwcHowA:10 a=zQP7CpKOAAAA:8 a=NncgfsOd]
X-AnalysisOut: [UGEA:10 a=rqrk_YMJAAAA:8 a=pGLkceISAAAA:8 a=ieNpE_y6AAAA:8]
X-AnalysisOut: [ a=48vgC7mUAAAA:8 a=7magjQlNXGDfX1yLrbIA:9 a=wPNLvfGTeEIA:]
X-AnalysisOut: [10 a=MSl-tDqOz04A:10 a=OYCTMcHRYOMA:10 a=lZB815dzVvQA:10 a]
X-AnalysisOut: [=jGqiy6jZAAAA:8 a=_W_S_7VecoQA:10 a=5ovjxN8rTVMA:10 a=kqzo]
X-AnalysisOut: [voQZadzOc-qR:21]
Cc: xml2rfc mailing list <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] [TOOLS-DEVELOPMENT] xml2rfc citation lib.
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, 10 Dec 2012 04:36:57 -0000

This is a multi-part message in MIME format.
--------------060004020102040502000301
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

A couple IETFs ago, I tried unraveling the rat's nest that makes up the 
bibxml directories during the codesprint. My hope was to make sure that 
each of the references that reflected data coming from other SDOs 
actually used a feed from those other SDOs.

I made little progress and haven't made it back to that effort.

As far as I know, all of the current data *is* in svn.

I like the idea of opening up editing privileges, and might even 
consider making it bibxml2 itself that was opened up. However, there 
needs to be a bit of quality control on the changes before getting 
pushed out. For example, verification for proper BIBREF XML is a minimum.

     Tony Hansen

On 12/6/2012 10:55 AM, Alice Russo wrote:
> Hi,
>
> FYI, this topic came up again on the xml2rfc list.
>
> An idea for making use of various individuals' energy to improve the citations library:
> - Start an experiment with the Miscellaneous directory (http://xml.resource.org/public/rfc/bibxml2/) Rationale: it's the one that primarily comes up in discussion of 'how do I update this'. It contains  citations for documents by various SDOs.
> - Keep the existing one in place.
> - Make a copy available that can be updated by community members, while still being available via rsync. (e.g., bibxml2exp/)
> - Announce experiment with disclaimer about quality (as good as you make it). Point to examples of good citations.
> - No gatekeeper on updates.
> - RPC role is contributing, but not reviewing every change. (If the experiment concludes and the decision is to replace the existing lib., more quality control at that time.)
>
> Thanks,
> Alice
>
> Begin forwarded message:
>
>> From: Glen Zorn <glenzorn@gmail.com>
>> Date: December 5, 2012 10:49:21 PM EST
>> To: =JeffH <Jeff.Hodges@KingsMountain.com>
>> Cc: xml2rfc list <xml2rfc@ietf.org>
>> Subject: Re: [xml2rfc] how to submit updates to the bibxml2 misc reference collection?
>>
>> On 12/06/2012 09:40 AM, =JeffH wrote:
>>
>>> Greetings again,
>>>
>>> In the distant past, I submitted various references to the
>>> "Miscellaneous" reference collection..
>>>
>>> http://xml.resource.org/public/rfc/bibxml2/
>>>
>>> ..back when Marshall Rose curated that collection by hand.
>>>
>>> How are updates to this collection being presently handled, or are
>>> they being handled at all?
>> AFAICT, nobody is doing this: I've submitted a number of references but none have ever showed up in the collection.  I've even offered to take over the job of updating the collection with no response (possibly because there is no one to take over /from/).
>>
>>> Am curious because I have a few references I'd contribute if I knew
>>> how.
>> In theory, you just send the reference to this list (but see above).
>>
>>> thanks,
>>>
>>> =JeffH _______________________________________________ xml2rfc
>>> mailing list xml2rfc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development


--------------060004020102040502000301
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
    <link href="chrome://translator/skin/floatingPanel.css"
      type="text/css" rel="stylesheet">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    A couple IETFs ago, I tried unraveling the rat's nest that makes up
    the bibxml directories during the codesprint. My hope was to make
    sure that each of the references that reflected data coming from
    other SDOs actually used a feed from those other SDOs.<br>
    <br>
    I made little progress and haven't made it back to that effort.<br>
    <br>
    As far as I know, all of the current data *is* in svn.<br>
    <br>
    I like the idea of opening up editing privileges, and might even
    consider making it bibxml2 itself that was opened up. However, there
    needs to be a bit of quality control on the changes before getting
    pushed out. For example, verification for proper BIBREF XML is a
    minimum.<br>
    <br>
    &nbsp;&nbsp;&nbsp; Tony Hansen<br>
    <br>
    <div class="moz-cite-prefix">On 12/6/2012 10:55 AM, Alice Russo
      wrote:<br>
    </div>
    <blockquote cite="mid:514A9964-5D1A-43C4-8821-81D658E9F95C@amsl.com"
      type="cite">
      <pre wrap="">Hi,

FYI, this topic came up again on the xml2rfc list.

An idea for making use of various individuals' energy to improve the citations library:
- Start an experiment with the Miscellaneous directory (<a class="moz-txt-link-freetext" href="http://xml.resource.org/public/rfc/bibxml2/">http://xml.resource.org/public/rfc/bibxml2/</a>) Rationale: it's the one that primarily comes up in discussion of 'how do I update this'. It contains  citations for documents by various SDOs.
- Keep the existing one in place.
- Make a copy available that can be updated by community members, while still being available via rsync. (e.g., bibxml2exp/)
- Announce experiment with disclaimer about quality (as good as you make it). Point to examples of good citations.
- No gatekeeper on updates.
- RPC role is contributing, but not reviewing every change. (If the experiment concludes and the decision is to replace the existing lib., more quality control at that time.)

Thanks,
Alice

Begin forwarded message:

</pre>
      <blockquote type="cite">
        <pre wrap="">From: Glen Zorn <a class="moz-txt-link-rfc2396E" href="mailto:glenzorn@gmail.com">&lt;glenzorn@gmail.com&gt;</a>
Date: December 5, 2012 10:49:21 PM EST
To: =JeffH <a class="moz-txt-link-rfc2396E" href="mailto:Jeff.Hodges@KingsMountain.com">&lt;Jeff.Hodges@KingsMountain.com&gt;</a>
Cc: xml2rfc list <a class="moz-txt-link-rfc2396E" href="mailto:xml2rfc@ietf.org">&lt;xml2rfc@ietf.org&gt;</a>
Subject: Re: [xml2rfc] how to submit updates to the bibxml2 misc reference collection?

On 12/06/2012 09:40 AM, =JeffH wrote:

</pre>
        <blockquote type="cite">
          <pre wrap="">Greetings again,

In the distant past, I submitted various references to the
"Miscellaneous" reference collection..

<a class="moz-txt-link-freetext" href="http://xml.resource.org/public/rfc/bibxml2/">http://xml.resource.org/public/rfc/bibxml2/</a>

..back when Marshall Rose curated that collection by hand.

How are updates to this collection being presently handled, or are
they being handled at all?
</pre>
        </blockquote>
        <pre wrap="">
AFAICT, nobody is doing this: I've submitted a number of references but none have ever showed up in the collection.  I've even offered to take over the job of updating the collection with no response (possibly because there is no one to take over /from/).

</pre>
        <blockquote type="cite">
          <pre wrap="">
Am curious because I have a few references I'd contribute if I knew
how.
</pre>
        </blockquote>
        <pre wrap="">
In theory, you just send the reference to this list (but see above).

</pre>
        <blockquote type="cite">
          <pre wrap="">
thanks,

=JeffH _______________________________________________ xml2rfc
mailing list <a class="moz-txt-link-abbreviated" href="mailto:xml2rfc@ietf.org">xml2rfc@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/xml2rfc">https://www.ietf.org/mailman/listinfo/xml2rfc</a>
</pre>
        </blockquote>
        <pre wrap="">
_______________________________________________
xml2rfc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:xml2rfc@ietf.org">xml2rfc@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/xml2rfc">https://www.ietf.org/mailman/listinfo/xml2rfc</a>

</pre>
      </blockquote>
      <pre wrap="">
_______________________________________________
TOOLS-DEVELOPMENT mailing list
<a class="moz-txt-link-abbreviated" href="mailto:TOOLS-DEVELOPMENT@ietf.org">TOOLS-DEVELOPMENT@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tools-development">https://www.ietf.org/mailman/listinfo/tools-development</a>
</pre>
    </blockquote>
    <br>
    <div style="bottom: auto; left: 44px; right: auto; top: 29px;
      display: none;" class="translator-theme-default"
      id="translator-floating-panel">
      <div title="Click to translate"
        id="translator-floating-panel-button"></div>
    </div>
  </body>
</html>

--------------060004020102040502000301--

From nico@cryptonector.com  Sun Dec  9 22:58:07 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 DAF9221F8E3F for <xml2rfc@ietfa.amsl.com>; Sun,  9 Dec 2012 22:58:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.989
X-Spam-Level: 
X-Spam-Status: No, score=-0.989 tagged_above=-999 required=5 tests=[AWL=-0.871, BAYES_20=-0.74, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZh--10Q+-ha for <xml2rfc@ietfa.amsl.com>; Sun,  9 Dec 2012 22:58:07 -0800 (PST)
Received: from homiemail-a88.g.dreamhost.com (caiajhbdccac.dreamhost.com [208.97.132.202]) by ietfa.amsl.com (Postfix) with ESMTP id 423A521F8E3D for <xml2rfc@ietf.org>; Sun,  9 Dec 2012 22:58:07 -0800 (PST)
Received: from homiemail-a88.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a88.g.dreamhost.com (Postfix) with ESMTP id DC6E526406B for <xml2rfc@ietf.org>; Sun,  9 Dec 2012 22:58:06 -0800 (PST)
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=ddQ2Z5fSfyQ3X+GrEw1H 9+HxgwE=; b=Tw0PvUEPPzNPEIRFdkHfxbozE3Sr+WFh1awU8lLpbpXE75g7kdMe A68FtHu0d83LrPhihHM+IIkrOKpFaV1FsOB/Z2xKcyTPqao3MZcXfFuXLKWj5AQb SFRiPreEnO0LNInYrUPoS+RgFIB/IY5YdFm8evO5jhStjDYkih1SFe0=
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) (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 86DC226406A for <xml2rfc@ietf.org>; Sun,  9 Dec 2012 22:58:06 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so1162223wey.31 for <xml2rfc@ietf.org>; Sun, 09 Dec 2012 22:58:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.86.170 with SMTP id q10mr394493wiz.11.1355122685171; Sun, 09 Dec 2012 22:58:05 -0800 (PST)
Received: by 10.216.216.164 with HTTP; Sun, 9 Dec 2012 22:58:04 -0800 (PST)
In-Reply-To: <50C003AA.8090801@KingsMountain.com>
References: <50C003AA.8090801@KingsMountain.com>
Date: Mon, 10 Dec 2012 00:58:04 -0600
Message-ID: <CAK3OfOhgYru0jMAAd5uXboU8e-A=L6U9=A_ibmy3OqMgPCBpQA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "=JeffH" <Jeff.Hodges@kingsmountain.com>
Content-Type: text/plain; charset=UTF-8
Cc: xml2rfc list <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] is there a bibtex-to-xml2rfc <reference> element converter?
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, 10 Dec 2012 06:58:08 -0000

On Wed, Dec 5, 2012 at 8:32 PM, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:
> Does anyone know of or have a bibtex-to-xml2rfc <reference> element
> converter?

I took your bibtex, added it as a bibtex DB to an empty LyX document,
added a citation to the one doc, exported to LyXHTML format, and got
this (reformatted a bit):

                <div class='bibtex'>
                    <div class='bibtexentry'>
                        <a id='forcehttps' />
                            <span class='bibtexlabel'>1</span>
                            <span class='bibtexinfo'>Collin Jackson
and Adam Barth, "ForceHTTPS: Protecting High-Security Web Sites from
Network Attacks", in <i>Proceedings of the 17th International World
Wide Web Conference (WWW)</i> (, 2008).</span>
                        </div>
                    </div>
                </div>

which... kinda sucks because we lose the metadata.  So then I exported
as plain HTML (but still got XHTML!) and got this (reformatted a bit):

<p class="biblio">
    <span class="entry">[
        <a class="biblioentry" name="biblio-1">
            <span class="bib-index">1</span>
        </a>]
    </span>
    <span class="bib-authors">Collin Jackson, Adam Barth</span>.
    <span class="bib-title">ForceHTTPS: Protecting High-Security Web
Sites from Network Attacks</span>.
    <i>
        <span class="bib-booktitle">Proceedings of the 17th
International World Wide Web Conference (WWW)</span>
    </i>,
    <span class="bib-year">2008</span>.
</p>


ah!  much better!

So, we could probably hack up a quick script to generate a LyX doc
just to export to (X)HTML, apply an XSL to massage into xml2rfc
schema, and presto: a bibtex->xml2rfc converter.

Nico
--

From nico@cryptonector.com  Sun Dec  9 23:35:41 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 ABC0E21F8F51 for <xml2rfc@ietfa.amsl.com>; Sun,  9 Dec 2012 23:35:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.868
X-Spam-Level: 
X-Spam-Status: No, score=-1.868 tagged_above=-999 required=5 tests=[AWL=0.109,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dp4hRIIMih46 for <xml2rfc@ietfa.amsl.com>; Sun,  9 Dec 2012 23:35:40 -0800 (PST)
Received: from homiemail-a36.g.dreamhost.com (caiajhbdccah.dreamhost.com [208.97.132.207]) by ietfa.amsl.com (Postfix) with ESMTP id D025821F8F49 for <xml2rfc@ietf.org>; Sun,  9 Dec 2012 23:35:40 -0800 (PST)
Received: from homiemail-a36.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a36.g.dreamhost.com (Postfix) with ESMTP id BC099778061 for <xml2rfc@ietf.org>; Sun,  9 Dec 2012 23:35:32 -0800 (PST)
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=6IRamjCbiQdMpTAIOzqz mzkWvuw=; b=lCmxoWhHLRYQY0UVPohuYnQgW3KOc6iPKF1mUMZuJK1a0tComej7 m4+MRIt3cP+KOvh5lqGzoWKgLpk4sMIPub86f9f8vh3oJquZ8Mhs1J/2E0Ywb58v Q4glBFpqyPiEPj85tNx35z9WlOmYHGvPRZbDYavCvJkoxZUQCBaSt2E=
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a36.g.dreamhost.com (Postfix) with ESMTPSA id 66069778057 for <xml2rfc@ietf.org>; Sun,  9 Dec 2012 23:35:32 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so1175447wey.31 for <xml2rfc@ietf.org>; Sun, 09 Dec 2012 23:35:31 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.88.71 with SMTP id be7mr9020746wib.17.1355124931219; Sun, 09 Dec 2012 23:35:31 -0800 (PST)
Received: by 10.216.216.164 with HTTP; Sun, 9 Dec 2012 23:35:30 -0800 (PST)
In-Reply-To: <CAK3OfOhgYru0jMAAd5uXboU8e-A=L6U9=A_ibmy3OqMgPCBpQA@mail.gmail.com>
References: <50C003AA.8090801@KingsMountain.com> <CAK3OfOhgYru0jMAAd5uXboU8e-A=L6U9=A_ibmy3OqMgPCBpQA@mail.gmail.com>
Date: Mon, 10 Dec 2012 01:35:30 -0600
Message-ID: <CAK3OfOg7T-pEKje=d9UxknivHi6ZUw_ArDiWn+mTAt08KBwO3g@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "=JeffH" <Jeff.Hodges@kingsmountain.com>
Content-Type: text/plain; charset=UTF-8
Cc: xml2rfc list <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] is there a bibtex-to-xml2rfc <reference> element converter?
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, 10 Dec 2012 07:35:41 -0000

Also, below are some useful resources.  Some of the programs listed in
these pages can export bibtex to XML.  In particular this one:
bibutils (http://sourceforge.net/p/bibutils/home/Bibutils/), which
includes a bib2xml utility.

http://wiki.lyx.org/BibTeX/Programs
http://wiki.lyx.org/Windows/BibTeX

bib2xml does this with your forcehttps bibentry:

<mods ID="forcehttps">
    <titleInfo>
        <title>ForceHTTPS</title>
        <subTitle>Protecting High-Security Web Sites from Network
Attacks</subTitle>
    </titleInfo>
    <name type="personal">
        <namePart type="given">Collin</namePart>
        <namePart type="family">Jackson</namePart>
        <role>
            <roleTerm authority="marcrelator" type="text">author</roleTerm>
        </role>
    </name>
    <name type="personal">
        <namePart type="given">Adam</namePart>
        <namePart type="family">Barth</namePart>
        <role>
            <roleTerm authority="marcrelator" type="text">author</roleTerm>
        </role>
    </name>
    <originInfo>
        <dateIssued>2008-April</dateIssued>
    </originInfo>
    <typeOfResource>text</typeOfResource>
    <relatedItem type="host">
        <titleInfo>
            <title>Proceedings of the 17th International World Wide
Web Conference (WWW)</title>
        </titleInfo>
        <genre authority="marcgt">conference publication</genre>
    </relatedItem>
    <identifier type="citekey">forcehttps</identifier>
    <part>
        <date>2008-April</date>
    </part>
</mods>

Wow!  It even figures out that that doc has two authors.  Writing an
XSL for massaging this into xml2rfc is left as an exercise to the
reader :)

Nico
--

From Jeff.Hodges@KingsMountain.com  Tue Dec 11 16:23:47 2012
Return-Path: <Jeff.Hodges@KingsMountain.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 B380F1F0CB0 for <xml2rfc@ietfa.amsl.com>; Tue, 11 Dec 2012 16:23:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.837
X-Spam-Level: 
X-Spam-Status: No, score=-102.837 tagged_above=-999 required=5 tests=[AWL=-0.238, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6MjBusI7IjCO for <xml2rfc@ietfa.amsl.com>; Tue, 11 Dec 2012 16:23:47 -0800 (PST)
Received: from oproxy11-pub.bluehost.com (oproxy11-pub.bluehost.com [173.254.64.10]) by ietfa.amsl.com (Postfix) with SMTP id 1B5E821F8696 for <xml2rfc@ietf.org>; Tue, 11 Dec 2012 16:23:47 -0800 (PST)
Received: (qmail 19122 invoked by uid 0); 12 Dec 2012 00:23:25 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy11.bluehost.com with SMTP; 12 Dec 2012 00:23:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=qjoHV5inxpl4GWO1RLcxNL3rko8USfH1yhS7V0NCVMM=;  b=LceizCXLXdSfkqLleQFkTa27FQLFVPOGFgC7SOD4T+Zj6HOa0pRz6aKtjFD+sB77C7VCzR+xy4hFd9TMTeQIHhErZIa+vwLlXVP/E9B4RINLSFL+KUGn7MSbaHR8IcCw;
Received: from [216.113.168.128] (port=58163 helo=[10.244.136.55]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1Tia6f-000067-G3; Tue, 11 Dec 2012 17:23:25 -0700
Message-ID: <50C7CE7E.30002@KingsMountain.com>
Date: Tue, 11 Dec 2012 16:23:26 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Nico Williams <nico@cryptonector.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Cc: xml2rfc list <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] is there a bibtex-to-xml2rfc <reference> element converter?
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: Wed, 12 Dec 2012 00:23:47 -0000

Thanks Nico, that stuff is cool/innaresting/helpful.

 >  Writing an
 > XSL for massaging this into xml2rfc is left as an exercise to the
 > reader :)

ok, if I get to it I'll share. In the meantime, if someone else does, please share.


thanks,

=JeffH



From arusso@amsl.com  Mon Dec 17 11:12:48 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 A977921F861B; Mon, 17 Dec 2012 11:12:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level: 
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pdbTFQoP2tYr; Mon, 17 Dec 2012 11:12:47 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id D4E2621F85D3; Mon, 17 Dec 2012 11:12:47 -0800 (PST)
Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id AC96E124AA0; Mon, 17 Dec 2012 11:12:47 -0800 (PST)
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 NvoSzZupS6Gi; Mon, 17 Dec 2012 11:12:47 -0800 (PST)
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 06DC51248DD; Mon, 17 Dec 2012 11:12:46 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Alice Russo <arusso@amsl.com>
In-Reply-To: <50C564B0.9070201@att.com>
Date: Mon, 17 Dec 2012 14:12:45 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5826101D-A101-482C-8C98-B6B340AF933A@amsl.com>
References: <50C015C1.8060700@gmail.com> <514A9964-5D1A-43C4-8821-81D658E9F95C@amsl.com> <50C564B0.9070201@att.com>
To: Tony Hansen <tony@att.com>
X-Mailer: Apple Mail (2.1085)
Cc: xml2rfc list <xml2rfc@ietf.org>, tools-development@ietf.org
Subject: Re: [xml2rfc] [TOOLS-DEVELOPMENT] xml2rfc citation lib.
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, 17 Dec 2012 19:12:48 -0000

Hi Tony,

> I like the idea of opening up editing privileges, and might even =
consider making it bibxml2 itself that was opened up. However, there =
needs to be a bit of quality control on the changes before getting =
pushed out. For example, verification for proper BIBREF XML is a =
minimum.

If there is automated verification when committing a file, seems there =
would still be a later QC step. How about this separation?

- bibxml2/ is fairly static (e.g., updated yearly) and content has been =
checked.
- bibxml2exp/ is open for community editing, so it's used with awareness =
that its content has not been checked (beyond minimal verification) and =
is a moving target.

Perhaps once a year the content of bibxml2exp/ is checked, and good refs =
are copied over to bibxml2/.

Thanks,
Alice

On Dec 9, 2012, at 11:27 PM, Tony Hansen wrote:

> A couple IETFs ago, I tried unraveling the rat's nest that makes up =
the bibxml directories during the codesprint. My hope was to make sure =
that each of the references that reflected data coming from other SDOs =
actually used a feed from those other SDOs.
>=20
> I made little progress and haven't made it back to that effort.
>=20
> As far as I know, all of the current data *is* in svn.
>=20
> I like the idea of opening up editing privileges, and might even =
consider making it bibxml2 itself that was opened up. However, there =
needs to be a bit of quality control on the changes before getting =
pushed out. For example, verification for proper BIBREF XML is a =
minimum.
>=20
>     Tony Hansen
>=20
> On 12/6/2012 10:55 AM, Alice Russo wrote:
>> Hi,
>>=20
>> FYI, this topic came up again on the xml2rfc list.
>>=20
>> An idea for making use of various individuals' energy to improve the =
citations library:
>> - Start an experiment with the Miscellaneous directory (
>> http://xml.resource.org/public/rfc/bibxml2/
>> ) Rationale: it's the one that primarily comes up in discussion of =
'how do I update this'. It contains  citations for documents by various =
SDOs.
>> - Keep the existing one in place.
>> - Make a copy available that can be updated by community members, =
while still being available via rsync. (e.g., bibxml2exp/)
>> - Announce experiment with disclaimer about quality (as good as you =
make it). Point to examples of good citations.
>> - No gatekeeper on updates.
>> - RPC role is contributing, but not reviewing every change. (If the =
experiment concludes and the decision is to replace the existing lib., =
more quality control at that time.)
>>=20
>> Thanks,
>> Alice
>>=20
>> Begin forwarded message:
>>=20
>>=20
>>> From: Glen Zorn <glenzorn@gmail.com>
>>>=20
>>> Date: December 5, 2012 10:49:21 PM EST
>>> To: =3DJeffH=20
>>> <Jeff.Hodges@KingsMountain.com>
>>>=20
>>> Cc: xml2rfc list=20
>>> <xml2rfc@ietf.org>
>>>=20
>>> Subject: Re: [xml2rfc] how to submit updates to the bibxml2 misc =
reference collection?
>>>=20
>>> On 12/06/2012 09:40 AM, =3DJeffH wrote:
>>>=20
>>>=20
>>>> Greetings again,
>>>>=20
>>>> In the distant past, I submitted various references to the
>>>> "Miscellaneous" reference collection..
>>>>=20
>>>>=20
>>>> http://xml.resource.org/public/rfc/bibxml2/
>>>>=20
>>>>=20
>>>> ..back when Marshall Rose curated that collection by hand.
>>>>=20
>>>> How are updates to this collection being presently handled, or are
>>>> they being handled at all?
>>>>=20
>>> AFAICT, nobody is doing this: I've submitted a number of references =
but none have ever showed up in the collection.  I've even offered to =
take over the job of updating the collection with no response (possibly =
because there is no one to take over /from/).
>>>=20
>>>=20
>>>> Am curious because I have a few references I'd contribute if I knew
>>>> how.
>>>>=20
>>> In theory, you just send the reference to this list (but see above).
>>>=20
>>>=20
>>>> thanks,
>>>>=20
>>>> =3DJeffH _______________________________________________ xml2rfc
>>>> mailing list=20
>>>> xml2rfc@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>> _______________________________________________
>>> xml2rfc mailing list
>>>=20
>>> xml2rfc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>>=20
>>>=20
>>>=20
>> _______________________________________________
>> TOOLS-DEVELOPMENT mailing list
>>=20
>> TOOLS-DEVELOPMENT@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-development
>=20
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc


From nico@cryptonector.com  Mon Dec 17 11:43: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 3FA0621F8548; Mon, 17 Dec 2012 11:43:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.874
X-Spam-Level: 
X-Spam-Status: No, score=-1.874 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ajmz-54nbFt; Mon, 17 Dec 2012 11:43:35 -0800 (PST)
Received: from homiemail-a16.g.dreamhost.com (caiajhbdcbbj.dreamhost.com [208.97.132.119]) by ietfa.amsl.com (Postfix) with ESMTP id AA6EF21F852E; Mon, 17 Dec 2012 11:43:35 -0800 (PST)
Received: from homiemail-a16.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a16.g.dreamhost.com (Postfix) with ESMTP id 43721508063; Mon, 17 Dec 2012 11:43:35 -0800 (PST)
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=7KtDWhimnwJAvixyk37K3SCaUyM=; b=YU1a5QrChTY jBxmN1mDo8d0Qew63hqu5OOWw3PabhF2J1XKOV8KcQL3jv7OlxQOLa+W4CL55qHi 6sma/LxEsni0+3pbd4tLOM+EbJcg8a9DjaEbig25E0Jc542T5xrq/mNFFL/xreXk ynj9VjMiPUbMGKP5r6FveZc0NqzxBVbA=
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a16.g.dreamhost.com (Postfix) with ESMTPSA id A4CC650808C;  Mon, 17 Dec 2012 11:43:34 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so3080348wey.31 for <multiple recipients>; Mon, 17 Dec 2012 11:43:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.7.104 with SMTP id i8mr19285338wja.27.1355773413332; Mon, 17 Dec 2012 11:43:33 -0800 (PST)
Received: by 10.217.82.73 with HTTP; Mon, 17 Dec 2012 11:43:32 -0800 (PST)
In-Reply-To: <5826101D-A101-482C-8C98-B6B340AF933A@amsl.com>
References: <50C015C1.8060700@gmail.com> <514A9964-5D1A-43C4-8821-81D658E9F95C@amsl.com> <50C564B0.9070201@att.com> <5826101D-A101-482C-8C98-B6B340AF933A@amsl.com>
Date: Mon, 17 Dec 2012 13:43:32 -0600
Message-ID: <CAK3OfOju1UMO1C3idKWTaOx1c_utiJH2Ub=_UYxSAV+6DT6-WQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Alice Russo <arusso@amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: xml2rfc list <xml2rfc@ietf.org>, tools-development@ietf.org
Subject: Re: [xml2rfc] [TOOLS-DEVELOPMENT] xml2rfc citation lib.
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, 17 Dec 2012 19:43:36 -0000

On Mon, Dec 17, 2012 at 1:12 PM, Alice Russo <arusso@amsl.com> wrote:
>> I like the idea of opening up editing privileges, and might even conside=
r making it bibxml2 itself that was opened up. However, there needs to be a=
 bit of quality control on the changes before getting pushed out. For examp=
le, verification for proper BIBREF XML is a minimum.
>
> If there is automated verification when committing a file, seems there wo=
uld still be a later QC step. How about this separation?
>
> - bibxml2/ is fairly static (e.g., updated yearly) and content has been c=
hecked.
> - bibxml2exp/ is open for community editing, so it's used with awareness =
that its content has not been checked (beyond minimal verification) and is =
a moving target.
>
> Perhaps once a year the content of bibxml2exp/ is checked, and good refs =
are copied over to bibxml2/.

Reference accuracy should be checked by the RFC-Editor for sure, no?
So who cares if there's bogus content in the bibxml directory, as long
as the RFC-Editor will eventually notice and can fix it then, it
should be OK, no?

One thing we may want is a repository that has only those references
that have been checked by the RFC-Editor in the process of publishing
an RFC that makes reference to them.  That way we can save the
RFC-Editor the work of doing this more than once per-entry.

Nico
--

From tony@att.com  Mon Dec 17 11:47:41 2012
Return-Path: <tony@att.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 7645721F88E7; Mon, 17 Dec 2012 11:47:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.953
X-Spam-Level: 
X-Spam-Status: No, score=-105.953 tagged_above=-999 required=5 tests=[AWL=0.647, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Il2fA198AyW; Mon, 17 Dec 2012 11:47:40 -0800 (PST)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) by ietfa.amsl.com (Postfix) with ESMTP id ED60A21F88E6; Mon, 17 Dec 2012 11:47:33 -0800 (PST)
Received: from unknown [144.160.128.153] (EHLO flpi408.enaf.ffdc.sbc.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.11.0-12) over TLS secured channel with ESMTP id 5d67fc05.0.358284.00-324.995293.nbfkord-smmo07.seg.att.com (envelope-from <tony@att.com>);  Mon, 17 Dec 2012 19:47:34 +0000 (UTC)
X-MXL-Hash: 50cf76d67d73281a-d16267276506c4ef7eb3e311d6ff3d3630458539
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id qBHJlVxN024789; Mon, 17 Dec 2012 11:47:32 -0800
Received: from fflint04.pst.cso.att.com (fflint04.pst.cso.att.com [150.234.39.64]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id qBHJlOLV024714 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Dec 2012 11:47:25 -0800
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by fflint04.pst.cso.att.com (RSA Interceptor); Mon, 17 Dec 2012 11:47:06 -0800
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id qBHJl69e024664; Mon, 17 Dec 2012 14:47:06 -0500
Received: from dns.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id qBHJl2Yh024532; Mon, 17 Dec 2012 14:47:02 -0500
Received: from [135.70.147.174] (vpn-135-70-147-174.vpn.mwst.att.com[135.70.147.174]) by maillennium.att.com (mailgw1) with ESMTP id <20121217194648gw1006327pe> (Authid: tony); Mon, 17 Dec 2012 19:46:48 +0000
X-Originating-IP: [135.70.147.174]
Message-ID: <50CF76B4.5000307@att.com>
Date: Mon, 17 Dec 2012 14:47:00 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Alice Russo <arusso@amsl.com>
References: <50C015C1.8060700@gmail.com> <514A9964-5D1A-43C4-8821-81D658E9F95C@amsl.com> <50C564B0.9070201@att.com> <5826101D-A101-482C-8C98-B6B340AF933A@amsl.com>
In-Reply-To: <5826101D-A101-482C-8C98-B6B340AF933A@amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.128.153]
X-AnalysisOut: [v=2.0 cv=eMikegV1 c=1 sm=0 a=xwOvzTHDVLE4u4nGvK72ag==:17 a]
X-AnalysisOut: [=kIYcBXARTZ8A:10 a=PJtIR_1cTkwA:10 a=XWWJqkO-AGMA:10 a=ofM]
X-AnalysisOut: [gfj31e3cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:10 a=zQP7CpK]
X-AnalysisOut: [OAAAA:8 a=1QaAitBYPDcA:10 a=rqrk_YMJAAAA:8 a=pGLkceISAAAA:]
X-AnalysisOut: [8 a=ieNpE_y6AAAA:8 a=48vgC7mUAAAA:8 a=B0YbnDTICOi8xY9AUwoA]
X-AnalysisOut: [:9 a=wPNLvfGTeEIA:10 a=MSl-tDqOz04A:10 a=OYCTMcHRYOMA:10 a]
X-AnalysisOut: [=lZB815dzVvQA:10]
Cc: xml2rfc list <xml2rfc@ietf.org>, tools-development@ietf.org
Subject: Re: [xml2rfc] [TOOLS-DEVELOPMENT] xml2rfc citation lib.
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, 17 Dec 2012 19:47:41 -0000

Alice, I think you're on the right track. Two issues come to mind:

*) Who should do the verification?

*) I think the frequency should be more often than once a year. Quarterly?

I also think it should be possible for someone to ask for a faster 
review of a particular entry.

     Tony

On 12/17/2012 2:12 PM, Alice Russo wrote:
> Hi Tony,
>
>> I like the idea of opening up editing privileges, and might even consider making it bibxml2 itself that was opened up. However, there needs to be a bit of quality control on the changes before getting pushed out. For example, verification for proper BIBREF XML is a minimum.
> If there is automated verification when committing a file, seems there would still be a later QC step. How about this separation?
>
> - bibxml2/ is fairly static (e.g., updated yearly) and content has been checked.
> - bibxml2exp/ is open for community editing, so it's used with awareness that its content has not been checked (beyond minimal verification) and is a moving target.
>
> Perhaps once a year the content of bibxml2exp/ is checked, and good refs are copied over to bibxml2/.
>
> Thanks,
> Alice
>
> On Dec 9, 2012, at 11:27 PM, Tony Hansen wrote:
>
>> A couple IETFs ago, I tried unraveling the rat's nest that makes up the bibxml directories during the codesprint. My hope was to make sure that each of the references that reflected data coming from other SDOs actually used a feed from those other SDOs.
>>
>> I made little progress and haven't made it back to that effort.
>>
>> As far as I know, all of the current data *is* in svn.
>>
>> I like the idea of opening up editing privileges, and might even consider making it bibxml2 itself that was opened up. However, there needs to be a bit of quality control on the changes before getting pushed out. For example, verification for proper BIBREF XML is a minimum.
>>
>>      Tony Hansen
>>
>> On 12/6/2012 10:55 AM, Alice Russo wrote:
>>> Hi,
>>>
>>> FYI, this topic came up again on the xml2rfc list.
>>>
>>> An idea for making use of various individuals' energy to improve the citations library:
>>> - Start an experiment with the Miscellaneous directory (
>>> http://xml.resource.org/public/rfc/bibxml2/
>>> ) Rationale: it's the one that primarily comes up in discussion of 'how do I update this'. It contains  citations for documents by various SDOs.
>>> - Keep the existing one in place.
>>> - Make a copy available that can be updated by community members, while still being available via rsync. (e.g., bibxml2exp/)
>>> - Announce experiment with disclaimer about quality (as good as you make it). Point to examples of good citations.
>>> - No gatekeeper on updates.
>>> - RPC role is contributing, but not reviewing every change. (If the experiment concludes and the decision is to replace the existing lib., more quality control at that time.)
>>>
>>> Thanks,
>>> Alice
>>>
>>> Begin forwarded message:
>>>
>>>
>>>> From: Glen Zorn <glenzorn@gmail.com>
>>>>
>>>> Date: December 5, 2012 10:49:21 PM EST
>>>> To: =JeffH
>>>> <Jeff.Hodges@KingsMountain.com>
>>>>
>>>> Cc: xml2rfc list
>>>> <xml2rfc@ietf.org>
>>>>
>>>> Subject: Re: [xml2rfc] how to submit updates to the bibxml2 misc reference collection?
>>>>
>>>> On 12/06/2012 09:40 AM, =JeffH wrote:
>>>>
>>>>
>>>>> Greetings again,
>>>>>
>>>>> In the distant past, I submitted various references to the
>>>>> "Miscellaneous" reference collection..
>>>>>
>>>>>
>>>>> http://xml.resource.org/public/rfc/bibxml2/
>>>>>
>>>>>
>>>>> ..back when Marshall Rose curated that collection by hand.
>>>>>
>>>>> How are updates to this collection being presently handled, or are
>>>>> they being handled at all?
>>>>>
>>>> AFAICT, nobody is doing this: I've submitted a number of references but none have ever showed up in the collection.  I've even offered to take over the job of updating the collection with no response (possibly because there is no one to take over /from/).
>>>>
>>>>
>>>>> Am curious because I have a few references I'd contribute if I knew
>>>>> how.
>>>>>
>>>> In theory, you just send the reference to this list (but see above).
>>>>
>>>>
>>>>> thanks,
>>>>>
>>>>> =JeffH _______________________________________________ xml2rfc
>>>>> mailing list
>>>>> xml2rfc@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>>> _______________________________________________
>>>> xml2rfc mailing list
>>>>
>>>> xml2rfc@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> TOOLS-DEVELOPMENT mailing list
>>>
>>> TOOLS-DEVELOPMENT@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tools-development
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc


From glenzorn@gmail.com  Mon Dec 17 16:04:52 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 8122421F85EF for <xml2rfc@ietfa.amsl.com>; Mon, 17 Dec 2012 16:04:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.374
X-Spam-Level: 
X-Spam-Status: No, score=-3.374 tagged_above=-999 required=5 tests=[AWL=0.225,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6mAfiYZ+Txg0 for <xml2rfc@ietfa.amsl.com>; Mon, 17 Dec 2012 16:04:51 -0800 (PST)
Received: from mail-pb0-f50.google.com (mail-pb0-f50.google.com [209.85.160.50]) by ietfa.amsl.com (Postfix) with ESMTP id 8E24F21F85D2 for <xml2rfc@ietf.org>; Mon, 17 Dec 2012 16:04:51 -0800 (PST)
Received: by mail-pb0-f50.google.com with SMTP id wz7so4035518pbc.23 for <xml2rfc@ietf.org>; Mon, 17 Dec 2012 16:04:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=msrCFfcDI6+XYwJ0W7mpwV3MDOVtHWcpQtYkh/V02/k=; b=JN2eovXlB2D9tN8ZWlUSpXW52OTlU9/I/urRC8W+Fypxb0T5KtedeyEM+5nuIzFQVD Ark2aq6lvwlhwvSsMLVlfZRjmBg375xjjIQh7hu6oEWQT9Cx2C4Ur28/Qr/mgrAvUNQk bL+4wYnLxOti4BnWwiPdpueMvKU7q8gtKA8sodv++5UiLTxr6bVG3xU8xHZZUtM1w/PI rJlcdYCFlINgmWbuQxWaFP3o6Uyl7kkzgly/lIKIAbM2maoFTf7+WI8iOR6a+8xNKpni obHIN2vuXAjU+XK2w6ENMkA07ax+7i4JXpNv1Zbt4RwWixSbWMlSRqrbPdIRoavc+785 ETlA==
X-Received: by 10.68.189.70 with SMTP id gg6mr311720pbc.97.1355789091277; Mon, 17 Dec 2012 16:04:51 -0800 (PST)
Received: from [192.168.0.102] (ppp-110-169-202-60.revip5.asianet.co.th. [110.169.202.60]) by mx.google.com with ESMTPS id gl9sm8993794pbc.51.2012.12.17.16.04.49 (version=SSLv3 cipher=OTHER); Mon, 17 Dec 2012 16:04:50 -0800 (PST)
Message-ID: <50CFB31F.70605@gmail.com>
Date: Tue, 18 Dec 2012 07:04:47 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: xml2rfc@ietf.org
References: <50C015C1.8060700@gmail.com> <514A9964-5D1A-43C4-8821-81D658E9F95C@amsl.com> <50C564B0.9070201@att.com> <5826101D-A101-482C-8C98-B6B340AF933A@amsl.com>
In-Reply-To: <5826101D-A101-482C-8C98-B6B340AF933A@amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [xml2rfc] [TOOLS-DEVELOPMENT] xml2rfc citation lib.
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, 18 Dec 2012 00:04:52 -0000

On 12/18/2012 02:12 AM, Alice Russo wrote:

> Hi Tony,
 >
 >> I like the idea of opening up editing privileges, and might even
 >> consider making it bibxml2 itself that was opened up. However,
 >> there needs to be a bit of quality control on the changes before
 >> getting pushed out. For example, verification for proper BIBREF XML
 >> is a minimum.
 >
 > If there is automated verification when committing a file, seems
 > there would still be a later QC step. How about this separation?
 >
 > - bibxml2/ is fairly static (e.g., updated yearly) and content has
 > been checked. - bibxml2exp/ is open for community editing, so it's
 > used with awareness that its content has not been checked (beyond
 > minimal verification) and is a moving target.
 >
 > Perhaps once a year the content of bibxml2exp/ is checked, and good
 > refs are copied over to bibxml2/.

Never mind, I'll just keep on generating my own citations for the 
documents I use (e.g., IEEE 802.1X -- widely referenced in RFCs, 
citations submitted at least 3 times (by me, undoubtedly by others as 
well) but utterly absent from the archive) .  At least now I know not to 
waste my time trying to share them...

>
 >
 > Thanks, Alice
 >
 > On Dec 9, 2012, at 11:27 PM, Tony Hansen wrote:
 >
 >> A couple IETFs ago, I tried unraveling the rat's nest that makes up
 >> the bibxml directories during the codesprint. My hope was to make
 >> sure that each of the references that reflected data coming from
 >> other SDOs actually used a feed from those other SDOs.
 >>
 >> I made little progress and haven't made it back to that effort.
 >>
 >> As far as I know, all of the current data *is* in svn.
 >>
 >> I like the idea of opening up editing privileges, and might even
 >> consider making it bibxml2 itself that was opened up. However,
 >> there needs to be a bit of quality control on the changes before
 >> getting pushed out. For example, verification for proper BIBREF XML
 >> is a minimum.
 >>
 >> Tony Hansen
 >>
 >> On 12/6/2012 10:55 AM, Alice Russo wrote:
 >>> Hi,
 >>>
 >>> FYI, this topic came up again on the xml2rfc list.
 >>>
 >>> An idea for making use of various individuals' energy to improve
 >>> the citations library: - Start an experiment with the
 >>> Miscellaneous directory (
 >>> http://xml.resource.org/public/rfc/bibxml2/ ) Rationale: it's the
 >>> one that primarily comes up in discussion of 'how do I update
 >>> this'. It contains citations for documents by various SDOs. -
 >>> Keep the existing one in place. - Make a copy available that can
 >>> be updated by community members, while still being available via
 >>> rsync. (e.g., bibxml2exp/) - Announce experiment with disclaimer
 >>> about quality (as good as you make it). Point to examples of good
 >>> citations. - No gatekeeper on updates. - RPC role is
 >>> contributing, but not reviewing every change. (If the experiment
 >>> concludes and the decision is to replace the existing lib., more
 >>> quality control at that time.)
 >>>
 >>> Thanks, Alice
 >>>
 >>> Begin forwarded message:
 >>>
 >>>
 >>>> From: Glen Zorn <glenzorn@gmail.com>
 >>>>
 >>>> Date: December 5, 2012 10:49:21 PM EST To: =JeffH
 >>>> <Jeff.Hodges@KingsMountain.com>
 >>>>
 >>>> Cc: xml2rfc list <xml2rfc@ietf.org>
 >>>>
 >>>> Subject: Re: [xml2rfc] how to submit updates to the bibxml2
 >>>> misc reference collection?
 >>>>
 >>>> On 12/06/2012 09:40 AM, =JeffH wrote:
 >>>>
 >>>>
 >>>>> Greetings again,
 >>>>>
 >>>>> In the distant past, I submitted various references to the
 >>>>> "Miscellaneous" reference collection..
 >>>>>
 >>>>>
 >>>>> http://xml.resource.org/public/rfc/bibxml2/
 >>>>>
 >>>>>
 >>>>> ..back when Marshall Rose curated that collection by hand.
 >>>>>
 >>>>> How are updates to this collection being presently handled,
 >>>>> or are they being handled at all?
 >>>>>
 >>>> AFAICT, nobody is doing this: I've submitted a number of
 >>>> references but none have ever showed up in the collection.
 >>>> I've even offered to take over the job of updating the
 >>>> collection with no response (possibly because there is no one
 >>>> to take over /from/).
 >>>>
 >>>>
 >>>>> Am curious because I have a few references I'd contribute if
 >>>>> I knew how.
 >>>>>
 >>>> In theory, you just send the reference to this list (but see
 >>>> above).
 >>>>
 >>>>
 >>>>> thanks,
 >>>>>
 >>>>> =JeffH _______________________________________________
 >>>>> xml2rfc mailing list xml2rfc@ietf.org
 >>>>> https://www.ietf.org/mailman/listinfo/xml2rfc
 >>>> _______________________________________________ xml2rfc mailing
 >>>> list
 >>>>
 >>>> xml2rfc@ietf.org https://www.ietf.org/mailman/listinfo/xml2rfc
 >>>>
 >>>>
 >>>>
 >>> _______________________________________________ TOOLS-DEVELOPMENT
 >>> mailing list
 >>>
 >>> TOOLS-DEVELOPMENT@ietf.org
 >>> https://www.ietf.org/mailman/listinfo/tools-development
 >>
 >> _______________________________________________ xml2rfc mailing
 >> list xml2rfc@ietf.org
 >> https://www.ietf.org/mailman/listinfo/xml2rfc
 >
 > _______________________________________________ xml2rfc mailing list
 > xml2rfc@ietf.org https://www.ietf.org/mailman/listinfo/xml2rfc


From nico@cryptonector.com  Mon Dec 17 16:17: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 B35B511E80A3; Mon, 17 Dec 2012 16:17:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.937
X-Spam-Level: 
X-Spam-Status: No, score=-1.937 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7jykndA-cnEN; Mon, 17 Dec 2012 16:17:15 -0800 (PST)
Received: from homiemail-a95.g.dreamhost.com (caiajhbdcbef.dreamhost.com [208.97.132.145]) by ietfa.amsl.com (Postfix) with ESMTP id 154C121F8667; Mon, 17 Dec 2012 16:17:15 -0800 (PST)
Received: from homiemail-a95.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a95.g.dreamhost.com (Postfix) with ESMTP id 8A18E1E069; Mon, 17 Dec 2012 16:17:14 -0800 (PST)
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=73rIsqdcdjfB7hNjZr8t Hl8GVfQ=; b=aZHXIvZHWz7KNAk95+ZvJmmc0QGTGhPvfJ0HB2TlgYdnOsSWbKRx qd7mZNKTvJjIfdc6qeAIfk+qsQMWSmUhg+jXZJ9f/NygIjeSvLYAmEeKWQr0V4CI tf6vS5VyE+QVNArn4iKGFlorbrVLTfR3nrCbg8JB+QtyQMRT/CrrLjo=
Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) (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 0BA6D1E064;  Mon, 17 Dec 2012 16:17:13 -0800 (PST)
Received: by mail-wi0-f173.google.com with SMTP id hn17so2327212wib.12 for <multiple recipients>; Mon, 17 Dec 2012 16:17:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.101.104 with SMTP id ff8mr731182wib.11.1355789832746; Mon, 17 Dec 2012 16:17:12 -0800 (PST)
Received: by 10.217.82.73 with HTTP; Mon, 17 Dec 2012 16:17:12 -0800 (PST)
In-Reply-To: <50CF76B4.5000307@att.com>
References: <50C015C1.8060700@gmail.com> <514A9964-5D1A-43C4-8821-81D658E9F95C@amsl.com> <50C564B0.9070201@att.com> <5826101D-A101-482C-8C98-B6B340AF933A@amsl.com> <50CF76B4.5000307@att.com>
Date: Mon, 17 Dec 2012 18:17:12 -0600
Message-ID: <CAK3OfOifdFRpghnRrcREODBYh1-90H9dgt3gTGZ5Y_90hppdHA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Tony Hansen <tony@att.com>
Content-Type: text/plain; charset=UTF-8
Cc: xml2rfc list <xml2rfc@ietf.org>, tools-development@ietf.org
Subject: Re: [xml2rfc] [TOOLS-DEVELOPMENT] xml2rfc citation lib.
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, 18 Dec 2012 00:17:15 -0000

On Mon, Dec 17, 2012 at 1:47 PM, Tony Hansen <tony@att.com> wrote:
> Alice, I think you're on the right track. Two issues come to mind:
>
> *) Who should do the verification?

The RFC-Editor.  Duh -- they have to anyways.  :)

> *) I think the frequency should be more often than once a year. Quarterly?
>
> I also think it should be possible for someone to ask for a faster review of
> a particular entry.

At RFC publication time, *not* periodically.

This way it's trivial: there's a repo we all contribute to with total
freedom and no checking whatsoever, possibly including garbage, and
there's a repo that the RFC-Editor contributes to only entries that
they've verified *because* they were referenced from I-Ds that made it
to the RFC-Editor queue.

Nico
--

From arusso@amsl.com  Tue Dec 18 08:20:12 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 69DB821F8A75; Tue, 18 Dec 2012 08:20:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O+8YMkoqEY5U; Tue, 18 Dec 2012 08:20:11 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 8CED421F8A5A; Tue, 18 Dec 2012 08:20:10 -0800 (PST)
Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 84D4F124A53; Tue, 18 Dec 2012 08:20:10 -0800 (PST)
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 znBs8gzd4hxD; Tue, 18 Dec 2012 08:20:10 -0800 (PST)
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 D185A12472E; Tue, 18 Dec 2012 08:20:09 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Alice Russo <arusso@amsl.com>
In-Reply-To: <50CF76B4.5000307@att.com>
Date: Tue, 18 Dec 2012 11:20:08 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D43DACEC-BF2F-4CCD-912C-D09BA93544E5@amsl.com>
References: <50C015C1.8060700@gmail.com> <514A9964-5D1A-43C4-8821-81D658E9F95C@amsl.com> <50C564B0.9070201@att.com> <5826101D-A101-482C-8C98-B6B340AF933A@amsl.com> <50CF76B4.5000307@att.com>
To: Tony Hansen <tony@att.com>
X-Mailer: Apple Mail (2.1085)
Cc: xml2rfc list <xml2rfc@ietf.org>, tools-development@ietf.org
Subject: Re: [xml2rfc] [TOOLS-DEVELOPMENT] xml2rfc citation lib.
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, 18 Dec 2012 16:20:12 -0000

On Dec 17, 2012, at 2:47 PM, Tony Hansen wrote:

> Alice, I think you're on the right track. Two issues come to mind:
>=20
> *) Who should do the verification?

Will talk more with the RFC Series Editor and the RFC Production Center =
(RPC) about this.  I see these potential roles for the RPC in this =
experiment:
- Add: commit new Misc. refs that are used in approved I-Ds.
- Edit: correct existing Misc. refs that are used in approved I-Ds.
- Review: periodic review of the diff between bibxml2 & bibxml2exp. Copy =
good refs over to bibxml2.

(Perhaps we could consider a ref that is added or edited by the RPC as =
already reviewed, so a ref could be committed to both bibxml2 and =
bibxml2exp at that time.)

>=20
> *) I think the frequency should be more often than once a year. =
Quarterly?
>=20

Was envisioning less frequency because it gives time for entries to be =
added and edited in the experimental directory by the community.  The =
more it gets used, the more it gets updated.  For example, if authors =
pull a ref into their draft, and it's not correct, then there's the =
motivation to fix it in the library. Then, when the periodic checking =
occurs, hopefully the refs are in better shape.

In response to Nico's suggestion, "At RFC publication time, *not* =
periodically" -- useful refs are in various I-Ds, and most I-Ds do not =
become RFCs, so I think *more* refs than just those in RFCs should be =
included in the library.  I.e., the hurdle should be 'the ref was added =
to the exp. directory and its content is correct', not 'the ref was used =
in an RFC'.

> I also think it should be possible for someone to ask for a faster
> review of a particular entry.

Why would some refs need to be reviewed quickly?

Thanks,
Alice

>=20
>    Tony
>=20
> On 12/17/2012 2:12 PM, Alice Russo wrote:
>> Hi Tony,
>>=20
>>> I like the idea of opening up editing privileges, and might even =
consider making it bibxml2 itself that was opened up. However, there =
needs to be a bit of quality control on the changes before getting =
pushed out. For example, verification for proper BIBREF XML is a =
minimum.
>> If there is automated verification when committing a file, seems =
there would still be a later QC step. How about this separation?
>>=20
>> - bibxml2/ is fairly static (e.g., updated yearly) and content has =
been checked.
>> - bibxml2exp/ is open for community editing, so it's used with =
awareness that its content has not been checked (beyond minimal =
verification) and is a moving target.
>>=20
>> Perhaps once a year the content of bibxml2exp/ is checked, and good =
refs are copied over to bibxml2/.
>>=20
>> Thanks,
>> Alice
>>=20
>> On Dec 9, 2012, at 11:27 PM, Tony Hansen wrote:
>>=20
>>> A couple IETFs ago, I tried unraveling the rat's nest that makes up =
the bibxml directories during the codesprint. My hope was to make sure =
that each of the references that reflected data coming from other SDOs =
actually used a feed from those other SDOs.
>>>=20
>>> I made little progress and haven't made it back to that effort.
>>>=20
>>> As far as I know, all of the current data *is* in svn.
>>>=20
>>> I like the idea of opening up editing privileges, and might even =
consider making it bibxml2 itself that was opened up. However, there =
needs to be a bit of quality control on the changes before getting =
pushed out. For example, verification for proper BIBREF XML is a =
minimum.
>>>=20
>>>     Tony Hansen
>>>=20
>>> On 12/6/2012 10:55 AM, Alice Russo wrote:
>>>> Hi,
>>>>=20
>>>> FYI, this topic came up again on the xml2rfc list.
>>>>=20
>>>> An idea for making use of various individuals' energy to improve =
the citations library:
>>>> - Start an experiment with the Miscellaneous directory (
>>>> http://xml.resource.org/public/rfc/bibxml2/
>>>> ) Rationale: it's the one that primarily comes up in discussion of =
'how do I update this'. It contains  citations for documents by various =
SDOs.
>>>> - Keep the existing one in place.
>>>> - Make a copy available that can be updated by community members, =
while still being available via rsync. (e.g., bibxml2exp/)
>>>> - Announce experiment with disclaimer about quality (as good as you =
make it). Point to examples of good citations.
>>>> - No gatekeeper on updates.
>>>> - RPC role is contributing, but not reviewing every change. (If the =
experiment concludes and the decision is to replace the existing lib., =
more quality control at that time.)
>>>>=20
>>>> Thanks,
>>>> Alice
