IETF Logo Mail Archive

Re: On XML and $EDITORs (Re: Things that used to be clear (was ...)) "Living Documents") side meeting at IETF105.)

Ted Lemon <mellon@fugue.com> Thu, 11 July 2019 15:09 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CAB712004E for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 08:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.603
X-Spam-Level:
X-Spam-Status: No, score=-0.603 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 u5CVyrig2U_n for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 08:09:20 -0700 (PDT)
Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) (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 14EAD12010F for <ietf@ietf.org>; Thu, 11 Jul 2019 08:09:20 -0700 (PDT)
Received: by mail-ua1-x933.google.com with SMTP id c4so2640173uad.1 for <ietf@ietf.org>; Thu, 11 Jul 2019 08:09:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=WkeTFYX2w/mKB8lXOMILG5XZZaOvplBYw7+t0nZbThs=; b=il/0kWB5Kamo1Nr9Qfg9XEv7cPYOeoglhG2xYdBWSKBgsbazhrp8d/lQv8BD9kKifr tR+MkW+WtujzoedNs41MOmMiaU7TdfFrceioiHjHSENzFeamRIJ1I4OuUCtJgWvAbn+R 9b/ffDdBahcWx3mNMNb0nz8vGh9bHCujNweJPCO9XN9sGeK4uMuVOYzbnNxHUrLK7ApA T2tdHydFYF3SAiUN7f1Rm27RolU0Ihkpj1263SPsuqO3gyKcFVY+9uquCTOQ42hjuy4h B1XM/mWjWVdvfKO0APtwbAWSgRGhYg6koiQFJld8zfK+rz56CGMg3mdnzZhwwE3KF9mV Sk0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=WkeTFYX2w/mKB8lXOMILG5XZZaOvplBYw7+t0nZbThs=; b=ed393Az8UP2pohsY+zLUzsu8WnE66dYToI3o8xeGAiy3X4cB7lFynyZ4V3cJLYbFZV +wYaBgjV7VzEACJXcaH7aQ6UDGw6g3pln632pNln9ZsgsRvITE2SW3UIBtwHzZz3dpKm uJJBylRrSGVpbFC/FH6iIGhlkZKqF9VzITFt7vBlv0LskMLhPp9UNODT9MxkQ2BHdA/6 23eq7exG/uW1l4LvjZ6WZfA2+TXBr92SLb4r9Lep4jECO2//wxXQBY9BDMhR2Credzul vfmqdjhdRC9TNdZ9jJAtK+0Y0Th5uriNfiBB4si7P8qJxJOT56zWJIZW8MPRrBej9e23 ptLA==
X-Gm-Message-State: APjAAAVkzZQTG8Lpm2VPpqQaVcD/HzElHGPe9ntQHwLzZaui2EExBZQe JQ5vIt1Vx83UhF2V/11I01jpHA==
X-Google-Smtp-Source: APXvYqxDQqczWgQbIDYEtIYDIcxy/IuZAAemykmfAN91h8+VjJav9Uf37+nnQqSLXXqdyIqw+0oZMQ==
X-Received: by 2002:ab0:3484:: with SMTP id c4mr5024772uar.51.1562857759059; Thu, 11 Jul 2019 08:09:19 -0700 (PDT)
Received: from ?IPv6:2001:470:c1a2:1:b1f3:9c1:5fa0:2362? ([2001:470:c1a2:1:b1f3:9c1:5fa0:2362]) by smtp.gmail.com with ESMTPSA id z3sm1295805uao.12.2019.07.11.08.09.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Jul 2019 08:09:18 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <0477F142-49A3-4BB4-A763-0BC90A3BF3C7@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_342F8397-8C36-415A-BFCC-06B1BF4F54DA"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: On XML and $EDITORs (Re: Things that used to be clear (was ...)) "Living Documents") side meeting at IETF105.)
Date: Thu, 11 Jul 2019 11:09:15 -0400
In-Reply-To: <4d10d37c-f6cc-f818-6ecd-244f54e6512f@gmx.de>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, Christian Huitema <huitema@huitema.net>, Keith Moore <moore@network-heretics.com>, IETF Discussion Mailing List <ietf@ietf.org>
To: Julian Reschke <julian.reschke@gmx.de>
References: <20190706185415.GB14026@mit.edu> <CABcZeBPgNr5UqQ0pLwwNu5wh0g9L9wCd6YyYKCUDO37SPru-_Q@mail.gmail.com> <20190708202612.GG60909@shrubbery.net> <9ae14ad1-f8d5-befb-64e4-fff063c88e02@network-heretics.com> <CABcZeBOH9LH8Jrz-A5eu9arqUb+bx8xs_eKWi0pyoh7a3qpOPA@mail.gmail.com> <20190708223350.GO3508@localhost> <af3b25d6-af16-a96a-c149-61d01afb4d01@network-heretics.com> <20190708233438.GP3508@localhost> <ea0b9894-ae9d-55a9-a082-af7aac5be66a@huitema.net> <20190710045202.GA3215@localhost> <20190710064451.GB3215@localhost> <06EF2608-038E-400F-86BA-34F57630B53F@fugue.com> <CAMm+LwjFgSK7DSaN2CpLxmL=PO22s2qjBvBHC48jH9UnFy8=wg@mail.gmail.com> <4d10d37c-f6cc-f818-6ecd-244f54e6512f@gmx.de>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qMtXqoLBXYwsje9xiiDE28Rlz74>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jul 2019 15:09:23 -0000

On Jul 11, 2019, at 10:25 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> The insertion of the second one could indeed be automated, but then you
> would have to give a hint about normative vs informative.

That would actually be a really nice enhancement.   It could be the rule that if no reference says, it’s normative, if all references either don’t say or say normative, it’s normative, if all don’t say or say informative, it’s informative, and if some say normative and some say informative, it’s informative.   The idea being that some references to the same document may be normative and some informative, and it makes sense to be able to signal that in the XML.  Maybe every reference should say, but I’m sure that would be a pain.

It would also be nice if the publication date could default to “today” and if the draft number could be determined automatically based on what is most recent…

v2.23.0 | Report a Bug | By Email