Re: [xml2rfc] sourcecode type for config files

Robert Moskowitz <rgm@htt-consult.com> Wed, 26 July 2023 21:32 UTC

Return-Path: <rgm@htt-consult.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 846AEC16B5C7 for <xml2rfc@ietfa.amsl.com>; Wed, 26 Jul 2023 14:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.091, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 l88GA-sEnlOy for <xml2rfc@ietfa.amsl.com>; Wed, 26 Jul 2023 14:32:23 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDBB9C169537 for <xml2rfc@ietf.org>; Wed, 26 Jul 2023 14:32:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 1F310625FC; Wed, 26 Jul 2023 17:31:42 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id LZghR0pcUT+S; Wed, 26 Jul 2023 17:31:36 -0400 (EDT)
Received: from [31.133.150.241] (dhcp-96f1.meeting.ietf.org [31.133.150.241]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 3FF416256E; Wed, 26 Jul 2023 17:31:34 -0400 (EDT)
Message-ID: <6b7563bc-96cd-0dcc-2b13-102c61db14e1@htt-consult.com>
Date: Wed, 26 Jul 2023 17:32:07 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0
Content-Language: en-US
To: Carsten Bormann <cabo@tzi.org>
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
References: <48ee015e-b8c4-a492-6de8-c73170c62d5e@htt-consult.com> <395A5D32-5D33-42C6-BB68-EA647DB88286@tzi.org>
From: Robert Moskowitz <rgm@htt-consult.com>
In-Reply-To: <395A5D32-5D33-42C6-BB68-EA647DB88286@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/L0KiTTPB-N5MURhpTS1i1WVNL0g>
Subject: Re: [xml2rfc] sourcecode type for config files
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2023 21:32:23 -0000


On 7/26/23 16:55, Carsten Bormann wrote:
> On 2023-07-26, at 22:06, Robert Moskowitz <rgm@htt-consult.com> wrote:
>> What is "recommended" type to use for conf files?
> "Configuration file” is a term for what you *use them for*, not what they *are*.
>
> They could be xml, yaml, even json, or some bespoke format (.ini anyone? OK, we now have toml.)
>
> What are they in your case?


openssl.cnf

No xml
No yaml
No json

variable=value

So for now I am using type="conf" as it is like so many linux conf files.

Just was trying to see if there was some pre-defined type to use. "conf" 
is actually quite common out in linux world....