- From: Larry Masinter <masinter@adobe.com>
- Date: Wed, 9 Feb 2011 08:35:32 -0800
- To: Chris Lilley <chris@w3.org>, "Eric J. Bowman" <eric@bisonsystems.net>
- CC: "www-tag@w3.org" <www-tag@w3.org>
So I suppose it's a matter of finding someone to do the work of writing up +json and +zip? Larry -- http://larry.masinter.net -----Original Message----- From: Chris Lilley [mailto:chris@w3.org] Sent: Tuesday, February 08, 2011 4:04 AM To: Eric J. Bowman Cc: Larry Masinter; www-tag@w3.org Subject: Re: Feedback on Internet Media Types and the Web On Tuesday, February 8, 2011, 6:00:14 AM, Eric wrote: EJB> Larry Masinter wrote: >> +xml got defined, for better or worse, without prior" groundwork". EJB> As an experiment. The experiment was a success. The standard needs to EJB> be updated to account for this success, so that the registry stays EJB> current with modern expectations based on that success. There was no EJB> need to define +suffix before +xml came along, i.e. no need for prior EJB> groundwork. Now that +xml *has* defined +suffix, it's time to adopt EJB> that definition in general, to lay the groundwork for insisting that EJB> they be defined uniformly (as opposed to +suffix meaning whatever any EJB> given media type says it means, in which case what's the point of the EJB> syntax even existing). In addition to +json I have seen requests for types that included +zip (EPUB for instance). I agree with Eric that a bit more needs to be said about suffixes in general and with Larry that something specific needs to be said about +json in particular (and +zip also, in a different document). -- Chris Lilley Technical Director, Interaction Domain W3C Graphics Activity Lead, Fonts Activity Lead Co-Chair, W3C Hypertext CG Member, CSS, WebFonts, SVG Working Groups
Received on Wednesday, 9 February 2011 16:36:05 UTC