Since one of the primary purposes of Content-Type: is to instruct a receiving program (email client, Web browser, or what have you) on the proper application to deploy in order to interpret the MIME entity, it seems to me that it would be useful to standardize a "type" parameter with application/xml and text/xml. Legal values would be "document", "entity" (including both external parsed entities and external parameter entities), and "dtd". Typically, "documents" would be passed to an XML browser, whereas "entity"s and "dtd"s would be simply stored; alternatively, "dtd"s could be passed to a DTD viewer. Passing "entity" or "dtd" MIME entities to an XML browser would or could produce an unwanted parsing error from the browser. -- John Cowan http://www.ccil.org/~cowan cowan@c... You tollerday donsk? N. You tolkatiff scowegian? Nn. You spigotty anglease? Nnn. You phonio saxo? Nnnn. Clear all so! 'Tis a Jute.... (Finnegans Wake 16.5) xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format