Curie vs Curies - pluralization mismatch about halbuilder-core HOT 5 CLOSED

It looks like at some point the rel was changed from "curie" to "curies" as http://stateless.co/hal_specification.html still mentions the former.

The fact its not an array should not actually matter, as single element/array should be handled automatically by any client processing library - as for any link entry. I do recall this being discussed on the list over weather it should ALWAYS be an array or not, but I don't think there was any conclusion.

I'll update the rel type tho when I get a chance and push a new release out.

from halbuilder-core.

My comment about the array vs not array is supported by this

https://groups.google.com/forum/?fromgroups=#!searchin/hal-discuss/curies$20array/hal-discuss/v-Uwcbspzl0/V6tOtAm8MisJ

but I agree this doesn't really constitute a conclusion. The curie -> curies change happened with rev 4 of the spec, with the diff seen here: http://tools.ietf.org/rfcdiff?url2=draft-kelly-json-hal-04.txt

Thanks for taking a look at this!

from halbuilder-core.

True, however my comments in thread still stand in my reasoning - The
"JSON Way" of doing arbitrary object/array replacement is stupid.

From a consumption point of view, you have NO IDEA if that link is
truely single, or multiple, and in a dynamic language/data type there's
no real way to codify that. Only via assumptions. If currying is a
special case, it should really be _curries and separate from links) IMHO.

This is just one of the odd differences between the XML and JSON specs.

There's also another thread calling for curries to be totally removed
from the spec, which personally - I'm down for.

asheldon wrote:

My comment about the array vs not array is supported by this

https://groups.google.com/forum/?fromgroups=#!searchin/hal-discuss/curies$20array/hal-discuss/v-Uwcbspzl0/V6tOtAm8MisJ

https://groups.google.com/forum/?fromgroups=#!searchin/hal-discuss/curies%2420array/hal-discuss/v-Uwcbspzl0/V6tOtAm8MisJ

but I agree this doesn't really constitute a conclusion. The curie ->
curies change happened with rev 4 of the spec, with the diff seen
here: http://tools.ietf.org/rfcdiff?url2=draft-kelly-json-hal-04.txt

Thanks for taking a look at this!

—
Reply to this email directly or view it on GitHub
#9 (comment).

from halbuilder-core.

FWIW, http://stateless.co/hal_specification.html now uses curies and all the examples show the value as an array.

from halbuilder-core.

Curies is used in the current code actually...closing.

from halbuilder-core.