Re: [calsify] Proposed Errata №5449 for RFC 7986: COLOR property with arbitrary RGB values

Дилян Палаузов <dilyan.palauzov@aegee.org> Sat, 19 January 2019 13:28 UTC

Return-Path: <dilyan.palauzov@aegee.org>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1C61130DC8 for <calsify@ietfa.amsl.com>; Sat, 19 Jan 2019 05:28:29 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=aegee.org
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 5nudjaafmr0S for <calsify@ietfa.amsl.com>; Sat, 19 Jan 2019 05:28:26 -0800 (PST)
Received: from mail.aegee.org (mail.aegee.org [144.76.142.78]) (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 76F6A12F1A5 for <calsify@ietf.org>; Sat, 19 Jan 2019 05:28:26 -0800 (PST)
Authentication-Results: mail.aegee.org/x0JDSMeq020079; auth=pass (PLAIN) smtp.auth=didopalauzov
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1547904502; i=dkim+MSA-tls@aegee.org; r=y; bh=VUH/Q6b7hIXoM+/16acaETHMiRtKTS/ZwgJ73f48Guk=; h=Subject:From:To:Date:In-Reply-To:References; b=MqOZeui0Ig+kEMcn3nS0HfYhXwqwhdT/7cDMqBUDdPEubtc8xN/0BReJI9Hr0UsN1 +Sl21Yaovfl/8m47pPn22gIrgkKkaYdsVP69mW4vT6sGtOCHYxkmNHjfVOTEif2jzK X8wrDYMu7lvMlwQxtqge6TAEH+/hC76MK7lfrP1ecQ0Qn4b6Vh3lvrhQ+Vyup0uXIo njH0Dd+MuS5joK2VFT8oDWPeNoVLSTEdmB/3Ztf6d18Elr2ZLmube3LZzBXgr7/zO0 7tduiE1G3bXlGekuINDzvDESos0cMg5mXDPa1M6oIBC9JC2f731ZNXWRudNXOPv5df BVR3OjQspmOBZOqyQDHgjCam7CdtGjx1A7vhIbTCForElqgsyrFpoBx27DQbIzr+ri yfPu5jp4/WUmj+4WA8qPlt8f9igE65epu5orI+yu7V6Rrlq8uYe0FW5lxaAUutiqTJ WzA66t0RGHwJCX8N2qmzzgCq0pl0FLs/bCv6+Dios14xJ1YIHYqFrCklJB/E09zQfq aWGdiz7+hzPlTJcqmol9cg1K9JrHy/rpLUhKOaAI6FBXl4TUQC4k9ulv6F7iveYJZo 6f9S5uKwTen3pXn+pdwJBLS7J2jkEQGY8Hnq5PxdChq8xz5fnTwHm5QvPqtVmTpb00 FgeHyW36nkwFH1jcuh0nZKpA=
Authentication-Results: mail.aegee.org/x0JDSMeq020079; dkim=none
Received: from Tylan (adsl-62-167-97-198.adslplus.ch [62.167.97.198]) (authenticated bits=0) by mail.aegee.org (8.15.2/8.15.2) with ESMTPSA id x0JDSMeq020079 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <calsify@ietf.org>; Sat, 19 Jan 2019 13:28:22 GMT
Message-ID: <ba934d0f3521a8322c97641ad1da0dfc40c60667.camel@aegee.org>
From: Дилян Палаузов <dilyan.palauzov@aegee.org>
To: calsify@ietf.org
Date: Sat, 19 Jan 2019 13:28:22 +0000
In-Reply-To: <b1fd8efff5952f94c53fafd29181ee02fddaa38f.camel@aegee.org>
References: <895f00bcf8af786b08011f8d3ee6f3cfd7f2f9f7.camel@aegee.org> <b1fd8efff5952f94c53fafd29181ee02fddaa38f.camel@aegee.org>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.31.90
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.101.1 at mail.aegee.org
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/P1-rVkeWLduiBDwZ62jPBjmLGvw>
Subject: Re: [calsify] Proposed Errata №5449 for RFC 7986: COLOR property with arbitrary RGB values
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jan 2019 13:28:30 -0000

Hello,

do I get weird by sending reminders for erratum 5449?

Regards
  Дилян

On Wed, 2018-10-10 at 09:16 +0000, Дилян Палаузов wrote:
> Hello,
> 
> what shall happen, so that https://www.rfc-editor.org/errata/eid5449
> makes progress?
> 
> Regards
>   Дилян
> 
> On Thu, 2018-06-28 at 22:04 +0000, Дилян Палаузов wrote:
> > Hello,
> > 
> > I would like to suggest the following Errata and welcome any comments
> > within a month.
> > 
> > My reading is that COLOR now cannot have the value RGB(61,211,68)
> > 
> > Please correct me, if I am wrong.
> > 
> > RFC 7986 (new Properties for iCalendar)  Section 5.9. COLOR Property
> > says:
> > https://tools.ietf.org/html/rfc7986#section-5.9
> > 
> > Type: Technical
> > Section: 5.9 COLOR Property
> > 
> > Origianl text:
> > 
> > Description:   ...The value is a case-insensitive color name taken from
> > the CSS3 set of names, defined in Section 4.3 of [W3C.REC-css3-color-
> > 20110607].
> > 
> > Example:  The following is an example of this property:
> >    COLOR:turquoise
> > 
> > Corrected text:
> > 
> > Description:   ...The value is either a case-insensitive color name
> > taken from the CSS3 set of names, defined in Section 4.3 of [W3C.REC-
> > css3-color-20110607], or an RGB() functional  notation with absolute
> > values specified in Section 4.2.1 of the same document
> > 
> > Examples:  The following are examples of this property:
> >    COLOR:turquoise
> >    COLOR:rgb(61\,211\,68)
> > 
> > Notes for the errata:
> > 
> > draft-daboo-icalendar-extensions-07 removed the possibily to have RGB
> > colours for COLOR.
> > 
> > CSS3 included color names, that browsers at that time suppored,
> > originating from X11's rgb.txt.  The color names and values were
> > randomly chosen.  The minimal distance between the colors isn't
> > consistent.  One motivation for creating a color name were hardware
> > capabilities - an argument which isn't valid for 20 years now.  There
> > is no reason to limit the number of possible values for COLOR.  A user
> > interface for choosing a named color has either to offer the user the
> > possibility to choose from a pre-filled list of colors, which could
> > clutter the interface, or let the user choose any RGB color and narrow
> > it later to the closest color with CSS3 name.  This narrowing isn't
> > trivial and performing it seems like having an RFC running in itself.
> > 
> > Notes for this message, outside the errata:
> > 
> > Gnome Evolution recently added support for the COLOR property and
> > uploaded iCalendar files by it now have:
> > COLOR:rgb(61\,211\,68)
> > 
> > https://www.w3.org/TR/2011/REC-css3-color-20110607/ lets also other
> > forms:
> > #f00
> > #ff0000
> > rgb(100%, 0%, 0%)
> > 
> > I have no propbem to let or exclude any of the forms above.  The main
> > challenge is neither to have the user chose from a final list of
> > colours, nor to let her choose any colour but narrow the selected
> > colour afterwards to something.  Letting more than one form of the
> > mentioned above would be overengineering for the mentined challanage.
> > 
> > https://github.com/w3c/csswg-drafts/issues/2813 states the colours are
> > chosen randomly, and http://christopher.org/history-web-color-names/
> > proves this thesis.
> > 
> > Randomly choosen colour values (having names coming from rgb.txt) are
> > not suitable to achieve any aim.
> > 
> > I haven't worked with colour terms until today, so feel free to
> > rephrase the rgb-functional sentence.
> > 
> > Regards
> >   Дилян
> > 
> > _______________________________________________
> > calsify mailing list
> > calsify@ietf.org
> > https://www.ietf.org/mailman/listinfo/calsify
> 
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify