Why not use a MIME type and content negotiation to request a description?
Content negotiation is designed to allow agents to select from among a set of alternate encodings. The distinction between a resource description and (other kind of) resource representations is not based on any distinction in encoding. In fact, a given description (which is itself a resource) may have several available encodings (RDF/XML, XTM, N3, etc.). Thus, if you use content negotiation to indicate that you want a description, you can’t use it to indicate the preferred encoding of the description (if/when other encodings than RDF/XML are available).
Related Questions
- I am a seller of equipment and machinery that qualifies for an exemption. When customers request the exemption, what description should they use for "Type of Tangible Personal Property Purchased?
- Can Troi URL Plug-in set the content type and other headers in the HTTP request?
- Why not use a MIME type and content negotiation to request a description?
