[xml2rfc-dev] RFC 7991 issue #38: Schema Issue, RFC 7991, In Section 2.20, <dl>
henrik@levkowetz.com Mon, 01 October 2018 11:35 UTC
Return-Path: <henrik@levkowetz.com>
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 4F8BC130DFA for <xml2rfc-dev@ietfa.amsl.com>; Mon, 1 Oct 2018 04:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_MANY_HDRS_LCASE=0.01, 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 vmenye_Wwi27 for <xml2rfc-dev@ietfa.amsl.com>; Mon, 1 Oct 2018 04:35:47 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FADE120072 for <xml2rfc-dev@ietf.org>; Mon, 1 Oct 2018 04:35:47 -0700 (PDT)
Received: from localhost ([::1]:40365 helo=durif.tools.ietf.org) by durif.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1g6wUN-0002BH-Et for xml2rfc-dev@ietf.org; Mon, 01 Oct 2018 04:35:47 -0700
to: xml2rfc-dev@ietf.org
from: henrik@levkowetz.com
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Message-Id: <E1g6wUN-0002BH-Et@durif.tools.ietf.org>
Date: Mon, 01 Oct 2018 04:35:47 -0700
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/POMMey4sUe2L5obIYu-mSmmaKDs>
Subject: [xml2rfc-dev] RFC 7991 issue #38: Schema Issue, RFC 7991, In Section 2.20, <dl>
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: Mon, 01 Oct 2018 11:35:50 -0000
This captures an issue noted during implementation, also described in https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation#section-3.1.3 Specification: https://tools.ietf.org/html/rfc7991#section-2.20 --- In Section 2.20, <dl> The current specification says: "The "hanging" attribute defines whether or not the term appears on the same line as the definition. hanging="true" indicates that the term is to the left of the definition, while hanging="false" indicates that the term will be on a separate line." This does not match established typographic terminology. In typographic terminology, "hanging indent" describes the case where the indentation of the second and subsequent lines of a paragraph is greater than the indentation of the first line. Whether the definition in a definition list starts on the first line or not has nothing to do with the presence of hanging indent; our definition lists will _always_ have hanging indent. The 'hanging' attribute also describes something different from what the term has been used to describe in the version 2 vocabulary. This will be confusing to users. A more descriptive name for the attribute we're talking about would be 'start-definition-on-first-line', but that's unwieldy. Maybe 'newline="false"' to start the definition on the first line, or something like 'definition-start="first"'? Recommendation: Change this to a different term that is more descriptive and does not use typographically incorrect terminology. Implementation: The current version of xml2rfc still uses "hanging". --- Regards, Henrik --- This issue is tracked at: https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/38 Discussion should take place on this list.