Type Coercion is confusing

[lanthaler]

I would like to discuss the type coercion feature which I find a bit confusing.

The reason is that it works the other way round as it is normally expected by developers/programmers. An exemplary type coercion definition looks as follows:

"@coerce":
{
  "xsd:integer": "age",
  "@iri": "homepage"
}

Which says that age is an integer and homepage is an IRI. I expect that an average developer would try to specify it exactly the other way round:

"@coerce":
{
  "age": "xsd:integer",
  "homepage": "@iri"
}

What was the rationale of doing it the other way round? Isn't it even in the processing algorithms more handy if it is stored in the second form?

[msporny]

This was discussed on the mailing list:

http://lists.w3.org/Archives/Public/public-linked-json/2011Oct/0004.html

[lanthaler]

It has been decided to change to spec as suggested above (http://json-ld.org/minutes/2011-10-18/). The spec hasn't been updated yet.

[msporny]

http://json-ld.org/spec/ED/json-ld-syntax/20120122/#type-coercion

http://json-ld.org/spec/ED/json-ld-syntax/20120122/#typed-values