Re the type parameter (sec. 12): I earlier suggested to define file extensions for feed and entry documents, and that suggestion got some +1s and no objections.
Let me reiterate points: 1. If the "different processing models" models require we be able to distinguish feeds from entries by mime types, then i we'll want to be able to distinguish them using file extensions. RFC 4288 has a place for you to fill it in. 2. When you do that exercise you'll see that no existing software will be able to map the mime type to the correct file extension. Existing software can choose a file extension based on the major type/subtype pair -- it will not parse out parameters looking for one named "type". The transformation is not reversible -- we can go from file extensions to mime types but not the other way. 3. There will be no such problem if you simply choose a new subtype to describe entry documents. Hugh -- Hugh Winkler Wellstorm Development http://www.wellstorm.com/ +1 512 694 4795 mobile (preferred) +1 512 264 3998 office
