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

Joe Hildebrand <hildjj@cursive.net> Fri, 02 December 2016 17:09 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 1D3721294F6 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 2 Dec 2016 09:09:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.987
X-Spam-Level:
X-Spam-Status: No, score=-6.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, 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=neutral reason="invalid (public key: not available)" header.d=cursive.net
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 M6nxGMvFFThX for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 2 Dec 2016 09:09:46 -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 4DC0A12952F for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 2 Dec 2016 09:09:46 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0CBDFB801BA; Fri, 2 Dec 2016 09:09:46 -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 35074B801C3 for <rfc-interest@rfc-editor.org>; Fri, 2 Dec 2016 09:09:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=cursive.net
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 65VVt6LzATHK for <rfc-interest@rfc-editor.org>; Fri, 2 Dec 2016 09:09:43 -0800 (PST)
Received: from mail-yb0-x236.google.com (mail-yb0-x236.google.com [IPv6:2607:f8b0:4002:c09::236]) by rfc-editor.org (Postfix) with ESMTPS id 75DDFB801B0 for <rfc-interest@rfc-editor.org>; Fri, 2 Dec 2016 09:09:43 -0800 (PST)
Received: by mail-yb0-x236.google.com with SMTP id v78so40903951ybe.3 for <rfc-interest@rfc-editor.org>; Fri, 02 Dec 2016 09:09:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google; h=from:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wRId2cVLGNn/O+y4O42OZ0EhZ9FgWflaBLmnnCyHRxw=; b=l140asJr3K0HxSQQE1KdXKVocnaxAFpuDi5HSohn0TlDETP2chH+fdNlJliSzEKwrT dUF71aTaQh1woERzHTan3B5dSAhKlmBzFJCKD6dq32mBai2IfGKBh22fkXxOaN+oML5i VSDXOfh1Z0SHSXCxAG+GpU8ewlRv7vWHjooss=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wRId2cVLGNn/O+y4O42OZ0EhZ9FgWflaBLmnnCyHRxw=; b=JiE3WED+PwsEKO8UETa9N4aryxESYGWihdPmEJUrPsi5DlErqYzc4PM05qnp8lIrgz d2//VhRfYC1PDaw2x49ZZMcCvIv1f2hLgXg+hyVx+OQplpHR84Var37uPiGB4u3yLd8Z rk5YDghbZk1otVsGT9Qre4lvAOahmZUYbRjPvfDHhbgwGclZLqpHE/SjtHWwtNdVCc0P 7nxzu7+NJ6DBt79N3jDOjcd/TJrlieNUifOzFgopJWsyPAdOdp44+5ea3z3HNjYT1J+y ALXA3i5L3dcViKOa7o9hEiOBiGlF8wyWSk3qmjPGSH/gur0QRoilAt2kWVz+FizuVieF 1UIQ==
X-Gm-Message-State: AKaTC03rKjjoCcBFaGhyO6UN0v1jHK/O5heGvMlO2IBxDalCAbqG5HJEE1yX/95uERLyTQ==
X-Received: by 10.37.86.198 with SMTP id k189mr17869974ybb.2.1480698582576; Fri, 02 Dec 2016 09:09:42 -0800 (PST)
Received: from [10.6.20.194] ([128.177.113.102]) by smtp.gmail.com with ESMTPSA id u18sm2167471ywf.28.2016.12.02.09.09.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Dec 2016 09:09:41 -0800 (PST)
From: Joe Hildebrand <hildjj@cursive.net>
X-Google-Original-From: Joe Hildebrand <joe@cursive.net>
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
In-Reply-To: <04f701d24c79$3df584e0$b9e08ea0$@olddog.co.uk>
Date: Fri, 02 Dec 2016 10:09:38 -0700
Message-Id: <297E37B4-ADE7-43C8-8F5F-07E142CA2F9E@cursive.net>
References: <0efdc6b9-5bc5-c14c-7d25-5f0e8e96ba72@rfc-editor.org> <04f701d24c79$3df584e0$b9e08ea0$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.3251)
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>
Cc: rfc-interest@rfc-editor.org, "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

> 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?  The idea is that extracting code from the XML should be much easier than parsing the text for <CODE BEGINS> and <CODE ENDS>.

> 2. It would be lovely if you could address the "Contributors" section (current
> schema means that the section has to be created by hand). An "obvious" solution
> is allow a new 'role' value of 'contributor' in 'author' and pull that out into
> the separate section.

That's an interesting idea for the next rev.  I've added an issue to ensure we come back to it:

https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/2

-- 
Joe Hildebrand

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