hal_specification
hal_specification copied to clipboard
mikekelly
HAL Specification
It would be nice if embedded resources could point to a location inside the current representation where the data lie. Example: instead of: ```json { "results": 2, "_embedded": { "foo:objects":...
On https://stateless.group/hal_specification.html, in the RFC section, http://tools.ietf.org/html/draft-kelly-json-hal is a broken link. Perhaps the link should be https://tools.ietf.org/html/draft-kelly-json-hal-07 but I don’t know if that’s the current draft.
By follow the link I found that FoxyCart is "partially REST", so it is not HAL. It also never mentioned that it is.
The linked documentation for ParkWhiz calls it REST and not HAL API. Also there is nothing like HAL in it.
The lib for https://katharsis.io/ doesn't point to any library associated with HAL appears to be someone's blog. Looks to be in Hebrew.
Hey there, I currently work on implementing the HAL specification along side with an API I build for a customer. Digging through the documentation and specification I found the description...
Say an api exposes blog posts and with each blog post, one would want to include a link to post comments, should that links be in `_links` ? or should...
the spec should maybe have stronger wording about what a link relation's identifier really is. when a HAL document uses CURIEs, does that mean that all link relations (in embedded...
the CURIE spec https://www.w3.org/TR/curie/ says that CURIEs work by concatenating the prefix value and the value from the CURIE. the example from the draft `http://docs.acme.com/relations/{rel}` (using a URI template-ish syntax)...