Re: [apps-discuss] W3C TAG Comment on Draft Media Type Specifications and Registration Procedures

Peter Saint-Andre <stpeter@stpeter.im> Mon, 16 April 2012 16:53 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 560C021F86E4 for <apps-discuss@ietfa.amsl.com>; Mon, 16 Apr 2012 09:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.651
X-Spam-Level:
X-Spam-Status: No, score=-102.651 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 DPJhFyrUJpRc for <apps-discuss@ietfa.amsl.com>; Mon, 16 Apr 2012 09:53:45 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id A359521F86DA for <apps-discuss@ietf.org>; Mon, 16 Apr 2012 09:53:44 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A8CB340058; Mon, 16 Apr 2012 11:07:51 -0600 (MDT)
Message-ID: <4F8C4E97.1000709@stpeter.im>
Date: Mon, 16 Apr 2012 10:53:43 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: "Murray S. Kucherawy" <msk@cloudmark.com>
References: <4F877CEE.5030107@arcanedomain.com> <01OE8S1I9Z2K00ZUIL@mauve.mrochek.com> <9452079D1A51524AA5749AD23E0039280EF063@exch-mbx901.corp.cloudmark.com> <CA8E55D5-822A-47DC-B5CB-583CC328227B@jenitennison.com> <4F87EBD4.90501@gmx.de> <CFA00AEC-F80B-4517-8101-A5DDA57555ED@jenitennison.com> <01OEABGEZ8RU00ZUIL@mauve.mrochek.com> <4F8C43AC.10005@stpeter.im> <9452079D1A51524AA5749AD23E0039280F37B9@exch-mbx901.corp.cloudmark.com>
In-Reply-To: <9452079D1A51524AA5749AD23E0039280F37B9@exch-mbx901.corp.cloudmark.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] W3C TAG Comment on Draft Media Type Specifications and Registration Procedures
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 16:53:46 -0000

On 4/16/12 10:49 AM, Murray S. Kucherawy wrote:
>> -----Original Message----- From: apps-discuss-bounces@ietf.org
>> [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Peter
>> Saint-Andre Sent: Monday, April 16, 2012 9:07 AM To: Ned Freed Cc:
>> Jeni Tennison; apps-discuss@ietf.org; 
>> tony+mtsuffix@maillennium.att.com; Julian Reschke; Noah
>> Mendelsohn; john+ietf@jck.com; www-tag@w3.org List Subject: Re:
>> [apps-discuss] W3C TAG Comment on Draft Media Type Specifications
>> and Registration Procedures
>> 
>>> If you want to put this stuff in an RFC, it needs to one that's
>>> on the regular standards track. And that means it needs to be in
>>> a different document. All you can put in this document are the
>>> registration rules for specifying a fragment identifier. Nothing
>>> more.
>> 
>> Ned is right: this document defines best practices for
>> *registering* media types. We all might want to more clearly
>> specify the syntax and semantics of fragment identifiers, but IMHO
>> that's out of scope for the registration procedures per se.
> 
> I think I agree.  Would it be an appropriate path forward to put that
> into another document, and then reference that one from this one as
> an Informative?

I don't think so. All we're trying to do here is make is easier for
folks to register media types. The thorny issues of the syntax and
semantics of media types and pointers thereto (which is what fragment
identifiers are at some level) are IMHO orthogonal to how you register
media types. Plus, the document we point to from the registration BCP
will likely change so significantly by the time it's done that the
citation will be mostly meaningless at this time.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/