title: django-rest-framework: api versioning
body: <p>so googling around it appears that the general consensus is that embedding version numbers in REST URIs is a bad practice and a bad idea.</p>
  
  <p>even on SO there are strong proponents supporting this.<br>
  e.g. <a href="https://stackoverflow.com/questions/389169/best-practices-for-api-versioning">Best practices for API versioning?</a></p>
  
  <p>My question is about how to accomplish the proposed solution of using the accept header / content negotiation in the django-rest-framework to accomplish this.</p>
  
  <p>It looks like content negotiation in the framework,<br>
  <a href="http://django-rest-framework.org/api-guide/content-negotiation/" rel="noreferrer">http://django-rest-framework.org/api-guide/content-negotiation/</a> 
  is already configured to automatically return intended values based on accepted MIME types. If I start using the Accept header for custom types, I'll lose this benefit of the framework. </p>
  
  <p>Is there a better way to accomplish this in the framework?</p>