Time
Using UNIX time may be easier for a developer, and I do concede that point, but by using UNIX time you're doing a few things:
1) You're exposing some internal logic or data structure of the system in the resource
2) You're removing information on time zone
3) In some circumstances where greater precision is needed you're precluding the use of nanoseconds
I know that some languages don't naturally handle ISO8601 dates with nanoseconds, but I do think that's the best format.
YYYY-MM-DDTHH24:MI:SS.NNNNNNNNNZ
With that format one can keep a deeper knowledge of timezone, of precision, of human readability (and JSON.org does say that JSON is easy for humans to read).
Content Types
Whilst it may be pragmatic to not plumb the depths of custom content types they should at least be mentioned and made compulsory even if they aren't typed to a detailed level of specificity. Content Type: application/json is fine, so long as it's used and paid attention to.
Capabilities
HATEOAS and meta-data... I like to encourage developers to explore what's possible in the API by showing them the actions that they can do on an item, and their permissions. As in... if they can update something, show them how by telling them the URL. The API should ideally not lead a developer to an action that they couldn't perform.
Minor Points
I generally prefer to restrict the possible HTTP status codes and publishing that list so that a developer implementing against the API can build a generic wrapper, know what to expect and take care of handling it. Which means, sometimes I will generalise a response rather than using a status code in one place and one place only.
I'm not so sure on using verbs for special actions like search, 'q' is a well understood part of the 'query string', and I'd make that just an optional parameter on the pluralised collection URL. But... perhaps that's just a bad example.