Re: [rfc-i] [xml2rfc] use of sourcecode type

Cullen Jennings <fluffy@iii.ca> Fri, 14 August 2020 21:48 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 570613A0B5E; Fri, 14 Aug 2020 14:48:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.898
X-Spam-Level:
X-Spam-Status: No, score=-2.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 PALF8gA1Z1fM; Fri, 14 Aug 2020 14:48:52 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 799773A0B80; Fri, 14 Aug 2020 14:48:52 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 909F9F4074C; Fri, 14 Aug 2020 14:48:42 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id B9B12F4073A for <rfc-interest@rfc-editor.org>; Fri, 14 Aug 2020 14:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ECwftWcAOuLs for <rfc-interest@rfc-editor.org>; Fri, 14 Aug 2020 14:48:36 -0700 (PDT)
Received: from smtp109.iad3b.emailsrvr.com (smtp109.iad3b.emailsrvr.com [146.20.161.109]) by rfc-editor.org (Postfix) with ESMTPS id 21216F40739 for <rfc-interest@rfc-editor.org>; Fri, 14 Aug 2020 14:48:36 -0700 (PDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp6.relay.iad3b.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id A3EA9201FE; Fri, 14 Aug 2020 17:48:43 -0400 (EDT)
From: Cullen Jennings <fluffy@iii.ca>
Message-Id: <3EC1101F-397C-4A64-AEDA-02BB809043D9@iii.ca>
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.15\))
Date: Fri, 14 Aug 2020 15:48:42 -0600
In-Reply-To: <C123625E-B24E-4719-8680-A764F88E8CD7@iii.ca>
To: XML2RFC Interest Group <xml2rfc@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>
References: <e13ad2a9-e460-58cb-3ffe-88acec803a8a@alum.mit.edu> <748F0BE8-5DDA-4CC1-9306-0C67F906C955@tzi.org> <C123625E-B24E-4719-8680-A764F88E8CD7@iii.ca>
X-Mailer: Apple Mail (2.3445.104.15)
X-Classification-ID: 5db7d30b-9b65-4709-8529-b0554f0f09fe-1-1
Subject: Re: [rfc-i] [xml2rfc] use of sourcecode type
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0236819283264060971=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Never-mind - I found 

https://www.rfc-editor.org/materials/sourcecode-types.txt <https://www.rfc-editor.org/materials/sourcecode-types.txt>

Not really sure how I supposed to find that. Could we rev the RFC to have the required information?




> On Aug 14, 2020, at 3:42 PM, Cullen Jennings <fluffy@iii.ca> wrote:
> 
> 
> Related to this, the RFC says "The RFC Series Editor will maintain a complete list of the preferred
>    values on the RFC Editor web site
> “
> 
> Does that list exist somewhere, I’m not finding it ?
> 
> 
> 
>> On Jul 21, 2020, at 9:10 AM, Carsten Bormann <cabo@tzi.org <mailto:cabo@tzi.org>> wrote:
>> 
>> A similar problem is giving examples that are intentionally bad in order to demonstrate a kind of error.
>> 
>> I typically tag them with a type that is derived from the one I would give for real code, e.g., “CDDLx” for a bad CDDL example.  I think it would be good to agree on some way to indicate this.
>> 
>> A related problem is that often several code blocks combine to one valid instance of CDDL, for example see Figure 1, 2, 3 in RFC 8428.  There is no way to say that Figure 1 and 2 combine into a valid instance, and so do Figure 1 and 3, but not any other combination.
>> 
>> And, by the way, those type tags are conventionally lower-cased, but this is not made very explicit; you have to infer that from the list in Section 2.48.4 of RFC 7991 or the RFC editor’s updated copy of that list:
>> 
>> https://www.rfc-editor.org/materials/sourcecode-types.txt <https://www.rfc-editor.org/materials/sourcecode-types.txt>
>> 
>> (Ha, this doesn’t even have “cddl” in it; I’m not sure how this is updated and whether there shouldn’t really be an IANA registry for these.)
>> 
>> Grüße, Carsten
>> 
>> 
>>> On 2020-07-21, at 16:36, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>> 
>>> I have a question about specification of type in sourcecode elements:
>>> 
>>> In RFC4566bis there are many examples that have fragments of SDP. But they aren't compliant to SDP syntax, since it requires that many things be present - that are intentionally omitted from these examples.
>>> 
>>> Is it valid to tag these with type="SDP"?
>>> 
>>> (In sip we had a similar problem. There is a mime-type message/sip, but we sometimes also return fragments of sip in error messages. We ended up defining a separate message/sipfrag mime-type for this.)
>>> 
>>> 	Thanks,
>>> 	Paul
>>> 
>>> _______________________________________________
>>> xml2rfc mailing list
>>> xml2rfc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>> 
>> _______________________________________________
>> rfc-interest mailing list
>> rfc-interest@rfc-editor.org <mailto:rfc-interest@rfc-editor.org>
>> https://www.rfc-editor.org/mailman/listinfo/rfc-interest <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest