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

Noah Mendelsohn <nrm@arcanedomain.com> Fri, 13 April 2012 01:10 UTC

Return-Path: <nrm@arcanedomain.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 2B21021F86F5 for <apps-discuss@ietfa.amsl.com>; Thu, 12 Apr 2012 18:10:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id M-HSiT1nylDP for <apps-discuss@ietfa.amsl.com>; Thu, 12 Apr 2012 18:10:11 -0700 (PDT)
Received: from homiemail-a6.g.dreamhost.com (caiajhbdccac.dreamhost.com []) by ietfa.amsl.com (Postfix) with ESMTP id A420B21F86F8 for <apps-discuss@ietf.org>; Thu, 12 Apr 2012 18:10:10 -0700 (PDT)
Received: from homiemail-a6.g.dreamhost.com (localhost []) by homiemail-a6.g.dreamhost.com (Postfix) with ESMTP id 4787F598077; Thu, 12 Apr 2012 18:10:10 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=arcanedomain.com; h=message-id :date:from:mime-version:to:cc:subject:content-type: content-transfer-encoding; q=dns; s=arcanedomain.com; b=EGCkTH/g kWNoxPmIaGUTLDI/QlgBVZdcJeDE1OmTycQRgHFcZLN1vRRjJXKqjeni0visQaSI vHfcRL/ahCvfLDPnTivTCnu+aPjU7SU8KY+PQ3AmOdg+oq/duXrypgjbFGD5sK52 qwaSpD+PNMzo8Zi/8XCPcMD1eCharXFHg10=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=arcanedomain.com; h= message-id:date:from:mime-version:to:cc:subject:content-type: content-transfer-encoding; s=arcanedomain.com; bh=m9AyqOH1i1D+WV c5zFdE7MgAiQ4=; b=NrjO2yBnnfXHCjhxofbfOmWuLA1YGwhXyIFEVsyynqJqP0 Yx9fnCXV3hjjkvXbs6jikFyuGj7M3gdklsDnMu1F0gMKBusiz8xZtFgvKDALVKF2 Xc3hVHLXnDp6NYiBx3Had8fsDY5vq2L0YeWHcoonKYAAaCMRXTkdj/gSKXpjY=
Received: from [] (unknown []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: webmaster@arcanedomain.com) by homiemail-a6.g.dreamhost.com (Postfix) with ESMTPSA id 76A9659807A; Thu, 12 Apr 2012 18:10:09 -0700 (PDT)
Message-ID: <4F877CEE.5030107@arcanedomain.com>
Date: Thu, 12 Apr 2012 21:10:06 -0400
From: Noah Mendelsohn <nrm@arcanedomain.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: ned+ietf@mrochek.com, john+ietf@jck.com, tony+mtsuffix@maillennium.att.com
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 13 Apr 2012 08:06:43 -0700
Cc: "www-tag@w3.org" <www-tag@w3.org>, apps-discuss@ietf.org
Subject: [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: Fri, 13 Apr 2012 01:10:12 -0000

The W3C Technical Architecture Group have been concerned about conflicting 
sources of definitions of fragment identifier semantics located by 
following RFC 3986 and the media type definition. We believe that those 
defining and registering media types (including ones that follow generic 
rules such as 3023bis) need more explicit advice than currently contained 
within draft-ietf-appsawg-media-type-regs.

In particular, we are working on defining best practice for use and 
definition of fragment identifier semantics, and the document 
http://www.w3.org/2001/tag/doc/mimeTypesAndFragids-2011-08-12 is under 
development (although it has not been formally reviewed or approved by the 

We believe media type registration authors should be pointed to these 
recommendations by reference from draft-ietf-appsawg-media-type-regs.

We would like to coordinate the development of these documents effectively 
and would appreciate your feedback on how best to accomplish this.

Noah Mendelsohn
For the W3C Technical Architecture Group