title: In django-tastypie, can choices be displayed in schema?
body: <p><strong>I am trying to figure out whether I can represent model field <code>choices</code> to clients consuming a tastypie API.</strong> </p>
  
  <p>I have a django (1.4.1) application for which I am implementing a django-tastypie (0.9.11) API.  I have a Model and ModelResource similar to the following:</p>
  
  <pre><code>class SomeModel(models.Model):
      QUEUED, IN_PROCESS, COMPLETE = range(3)
  
      STATUS_CHOICES = (
          (QUEUED, 'Queued'),
          (IN_PROCESS, 'In Process'),
          (COMPLETE, 'Complete'),
      )
  
      name = models.CharFIeld(max_length=50)
      status = models.IntegerField(choices=STATUS_CHOICES, default=QUEUED)
  
  class SomeModelResource(ModelResource):
      class Meta:
          queryset = SomeModel.objects.all()
          resource_name = 'some_model'
  </code></pre>
  
  <p>When I look at objects in the API, the name and status fields are displayed as follows:</p>
  
  <pre><code>{
      ...
      "objects":[
      {
          "name": "Some name 1",
          "status": 0
      },
      {
          "name": "Some name 2",
          "status": 2
      }]
  }
  </code></pre>
  
  <p>I know I can alter <code>SomeModelResource</code> with hydrate/dehydrate methods to display the string values for status as follows, which would have more value to clients:</p>
  
  <pre><code>{
      ...
      "objects":[
      {
          "name": "Some name 1",
          "status": "Queued"
      },
      {
          "name": "Some name 2",
          "status": "Complete"
      }]
  }
  </code></pre>
  
  <p>But how would the client know the available choices for the status field without knowing the inner workings of SomeModel?</p>
  
  <p>Clients <em>creating</em> objects in the system may not provide a status as the default value of <code>QUEUED</code> is desirable.  But clients that are <em>editing</em> objects need to know the available options for status to provide a valid option.</p>
  
  <p>I would like for the choices to be listed in the schema description for SomeModelResource, so the client can introspect the available choices when creating/editing objects.  But I am just not sure whether this is something available out of the box in tastypie, or if I should fork tastypie to introduce the capability.</p>
  
  <p>Thanks for any feedback!</p>