handle CURIEs properly

[bantic]

Types prefaced with a curie should be handled. Presumably, since CURIEs are for documentation purposes, all that needs to happen here is to strip the curies, so property names with a colon can be split and discard the first part.

I.e., if a property name is "acme:widgets", we transform it to, simply "widgets".

[rwjblue]

Took me a few minutes to figure out what a CURIE is, figured I'd share some info...

Custom link relation types (Extension Relation Types in [RFC5988])
SHOULD be URIs that when dereferenced in a web browser provide
relevant documentation, in the form of an HTML page, about the
meaning and/or behaviour of the target Resource. This will improve
the discoverability of the API.

The CURIE Syntax [W3C.NOTE-curie-20101216] MAY be used for brevity
for these URIs. CURIEs are established within a HAL document via a
set of Link Objects with the relation type "curies" on the root
Resource Object. These links contain a URI Template with the token
'rel', and are named via the "name" property.

• http://www.w3.org/TR/2010/NOTE-curie-20101216/
• https://tools.ietf.org/html/draft-kelly-json-hal-07#section-8.2 (where the quote above comes from)

[bantic]

👍 thanks! There's a rewrite of the hal adapter to support ember data 1.13+ in this branch, perhaps we can fold in proper curie support there.