Adds link to the API-craft google group to the readme
Merge pull request #22 from duksis/add_link_to_api_craft_to_readme

Adds link to the API-craft google group to the readme
WIP - Work started to create yard documentation

This is a WIP commit.
Merge pull request #23 from bjoska/yard_documentation

WIP - Work started to create yard documentation
Use Rack::Accept::MediaType for mime type check

although `Rack::Accept::Charset` works, `Rack::Accept::MediaType` seems to be the "correct way" of testing against mime types.
Allows to not match a mime type
Prepare for 0.4.3 release

Update the README, bump the version, add a post_install message for
breaking changes.
Start a new CHANGELOG stanza for the next version
Merge pull request #24 from fnordfish/patch-1

Use Rack::Accept::MediaType for mime type check
Derive the collection type from the first item in the collection

Deriving a nice rel for the inside of the collection continues to be a
sticking point. Ideally we don't need to inspect the objects being
serialized, instead the collection gets an :item_mapper from the
association, and can take the type from the item_mapper.

If the collection sits at the top level then things are different. In
that case you could be explicit about the item mapper when calling the
top level call to yaks, but otherwise we need to derive the type at
mapping time from the contents, and this only works when the collection
contains at least one object. So not ideal, but has worked so far.

This adds some extra complexity to the policy, but it brings back the
pre 0.4.3 behavior.
Yard fix, format_class returns a subclass of Yaks::Format, not an instance
Prepare version 0.4.4
Fix test after changing the collection rel logic
Add documentation to Format and FP

As we progress a bit further here we are with a couple of more classes and
modules documented.
Add benchmark script, bring back top-level :item_mapper support
Get some profiling information
Merge pull request #26 from bjoska/More_documentation

Add documentation to Format and FP
spike on runner/pipeline
Get the Runner to a working state

Yaks::Runner generalizes the concept of a pipeline of transformations,
so it's easier to provide before/after/around hooks for each steps.

Also contains a fix for passing in an item_mapper to Yaks#call.
Add another benchmark

This is just the first, the idea is to compare flat vs deep structures.