IETF Logo Mail Archive

Re: [xml2rfc-dev] [rfc-i] RFC 8661 in AUTH48, was: [v3] Please help review v3 files

Heather Flanagan <rse@rfc-editor.org> Wed, 18 September 2019 20:09 UTC

Return-Path: <rse@rfc-editor.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A909120953 for <xml2rfc-dev@ietfa.amsl.com>; Wed, 18 Sep 2019 13:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 VOYziJ1U5VxN for <xml2rfc-dev@ietfa.amsl.com>; Wed, 18 Sep 2019 13:09:18 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B50DE120086 for <xml2rfc-dev@ietf.org>; Wed, 18 Sep 2019 13:09:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A5729202192; Wed, 18 Sep 2019 13:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UrFgB5BC_QNI; Wed, 18 Sep 2019 13:08:53 -0700 (PDT)
Received: from [10.15.85.93] (pppoe-72-19-47-021.cascadeaccess.com [72.19.47.21]) by c8a.amsl.com (Postfix) with ESMTPSA id 230B5202191; Wed, 18 Sep 2019 13:08:53 -0700 (PDT)
From: Heather Flanagan <rse@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 18 Sep 2019 13:09:17 -0700
References: <6D7CF9A5-F8FA-4D78-9001-ADC7CD0B2A36@amsl.com> <6AFC0271-060C-4A2F-84EE-CB40DD328039@amsl.com> <eaf9e970-c570-4ee8-096c-ec70e85c4af5@gmx.de> <dabe2baa-9d71-0089-a486-844a3b24a08b@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>, XML Developer List <xml2rfc-dev@ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
In-Reply-To: <dabe2baa-9d71-0089-a486-844a3b24a08b@gmx.de>
Message-Id: <D7552A58-F10A-4600-962B-151DAB4DA6CB@rfc-editor.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/ME7bvnJPfRNJ-6VRYfdejhUugRA>
Subject: Re: [xml2rfc-dev] [rfc-i] RFC 8661 in AUTH48, was: [v3] Please help review v3 files
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 20:09:20 -0000


> On Sep 17, 2019, at 9:32 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> On 03.08.2019 14:51, Julian Reschke wrote:
>> ... >
>>> ... >> The contributors section in both documents looks terrible in HTML.
>> Probably because there is no defined way to add contributors in a way
>> that renders in a manner consistent with authors in text formats, so the
>> authors choose to use <pre>/<artwork> for that section.  We need to fix
>> that somehow.
>>> 
>>> Right - that was the only way we could get the info to display similar
>>> to Authors’ Addresses.
>>> We will discuss this.
>> 
>> Please discuss here:
>> <https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/81>
>> ...
> 
> FWIW, RFC 8661 (in AUTH48) has that problem.
> 
> Would be good to resolve it in some way before publication.

HI Julian, et al.,

The RFC Editor discussed this internally; we recognize it as a problem for more than just RFC-to-be 8661. That said, for now we’re going to use a work around, as the implementing of a new way of handling the role of “contributor” is outside the existing scope of work. 

The plan for now is touse <artwork> element. Yes, it will look differently than Authors' Addresses in the HTML and PDF outputs. It is not ideal.

The future solution (TBD) may have us creating the role “contributor” and having that signal specific rendering details within the Contributor section. 

This isn’t a showstopper for going live with v3.

-Heather

v2.23.0 | Report a Bug | By Email