Re: [rfc-i] [xml2rfc] use of sourcecode type
Carsten Bormann <cabo@tzi.org> Thu, 23 July 2020 04:36 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 756993A0C3C; Wed, 22 Jul 2020 21:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level:
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=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 fSvzltYx-Bfq; Wed, 22 Jul 2020 21:36:01 -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 AA0F93A0C3B; Wed, 22 Jul 2020 21:36:01 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 2E3D3F40755; Wed, 22 Jul 2020 21:35:45 -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 2C94EF40755 for <rfc-interest@rfc-editor.org>; Wed, 22 Jul 2020 21:35:43 -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 BX7iB3zPrOdA for <rfc-interest@rfc-editor.org>; Wed, 22 Jul 2020 21:35:39 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) by rfc-editor.org (Postfix) with ESMTPS id 288A0F4074D for <rfc-interest@rfc-editor.org>; Wed, 22 Jul 2020 21:35:39 -0700 (PDT)
Received: from [172.16.42.100] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4BBzzY6cgPzySL; Thu, 23 Jul 2020 06:35:53 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5858459-521b-fa9f-aeff-798fccd9320@taugh.com>
Date: Thu, 23 Jul 2020 06:35:53 +0200
X-Mao-Original-Outgoing-Id: 617171753.247084-efa967b4435ba63bf3bf97c8d847a1ab
Message-Id: <76637229-EBA3-4A33-B490-AB38E48F0896@tzi.org>
References: <20200723024552.38FAE1D65AD2@ary.qy> <8ea0ca88-15da-4d86-b199-0d99dc7675fe@www.fastmail.com> <6d87c55-6d3-81fb-bf70-8f9a46d76b0@taugh.com> <4A99E8F7-4D7F-43C4-B66E-0BB27A16387A@tzi.org> <5858459-521b-fa9f-aeff-798fccd9320@taugh.com>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3608.120.23.2.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>
Cc: rfc-interest@rfc-editor.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
> On 2020-07-23, at 06:22, John R Levine <johnl@taugh.com> wrote: > > On Thu, 23 Jul 2020, Carsten Bormann wrote: >> On 2020-07-23, at 05:40, John R Levine <johnl@taugh.com> wrote: >>> >>> o svg >> >> In an authoring system such as kramdown-rfc, you get to use source-code (e.g., some form of UML) to generate artwork (right now limited to our SVG subset, or plaintext (“ASCII”) art). >> >> The existing vocabulary cannot represent this. >> But that is maybe mostly OK, because at the author-publisher interface, the source code (i.e., editable form) is no longer needed. >> Until it is. > > This list of artwork types isn't cast in stone. If we need new ones, we can add them. If we want to add the artwork source code to the artwork types, we need to identify them as “needing processing” — presenting them as plaintext (“ASCII”) art may make more or less sense, but they really aren’t. So we have TXT HTML Plaintext art x x SVG - (*) x Source code ? (**) p Where x means “can be presented in” and p means “needs processing for”. (With tools such as ditaa and goat, the difference between source code and plaintext art diminished.) (**) Some tools are able to generate fallback TXT, notably plantuml for some of its input forms. (*) This is the place where artset was intended to help. We may see all three, source code, fallback plaintext, and SVG in an artset... Grüße, Carsten _______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- Re: [rfc-i] [xml2rfc] use of sourcecode type Carsten Bormann
- Re: [rfc-i] [xml2rfc] use of sourcecode type Paul Kyzivat
- Re: [rfc-i] [xml2rfc] use of sourcecode type Henrik Levkowetz
- Re: [rfc-i] [xml2rfc] use of sourcecode type John R Levine
- Re: [rfc-i] [xml2rfc] use of sourcecode type Martin Thomson
- Re: [rfc-i] [xml2rfc] use of sourcecode type John Levine
- Re: [rfc-i] [xml2rfc] use of sourcecode type Martin Thomson
- Re: [rfc-i] [xml2rfc] use of sourcecode type John R Levine
- Re: [rfc-i] [xml2rfc] use of sourcecode type Carsten Bormann
- Re: [rfc-i] [xml2rfc] use of sourcecode type John R Levine
- Re: [rfc-i] [xml2rfc] use of sourcecode type Carsten Bormann
- Re: [rfc-i] [xml2rfc] use of sourcecode type Julian Reschke
- Re: [rfc-i] [xml2rfc] use of sourcecode type Paul Kyzivat
- Re: [rfc-i] [xml2rfc] use of sourcecode type Carsten Bormann
- Re: [rfc-i] [xml2rfc] use of sourcecode type Paul Kyzivat
- Re: [rfc-i] [xml2rfc] use of sourcecode type Carsten Bormann
- Re: [rfc-i] [xml2rfc] use of sourcecode type Julian Reschke
- Re: [rfc-i] [xml2rfc] use of sourcecode type Carsten Bormann
- Re: [rfc-i] [xml2rfc] use of sourcecode type Julian Reschke
- Re: [rfc-i] [xml2rfc] use of sourcecode type Carsten Bormann
- Re: [rfc-i] [xml2rfc] use of sourcecode type Cullen Jennings
- Re: [rfc-i] [xml2rfc] use of sourcecode type Cullen Jennings
- Re: [rfc-i] [xml2rfc] use of sourcecode type Julian Reschke
- Re: [rfc-i] [xml2rfc] use of sourcecode type Henrik Levkowetz