W3C home > Mailing lists > Public > www-tag@w3.org > April 2012

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

From: Jeni Tennison <jeni@jenitennison.com>
Date: Mon, 16 Apr 2012 09:33:46 +0100
Cc: Julian Reschke <julian.reschke@gmx.de>, Noah Mendelsohn <nrm@arcanedomain.com>, "www-tag@w3.org List" <www-tag@w3.org>, apps-discuss@ietf.org
Message-Id: <098D7D86-2FF3-4287-800F-5FAB6C0212F2@jenitennison.com>
To: Ned Freed <ned.freed@mrochek.com>, "Murray S. Kucherawy" <msk@cloudmark.com>, john+ietf@jck.com, tony+mtsuffix@maillennium.att.com
Hi Ned, all,

Here is a set of concrete suggestions for amendments to draft-ietf-appsawg-media-type-reg that I hope might focus discussion. Basically they 

  * create a specific section in the media type registration template for information about fragment identifier processing and provide some high-level guidance about what should go there
  * create a section within the structured syntax suffix registration template for discussions of generic processing of fragment identifiers across media types that use that structured syntax

I think there'd then be scope for a separate document that on all the details about prioritising between overlapping fragment identifier schemes and so on, but no need for that to be referenced from draft-ietf-appsawg-media-type-reg.

Thanks for your consideration,



1. Add a new section 'Fragment Identifier Recommendations' (before the current 4.11 Additional Information) which says:

 Media type registrations SHOULD specify how applications should interpret
 fragment identifiers [RFC3986] within the media type.

 Media types SHOULD adopt fragment identifier schemes that are used with
 other similar media types, to facilitate content negotiation across them.
 In particular, media types that use a named structured syntax with a 
 registered "+suffix" SHOULD adopt any and all fragment identifier schemes 
 defined within the structured syntax suffix registration.

2. Remove the last bullet point from the list in 4.11 Additional Information, namely:

 o Information about how fragment/anchor identifiers [RFC3986] are
   constructed for use in conjunction with this media type.

3. In 5.7 Registration Template:

 a. Add a section 'Fragment identifier considerations'
 b. Remove the entry 'URI fragment/anchor identifier(s):' under Additional information

4. Within 6.2 Structured Syntax Suffix Registration Template add a new section:

 Fragment identifier considerations
   Generic processing of fragment identifiers for any type employing this
   syntax should be described here.

Jeni Tennison
Received on Monday, 16 April 2012 08:34:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:44 UTC