IETF Logo Mail Archive

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

Robert Sparks <rjsparks@nostrum.com> Fri, 04 February 2022 14:31 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 81E053A13F3 for <xml-sg-cmt@ietfa.amsl.com>; Fri, 4 Feb 2022 06:31:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level:
X-Spam-Status: No, score=-2.079 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, 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 MJFVA5BG5kdI for <xml-sg-cmt@ietfa.amsl.com>; Fri, 4 Feb 2022 06:30:57 -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 549DE3A13F0 for <xml-sg-cmt@ietf.org>; Fri, 4 Feb 2022 06:30:55 -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 214EUq8q015147 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <xml-sg-cmt@ietf.org>; Fri, 4 Feb 2022 08:30:53 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1643985053; bh=eS8t7gAw0cPdIVMcBb6I3iwt247ZjoFgO5j8Js03qSQ=; h=Date:To:From:Subject; b=jyIOZzPmVkb+Q5DB2qiXM61VmOr2uaCg0rX5mQ8y//4a3SUu2+/kwB0N2lhKKxY05 x02nlwO3STv+jp67z8HwDjRZDXEDEY0aavYX5fxysQCcgN8m4NlWSNgyU0ymBxFqKh CxeV26xQMFLZXwpIj96cnuraRSom1fIIj2IDnWn4=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.114]
Message-ID: <89fcb770-28d8-fb59-101c-a62dbdf358cb@nostrum.com>
Date: Fri, 04 Feb 2022 08:30:47 -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" <xml-sg-cmt@ietf.org>
From: Robert Sparks <rjsparks@nostrum.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/jxDibCUKZHvlC2BeqCqtQzsxfSk>
Subject: [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: Fri, 04 Feb 2022 14:31:02 -0000

Working through the new bibxml service, I've been reminded that the 
datatracker is currently generating bibxml-ids with a deprecated element:

<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.sparks-sipcore-multiple-reasons">
    <front>
       <title>Multiple SIP Reason Header Field Values</title>
       <author fullname="Robert Sparks">
      </author>
       <date month="November" day="12" year="2021" />
       <abstract>
      <t>   The SIP Reason Header Field as defined in RFC 3326 allows 
only one
    Reason value per protocol value.  Practice shows it is useful to
    allow multiple values with the same protocol value.  This update to
    RFC 3326 allows multiple values for an indicated registered protocol
    when that protocol defines what the presence of multiple values
    means.

      </t>
       </abstract>
    </front>
    <seriesInfo name="Internet-Draft" 
value="draft-sparks-sipcore-multiple-reasons-00" />
    <format type="TXT" 
target="https://www.ietf.org/archive/id/draft-sparks-sipcore-multiple-reasons-00.txt" 
/>
</reference>

In particular at <format>.

The new service plans to instead emit.

<reference 
target="https://www.ietf.org/archive/id/draft-sparks-sipcore-multiple-reasons-00.txt" 
anchor="I-D.sparks-sipcore-multiple-reasons">
   <front>
     <title>Multiple SIP Reason Header Field Values</title>
     <author fullname="Robert Sparks"/>
     <date year="2021" month="November" day="12"/>
     <abstract>
       <t>The SIP Reason Header Field as defined in RFC 3326 allows only 
one Reason value per protocol value. Practice shows it is useful to 
allow multiple values with the same protocol value. This update to RFC 
3326 allows multiple values for an indicated registered protocol when 
that protocol defines what the presence of multiple values means.</t>
     </abstract>
   </front>
   <seriesInfo name="Internet-Draft" 
value="draft-sparks-sipcore-multiple-reasons-00"/>
</reference>

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?

RjS

v2.23.0 | Report a Bug | By Email