IETF Logo Mail Archive

Re: [rfc-i] Request for feedback: the new CSS

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 02 December 2016 19:34 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 D601B12951F for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 2 Dec 2016 11:34:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.984
X-Spam-Level:
X-Spam-Status: No, score=-6.984 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=gmail.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 soqZZM3n0wzU for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 2 Dec 2016 11:34:37 -0800 (PST)
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 E82271295DF for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 2 Dec 2016 11:34:36 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id DE8D7B8012C; Fri, 2 Dec 2016 11:34:36 -0800 (PST)
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 B582DB8012D for <rfc-interest@rfc-editor.org>; Fri, 2 Dec 2016 11:34:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 QMGwVgryDMXZ for <rfc-interest@rfc-editor.org>; Fri, 2 Dec 2016 11:34:34 -0800 (PST)
Received: from mail-pg0-x230.google.com (mail-pg0-x230.google.com [IPv6:2607:f8b0:400e:c05::230]) by rfc-editor.org (Postfix) with ESMTPS id 941B7B8012C for <rfc-interest@rfc-editor.org>; Fri, 2 Dec 2016 11:34:34 -0800 (PST)
Received: by mail-pg0-x230.google.com with SMTP id p66so110561863pga.2 for <rfc-interest@rfc-editor.org>; Fri, 02 Dec 2016 11:34:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=AiSgcW7Dee9BfAInyC9rBHKiXVWkyJ7PAxcwILAdKl4=; b=0YtZeYeBa/f/88gHkNkHoInmFFPztd4D9ebUuONvaLbGKFh4/pghw7XQtFF2m9Yx8h TerP3oMvpZhIbOkuAZdzemRj3lWj6ZyT2Vx5GbasG7dUeNVz3R6R7FBbFQoDBZj0EcIb voojoq2j7SF/9Eu/Fx+JV8n7nZQsHw5Efz5LzbYpNP+UNAx93WyVV1es7j7T07cpNcmM sr5T056QvvXPXhq6+76i5ZpUXNVvBqkYCEqHlRF1DLLQHsvwXQrLoqnnZM3MMXJrYcWE dDmCDAJaz3bm8fa+Wzsbqmi8pE01Qc155/7LpDQCqMBK6BmdDZ6L54HHF80DQG9+Ubez dvyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=AiSgcW7Dee9BfAInyC9rBHKiXVWkyJ7PAxcwILAdKl4=; b=JK1LFiIFLwP15OlEvX9SBcl6iS2rQ/tBfygOp4403Q2ZTMlDmf7qz1YxntrI6RYhy2 94thsAVIANCZ91vjuLKRHAGqE7Yd6WilN3srjiUiAzek3mt6RozVRyK1rFkfcs8BzGlG c0Wg5UOeqBR1JkE0Soz/0aAmn6EAlIsn96Q9t4SCrKQjCoZ5m/UeLCdwm3o8BJGAl0wy UOl5jVsPnKzQtZBiiZtsaH28hK1/b5jmgeCOPdD6c3aeIsPYqHXE6H5CXL3foXkrYo7q IYezNS/23gUUM218Mvv/0mGDIKAXdFTDkCXovO3TWqK5+81LfUa5g4z8v5nNsdGPuBDU b4UQ==
X-Gm-Message-State: AKaTC007IVI/pRPk3FZX2TaYva0jjIrBTbtnEx7WdCMOAp39iAFamHeIb6+w/IrCCjHLUw==
X-Received: by 10.99.133.200 with SMTP id u191mr81373764pgd.28.1480707273924; Fri, 02 Dec 2016 11:34:33 -0800 (PST)
Received: from [192.168.178.21] ([118.148.125.241]) by smtp.gmail.com with ESMTPSA id o29sm9598791pgn.28.2016.12.02.11.34.32 for <rfc-interest@rfc-editor.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Dec 2016 11:34:33 -0800 (PST)
To: rfc-interest@rfc-editor.org
References: <0efdc6b9-5bc5-c14c-7d25-5f0e8e96ba72@rfc-editor.org> <04f701d24c79$3df584e0$b9e08ea0$@olddog.co.uk> <297E37B4-ADE7-43C8-8F5F-07E142CA2F9E@cursive.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <dcf267f7-a40c-bb7a-6511-5b7bfa99862f@gmail.com>
Date: Sat, 03 Dec 2016 08:34:42 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <297E37B4-ADE7-43C8-8F5F-07E142CA2F9E@cursive.net>
Subject: Re: [rfc-i] Request for feedback: the new CSS
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.21
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: 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 03/12/2016 06:09, Joe Hildebrand wrote:
>> On Dec 2, 2016, at 1:51 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
>>
>> Thanks for this Heather,
>>
>>> If you have suggestions or recommendations, please add them as an issue
>>> in github.
>>
>> No, it's alright, I'll just raise them in an email (this email) for discussion
>> on the mailing list as normal so other only have to look in one place for the
>> conversation :-)
>>
>> 1. You have some embedded code fragments. Is it your intention that these will
>> still be visibly marked <CODE BEGINS> and <CODE ENDS>?
> 
> As far as I know, those markings are optional, right?

Not exactly. And they aren't our choice - they are defined in the IETF Trust
legal provisions:

>>> License to Code Components.
>>> 
>>> Definition. IETF Contributions and IETF Documents often include
>>> components intended to be directly processed by a computer (“Code Components”).
>>> A list of common Code Components can be found at http://trustee.ietf.org/license-info/. 
>>> 
>>> Identification. Text in IETF Contributions and IETF Documents of the types
>>> identified in Section 4.a above shall constitute “Code Components”. In addition,
>>> any text found between the markers <CODE BEGINS> and <CODE ENDS>, or otherwise
>>> clearly labeled as a Code Component, shall be considered a “Code Component”.

So regardless of what would be most elegant in XML2RFCv3, authors must be able
to include these labels explicitly.

> The idea is that extracting code from the XML should be much easier than parsing the text for <CODE BEGINS> and <CODE ENDS>.
> 

    Brian

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email