Friday, June 17, 2005, 6:14:38 PM, you wrote:
> Uh, has Mark spotted a dumb bug here that we should fix? Do we care > if *remote* content is of a composite MIME type? My feeling was that > we ruled out composite types in *local* content, for fairly obvious > reasons. The fix is obvious, in 4.1.3.1 > "Failing that, it MUST be a MIME media type. If the "src" attribute > is not provided, i.e. the content is local, the value of the "type" > attribute MUST NOT be a composite type... " > -Tim Can somebody give me a link to where we discussed the requirement that atom:content MUST NOT contain a composite type? I've tried searching my archive but I couldn't find anything at all. The change was introduced in draft-08. I can't agree that this is a mere spec bug until I can find where it was discussed, and what the intent for this ban was. I don't really see why we are banning these MIME types from either local or remote content. -- Dave
