handle polymorfism in property ranges during deserialization about jb4jsonld HOT 7 CLOSED

Hi,
this behavior is intentional. JB4JSON-LD will try to find the most specific matching type and if there are multiple (D' and D'' in your case), the library cannot decide which one to use. Using the parent (D) is theoretically possible, but what if it is abstract, or an interface? In addition, if D is a concrete class, the JSON can contain attributes mapped by D' or D'' which in this case wouldn't match in D.
I suppose a configuration parameter could be used to override the default behavior in favor of using the parent, with the risk of loosing some attributes. In that case, a PR would be welcome.

from jb4jsonld.

I think the planned support for custom (de)serializers would help in this case as well. See #28

from jb4jsonld.

Honestlt It is quite common in the semantic web realm that a class has some subclasses not necessarily disjoint. So we have to think about a solution in which no exception is thrown in this case.

from jb4jsonld.

Fair enough. @psiotwo , what do you think?

from jb4jsonld.

but what if it is abstract, or an interface?

Good point. We can try to go higher in the hierarchy.

with the risk of loosing some attributes.

If D has unmapped properties, the additional D',D'' props should appear there.

I think it makes sense to support this parent resolution and a configuration parameter for using parents optimistically should be appropriate.

from jb4jsonld.

In this case one expect an object of class D, so returning an individual of any of its subclasses D' or D'' is good enough.

from jb4jsonld.

Implemented in 0.8.2. Configured via the enableOptimisticTargetTypeResolution and preferSuperclass parameters. Feel free to check it out and reopen (or report a new issue) if there are any problems.

from jb4jsonld.