Re: [ietf-types] Update to text/html registration

Paul Libbrecht <paul@hoplahup.net> Thu, 09 August 2012 14:45 UTC

Return-Path: <paul@hoplahup.net>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6B6021F865E for <ietf-types@ietfa.amsl.com>; Thu, 9 Aug 2012 07:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.63
X-Spam-Level:
X-Spam-Status: No, score=-3.63 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_DE=0.35, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XCU-ngIJgSBT for <ietf-types@ietfa.amsl.com>; Thu, 9 Aug 2012 07:45:49 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by ietfa.amsl.com (Postfix) with ESMTP id CE75221F8652 for <ietf-types@ietf.org>; Thu, 9 Aug 2012 07:45:48 -0700 (PDT)
Received: from [192.168.1.185] (ip-109-84-0-72.web.vodafone.de [109.84.0.72]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0MKbX5-1SzkqD45bT-001cKs; Thu, 09 Aug 2012 16:45:39 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Paul Libbrecht <paul@hoplahup.net>
In-Reply-To: <01OIRYFYVNZK0006TF@mauve.mrochek.com>
Date: Thu, 09 Aug 2012 16:44:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <416304E6-3651-4237-9526-D1AC8FEDDEF4@hoplahup.net>
References: <20120807111647.GB67292@sideshowbarker> <D0209276-1489-4A26-BFD8-4EB52957FBE3@hoplahup.net> <20120807171420.GG68105@sideshowbarker> <01OIRYFYVNZK0006TF@mauve.mrochek.com>
To: Ned Freed <ned.freed@mrochek.com>
X-Mailer: Apple Mail (2.1084)
X-Provags-ID: V02:K0:4i81qLUgbzpolOfq0gVZfaCGM2Ej17UugHUo/cwkKIe hsr45J9tY7IsKotjp+WFcMfwDbjALG4JBdVmT+SV0Fy/38GRFk pZ2XjvGkhrxQbHepqqYM+z52TJ91sMz0s4A/wvVVMAmkz4+uSC UsLybOOg3dP49/iVUrspLOR0qrbFPBKYPlWPtPeovLDlgsvBEt G5IhJ/8f8eyVsDMbp7hwTpKmAO87edPQ2zcs1yX89wNiD5px3A jguSaI8kzo+IdH3ooOqP6ICxs8/pkqduiLEiE3ZuzE4N6bAL6/ wWY2os2s6+z+UjLqInCqZ2EgPltuPvijbHUsyJwCqDErDuatfG nvZ2xPuPYLYgKIsA4JkfunTywCqSSKzaBGFOXPPJWksG8O/VKL uwo80Ric+1xLQ==
Cc: ietf-types@ietf.org
Subject: Re: [ietf-types] Update to text/html registration
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 14:45:49 -0000

Michael, Ned,

>> Are those important just for HTML and XHTML, or are there other formats
>> which would benefit from having those defined as part of their
>> registrations?
> 
> They probably are.

Thus far, I have been monitoring the list and suggested this when it appeared to make sense. Sometimes, media-types seem to be too specific to be entering a clipboard.

HTML and its cousins are clearly good candidates to live in the clipboard!

>> If those would be useful or other formats, I'd suggest the guidelines for
>> media-type registrations be updated to suggest including them for all
>> registrations.
> 
> I'm afraid it is a little late for that. The media types registration
> were just updated. Had this been proposed during the updating process (which
> took over a years), I can pretty much guarantee it would have been included,
> but the document is now final and it's too late.

Ned, is there another list I should monitor to see discussion of another round of update of this recommendation?
(as indicated elsewhere, I'd also suggest that the Macintosh 4-letter type be dropped)

> My suggestion would be to put these in the additional information section.

Thanks, I have formulated this on the bug I just opened:
	https://www.w3.org/Bugs/Public/show_bug.cgi?id=18508

Paul