- From: Chris Lilley <chris@w3.org>
- Date: Thu, 10 Feb 2011 15:57:58 +0100
- To: Julian Reschke <julian.reschke@gmx.de>
- CC: "Eric J. Bowman" <eric@bisonsystems.net>, Larry Masinter <masinter@adobe.com>, "www-tag@w3.org" <www-tag@w3.org>
On Thursday, February 10, 2011, 1:53:59 PM, Julian wrote: JR> My understanding is that we only need to define a notation if there's a JR> common way to handle those media types. I can see that for +xml and JR> +json, but I am not so sure about +zip... I agree that the benefit of a suffixed notation +toto is that some class of handling can be done for all foo/bar+toto even if you don't recognise bar (or foo). For +xml, that handling is - parsing - well formedness checking - validation - looking for namespaces you recognise - handing a dom to some other process For +json I guess it would be - convert to an internal JavaScript structure - throw exceptions if malformed - pass to some other process For +zip: - display contents of zipfile (as a tree-like filebrowser) - look for particular things inside (manifest.xml) - offer to extract some, rather than all, of the contents -- 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 Thursday, 10 February 2011 14:59:45 UTC