Saturday, June 18, 2005, 4:40:54 PM, Robert Sayre wrote:
> Incorrect. Multipart content presents an accessibility issue because > the entry metadata is no longer sufficiently granular. There would > have to be Atom metadata for each part.[0] A message/rfc822 email or an MHTML document with embedded images isn't any more or less granular than an HTML document with linked images or an application/zip file. The granularity problem came from Atom 0.3 allowing multiple payloads, this is different from allowing a single composite payload. The earlier discussion was about the rejection of Atom-0.3's multiple content elements, and the quirky multipart/alternative thing for nesting content elements. The conclusion was to reject multiple atom:content elements, and to require text or html in text fields such as title and summary, leaving atom:content unrestricted. Placing a restriction on the MIME types that can be contained as the payload of atom:content is contrary to the earlier conclusion. -- Dave
