Re: [Xml-sg-cmt] Use of Reference elements in bibxml

Robert Sparks <rjsparks@nostrum.com> Mon, 07 February 2022 16:03 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: xml-sg-cmt@ietfa.amsl.com
Delivered-To: xml-sg-cmt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F35653A08A8 for <xml-sg-cmt@ietfa.amsl.com>; Mon, 7 Feb 2022 08:03:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.793
X-Spam-Level:
X-Spam-Status: No, score=-7.793 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_HI=-5, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dqfe1TrBSgPB for <xml-sg-cmt@ietfa.amsl.com>; Mon, 7 Feb 2022 08:03:12 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 067943A0F74 for <xml-sg-cmt@ietf.org>; Mon, 7 Feb 2022 08:02:25 -0800 (PST)
Received: from [192.168.1.114] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 217G2NDv008733 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <xml-sg-cmt@ietf.org>; Mon, 7 Feb 2022 10:02:23 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1644249743; bh=R0CAZoC6lmAYJXAUO0DlyeR1MWYwzvJG1mYCLsDFJfc=; h=Date:Subject:To:References:From:In-Reply-To; b=DROhsN3O2KK7g2z3SHI51DQBeKy1CIDg8tH09FpHTN4VTelK3UGifxEwUICgk4zGi yr5J5j63qlNOU1gsz0lD50X0bH9fcmpOixP9W3qAYvcDHWAe7/d+LzmOrimXStqIFk 0e7X0y4lWqSjBuj3K+Ee6czcBegaCBVbEv1v0b+8=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.114]
Message-ID: <a1f154cf-a9ee-83c5-9b0e-5e0ea3e4c69f@nostrum.com>
Date: Mon, 07 Feb 2022 10:02:18 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.1
Content-Language: en-US
To: xml-sg-cmt@ietf.org
References: <89fcb770-28d8-fb59-101c-a62dbdf358cb@nostrum.com> <3149c720-e2fb-2b96-fcaa-4c495ba5a58f@taugh.com>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <3149c720-e2fb-2b96-fcaa-4c495ba5a58f@taugh.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml-sg-cmt/0gSfQh59Vc_w-pRfe1ad8wtCjQw>
Subject: Re: [Xml-sg-cmt] Use of Reference elements in bibxml
X-BeenThere: xml-sg-cmt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working list for the xml and style guide change management team <xml-sg-cmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml-sg-cmt/>
List-Post: <mailto:xml-sg-cmt@ietf.org>
List-Help: <mailto:xml-sg-cmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Feb 2022 16:03:17 -0000

On 2/4/22 11:23 AM, John R Levine wrote:
>> We had (I thought) an open question around the deprecation of 
>> <format> at 
>> https://datatracker.ietf.org/doc/html/draft-levkowetz-xml2rfc-v3-implementation-notes-13#section-3.1.27, 
>> but I'm not finding a ticket (open or closed). Am I missing something?
>
> No, I think you're right, we never resolved it.
Was this a single issue from the draft that we missed, or do we need to 
scrape the draft again?
>
> I am of two minds about the fornat question.  On the one hand, we 
> publish in multiple formats and plan to do so indefinitely.
>
> On the other hand, this is a bibliography entry so it makes sense to 
> have one link to the info page, not try and guess what formats are 
> available. In practice you cannot tell what RFCs have what formats 
> without looking at the web site.  The entries in rfc-index.xml say 
> which ones are supposed to be there, but some are missing, and in 
> several cases there are two different PDFs (printout of the text, and 
> either a scan of a paper document or converted Postscript), so this is 
> another place where I don't think the benefit from the extra details 
> are worth it.  Sort of like the postal thing.
You're still thinking with RFC blinders on. The bibxml references for 
_drafts_ could be constructed pointing to all versions the datatracker 
knows about. Or it could point only to the datatracker's main page 
instead of the txt version of the document, but there's a lot of dissent 
in the community about what "real" customers of our products should see 
most easily.
>
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
>