Re: [media-types] updates to RFC6838 in the horizon?

Eric Prud'hommeaux <eric@w3.org> Sun, 21 October 2018 04:43 UTC

Return-Path: <eric@w3.org>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 487D7130E1E for <media-types@ietfa.amsl.com>; Sat, 20 Oct 2018 21:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Mv-3s0V5W1GV for <media-types@ietfa.amsl.com>; Sat, 20 Oct 2018 21:43:28 -0700 (PDT)
Received: from raoul.w3.org (raoul.w3.org [128.30.52.128]) (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 00926130E06 for <media-types@ietf.org>; Sat, 20 Oct 2018 21:43:27 -0700 (PDT)
Received: from [90.114.230.151] (helo=w3.org) by raoul.w3.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <eric@w3.org>) id 1gE5aA-000613-2Q; Sun, 21 Oct 2018 04:43:18 +0000
Date: Sun, 21 Oct 2018 00:43:16 -0400
From: Eric Prud'hommeaux <eric@w3.org>
To: Ned Freed <ned.freed@mrochek.com>
Cc: Paul Libbrecht <paul@hoplahup.net>, media-types@ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>, Chris Lilley <chris@w3.org>
Message-ID: <20181021044314.GA15061@w3.org>
References: <e25a4143-7999-4ed0-9947-776033636f15@getmailbird.com> <01Q88GLSKJC4011H9Q@mauve.mrochek.com> <44F6AEF0-8A25-4981-8620-293FD5907483@hoplahup.net> <D01957F2-D4C6-4899-8417-C90B7546CD54@hoplahup.net> <f63aa5c6-5c45-8c91-3285-3421621e2621@isode.com> <01QYLCD6GWBE00BGSX@mauve.mrochek.com> <D2F76E58-663D-4BCD-8F85-B30224BA4EAE@hoplahup.net> <01QYNOB5YLQS00BGSX@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <01QYNOB5YLQS00BGSX@mauve.mrochek.com>
Organization: World Wide Web Consortium (W3C) - http://www.w3.org/
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/z8UdfkO-3omDfPWrdfzYQryTO1k>
Subject: Re: [media-types] updates to RFC6838 in the horizon?
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Oct 2018 04:43:30 -0000

* Ned Freed <ned.freed@mrochek.com> [2018-10-20 07:41-0700]
> > Thank you Ned,
> 
> > On 19 Oct 2018, at 0:38, Ned Freed wrote:
> 
> > > I don't see a problem with a draft updating the template. Pretty low
> > > cost thing
> > > to do. OTOH, nothing prevents a registration from including
> > > "additional"
> > > additional information, nor is a registration precluded from omitting
> > > any or
> > > all of the additional information fields.
> 
> > That’s pretty clear and it seems like, such an actualisation is
> > probably useful to at least give a hint that clipboard types may be
> > relevant.
> 
> > > So the value of formally adding the fields would be if it gets people
> > > to
> > > list them when they wouldn't otherwise. Given past experience I'm
> > > skeptical
> > > this will happen.
> 
> > Well, on this, I think it does depend a lot on the type.
> > Sometimes it makes no sense (to all or to some) to make consider put
> > this into a clipboard (e.g. because a selection does not make sense) and
> > for these, the authors will simply ignore it. At least, it seems to me
> > that clipboard type names make more sense than Macintosh 4-letter codes.
> 
> It's not a question of what makes sense, it's a question of the information
> people have available and thus what they are able and willing to put in a
> registration.
> 
> Past experience says people are unlikely to go the extra mile to think
> about any of this stuff even if we prompt them for it.

Speaking from experience, it occurs to almost no one to think about a
clipboard type name and then wedge it into an unreceptive form. I
believe that the folks who fill these out are pretty diligent. Clearly
marking optional fields as such and providing links to understand,
e.g. clipboard type names, allows said diligent netizens to leave less
interop to chance, which is why they're filling out the form in the
first place.


> 				Ned
> 
> 
> _______________________________________________
> media-types mailing list
> media-types@ietf.org
> https://www.ietf.org/mailman/listinfo/media-types

-- 
-ericP

office: +1.617.599.3509
mobile: +33.6.80.80.35.59

(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.

There are subtle nuances encoded in font variation and clever layout
which can only be seen by printing this message on high-clay paper.