IETF Logo Mail Archive

Re: [rfc-i] Information in .json files

Mark Nottingham <mnot@mnot.net> Mon, 11 March 2024 22:07 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D83D3C14F5EC for <rfc-interest@ietfa.amsl.com>; Mon, 11 Mar 2024 15:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.807
X-Spam-Level:
X-Spam-Status: No, score=-2.807 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b="oDOGq+Ch"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="GPaBpa2K"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kZ1xps-Hgrpm for <rfc-interest@ietfa.amsl.com>; Mon, 11 Mar 2024 15:06:56 -0700 (PDT)
Received: from wfout8-smtp.messagingengine.com (wfout8-smtp.messagingengine.com [64.147.123.151]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FEB8C14CEE3 for <rfc-interest@rfc-editor.org>; Mon, 11 Mar 2024 15:06:55 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailfout.west.internal (Postfix) with ESMTP id D31291C00088; Mon, 11 Mar 2024 18:06:54 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 11 Mar 2024 18:06:55 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1710194814; x=1710281214; bh=2SdXuTO1vVX51gXbhkVyBO/e9wdaTBD9+I2Kd8b3cBY=; b= oDOGq+Chcu6DUV+srMycUHaIudFZlUOetFJ3G1jZWtqGeYhFQ3rrv75m4gSO5Zmb zwdeuHtqp6CBr9wI8K7HS9V1Dwe7tMjpkD+vJwqzQkTpai1RNLoYEXHB9M/9EQC1 AIjqQzSjP10BcDj+uilcYsB5AYC6wbFUoxVdt/7jlR5l3x9rMgFTW78U8bl4RKaA KtaJbKoA0FdiqXSe31ahw78XeKshD33m/MiVG1+ZZFnq9nIvAGqbc7jCWU0zqBw/ umSU1PnHSvL3ovXLAboVipLmzn1a+JbORAkdaxsG61w2GMD9AsOfMltxSq5PtlkN aAgy+HCBMIDo/c8SW4XPeQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1710194814; x= 1710281214; bh=2SdXuTO1vVX51gXbhkVyBO/e9wdaTBD9+I2Kd8b3cBY=; b=G PaBpa2KOgLkTErkNY0thwA3S5pTkeF8TyD88SgVZC/7MtKcigzOkCpumhebPioex 8xorWOW7s0U7dH9xZJZ6ALXdKQ0/1dpckh6PfqC6iHsN5ghEJL0Bhzsg87tCVIbd Us5t0C92xfil5jAo85LSa2mShomE/dNYhfFbtLVY1RRsanfE3Av15c4zlRJyt3nl 0MYRMAVKNZX8fO85hxwRtBgIMCYvc+M34xDPmPOoO4BTAxoS4n4AxcsD2tgipTE7 5qyUz2uq5xdfbsElBldnP7/iwI6qhI3U/Bk+59LlLgZ1aSF3cmRsvVEqgfmkpdp5 cSzb4OWUiDDQniK2Agj9w==
X-ME-Sender: <xms:foDvZbUgmi5aiziK-7vcRzEQINTbc6txQyHqVpaC29ENgAP5zT28xQ> <xme:foDvZTmn1LVqG0-i_emsltdSUhsoyZz1s8movrHQejTkCVq610fsFwTcfaAYMyShN CDxsJWAuN0pCFsqlQ>
X-ME-Received: <xmr:foDvZXbBtAfZR0_i6Q6aTUzeT9aGf1Kn-VZxuEpZLe2RzNxMR_ZqTo14KjlueQI1hlp34BAbjw_8qzmOn-8LDp0I1JBAEKfuAWCxjAhqpE8R-OX-xUphZB4N>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrjedugdduheekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptgfghfggufffkfhfvegjvffosehtqhhmtdhhtdejnecuhfhrohhmpeforghr khcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrth htvghrnhepkeekvdevtdeuieevvdetjefhhfdthfeukeelgedvvedvleetueeugfffjeef udfgnecuffhomhgrihhnpehmnhhothdrnhgvthdprhhftgdqvgguihhtohhrrdhorhhgne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohht sehmnhhothdrnhgvth
X-ME-Proxy: <xmx:foDvZWXPcZ-9wKBEtVFzMezDhxnjpb2xuf6MQZOSaOdytE-a1SM59g> <xmx:foDvZVnQKScdeGFKGIu8MPvvPJX7ctwwDeCVS3204Qvf6yVvg9ztSw> <xmx:foDvZTdI8P7VyaGFNSfubvNzRplqZBEvqQJEBEn3fEGeGYexAj0-Uw> <xmx:foDvZawvcyW4oCt8SGgw295T3d4DCqHMo5ah-QXN46a84Tu9NlwMmbVPA0w>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 11 Mar 2024 18:06:53 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Mark Nottingham <mnot@mnot.net>
Mime-Version: 1.0 (1.0)
Date: Tue, 12 Mar 2024 09:06:49 +1100
Message-Id: <61C0E854-A65A-4CC5-90E2-51FC160481F9@mnot.net>
References: <67306CB7-C44D-4F33-A894-0F9924A2CE08@amsl.com>
Cc: rfc-interest@rfc-editor.org
In-Reply-To: <67306CB7-C44D-4F33-A894-0F9924A2CE08@amsl.com>
To: Alice Russo <arusso@amsl.com>
X-Mailer: iPhone Mail (21E219)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/UQTpse6pL1BG5GV5zt4qA2MoaxE>
Subject: Re: [rfc-i] Information in .json files
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2024 22:07:01 -0000

Thanks, Alice. 

I noticed that the source field doesn’t contain the same information as the index - for example, the most recent revisions of http contain”HTTP” not “httpbis”.  That makes it hard to use in an automated fashion (and even if it matched the wg short names, you’d still need a canonical mapping of wg names to streams to process it).

Cheers,

Sent from my iPhone

> On 12 Mar 2024, at 9:00 AM, Alice Russo <arusso@amsl.com> wrote:
> 
> Hi Mark,
> 
> For JSON files of RFCs
> - from the IETF stream, source holds the WG name or "IETF - NON WORKING GROUP".
> - from other streams, source holds "IAB", "IRTF" (or RG name for more recent RFCs), "INDEPENDENT", or "Editorial" (although none exist yet).
> - without stream information, source holds "Legacy".
> 
> Examples below.
> 
> Alice Russo
> RFC Production Center
> --
> 
> Examples:
> rfc7654.json contains "source":"Benchmarking Methodology"
> rfc9373.json contains "source":"IETF - NON WORKING GROUP"
> rfc9383.json contains "source":"INDEPENDENT"
> rfc9510.json contains "source":"Information-Centric Networking Research Group"
> 
>> On Mar 8, 2024, at 5:42 PM, Mark Nottingham <mnot=40mnot.net@dmarc.ietf.org> wrote:
>> 
>> Hello,
>> 
>> I'm trying to use the information in the per-RFC JSON files (obtained via rsync), but I'm finding that it doesn't have everything available in rfc-index.xml.
>> 
>> Specifically, it doesn't seem to have stream, area, or WG information.
>> 
>> Would it be possible to add this info to those files?
>> 
>> Cheers,
>> 
>> --
>> Mark Nottingham   https://www.mnot.net/
>> 
>> _______________________________________________
>> rfc-interest mailing list
>> rfc-interest@rfc-editor.org
>> https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
>> 
>

v2.23.0 | Report a Bug | By Email