this should be:

```ruby
describe '.new' do
```
vs. using context.

Bigger issue here is that instead of having explicit rspec examples (describe) that can have related expectations (it ...), it is all muddled together. And given some of other comments I made about testing nil value cases this has some issues. Further, per rspec best practices examples should be worked it '{action verb} ....' etc. vs. using should.

For example, 

```ruby
# . indicates class method example
describe '.new' do
  it 'returns a Crichton::Representor instance' do
    subject.should be_an_instance_of(Crichton::Representor)
  end
  # not saying we need this spec, but the point is how to manage multiple expectations.
  it 'raises an error with a nil argument' do
     expect { Crichton::Representor.new(nil) }.to_raise(ArgumentError) 
  end
end

# # indicates instance method example
describe '#attributes' do
  it 'returns a hash of attributes associated with the represented resource' do
     subject.attributes.should == #...
  end

  it 'returns an empty hash when no semantics are specified' do
    representor = Representor.new
    representor.attributes.should be_empty
  end
end
```
etc. So, this applies in general to getting other examples and expectations conforming to rspec best practices.